Duet Error?
-
I woke up this morning pulled off the test print I did over night and started a Z tower (wobble) test print.
I checked the Gcode Console a few minutes later, and found this....
10:11:39 AM
Error: motor phase B disconnected on drivers 2
10:11:35 AM
Error: motor phase A disconnected on drivers 2
10:11:31 AM
Error: motor phase B disconnected on drivers 2
10:11:28 AM
Error: motor phase A disconnected on drivers 2
10:11:22 AM
Error: motor phase A disconnected on drivers 2
10:11:17 AM
Error: motor phase A disconnected on drivers 2
10:11:04 AM
Error: motor phase A disconnected on drivers 2What does this mean? The printer appears to be working fine. Quick Google search wasn't helpful.
I haven't tried another print yet, as this one is still printing (and working), but could this be caused by this gcode/print? Maybe printing too fast? I have printed faster... this one is printing at 100mm (no print travel at 150mm/s), but I doubt it is getting that fast due to the short distances it has to go for this print.I did stop it, and reslice it... So this is my 2nd attempt of this print, and it happened again. Just not as many. And again, so far only in the beginning of the print.
10:27:06 AM
Error: motor phase A disconnected on drivers 2
10:26:28 AM
Error: motor phase B disconnected on drivers 2Thanks for your help!
-
Started a different print...
It happened again right after it started.12:03:04 PM
Error: motor phase B disconnected on drivers 2
12:02:58 PM
Error: motor phase B disconnected on drivers 2
12:02:52 PM
Error: motor phase B disconnected on drivers 2
12:02:26 PM
Error: motor phase B disconnected on drivers 2
12:02:06 PM
Error: motor phase A disconnected on drivers 2 -
Double check your wiring. Could be a loose crimp maybe?
-
I think driver 2 is the Z axis?
If so, I checked those wires, and they are good. It seems to be happening rare and randomly through prints now. But I am not sure if it is hurting the prints or not. Appears it reconnects after it has the issue. 1) because it can say disconnected the same thing multiple times, and still printer appears to working OK. Or at least the problems I am having right now appear to be with the extruder and or/config. -
Are you are using the 2.02RC1 firmware? I enabled open load warnings in this version, with a timer to try to suppress the false ones that the drivers report when the motors are moving very slowly. If the print worked, then the open load messages were probably spurious and it looks like the timer is insufficient to suppress those. So it looks like I need to either turn them off completely again, or find a better way of suppressing the false ones.
-
Yup
Software Information
Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet Ethernet 1.02 or later
Firmware Version: 2.02RC1(RTOS) (2018-08-31b4)
Web Interface Version: 1.22.3
Web Interface by Christian Hammacher
Licensed under the terms of the GPL v3I just got this error too.
6:12:40 PM
Error: Bad command: 2000When it popped up, the hotend appeared to move off the print.... and then go back to continue printing. I am not sure what is going on. As I am a Duet Noob, and just built this printer, I am not sure if it is me, the RC1, or something else.
EDIT: ... its probably me...
-
As you are a Duet noob, it's probably better for you to use the stable 2.01 firmware instead of the 2.02 release candidate.
-
I was going to ask if I could do revert back and if it was compatible with the current web interface.
-
Yes you can, and RRF 2.01 is compatible with DWC 1.22.3.
-
Thank you!
-
I just got some of these. Everything looks good on the print, cannot spot any shift or layer problem. I guess driver 2 is Z, I have two motors in series.
I will double check the cabling, but I think it's good. I did the cables myself, connectors are well crimped and plus are ok.
Using 20.2RC1.
-
I also have two Z motors
-
If the printer is moving OK then those errors are spurious.
-
Thanks for the help and fast replies!
I rolled back the update last night and the errors are gone! I was thinking it was my Z steppers slipping but couldn't see it actualy happen, like ot recovered way to fast.
Your awesome!
As always, your help is much appreciated!
