Drivers error short to ground - Multiple
-
@droftarts I've gone through and fixed the config.g and now don't get the error which is good,
I've gone through again and double checked all the stepper motors for there resistance and continuity on the phases.
Stepper motor Resistance
X1 A2.1 B2.1
X2 A2.1 B2.1
E0 A1.9 B1.9
Y A2.2 B2.2
Z1 A2.6 B2.6
Z2 A3.1 B3
Z3 A3.1 B3.1
Z4 A2.6 B2.6I have continuity on each phase A1A2 and B1B2 for each motor and no continuity on A to B phase for each motor. This was checked at the connector end at the Duet and also on the motor pins with the connector off. I also checked each phase to the motor body and had no continuity.
-
@ZakariahMT said in Drivers error short to ground - Multiple:
M122 after home axis
Did you get a short-to-ground report while homing the axes?
-
Yeah they even appear with nothing connected to that driver. Modix Support said it may be the power supply with VIN to thr Duet but I've checked that with a multimeter.
When I have all the driver mapping standard as the config.g I can home the X axis but I get the event notification about driver one having a short right away even though it still moves and homes but then the Y motor won't move.
If I remap driver 5 (Y Axis) to driver 4 (E1 Axis in my case not in use) and home the printer the X Axis will home and the Y Axis homes but I get a two event notifications that drivers 1 and 4 have shorts and the Z axis won't home.
If I just hit the Z limit switch so then there homed I can Jogg the X and y axis fine with no event notifications but the Z won't move at all.
This is present on both boards, I have also reset the firmware and started from scratch with a different SD card to see if maybe that's a cause but the issue still persists.
I have tried different wiring looms with new stepper motors but the issues are still there.
I removed the boards from the printer and checked for any signs of magic smoke but none a are present
-
@ZakariahMT As the Z axis won't move and all those motors are on the Duex, try disconnecting the Duex by disconnecting the ribbon cable between them, and removing the power from the Duex. Then test the Duet on it's own.
You also have one driver with reporting disabled:
M569 P2 R-1
. Has this previously burnt out, or did you disable it when these problems started?Ian
-
It's Alive!
So i've narrowed down what the problem/problems was. The Duex board is dead to a degree. Not supplying voltage to any of the divers but is supplying voltage to everything else on the board like LED strip, griffin Z Puck and clog detector, the Duex is receiving 24v though. I was able to get a hand today from a mate who held the multimeter in the connectors of the axis while i hit home. We tested it against the X Axis which would home but the Y Axis had almost not voltage. We then tried it with the Z axis motors where i would trip the Y axis stop so the BL Touch would trigger and the Z Axis also showed no voltage.
So from there i then removed the Duex out and wired up everything to run off the Duet. I did the config.g for the Duet modix big 60 and it worked right away. I have also tested it with the old Duet2 that was in it and it is also working.
What is the warranty on the boards as i would like to get another Duex back into it so i can use tilt calibration in the future again. Thanks for the help and guidance!
@droftarts said in Drivers error short to ground - Multiple:
As the Z axis won't move and all those motors are on the Duex, try disconnecting the Duex by disconnecting the ribbon cable between them, and removing the power from the Duex. Then test the Duet on it's own.
You also have one driver with reporting disabled: M569 P2 R-1. Has this previously burnt out, or did you disable it when these problems started?Also only just saw your message, for driver 2 it's not used and set to that in the Modix Big 60 V3 Duex Config folder.
-
@ZakariahMT It could just be the ribbon cable between the Duet and Duex is damaged, or one of the wires is making intermittent contact; have a good look at it. That would cause random driver errors, and possibly for the drives on the Duex to not enable. Plug it into the Duet and Duex, then measure resistance across the ribbon cable by testing at the pins on the back of the board. Check all the pins are soldered properly on each board too. There isn't much to go wrong on a Duex!
Are there any heater or motor wires running close to the ribbon cable? It can be susceptible to interference.
Ian