"Error: short-to-ground reported by driver(s) 3"

akayoshi

Hi All,

I have purchased a duet 3 within the last 2 weeks.

I just connected my extruder to driver 3, and I get the error
"Error: short-to-ground reported by driver(s) 3"

I checked that the stepper motor was wired correctly by checking the phases with a multimeter prior to connecting to the duet. (https://duet3d.dozuki.com/Wiki/Choosing_and_connecting_stepper_motors#Section_Identifying_the_stepper_motor_phases).

I've tried a few things to troubleshoot

the extruder works when plugged into stepper driver 4 indicating that my wiring is correct
The same error is returned even when I unplugged the extruder from the duet 3.
I've read @DC42 post https://forum.duet3d.com/topic/4160/error-short-to-ground-on-drivers-1/8 and think I probably have a defective stepper motor.
I've plugged the Y axis into stepper driver 3 and have the same problems (also reconfigured the config.g to suit)
No metal shorting the pins on the duet
Rewired the cable, checked continuity from plug to plug
Read through the warranty info @https://www.duet3d.com/warranty and posted here to seek approval for a warranty claim

Here is my config.g


; Configuration file for Duet 3 (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Wed Mar 31 2021 21:23:47 GMT+1100 (Australian Eastern Daylight Time)

; General preferences
G90                                                ; send absolute coordinates...
M83                                                ; ...but relative extruder moves
M550 P"duet 3"                                     ; set printer name

; Network
M552 P0.0.0.0 S1                                   ; enable network and acquire dynamic address via DHCP
M586 P0 S1                                         ; enable HTTP
M586 P1 S0                                         ; disable FTP
M586 P2 S0                                         ; disable Telnet

; Drives
M569 P0.0 S1                                       ; physical drive 0.0 goes forwards
M569 P0.1 S1                                       ; physical drive 0.1 goes forward
M569 P0.2 S0                                       ; physical drive 0.2 goes backwards
M569 P0.3 S0                                       ; physical drive 0.3 goes forwards
M584 X0.0 Y0.1 Z0.2 E0.3                           ; set drive mapping
M350 X16 Y16 Z16 E16 i1                             ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E394.20                  ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00                ; set maximum instantaneous speed changes (mm/min)
M203 X12000.00 Y12000.00 Z180.00 E1200.00          ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00                ; set accelerations (mm/s^2)
M906 X800 Y725 Z800 E800 I30                      ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                            ; Set idle timeout

; Axis Limits
M208 X-225 Y-225 Z0 S1                                   ; set axis minima
M208 X225 Y225 Z470 S0                             ; set axis maxima

; Endstops
M574 X1 S1 P"io4.in"                               ; configure active-high endstop for low end on X via pin io4.in
M574 Y2 S1 P"io3.in"                               ; configure active-high endstop for high end on Y via pin io3.in
M574 Z1 S2                                         ; configure Z-probe endstop for low end on Z

; Z-Probe
M950 S0 C"io7.out"                                 ; create servo pin 0 for BLTouch
M558 P9 C"io7.in" H5 F120 T6000                   ; set Z probe type to bltouch and the dive height + speeds
;G31 P500 X-41 Y5 Z2.5                              ; set Z probe trigger value, offset and trigger height
G31 P500 x-41 Y5 z5.24
M557 X-195:225 Y-225:175 S75                           ; define mesh grid
M280 P0 S90
g29 s1
; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4138       ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out2" T0                                 ; create bed heater output on out2 and map it to sensor 0
M307 H0 B0 S1.00                                   ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0                                            ; map heated bed to heater 0
M143 H0 S120                                       ; set temperature limit for heater 0 to 120C
M308 S1 P"temp1" Y"thermistor" T100000 B4138       ; configure sensor 1 as thermistor on pin temp1
M950 H1 C"out1" T1                                 ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 B0 S1.00                                   ; disable bang-bang mode for heater  and set PWM limit
M143 H1 S280                                       ; set temperature limit for heater 1 to 280C

; Fans
M950 F0 C"out7" Q500                               ; create fan 0 on pin out7 and set its frequency
M106 P0 T45 h1                                   ; set fan 0 value. Thermostatic control is turned on
;m106 p0 s255
;M950 F1 C"out8" Q500                               ; create fan 1 on pin out8 and set its frequency
;M106 P1 S1 H1 T45                                  ; set fan 1 value. Thermostatic control is turned on
;m106 p1 s255
; Tools
M563 P1 S"extruder 1" D0 H1 F0                     ; define tool 1
G10 P1 X0 Y0 Z0                                    ; set tool 1 axis offsets
G10 P1 R0 S0                                       ; set initial tool 1 active and standby temperatures to 0C

; Custom settings are not defined

; Miscellaneous
M501                                               ; load saved parameters from non-volatile memory
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss

thanks in advanced

Cheers P

Phaedrux

Thanks for proving such complete troubleshooting.

Can you provide one last thing? The results of M122 and M98 P"config.g"

When and where did you purchase the Duet 3?

Do you see any visible damage to the driver chip itself?

akayoshi

@phaedrux said in "Error: short-to-ground reported by driver(s) 3":

M122

Thanks @Phaedrux

I purchased the duet 3 from https://aurarum.com.au/ the Australian reseller on the 26 March 2021.

I can't see any visible damage on the driver chip.

M122

11/04/2021, 11:41:10	Error: short-to-ground reported by driver(s) 3
11/04/2021, 11:41:06	Error: short-to-ground reported by driver(s) 3
11/04/2021, 11:41:03	m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2.2 running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-956L2-G43S8-6JKD0-3S46K-9U2YD
Used output buffers: 3 of 40 (22 max)
=== RTOS ===
Static ram: 149788
Dynamic ram: 92972 of which 92 recycled
Never used RAM 115980, free system stack 122 words
Tasks: NETWORK(ready,169) ETHERNET(blocked,110) HEAT(blocked,297) CanReceiv(blocked,927) CanSender(blocked,352) CanClock(blocked,352) TMC(blocked,17) MAIN(running,1119) IDLE(ready,19)
Owned mutexes:
=== Platform ===
Last reset 00:08:22 ago, cause: power up
Last software reset at 2021-04-11 11:30, reason: User, GCodes spinning, available RAM 116064, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU temperature: min 36.2, current 38.3, max 38.3
Supply voltage: min 24.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0
Driver 0: position 0, standstill, reads 42148, writes 8 timeouts 0, SG min/max not available
Driver 1: position 0, standstill, reads 42149, writes 7 timeouts 0, SG min/max not available
Driver 2: position 4096, standstill, reads 42150, writes 7 timeouts 0, SG min/max not available
Driver 3: position 0, short-to-ground, standstill, reads 42146, writes 11 timeouts 0, SG min/max 0/70
Driver 4: position 0, standstill, reads 42156, writes 0 timeouts 0, SG min/max not available
Driver 5: position 0, standstill, reads 42156, writes 0 timeouts 0, SG min/max not available
Date/time: 2021-04-11 11:41:00
Slowest loop: 23.13ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 20.9ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, maxWait 396543ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 17, completed moves 17, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], 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 -1 -1 -1 -1 -1 -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
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.
=== Network ===
Slowest loop: 2.27ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 2 of 8
- Ethernet -
State: active
Error counts: 0 0 1 0 0
Socket states: 5 2 2 2 2 0 0 0
=== CAN ===
Messages queued 1327, send timeouts 2986, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 48

M98 P"config.g"


11/04/2021, 11:40:14	M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Warning: the height map was loaded when the current Z=0 datum was not determined probing. This may result in a height offset.
Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 538C

Cheers

P

Phaedrux

Please contact your vendor and initiate a warranty exchange. Include a link to this thread as authorization.

akayoshi

@phaedrux Thank you phaedrux

akayoshi

@phaedrux
Hi phaedrux,

I contacted my reseller and they asked me to complete the following link https://docs.google.com/forms/d/e/1FAIpQLSdXpbRCNxUc2j_OePtuWdwyKPJ9VEg2Ohq_80f-VCZ4SCJJ9w/viewform (which I have now completed)

Is this something that needs to be processed on your end?

Cheers
P

Phaedrux

Nothing on my end personally no. Your reseller should take it from here.

akayoshi

@phaedrux
Hi Phaedrux, my reseller said they are awaiting your approval through that submitted google form. I provided them with this forum link, and they still said they needed duet3d’s approval. See below

————
Hi Paul,

yes - it should be ok. I think we still have them in stock.
just need to wait to hear from Duet

Kind regards,
Aurarum Team

If you like our products/service and if you don't mind we would appreciate your feedback on Facebook and Google
https://g.page/Aurarum/review?rc

——-

Create something “

Cheers

P

Phaedrux

Thanks for bringing that to our attention. We'll get that tightened up. Thanks for your patience.

Kevvv

@phaedrux
Hi, I think I have a similar problem, but in my case all the wires are ok. When printing the model, the printer resets more or less on the 4th or 5th layer. I made 15 tries with the same effect. My aim is that the code contained in the line "software reset code" is the same as in the case of my colleague. Could you please help me, I am trying to find out what is causing the whole week but to no avail.
Sorry for screen shot but i can't download m122 comand from console.... when i click "download txt or csv" nothing do.

config.g

Phaedrux

@kevvv Can I ask that you create a new thread for your issue?

You can also highlight, copy, and paste the text from the M122 report into the forum post.