Repeated "short-to-ground" error in console.....

jch

Hi guys,

I hope someone is able to help me with an error I keep getting.

The below error keeps on popping up, even when nothing but the power is plugged in to the board.

Error: short-to-ground reported by driver(s) 3
Error: over temperature shutdown reported by driver(s) 3

I get it around every 4-5 seconds, and from what I've read, this is not a good error to get.

As suggested by other posts, I've checked all my wiring, to ensure there are no shorts, and all looks ok, so I'm a little worried....

Any help would be greatly appreciated.

Thanks

Veti

driver 3 is the extruder motor.
check the chip underneath the connector if it looks different to the other ones.

but an over temperature warning with nothing going on is not a good sign.

jch

Hey @Veti

Thanks for the input.

Everything on the board looks ok, no differences between the chips, so not quite sure what's going on.

From the other posts I've been reading, this seems to be a fatal issue, so makes me really sad (relatively expensive board) to think the board/chip might be damaged.

So...... watch this space, I guess.

Thanks!

MaracMB

@jch before you toss everything, check the wiring. You need nice, solid and cleanly crimped connectors. All of them. Cables that go into screw in connectors (like heater cables), need ferrule caps. Included in the box.
Don’t rush, just make it right. Do not improvise, check tutorials or read about something you don’t know. And i say know because there is a difference between “i have seen a lion being tamed” and “i can tame a lion”.
I had this “ short to ground” on one of my machines i was modding and it was wiring. Also, the second error indicates wiring issues with thermistor.

Hope this helps.

jch

Hey @MaracMB,

Thanks for the input.

So, although I've checked and re-checked. My connections are 100% (got all the correct crimping tools and connectors for this project, and trust me when I say, I'm taking my time ), the issue still occurs when nothing esle but power's connected.

Hopefully one fo the Duet Engineers can shed a little light on this.... A little stuck right now....

Thanks

Veti

is this a new board?

jch

Hey @Veti ,

Yep, brand new.

Bought it about a month ago, and when I got my printer parts last week, started using it, so yeah, new.

Thanks!

Veti

@dc42 needs to way in here as this might be a warranty replacement case.

MaracMB

@jch for Duet engineers and others to be able to help you, it would be of great benefit, if you post a diagnostics log.

Use M122 after error copy and post it here.

jch

@Veti @MaracMB - thank you both again!

This is the diagnostic I get back

=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later
Board ID: 08DGM-917DA-G4MSJ-6J9F6-3S86R-19NBA
Used output buffers: 3 of 24 (10 max)
=== RTOS ===
Static ram: 25680
Dynamic ram: 93644 of which 416 recycled
Exception stack ram used: 260
Never used ram: 11072
Tasks: NETWORK(ready,524) HEAT(blocked,1236) MAIN(running,3748) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:00:32 ago, cause: power up
Last software reset at 2019-07-01 14:30, reason: User, spinning module GCodes, available RAM 10792 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 21.1, current 29.6, max 29.6
Supply voltage: min 22.7, current 22.8, max 23.1, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: temperature-shutdown! short-to-ground standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2019-07-02 09:35:32
Cache data hit count 117795349
Slowest loop: 5.70ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
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
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 15.66ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
- WiFi -
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address ec:fa:bc:2d:df:3e
WiFi Vcc 3.43, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 25272
WiFi IP address 192.168.1.160
WiFi signal strength -42dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0

dc42

I'm sorry to see that your Duet appears to have blown a driver. Please ask your supplier for a replacement under warranty. https://www.duet3d.com/warranty

jch

So it's as I feared... Thank you @dc42

jch

Thank you again @dc42 - Going through the warranty process with my supplier now.