Short to ground reported by driver
-
Hi - I am getting a “Short to ground reported by driver” error message - Wiring look all good and I can’t see any problem on the board (Duet 3 mini5+ Ethernet). All the wiring is set as per the instructions plus a 12v fan I wired to the always on 12v supply on the middle of the board. Got the message while configuring the endstop for driver 0 (mapped to the C axis in my machine) but I do not think this is the source of the problem. I am running the most recent firmware available.
My config.g file is below (in my installation I have the configuration separated in several files, I find easy to split code by themes; have compiled all in one file here)
; Configuration file for Duet mini5+
; M98 P"config-network.g"
; -----------------------------------------------------
; Network configuration executed by config.g; Configure Connection - ENABLE ONLY ONE OF THE BELOW THREE
;M552 S1 ; Enable Wifi Network
;M552 S2 ; Enable Access Point Mode
M552 S1 P192.168.2.1 ; Enable Ethernet - set IP Address to suit HP
M553 P255.255.255.0 ; Set Net mask; Network settings
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet; Set Network machine name
M550 P"CNC-Butterfield"; M98 P"config-drives.g"
; -----------------------------------------------------
; Drive configuration executed by config.g; Axes steppers directions, P refers to the driver and S refers to the direction (0=clockwise or 1=anticlockwise)
M569 P0 S0 ; Drive 0 axis x goes right, from origen
M569 P1 S1 ; Drive 1 axis y1 goes forwards
M569 P2 S0 ; Drive 2 axis z goes up
M569 P3 S1 ; Drive 3 axis y2 goes forwards; M98 P"config-axes.g"
; -----------------------------------------------------
; Axes configuration executed by config.g; drive mapping to axes
M584 X0 Y1:3 Z2 ; Apply mapping to axes
M584 P3 ; 3 is the number of axes;M584 X0 Y4 Z2 E3 ;remap driver Y to driver E1
;M569 P0 S1 ; Drive 0 goes forwards
;M569 P1 S1 ; Drive 1 goes forwards
;M569 P2 S0 ; Drive 2 goes forwards
;M569 P3 S1 ; Drive 3 goes forwards
;M569 P4 S1 ; Drive 3 goes forwards; sets motor currents (mA), set this to 80% max rated current - I is Idle factor 30%
M906 X2000 Y2000 Z2000 I400; sets the steps per mm axis travel
M92 X400 Y400 Z400 ; Set steps per mm; sets microstepping, 1 is full step, 16 is 1/16 step, I is microstep interpolation 1=Enable
M350 X16 Y16 Z16 I1; sets the maximum speed (mm/min) useful to prevent damage if axis aproach its limits
M203 X2500 Y2500 Z2500; sets accelerations (mm/s^2) - the higher the number the quicker the steppers get to their set speeds
M201 X150 Y150 Z150; sets the max instantaneous speed change (mm/min)
; optimise or machine could rattle itself apart or become too slow when cutting curves
M566 X500 Y500 Z500 ; Set maximum instantaneous speed changes;sets kinematics type and kinematics parameters, k 0 = Cartesian
M669 K0 X1:0:0:0 Y0:1:0:1 Z0:0:1:0; M98 P"config-axes-limits.g"
; -----------------------------------------------------
; Axes Limits configuration executed by config.gM208 X0 Y0 Z0 S1 ; 1 Set axis minima - xyz origen
M208 X500 Y600 Z90 S0 ; 0 Set axis maxima, positions assumed when an endstop is triggered; M98 P"config-axes-calibration.g"
; -----------------------------------------------------
; Axes Calibration configuration executed by config.gM92 X400 Y400 Z400 ; Set steps per mm
; M98 P"config-axes-endstops.g"
; -----------------------------------------------------
; Endstop configuration executed by config.g; sets position of endstop sensor on axis with 1 = low axis end
; S sets the endstop sensing type 0 = active low endstops
; M574 X2 Y2 Z2 S0
M574 X2 P"!io0.in" S1
M574 Y2 P"!io1.in" S1
M574 Z2 P"!io3.in" S1; Other Settings
; ------------------------------------------------------
M453 ; Put the machine into CNC Modes
G90 ; Set absolute coordinates
M140 H-1 ; Disable heated bed
M564 S1 H1 ; Disable jog commands when not homed
;M564 S1 H0 ; use for disabled jog commands
M911 S21.0 R23 P"G91 G1 Z3 F1000" ; Configure power loss resume; User Configuration files
; M98 P"config-user-settings.g"
; -------------------------------------------------------
; Additional user settings executed by config.gM564 S1 H0
M501 ; Load Stored Parameters
————————————————————-
Running M122 I got:M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus Ethernet (standalone mode)
Board ID: 9H0Q1-W396U-D65J0-40KM8-M313Z-HH9AB
Used output buffers: 3 of 40 (11 max)
=== RTOS ===
Static ram: 102724
Dynamic ram: 99760 of which 0 recycled
Never used RAM 41220, free system stack 200 words
Tasks: NETWORK(ready,27.0%,280) ETHERNET(notifyWait,0.1%,572) HEAT(delaying,0.0%,406) Move(notifyWait,0.1%,362) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.0%,332) TMC(delaying,0.7%,106) MAIN(running,71.3%,504) IDLE(ready,0.0%,29) AIN(delaying,0.8%,264), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 01:10:47 ago, cause: software
Last software reset at 2021-12-10 19:04, reason: User, GCodes spinning, available RAM 41220, slot 0
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 4248031, completed 4248030, timed out 0, errs 0
Step timer max interval 1487
MCU temperature: min 17.2, current 17.9, max 18.6
Supply voltage: min 23.9, current 24.0, max 24.0, 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 1, ifcnt 19, reads 26944, writes 9, timeouts 0, DMA errors 0
Driver 1: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 19, reads 26944, writes 9, timeouts 0, DMA errors 0
Driver 2: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 19, reads 26944, writes 9, timeouts 0, DMA errors 0
Driver 3: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 19, reads 26944, writes 9, timeouts 0, DMA errors 0
Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 19, reads 26944, writes 9, timeouts 0, DMA errors 0
Driver 5: position 0, assumed not present
Driver 6: position 0, assumed not present
Date/time: 2021-12-10 20:14:56
Cache data hit count 4294967295
Slowest loop: 5.95ms; fastest: 0.11ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.8ms, 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 = -1 -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 21240, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17), ts 21240/0/0
Tx timeouts 0,0,21239,0,0,0 last cancelled message type 30 dest 127=== Network ===
Slowest loop: 4.37ms; fastest: 0.03ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8- Ethernet -
State: active
Error counts: 0 0 0 0 0
Socket states: 5 2 2 2 2 0 0 0
Any ideas as to what might be the problem?
Cheers
Rafa - Ethernet -
-
@r-perezdominguez which driver is having the short to ground error? Do you get the error with no motor plugged in?
-
@t3p3tony It’s Driver 0, got the error with the motor plugged in. Twice got the error. Prior to that the motor was operating okay.
-
@t3p3tony Have done more tests - Essentially disconnected the motors from drivers 0 and 1 and switched the machine on. No errors showing without motors - next I powered all off and connected back the motors. After all was connected I switched all back on and now the motors spins normally and no errors. Axes all moving smoothly and apparently all is now as it was initially. Only difference is that I am now controlling the board via the same laptop but this time it is running on battery power only. Can’t understand - has anyone experienced something similar? I.e. an intermittent driver error
Cheers
R -
@r-perezdominguez said in Short to ground reported by driver:
Only difference is that I am now controlling the board via the same laptop but this time it is running on battery power only. Can’t understand - has anyone experienced something similar?
There would be potential for a USB ground loop.
https://duet3d.dozuki.com/Wiki/USB_ground_loops
It's also possible it was a bad crimp or connection at the motor?
-
@phaedrux All sorted now- likely to have been a bad connector. Many thanks for the help. R
-
undefined Phaedrux marked this topic as a question
-
undefined Phaedrux has marked this topic as solved
