@deckingman said in Extruder Stepper suddenly only vibrates:

If I understand correctly, it was all working fine and then suddenly stopped working yes? Did you make any changes between when it worked and when it stopped working, including changes to firmware? If the answer is no, then the cause is unlikely to be firmware unless the file(s) have got corrupted somehow (unlikely). You get the same behaviour using different driver chips, different motors, and different cables yes?

If the answer to all the above are yes, then the only common denominator is the hot end itself. i.e. you have a blockage and the extruder can't push the filament against this blockage so it "vibrates". The other alternative might be something mechanically wrong with the nimble causing it to bind, stick or otherwise not rotate, but I have no experience of these so can't comment further.

I did not make any changes to config or Firmware.
I did check the extruder for blockage and everything worked fine, until I applied power.
This applied to any stepper I connected, even without any load on it.

I just created a new config and everything works now, seems the config got somehow corrupted in between or the SD had a bad sector.

Usually this is a bad crimp connection or switched wires in the stepper cabling.
Have you tried a different (known good) cable?
Have you tested the cable, that it is wired correctly?

Have you tried to input the information in a M307 command in config.g?
I’ve had the same issue with one of my printers heaters until I composed the M307 from the autotune result, as it was not reading the values from config-override.g

You could slave one of the other (extruder) drivers to the z, if you don’t use dual extrusion, that should work as well.

@deckingman said in Extruder Stepper suddenly only vibrates:

If I understand correctly, it was all working fine and then suddenly stopped working yes? Did you make any changes between when it worked and when it stopped working, including changes to firmware? If the answer is no, then the cause is unlikely to be firmware unless the file(s) have got corrupted somehow (unlikely). You get the same behaviour using different driver chips, different motors, and different cables yes?

If the answer to all the above are yes, then the only common denominator is the hot end itself. i.e. you have a blockage and the extruder can't push the filament against this blockage so it "vibrates". The other alternative might be something mechanically wrong with the nimble causing it to bind, stick or otherwise not rotate, but I have no experience of these so can't comment further.

I did not make any changes to config or Firmware.
I did check the extruder for blockage and everything worked fine, until I applied power.
This applied to any stepper I connected, even without any load on it.

I just created a new config and everything works now, seems the config got somehow corrupted in between or the SD had a bad sector.

Enjoy!
You’ve more than earned it

@sigxcpu said in Extruder Stepper suddenly only vibrates:

Maybe that is not the problem but:

M92 X80 Y80 Z640 E2740:2740
M203 X24000 Y24000 Z180 E5000:5000

2740 steps/mm * 5000 mm/min = 13700000 steps/min = 228333 steps/second for the extruder.

Are you sure that's what you want?

That is max feedrate, I am testing at 5 and 10mm, so I will not even reach that limit.

@dc42 said in Extruder Stepper suddenly only vibrates:

The usual causes of stepper motors just vibrating are:

• Bad crimp connection in the stepper motor cable (most common)

I tested with 4 different known good cables, so it seems kind of improbable

• Stepper motor wired not paired in the correct phases (but it used to work, so not this reason)

Tested each of them with the motor before plugging in an they are wired correctly

• Failed driver on the Duet (but you have already changed it, so not this reason)

• Failed motor (least common)

Tested with 3 Steppers by now, unlikely.

OK, tested something different as well:
I did plug in the CoreXY config SD into another printer and it doesn't work. Plugging in the normal config works fine...
So I think this means it's not the cable, stepper or driver, but the config or FW?

I could try to update the FW to the newest version

After printing several spools successfully, suddenly E0 only vibrates on my CoreXY.
I tested multiple Steppers, known good cables etc.
Switched cables to working E1, which now shows the same behaviour as E0 (worked fine before, works if I up it to 800ma on E1, still not on E0).
Even switched Duet Wifi to another one, works with my delta config, doesn't work with the CoreXY
esteps are for a Nimble, in case you are wondering...
Config below:

; Configuration file for Duet WiFi (firmware version 1.17)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Sat Oct 07 2017 22:26:24 GMT+0200 (CEST)

; General preferences
M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
M555 P2 ; Set firmware compatibility to look like Marlin

M667 S1 ; Select CoreXY mode
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X230 Y220 Z320 S0 ; Set axis maxima

; Endstops
M574 X2 Y2 Z2 S1 ; Define active high microswitches
M558 P1 X0 Y0 Z0 H5 F120 T6000 ; Set Z probe type to unmodulated, the axes for which it is used and the probe + travel speeds
G31 P600 X0 Y0 Z2.5 ; Set Z probe trigger value, offset and trigger height
M557 X15:214 Y15:242 S20 ; Define mesh grid

; Drives
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S0 ; Drive 1 goes backwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S0 ; Drive 3 goes forwards
M569 P4 S0 ; Drive 4 goes forwards
M350 X16 Y16 Z16 E16:16 I0 ; Configure microstepping without interpolation
M92 X80 Y80 Z640 E2740:2740 ; Set steps per mm
M566 X1500 Y1500 Z12 E5000:5000 ; Set maximum instantaneous speed changes (mm/min)
M203 X24000 Y24000 Z180 E5000:5000 ; Set maximum speeds (mm/min)
M201 X1000 Y1000 Z450 E2500:2500 ; Set accelerations (mm/s^2)
M906 X800 Y800 Z800 E350:350 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Heaters
M143 S260 ; Set maximum heater temperature to 260C
M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M305 P1 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 1
M305 P2 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 2

; Tools
M563 P0 D0 H1 ; Define tool 0
G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C
M563 P1 D1 H2 ; Define tool 1
G10 P1 X-18 Y0 Z0 ; Set tool 1 axis offsets
G10 P1 R0 S0 ; Set initial tool 1 active and standby temperatures to 0C

; Network
M550 PCorexy ; Set machine name
M552 S1 ; Enable network
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet

; Fans
M106 P0 S0.3 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H1:2 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S1 I0 F500 H1:2 T45 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

; Custom settings are not configured

Great!
I already have 3 1.02 running ... so maybe it’s time to get a 4th printer

@dc42 said in Shorted out always on Fan, none are working anymore:

You can link VIN to either the VIN end of the V_FAN jumper block (make sure you get the VIN end, not the 5V end!) or to the centre pin (V_FAN). That should be sufficient.

Thanks!
I now wired from VIN to V_FAN jumper block VIN and everything works perfectly.
Would there be a downside to make the via more resilient, as shorting any FAN wires against bare metal can happen easily? (Fix is easy as well, maybe add it to the wiki?)

During a print my always on fan disconnected and shorted against the metal arms.
None of the fans are working any longer.
I checked VIN to v_fan continuity to always on fans and it seems the via is blown.
Is it sufficient to wire v_fan to VIN for always on, or do I need something else to get the PWM fans working again as well?