Driver 0 Phase May Be Disconnected
-
CoreXY 3 axis Z RR 500... I have been having this intermittant issue, with the "Driver 0 Phase A/B may be disconnected" message repeatedly coming on during prints. Eventually at one point during bed leveling that z motor stopped moving altogether. Luckily I was there to save it from bed damage. I checked the wiring thoroughly, and to isolate it, I even swapped the board plug from that stepper with the other stepper and assigned the Driver 0.0 from the right front Z motor to the left front Z motor, to see if the problem moved to the other driver or remained at Driver 0.
Well, today during bed leveling, I got the warning again and the right front (Driver 0) completely failed to move, which tells me its an definitely an issue at the board, not the wiring. Does this indicate a bad board Driver 0, or is there something else I should check?
All my Z axis motor currents are set at 1600mA. The steppers are LDO-425TH48, rated at 2.5A.
As with the extruder issue I am also having, it is a completely intermittant and unpredictable.
-
So just to confirm, the error follows the driver even when a different motor/wire harness are connected?
Can you share your full config.g, along with the results of M122 and M98 P"config.g" ?
When and where was the board purchased?
-
@Phaedrux Yes. It stayed at the same driver even with a different cable and stepper hooked up. It was purchased through Filastruder on 11/21/22 with 8 other 1LC boards.
m122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.4.6 (2023-07-21 14:09:13) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: GS9VZ-V296U-D65J0-40KMY-L713Z-RU7ZK Used output buffers: 1 of 40 (13 max) === RTOS === Static ram: 103712 Dynamic ram: 116740 of which 20 recycled Never used RAM 21240, free system stack 200 words Tasks: NETWORK(notifyWait,10.1%,223) HEAT(notifyWait,0.0%,374) Move(notifyWait,0.0%,363) CanReceiv(notifyWait,0.0%,798) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.0%,351) TMC(notifyWait,0.7%,115) MAIN(running,86.6%,411) IDLE(ready,1.8%,30) AIN(delaying,0.8%,263), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:00:23 ago, cause: software Last software reset at 2023-08-28 19:16, reason: User, GCodes spinning, available RAM 20364, slot 2 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 MCU revision 3, ADC conversions started 23964, completed 23962, timed out 0, errs 0 Step timer max interval 1488 MCU temperature: min 40.6, current 41.2, max 41.4 Supply voltage: min 24.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 29, reads 1220, writes 11, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 29, reads 1220, writes 11, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 29, reads 1220, writes 11, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 2, read errors 0, write errors 1, ifcnt 29, reads 1219, writes 11, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 29, reads 1220, writes 11, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2023-08-28 19:17:01 Cache data hit count 43911812 Slowest loop: 12.40ms; fastest: 0.13ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 3.3ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 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 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === CAN === Messages queued 218, received 451, lost 0, boc 0 Longest wait 3ms for reply type 6053, peak Tx sync delay 3, free buffers 18 (min 17), ts 119/118/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 23.75ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 = WiFi = Interface state: active Module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.27 WiFi MAC address f0:08:d1:03:80:d7 WiFi Vcc 3.38, reset reason Power up WiFi flash size 2097152, free heap 25056 WiFi IP address 192.168.0.67 WiFi signal strength -48dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0M98 P"config.g" HTTP is enabled on port 80 FTP is disabled TELNET is disabled Accelerometer 121:0 type LIS3DH with orientation 54 samples at 1344Hz with 10-bit resolution -
Yes it seems like the driver is failing.
Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.
-
@Phaedrux said in Driver 0 Phase May Be Disconnected:
Yes it seems like the driver is failing.
Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.
My mistake; this board was actually purchased from Ratrig. I'm assuming the return procedure is the same.
-
Have you sent the email yet?
-
@Phaedrux said in Driver 0 Phase May Be Disconnected:
Have you sent the email yet?
Working on that right now.
