How to diagnose an issue with broken stepper output
-
Can you post the full M122 result from the console tab please?
motor phase disconnected can mean exactly that and the wiring it not actually connected to the right phases.
Are you able to test that same wiring and motor on another driver successfully?
-
@phaedrux
I have successfully used the stepper motor (w/ the same wiring) from different ports
m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2 running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-956BA-NA3TJ-6J1F6-3SJ6T-TVAUV
Used output buffers: 3 of 40 (20 max)
=== RTOS ===
Static ram: 149788
Dynamic ram: 93140 of which 284 recycled
Never used RAM 115620, free system stack 130 words
Tasks: NETWORK(ready,175) ETHERNET(blocked,109) HEAT(blocked,277) CanReceiv(blocked,927) CanSender(blocked,352) CanClock(blocked,349) TMC(blocked,19) MAIN(running,1123) IDLE(ready,19)
Owned mutexes:
=== Platform ===
Last reset 22:26:15 ago, cause: software
Last software reset at 2022-01-31 18:14, reason: User, GCodes spinning, available RAM 115868, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU temperature: min 41.8, current 44.3, max 45.6
Supply voltage: min 23.9, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 11.9, current 12.0, max 12.0, under voltage events: 0
Driver 0: position 0, standstill, reads 6966, writes 20 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 6966, writes 20 timeouts 0, SG min/max 0/0
Driver 2: position 40000, standstill, reads 6961, writes 25 timeouts 0, SG min/max 0/126
Driver 3: position 0, standstill, reads 6961, writes 25 timeouts 0, SG min/max 0/106
Driver 4: position 0, standstill, reads 6967, writes 20 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 6962, writes 25 timeouts 0, SG min/max 0/0
Date/time: 2022-02-01 16:40:23
Slowest loop: 17.78ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 7.6ms, write time 4.7ms, max retries 0
=== Move ===
DMs created 125, maxWait 19187302ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 7, completed moves 7, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 4], 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 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== 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.
=== Network ===
Slowest loop: 45.32ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8- Ethernet -
State: active
Error counts: 0 0 0 0 0
Socket states: 5 2 2 2 2 0 0 0
=== CAN ===
Messages queued 323102, send timeouts 726977, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 48
- Ethernet -
-
When and where did you purchase your Duet?
-
@phaedrux I bought the duett board with a 3d printer (used) off FB Marketplace. I bought it last summer (2021), I do not know how long ago the previous owner had the board.
-
Ah, that does complicate things on the warranty front as we don't know the vendor, it's age, or even if it is genuine. If you can post some photos of the board we may be able to get a better idea of it's provenance. The 6HC is a fairly recent board and only very recently cloned, so I think the likelihood of it being genuine is good.
-
@dima if it's black it's a clone and if it's blue it's real
-
-
@Dima still doing a little digging to see if we can pin down the original purchase of the board to determine warranty status.
Barring that, there are two other options available.
We have some refurbished Duet3 boards that we offer at reduced cost on exchange with the old board.
Or, if that's too expensive an option, and you require all the drivers perhaps using a toolboard for the extruder would be a good option?
-
@Phaedrux
would this mean that it is not a software/firmware issue?
Could I be running too old of a firmware? -- even if its 'stable' -
No it doesn't seem like a firmware issue. The phase error would indicate there is a connection issue, but you have tested the motor and wiring successfully on a different driver. That would indicate that the driver has failed/damaged.
Though if you'd like to update to 3.3 just in case feel free.
Upload this zip file to the system tab.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip
-
@phaedrux Is there a way to check which chip is broken, such that I could try and replace it?
-
It's likely the driver chip itself but it's hard to tell without any obvious visible damage to point the way.
-
@phaedrux ok, thank you for all the help
-
undefined Phaedrux has marked this topic as solved
