Motors all stopped moving
-
Post your config.g as well so we can see which drivers were mapped to which axis.
Perhaps post a photo of the board close up and well lit in case we can spot something blown.
Are all of the LEDs on the board lit?
Do you get any error messages in the console when you try and move an axis?
Double check the fuse?
-
@phaedrux
driver definitions are as follows
M584 X8 Y9 Z5:6:7 C1 E3:2:4:0!
as seen in the pictures it looks like driver 7 is potentially blown but would this cause all drivers to stop? fuses are all fine.
-
Yes driver 7 definitely looks to have given up the ghost. There may be other damage that's less visible. I'll see what DC42 thinks.
-
@phaedrux what should i do from here if the expansion board is replaced will it be back up and fully functioning or is it likely something else is broken?
-
Sorry about that, let me follow up again with DC42
-
Do the drivers on the main duet board still function?
It's hard to say how much would have blown on the Duex. If a trace was damaged, etc. Better lit close up photos might show more, but I can't see anything from the photo you poted other than the obvious damage to driver 7.
What's odd is that the M122 reports normal driver status for 7.
Can you try and gather another M122 after trying to command movement on all the drivers? -
@ddunn if you disconnect the ribbon cable to the expansion board, do the drivers on the main board work?
When did you purchase the DueX?
-
Tried to move x then y axis which are on the main board then the z axis motors none of which moved (as expected neither moving nor homing moves) then ran M122 command. The x,y and z coordinates on the duet dashboard are changing as if the controller believes it is moving if that helps. Are there any specific areas that you want closer images of?
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-917DA-G4MS4-6JKD8-3SJ6K-K8XH9
Used output buffers: 3 of 24 (20 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 74336 of which 60 recycled
Never used RAM 14224, free system stack 125 words
Tasks: NETWORK(ready,163) HEAT(blocked,308) DUEX(blocked,31) MAIN(running,449) IDLE(ready,20)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:03:32 ago, cause: power up
Last software reset at 2021-05-26 13:01, reason: User, GCodes spinning, available RAM 13808, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 30.8, current 42.7, max 42.9
Supply voltage: min 24.1, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 15000, ok, SG min/max not available
Driver 1: position 5000, ok, SG min/max not available
Driver 2: position -32050, ok, SG min/max not available
Driver 3: position 0, ok, SG min/max not available
Driver 4: position 0, ok, SG min/max not available
Driver 5: position 0, ok, SG min/max 0/992
Driver 6: position 0, ok, SG min/max 0/896
Driver 7: position 0, ok, SG min/max 0/0
Driver 8: position 0, ok, SG min/max 0/0
Driver 9: position 0, ok, SG min/max 0/0
Driver 10: position 0
Driver 11: position 0
Date/time: 2021-06-07 09:01:31
Cache data hit count 253440027
Slowest loop: 11.72ms; fastest: 0.19ms
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 4.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 90765ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 14, completed moves 14, 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, 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 25.82ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 2 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.25
WiFi MAC address 60:01:94:2e:a5:96
WiFi Vcc 3.41, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 23752
WiFi IP address 192.168.1.16
WiFi signal strength -67dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
=== DueX ===
Read count 1, 0.28 reads/min
- WiFi -
-
@phaedrux
As for purchase dates i purchased the original boards in i believe june of last year but they weren't installed until March of this year as the machine was still waiting on parts to be machined. My original wifi board was replaced with a refurbished board at the end of march. The replacement wifi board was installed and functional beginning of April and everything worked without issue until end of may when i posted here with this issue. -
@ddunn and the answer to my other question?
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42
sorry no they still didn't work here is the M122 after removing ribbon cable and attempting to move the main board drivers.M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later
Board ID: 08DGM-917DA-G4MS4-6JKD8-3SJ6K-K8XH9
Used output buffers: 3 of 24 (16 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 73804 of which 56 recycled
Never used RAM 14760, free system stack 125 words
Tasks: NETWORK(blocked,182) HEAT(blocked,308) MAIN(running,449) IDLE(ready,20)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:56 ago, cause: power up
Last software reset at 2021-05-26 13:01, reason: User, GCodes spinning, available RAM 13808, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 31.7, current 36.6, max 36.8
Supply voltage: min 24.1, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position -19000, standstill, SG min/max not available
Driver 1: position -3000, standstill, SG min/max not available
Driver 2: position -16025, 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
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2021-06-07 09:55:14
Cache data hit count 64412946
Slowest loop: 12.27ms; fastest: 0.21ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 3.9ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 14377ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 20, completed moves 19, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 6], CDDA state 3
=== 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
=== GCodes ===
Segments left: 0
Movement lock held by Aux
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 doing "G30" in state(s) 0 8, running macro
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.
=== Network ===
Slowest loop: 26.85ms; 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.25
WiFi MAC address 60:01:94:2e:a5:96
WiFi Vcc 3.41, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 26952
WiFi IP address 192.168.1.16
WiFi signal strength -65dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 4 0 0 0 0 0 0 0
- WiFi -
-
@phaedrux
Tried to get some better images not sure what all is relevant
-
Any ideas?
-
Hi, please send an email to warranty@duet3d.com and we'll see if we can get you a replacement Duet and Duex.
