duet 3 mini 5+ short to ground reported by driver 1
-
Ive been using the Duet 3 mini wifi since i got it and it have been running nicely. And have not made any modifications lately.
But a week ago it showed a error message (short to ground reported by driver 1). And whouldnt move.Luckily i have a second Duet mini motherboard and i put in the same directory files into that one and swaped motherboards on my printer and it works so the duet board.
This make me think the Duet 3 mini motherboard is defective. I sent a mail to the retailer and he asked me to post here.
I have taken some printscreens of the error if this helps.
Also took some pictures of the board, cant see any obvius problems.Let me know how we can solve this issue. Am more than happy to send the defective motherboard back to you if you want to try to fint the problem with it
-
Can you send M122 and M98 P"config.g" in the Gcode console in DWC and post the results here? Also post your config.g.
When and where did you purchase the Duet3 mini5+?
-
2021-11-27 10:03:01 m122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: JRUS0-R196U-D65J0-40KMA-0S03Z-RNU3L
Used output buffers: 3 of 40 (11 max)
=== RTOS ===
Static ram: 102724
Dynamic ram: 106120 of which 144 recycled
Never used RAM 34716, free system stack 196 words
Tasks: NETWORK(ready,15.4%,262) HEAT(notifyWait,0.0%,366) Move(notifyWait,0.1%,362) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.0%,340) TMC(delaying,0.7%,115) MAIN(running,82.9%,426) IDLE(ready,0.2%,29) AIN(delaying,0.8%,273), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:02:11 ago, cause: power up
Last software reset at 2021-11-02 18:52, reason: User, GCodes spinning, available RAM 31684, 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 131907, completed 131907, timed out 0, errs 0
Step timer max interval 1486
MCU temperature: min 19.6, current 27.0, max 27.0
Supply voltage: min 12.7, current 14.9, max 15.1, 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
Driver 0: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 10, reads 6913, writes 10, timeouts 0, DMA errors 0
Driver 1: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 6914, writes 9, timeouts 0, DMA errors 0
Driver 2: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 6914, writes 9, timeouts 0, DMA errors 0
Driver 3: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 6914, writes 9, timeouts 0, DMA errors 0
Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 10, reads 6913, writes 10, timeouts 0, DMA errors 0
Driver 5: position 0, assumed not present
Driver 6: position 0, assumed not present
Date/time: 2021-11-27 10:03:01
Cache data hit count 249144811
Slowest loop: 5.96ms; fastest: 0.12ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.7ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, 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, chamberHeaters = -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.
=== CAN ===
Messages queued 1185, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17), ts 660/0/0
Tx timeouts 0,0,659,0,0,524 last cancelled message type 30 dest 127=== Network ===
Slowest loop: 10.59ms; 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 f0:08:d1:02:e8:44
WiFi Vcc 3.36, reset reason Power up
WiFi flash size 2097152, free heap 24096
WiFi IP address 192.168.1.77
WiFi signal strength -46dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
2021-11-27 10:02:45 Connected to 192.168.1.77
2021-11-27 10:08:07 M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: in file macro line 76 column 8: M18: expected number after 'E'I bought the Duet3mini5+ from E3D Online 1 juni 2021
- WiFi -
-
@hampusåström I aussme that M122 is from the working mini5+ not the one with the driver error reported?
-
Hi,
This is the old defective board.
If i dont try to Home the printer or move any stepper it wont show a short and M122 seems good.But i ran the M122 after trying to home and this message came up.
2021-11-29 17:14:06 m122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: JRUS0-R196U-D65J0-40KMA-0S03Z-RNU3L
Used output buffers: 3 of 40 (12 max)
=== RTOS ===
Static ram: 102724
Dynamic ram: 106216 of which 48 recycled
Never used RAM 31860, free system stack 152 words
Tasks: NETWORK(ready,14.9%,253) HEAT(delaying,0.0%,366) Move(notifyWait,0.1%,305) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.0%,340) TMC(notifyWait,0.7%,115) MAIN(running,83.3%,426) IDLE(ready,0.2%,29) AIN(delaying,0.8%,273), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:02:14 ago, cause: power up
Last software reset at 2021-11-02 18:52, reason: User, GCodes spinning, available RAM 31684, 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 134517, completed 134517, timed out 0, errs 0
Step timer max interval 1487
MCU temperature: min 20.9, current 27.9, max 28.3
Supply voltage: min 14.8, current 14.8, max 14.9, 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 25800, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 12, reads 7048, writes 12, timeouts 0, DMA errors 0
Driver 1: position 9500, short-to-ground, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 11, reads 7049, writes 11, timeouts 0, DMA errors 0
Driver 2: position 2000, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 11, reads 7049, writes 11, timeouts 0, DMA errors 0
Driver 3: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 7051, writes 9, timeouts 0, DMA errors 0
Driver 4: position 0, standstill, SG min/max 0/2, read errors 0, write errors 0, ifcnt 12, reads 7048, writes 12, timeouts 0, DMA errors 0
Driver 5: position 0, assumed not present
Driver 6: position 0, assumed not present
Date/time: 2021-11-29 17:14:05
Cache data hit count 252422784
Slowest loop: 6.85ms; fastest: 0.10ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.6ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 117478ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 12, completed moves 12, 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, chamberHeaters = -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.
=== CAN ===
Messages queued 1209, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17), ts 673/0/0
Tx timeouts 0,0,672,0,0,535 last cancelled message type 4514 dest 127=== Network ===
Slowest loop: 10.64ms; 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 f0:08:d1:02:e8:44
WiFi Vcc 3.36, reset reason Power up
WiFi flash size 2097152, free heap 19720
WiFi IP address 192.168.1.77
WiFi signal strength -48dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
2021-11-29 17:14:04 Error: short-to-ground reported by driver(s) 1
You can see the picture i posted.
I ran an emergency stop and it reseted and i ran a M122 and the same as i posted first came up.
I hope this helps to get a better picture of my issue with this board.
- WiFi -
-
I am experiencing the exact same problem in my case with driver 2.
What can I do to solve it?Thanks in advance
Regards
Julián. -
@juliann Hi, please create a new thread for your issue. Include as much detail as possible.
-
@hampusåström said in duet 3 mini 5+ short to ground reported by driver 1:
I bought the Duet3mini5+ from E3D Online 1 juni 2021
Thanks for the updated M122 showing the short to ground error after trying to initiate movement.
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.
-
undefined juliann referenced this topic
