Possible to disable a driver/suppress driver error messages?

jsteele22

Hi All,

I had a "little problem" with stepper driver 3 (E0) on My Duet2 Ethernet board. It blistered and smoked, and any time I powered up the board it got real, hot real fast. To remedy this, I removed the chip. Under a microscope, it doesn't appear that that there are any shorts or other problems with the footprint. It is, however, damaged so replacing the chip is not an option.

I fixed the original problem (extruder stepper was mis-wired). I then connected the extruder to driver 4 (E1) and adjusted my config.g

Now, everything works fine. The extruder is happy.

Except... I keep getting errors from driver 3 (i.e., E0) I get "short to ground" and "overtemperature shutdown" messages. Over and over. It makes the LCD interface unusable.

Q1) Is there a way (in config.g) to tell the firmware to ignore driver 3? Again, that chip physically IS NOT THERE. It can't be sending these messages via SPI!

Q2) If not, is there a way to suppress the warning messages?

Q3) If not, would this problem "go away" if I upgraded my firmware? I'm currently running 2.0.5. The issue, frankly, seems like a bug; maybe it got fixed at some point?

Q4) In a worst case scenario, is there a way to "comment out" driver 3 in the firmware source code?

I was so close to having a printer again......

Thanks

dc42

@jsteele22 see the R-1 parameter in the M569 command, https://docs.duet3d.com/User_manual/Reference/Gcodes#m569-set-motor-driver-direction-enable-polarity-mode-and-step-pulse-timing.

jsteele22

@dc42

Wow, that was fast! And it worked like a charm.

Thank you this much (holds hands far apart.)

I had been referring to the G-code documentation at :
https://reprap.org/wiki/G-code#M569:_Stepper_driver_control, which seems like it should be up to date and official. But it does not mention the -1 option for the R parameter.

Is there supposed to be a discrepancy between this reference and the one you posted?

dc42

@jsteele22 the reprap.org wiki covers many different firmwares. For any particular firmware it's best to look at the documentation for that particular firmware if you want the fine detail.

jsteele22

@dc42
Okay, thanks a lot.