Error Short to Ground reported by driver(s)

davidewen

After running M122, I'm attempting to download log files from console, but nothing happens.

So here is a copy/paste
9/24/2021, 8:53:59 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:53:55 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:53:50 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:53:46 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:53:41 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:53:37 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:53:32 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:53:28 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:53:23 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:53:19 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:53:14 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:53:10 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:53:05 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:53:01 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:52:56 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:52:52 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:52:47 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:52:43 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:52:38 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:52:34 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:52:29 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:52:25 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:52:20 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:52:16 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:52:11 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:52:07 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:52:04 AM 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: F4835-L296U-D65J0-40KML-JK03Z-HP6R5
Used output buffers: 3 of 40 (13 max)
=== RTOS ===
Static ram: 102724
Dynamic ram: 110268 of which 40 recycled
Never used RAM 27816, free system stack 120 words
Tasks: NETWORK(ready,47.0%,240) HEAT(notifyWait,0.1%,366) Move(notifyWait,0.2%,284) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,357) CanClock(delaying,0.0%,340) TMC(notifyWait,2.1%,114) MAIN(running,47.8%,408) IDLE(ready,0.0%,29) AIN(delaying,2.7%,273), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 02:21:07 ago, cause: software
Last software reset at 2021-09-24 06:30, reason: User, GCodes spinning, available RAM 30672, slot 1
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 8467337, completed 8467337, timed out 0, errs 0
Step timer max interval 1488
MCU temperature: min 43.9, current 47.4, max 52.9
Supply voltage: min 23.1, current 23.9, 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/32/32, gc cycles 0
Driver 0: position 0, standstill, SG min/max 0/110, read errors 0, write errors 1, ifcnt 25, reads 52386, writes 14, timeouts 0, DMA errors 0
Driver 1: position 0, standstill, SG min/max 0/86, read errors 0, write errors 1, ifcnt 24, reads 52386, writes 14, timeouts 0, DMA errors 0
Driver 2: position 2071, standstill, SG min/max 0/56, read errors 0, write errors 1, ifcnt 24, reads 52385, writes 14, timeouts 0, DMA errors 0
Driver 3: position 0, short-to-ground, standstill, SG min/max 0/224, read errors 0, write errors 1, ifcnt 29, reads 52383, writes 16, timeouts 0, DMA errors 0
Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 19, reads 52391, writes 9, timeouts 0, DMA errors 0
Driver 5: position 0, assumed not present
Driver 6: position 0, assumed not present
Date/time: 2021-09-24 08:52:04
Cache data hit count 4294967295
Slowest loop: 78.83ms; fastest: 0.07ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 4.3ms, write time 2.5ms, max retries 0
=== Move ===
DMs created 83, maxWait 3310924ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 415, completed moves 415, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 9], 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
Heater 0 is on, I-accum = 0.3
Heater 1 is on, I-accum = 0.3
=== 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 76439, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17), ts 42337/0/0
Tx timeouts 0,233,42336,0,0,33867 last cancelled message type 30 dest 127

=== Network ===
Slowest loop: 85.33ms; 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:4f
WiFi Vcc 3.31, reset reason Power up
WiFi flash size 2097152, free heap 24312
WiFi IP address 192.168.16.220
WiFi signal strength -50dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
9/24/2021, 8:52:03 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:51:58 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:51:54 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:51:49 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:51:45 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:51:40 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:51:36 AM Error: short-to-ground reported by driver(s) 3
9/24/2021, 8:51:31 AM Error: short-to-ground reported by driver(s) 3

dc42

@davidewen with power off please unplug the motor from driver 3, then power up, command driver 3 to move and see if you get the same error message.

Also check that there is nothing conductive under the board that it could be shorting against.

davidewen

@dc42

I have a couple large / long print jobs that need to be completed. Customers are waiting for product, so I will not be able to do this until sometime late next week.

There is nothing conductive under the board. It is elevated off the Ender 6 mounts by a 3D printed PETG spacer.

davidewen

@dc42 said in Error Short to Ground reported by driver(s):

@davidewen with power off please unplug the motor from driver 3, then power up, command driver 3 to move and see if you get the same error message.

Also check that there is nothing conductive under the board that it could be shorting against.

I would to make a note for us to refer back to should it be needed.

After the 1st failure of D3, I moved the Extruder to D4 with no problems since.

When @droftarts sent the 1st request for info on 9/17, I reconnected the Extruder to D3 and revised my config.g to match.

I was able to run for about 20-30 minutes before the error "short to ground" was reported.

I suspect this will be the same when I move the extruder back to D3 again.

I don't think it will do any good if D3 is not reporting the error, so I'm suspecting that you will want me to run it until the error shows up, then run the test you requested?

Please confirm.

David

dc42

@davidewen if RRF reports an intermittent "short to ground" message, then normally either there is a genuine intermittent short in the wiring, or the message is caused by running the driver in stealthChop mode and you are trying to move the motor too fast (this is a behaviour documented by Trinamic). Are you running that driver in stealthChop mode at high speeds?

If the message is caused by a driver failure, then normally the error occurs immediately you try to move the motor.

davidewen

@dc42 said in Error Short to Ground reported by driver(s):

@davidewen if RRF reports an intermittent "short to ground" message, then normally either there is a genuine intermittent short in the wiring, or the message is caused by running the driver in stealthChop mode and you are trying to move the motor too fast (this is a behaviour documented by Trinamic). Are you running that driver in stealthChop mode at high speeds?

If the message is caused by a driver failure, then normally the error occurs immediately you try to move the motor.

As far as I know, I am not running in stealth/chop mode.
Is there some way I can test / confirm that?

As far as a short in the wiring.
Why would I get the error only for D3 and not on D4?

David

davidewen

@dc42

Any update to this case yet?

Thanks,
David

davidewen

@dc42

Have you had the opportunity to look over my last post from Sept 28?

Are there any other questions or tests you want me to run or can I get a RMA for a replacement board?

@davidewen said in Error Short to Ground reported by driver(s):

@dc42 said in Error Short to Ground reported by driver(s):

@davidewen if RRF reports an intermittent "short to ground" message, then normally either there is a genuine intermittent short in the wiring, or the message is caused by running the driver in stealthChop mode and you are trying to move the motor too fast (this is a behaviour documented by Trinamic). Are you running that driver in stealthChop mode at high speeds?

If the message is caused by a driver failure, then normally the error occurs immediately you try to move the motor.

As far as I know, I am not running in stealth/chop mode.
Is there some way I can test / confirm that?

As far as a short in the wiring.
Why would I get the error only for D3 and not on D4?

David

dc42

@davidewen we will replace the Duet. Please email warranty@duet3d.com and include a link to this thread.

davidewen

@dc42 said in Error Short to Ground reported by driver(s):

@davidewen we will replace the Duet. Please email warranty@duet3d.com and include a link to this thread.

Thank you.

I have sent an email as requested.

David

davidewen

@dc42
I received the replacement board.

Swapped old board with new board.
Put SD card from old board into new board.

Could not connect via Wi-Fi.
Took new board out.
Put SD card that came with new board back in.
Connected USB to Mac. (macOS 11.6.1 with M1 chip)
Could not detect board

Followed "Fallback 1 & Fallback 2" instructions @ https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware

Neither worked.
Still can not connect to board via USB
Board does not show up in System Information, or in Terminal via ls /dev/tty.*.

Any suggestions?

Thanks,
David

T3P3Tony

@davidewen with nothing other than the power plugged inot the board, what LEDS are lit? also please send a picture of the board.

davidewen

@t3p3tony

R40 = off
R49 = flashing red (slow flash)
R28 = off
R27 = off
R29 = Red
P30 = Green
ESP = off

elmoret

@T3P3Tony Could you assist David, please?

T3P3Tony

@davidewen with it setup as you have it in the image above, please double click the reset button and see if a Duetboot drive becomes available on the PC over USB. If it does then you can drop the 3.3 firmware for mini 5+ into that drive, it will.opy across then install. After that it should be available over YAT.

Firmware is here:

Duet3Firmware_Mini5plus.uf2
https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet3Firmware_Mini5plus.uf2

davidewen

@t3p3tony
Tony, as mentioned in a previous post.
I have followed all instructions for Fallback 1 & 2 per the guide.
Neither work. Board is not found on computer under System Information, via Terminal or Disk Utility.

@davidewen said in Error Short to Ground reported by driver(s):

Followed "Fallback 1 & Fallback 2" instructions @ https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware
Neither worked.
Still can not connect to board via USB
Board does not show up in System Information, or in Terminal via ls /dev/tty.*.

Results from Terminal
@Macmini-M1 ~ % ls /dev/tty..
zsh: no matches found: /dev/tty..

Results from System Information.
This is what shows up when board is plugged in.

Results from Disk Utility
I do get a "DuetBOOT" after double clicking the reset button, and copying the firmware to the drive does cause a restart, but then I'm back to square 1.

No Duet in System Info or Terminal.
Even with a good copy of sys folder files, no Duet on my WiFi.

T3P3Tony

@davidewen if DuetBoot shows up and the file is transferred successfully then at least part of the USB system is working as expected. I don't have a Mac to test this on - there might be some interaction between the USB driver in that particular version of MacOS/Mac hardware and the Duet. Or it might be a (partially) faulty USB hardware on the Duet.

Would it be possible to try connecting on a PC/laptop running windows?

davidewen

@t3p3tony
I don't have a Windows computer. I do run Windows in Parallels and/or Bootcamp, but still on a Mac computer.

I've tested the connection on the new M1 macMini and an older Intel based MacBookPro_2017. Same issue on both.

I attempted to connect via Parallels.
Did not work.
Could not update the device drivers.

T3P3Tony

@davidewen in that screenshot it showed a serial port on com4 - is that the Duet?

davidewen

@t3p3tony
yes, that's correc