Burnt Driver 3 on Duet Wifi

gta18

So, I installed my Hemera E3d head and did not pay attention to the wiring then unintentionally burnt driver 3 short to ground and Over temp error alarm...

Since then I have changed the Extruder to use E1 and have M584 X0 Y1 Z2 E4 on my config.g and everything is working well except for the alarm of short to ground and over temperature keeps popping up even though I don't have Driver 3 configured to be used.

Is the firmware checking status of the drivers even if its not used? How can I disable that part of the code?

I can live with that without that driver until I save up to get another one.

Thanks!

droftarts

@gta18 You can use M569 with parameter R-1 to disable monitoring of a driver. See https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M569_Set_motor_driver_direction_enable_polarity_and_step_pulse_timing

Also see this thread if you don't want to solder the driver yourself: https://forum.duet3d.com/topic/13875/community-repairs

Ian

gta18

I actually took out the driver already and still getting the same errors. I'm now waiting for replacement chip for it. Hopefully the miswiring didnt mess up the board itself.

Was wondering why it would still alarm the same faults even with no chip there?

droftarts

@gta18 See this thread https://forum.duet3d.com/topic/12896/short-to-ground-reported-by-driver-s-2-4-9
The OP had removed the drivers also, and M569 stopped the reporting. Send:
M569 P3 R-1

Ian

dc42

@gta18 said in Burnt Driver 3 on Duet Wifi:

Was wondering why it would still alarm the same faults even with no chip there?

Because without the chip, the SPI data out line floats high, so all the status bits are recorded as being set.

gta18

@dc42 said in Burnt Driver 3 on Duet Wifi:

@gta18 said in Burnt Driver 3 on Duet Wifi:

Was wondering why it would still alarm the same faults even with no chip there?

Because without the chip, the SPI data out line floats high, so all the status bits are recorded as being set.

That would make sense, the alarm per data sheet says "Set" to alarm, I was assuming that the firmware will check for successful spi comms b4 deciding that the alarm bits are valid.

So this adding this per @droftarts M569 P3 R-1 will disable the alarm for driver 3 or all alarms?

Is there a command to just disable for driver 3?

Thanks!
Arnold

richardmckenna

@gta18 according to the gcode docs for M569 https://duet3d.dozuki.com/Wiki/Gcode#Section_M569_Set_motor_driver_direction_enable_polarity_and_step_pulse_timing P3 is selecting driver 3 and R-1 sets "driver is always disabled and is not monitored"

So I guess that will disable just driver 3.

droftarts

@gta18 said in Burnt Driver 3 on Duet Wifi:

So this adding this per @droftarts M569 P3 R-1 will disable the alarm for driver 3 or all alarms?

This should disable (that's the R-1 part) the warnings for driver 3 (that's the P3 part). I thought this should work even with driver removed from the board, but have never tested. Please report your findings!

Ian

gta18

The M569 command worked! thanks! no more bugging by driver 3! now onto waiting for the replacement driver and figuring out why my board hangs up after booting intermittently before this chip burned out.

@droftarts said in Burnt Driver 3 on Duet Wifi:

@gta18 said in Burnt Driver 3 on Duet Wifi:

So this adding this per @droftarts M569 P3 R-1 will disable the alarm for driver 3 or all alarms?

This should disable (that's the R-1 part) the warnings for driver 3 (that's the P3 part). I thought this should work even with driver removed from the board, but have never tested. Please report your findings!

Ian

@droftarts said in Burnt Driver 3 on Duet Wifi:

@gta18 said in Burnt Driver 3 on Duet Wifi:

So this adding this per @droftarts M569 P3 R-1 will disable the alarm for driver 3 or all alarms?

This should disable (that's the R-1 part) the warnings for driver 3 (that's the P3 part). I thought this should work even with driver removed from the board, but have never tested. Please report your findings!

Ian