Motor phase A/B may be disconnected
-
My printer (Voron 2.4) was working flawlessly with Duet2Wifi/Duex5. Last night after the last print I've shut it off and went to sleep. Today I turned it on and sent a G28 (home) to start a new print but it didn't move. Console reported:
G28 Warning: motor phase A may be disconnected reported by driver(s) 0 1 Warning: motor phase B may be disconnected reported by driver(s) 0 1
So, I google it and read a lot of posts about it here. First thing I did was to check all the wires with a multimeter and couldn't find any breaks. Phases were ok as well. Changed the X/Y cable to new drivers and the same behavior happened (only changing drivers number on the warning to the new ones). When trying to home z I get:
G28 Warning: motor phase A may be disconnected reported by driver(s) 5 6 7 8 Warning: motor phase B may be disconnected reported by driver(s) 5 6 7 8
Upgraded firmware from 3.2.2 to 3.3 but still same thing. Here's some info that might be helpful:
M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later + DueX5 Board ID: 08DGM-9T6BU-FG3S4-6J9FJ-3S46T-1SQRF Used output buffers: 3 of 24 (11 max) === RTOS === Static ram: 23876 Dynamic ram: 80076 of which 0 recycled Never used RAM 7608, free system stack 134 words Tasks: NETWORK(notifyWait,5.4%,244) HEAT(delaying,0.0%,330) Move(notifyWait,0.1%,277) DUEX(notifyWait,0.0%,24) MAIN(running,93.5%,441) IDLE(ready,1.0%,29), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:01:13 ago, cause: power up Last software reset at 2021-06-21 13:01, reason: User, GCodes spinning, available RAM 10472, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Step timer max interval 0 MCU temperature: min 21.3, current 25.9, max 29.9 Supply voltage: min 23.9, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/12/12, gc cycles 0 Driver 0: position 0, standstill, SG min/max not available Driver 1: position 0, standstill, SG min/max not available Driver 2: position 0, standstill, SG min/max not available Driver 3: position 0, standstill, SG min/max not available Driver 4: position 0, standstill, SG min/max not available Driver 5: position 0, standstill, SG min/max not available Driver 6: position 0, standstill, SG min/max not available Driver 7: position 0, standstill, SG min/max not available Driver 8: position 0, standstill, SG min/max not available Driver 9: position 0, ok, SG min/max not available Driver 10: position 0 Driver 11: position 0 Date/time: 2021-06-21 13:58:06 Cache data hit count 4294967295 Slowest loop: 17.27ms; fastest: 0.18ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 2.2ms, write time 0.0ms, max retries 0 === Move === DMs created 83, maxWait 19004ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 Heater 1 is on, I-accum = 0.0 === GCodes === Segments left: 0 Movement lock held by null HTTP is idle in state(s) 0 Telnet is idle in state(s) 0 File is idle in state(s) 0 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger is idle in state(s) 0 Queue is idle in state(s) 0 LCD is idle in state(s) 0 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === DueX === Read count 1, 0.81 reads/min === Network === Slowest loop: 203.01ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 - WiFi - Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.26 WiFi MAC address 80:7d:3a:15:01:82 WiFi Vcc 3.42, reset reason Turned on by main processor WiFi flash size 4194304, free heap 23568 WiFi IP address 192.168.5.208 WiFi signal strength -41dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0
M913 Motor current % of normal - X:75, Y:75, Z:100, E:100
M906 Motor current (mA) - X:900, Y:900, Z:900, E:600, idle factor 30%
Really don't know what to look/test anymore. Anyone have any thoughts on what else should I try? Thanks
-
So every single driver you try to use reports the same warning?
Do you see any damage to the driver chips themselves? Are they getting hot to the touch?
When and where did you purchase your Duet and Duex?
Can you share your config file (and any called macros?)
-
@phaedrux said in Motor phase A/B may be disconnected:
So every single driver you try to use reports the same warning?
Yes, just tried to extrude and got same warning but for driver 3.
Do you see any damage to the driver chips themselves? Are they getting hot to the touch?
Nothing visible on the board. Drivers are at room temp.
When and where did you purchase your Duet and Duex?
Don't know where/when it was originally bought. It was a 2nd hand purchase mid 2020.
Can you share your config file (and any called macros?)
M111 S0 G21 G90 M83 M669 K1 M564 S1 H1 M918 P2 R6 C30 E-4 F200000 M550 PVoron24 M552 S1 M586 P0 S1 M586 P1 S1 M586 P2 S0 M569 P5 S1 ; Z0 M569 P6 S0 ; Z1 M569 P7 S1 ; Z2 M569 P8 S0 ; Z3 M569 P3 S0 ; Extruder M569 P0 S1 ; A M569 P1 S0 ; B M584 X0 Y1 E3 Z5:6:7:8 M350 X16 Y16 Z16 E16 I1 M92 X80 Y80 Z400 M92 E436 M906 X900 Y900 Z900 E600 M906 I30 M84 S120 M566 X600 Y600 Z60 E8000 M203 X18000 Y18000 Z3000 E15000 M201 X2000 Y2000 Z250 E1800 M204 P1500 T2000 M208 X0 Y0 Z0 S1 M208 X298 Y303 Z270 S0 M574 X2 S1 P"xstop" M574 Y2 S1 P"ystop" M574 Z0 P"nil" M558 K0 P8 C"^zprobe.in" T18000 F120 H5 A5 S0.01 R0.2 G31 K0 P500 X0 Y25 Z2.0 M558 K1 P8 C"^zstop" T18000 F60 H2 A10 S0.005 R0.2 G31 K1 P500 X0 Y0 Z0.77 M671 X-50:-50:350:350 Y5:378:378:5 S20 M557 X25:275 Y25:275 S25 M308 S0 P"bed_temp" Y"thermistor" T100000 B3950 A"Bed Heater" M950 H0 C"bed_heat" T0 Q10 M140 P0 H0 M143 H0 S120 M307 H0 B0 S0.6 M308 S1 A"Hotend" P"e0_temp" Y"thermistor" T100000 B4138 M950 H1 C"e0_heat" T1 M307 H1 B0 S1.00 M143 H1 S300 M308 S3 Y"mcu-temp" A"MCU" M308 S4 Y"drivers" A"Drivers" M308 S5 Y"drivers-duex" A"Duex Drivers" M950 F0 C"fan0" Q250 M106 P0 S1 H1 T50 C"Hotend" M950 F1 C"fan1" Q20 M106 P1 S0 H-1 C"Part Fan" M563 P0 D0 H1 F1 G10 P0 X0 Y0 Z0 G10 P0 R0 S0 M572 D0 S0.01 M592 D0 A0.015 B0.0012 L0.2 M376 H10 M912 P0 S-8.5 M593 F42.5 M80 M501 T0
One werid thing I just found. Tried to remove the IDC cable (disconnecting Duex) and X/Y/E motors worked. So it's not wiring or drivers on Duet, but something on Duex. When I reconnected the Duex the warnings were back. Any thoughts?
-
How do you have the power and ground for the Duex wired up?
Should be like this: https://duet3d.dozuki.com/Wiki/Duex2_and_Duex5_Features#Section_Wiring
Do any of the other fan/heater/etc ports on the Duex work correctly?
Photos of the board in case we can spot something?
-
@phaedrux said in Motor phase A/B may be disconnected:
How do you have the power and ground for the Duex wired up?
Should be like this: https://duet3d.dozuki.com/Wiki/Duex2_and_Duex5_Features#Section_Wiring
Yes, 24V/GND are coming from the Duet as shown in the link
Do any of the other fan/heater/etc ports on the Duex work correctly?
Just moved a fan and the extruder heater to duex.fan8 and duex.e2_heat and both worked. Tried also to disconnect everything from Duex (except the IDC cable) and the warnings were still there and X/Y/E motors didn't work.
Photos of the board in case we can spot something?
-
The photo is not high enough quality for me to make out any individual components clearly. A couple close up well lit shots would help.
-
@phaedrux see if this one is better: https://imgur.com/a/kx5lfiu
-
@ice it could be just me , but have you checked the plugs ?
some connecters look like there deeper in the socket . -
@peter247 Yes, just checked again and they all are all the way in. But even with all the 4 motors not connected to the board I still have the same issue.