Error: short-to-ground reported by driver(s) 2 and status busy

Magicride

Hello,

I am building a HyperCube Evolution with the Duet 2 WiFi, and I got everything hooked up and all I get is the error "Error: short-to-ground reported by driver(s) 2" popping up in the corner of the web interface. The steppers that I hooked up came from my old MakerFarm i3 Z axis, so I know that the wiring on them is good and they work, but all I get if I try a "G0 H2 Z5 F3000" is the steppers 'buzzing' and not actually moving along with the aforementioned error. In my config.g I've changed the line "M584 X0 Y1 Z2 E3" to "M584 X0 Y1 Z4 E3" and hooked the steppers up in serial to the E1 Driver and everything works great and as it should without the error message. My problem with this solution is that I want this to be a dual extruder setup like my other printer with a Duet 0.8.5 without purchasing an expansion board or anything else external to the Duet 2 board.

Another thing that happens is the Duet 2 seems to 'lock up' with status "Busy" on the Dashboard and no commands can be sent to the board until I click the Emergency Stop button on the web interface. I don't know if this is related or not, but it definitely is not a favorable thing to have happen.

Here is the output from M115: "M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.0 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2020-01-03b3"

I might be new to the forum, but I am not new to the Duet family as I converted my Rostock MAX V2 to fun on the Duet 0.8.5. There appears to be no damage to the Driver chip, and everything is wired up properly according to the diagram. I think the board may be faulty and tried to contact Filastruder about the issue, but they said that there needs to be authorization by an admin here on the forum for an exchange.

Can an admin help me out here?

Veti

the z connector has 2 plugs. if you only use one the other has to be covered with 2 jumpers.

Magicride

I was using both when I first connected everything. Even tried it with a single stepper with the jumpers on the second connector.

droftarts

@Magicride Please post your config.g, so we can check it. While a stepper driver failure is possible, it's more common that a configuration or wiring issue is to blame. Possibly the Z axis has been configured with motor current set too low for the dual motor setup.

Ian

dc42

@Magicride said in Error: short-to-ground reported by driver(s) 2 and status busy:

The steppers that I hooked up came from my old MakerFarm i3 Z axis, so I know that the wiring on them is good and they work, but all I get if I try a "G0 H2 Z5 F3000" is the steppers 'buzzing' and not actually moving along with the aforementioned error. In my config.g I've changed the line "M584 X0 Y1 Z2 E3" to "M584 X0 Y1 Z4 E3" and hooked the steppers up in serial to the E1 Driver and everything works great and as it should without the error message.

I'm sorry, it does sound like a faulty driver to me. Please contact Filastruder for a replacement under warranty, referring them to this post for authorisation.

Another thing that happens is the Duet 2 seems to 'lock up' with status "Busy" on the Dashboard and no commands can be sent to the board until I click the Emergency Stop button on the web interface. I don't know if this is related or not, but it definitely is not a favorable thing to have happen.

That's a known issue between some versions of DWC and RRF 3.0. Try DWC 2.0.7 and RRF 3.01-beta3.

Magicride

@dc42 Thank you very much for the auth, I will contact them. When I get the new one I will give DWC 2.0.7 + RRF 3.01-beta3 a try and see how that works.