Error:short-to-ground/over temp shutdown reported by driver 0
-
So I'm new to this kind of stuff and I'm having a little trouble getting everything up and running. The wiring was easy, I've done that lots before. The configuration not so much apparently. I could use some help from someone who is far more qualified than me. I'll include all the info I have below. If any more is needed don't hesitate to let me know. I just want to get printing again!!
So here is what I'm running:
Firmware Name: RepRapFirmware for Duet 2 WiFi
Firmware Electronics: Duet WiFi 1.02 or later
Firmware Version: 2.03 (2019-06-13b2)
WiFi Server Version: 1.23
Web Interface Version: 1.22.6All the wiring looks good to me, nothing is on the board. In the web interface, I can move the X, Y, and Z motors up and down. I can heat the bed and hot end, I can even extrude. So I can't for the life of me figure out what this error code is popping up for!
*M122
Error: short-to-ground reported by driver(s) 0
Error: over temperature shutdown reported by driver(s) 0
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later
Board ID: 08DGM-956GU-DGMSN-6JKF0-3S46N-KVQHG
Used output buffers: 4 of 24 (9 max)
=== RTOS ===
Static ram: 25680
Dynamic ram: 93688 of which 0 recycled
Exception stack ram used: 268
Never used ram: 11436
Tasks: NETWORK(ready,652) HEAT(blocked,1236) MAIN(running,3780) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:07:07 ago, cause: power up
Last software reset at 2019-10-02 19:03, reason: User, spinning module GCodes, available RAM 11352 bytes (slot 3)
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: 3.4ms, max retries 0
MCU temperature: min 20.1, current 38.4, max 38.6
Supply voltage: min 24.1, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: temperature-shutdown! short-to-ground standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2019-10-02 19:55:53
Cache data hit count 1697445996
Slowest loop: 4.88ms; 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: 40.56ms; 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 dc:4f:22:6e:6e:fc
WiFi Vcc 3.36, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 22888
WiFi IP address 192.168.0.17
WiFi signal strength -46dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0*
- WiFi -
-
I am not certain, but there are two possibilities I am aware of. I could also be totally off base as I'm not an expert on the wifi - but reported errors are not normally a fluke and usually mean wiring harness issues, overheating, or a damaged driver.
- overtemperature warnings on motor drivers may be a subset of 'short to ground' which is the most general kind of warning on the maestro. Perhaps it's just a temperature fault which is reported on the wifi
- your X axis (drive 0) can be moving just fine 99% of the time but shutting down due to overheating. Usually it's quite an audible click sound, the time off would be 100-1000s of milliseconds and a print would fail due to skips.
Follow up:
- see if the driver is actually hot - measure indirectly, the temps could be over the boiling point!
- look for actual shorts
- try lower current, in case it is excessive
- if these fail, need to disconnect everything else to look for signal crosstalk
-
@3ddevil The X axis has since stopped working completely. I'm thinking it's a blown driver. What could I have done that blew the driver?
Along with the board install I put on a E3D V6 hot end and BLTouch. Following all the installation guides. Any help or tips are appreciated.
-
Either there is a short in the wiring to that motor, or the driver has blown. So check the wiring very carefully, and if you don't find a problem, try connecting a different motor and cable to that driver output. If the problem persists when using a different motor and cable, please ask your supplier to replace the Duet under warranty. Unfortunately, a small proportion of stepper driver chips fail within the first few hours of use.
-
today i transfered my duet to a new corexy build and before i go on i wanted to test the movement..after connecting i had movement but in the wrong way...so i sent a m564 to check each motor separately...Z all ok disconected z wiring plug in X movement but i get the short to ground driver 0 error.....unplugged everything and click on x to move i get the same message.....is that normal?????note that i running the 2.04 firmware
-
@kostasbmw said in Error:short-to-ground/over temp shutdown reported by driver 0:
today i transfered my duet to a new corexy build and before i go on i wanted to test the movement..after connecting i had movement but in the wrong way...so i sent a m564 to check each motor separately...Z all ok disconected z wiring plug in X movement but i get the short to ground driver 0 error.....unplugged everything and click on x to move i get the same message.....is that normal?????note that i running the 2.04 firmware
Please start a new thread and include your config.g file in your post.
-
@kostasbmw said in Error:short-to-ground/over temp shutdown reported by driver 0:
today i transfered my duet to a new corexy build and before i go on i wanted to test the movement..after connecting i had movement but in the wrong way...so i sent a m564 to check each motor separately...Z all ok disconected z wiring plug in X movement but i get the short to ground driver 0 error.....unplugged everything and click on x to move i get the same message.....is that normal?????note that i running the 2.04 firmware
ok
