Duet 3 Mini 5+ Error: short-to-ground reported by driver(s)
-
I have been running a Two Trees Sapphire Pus (CoreXY) printer with a Duet WiFi Clone for 6 months without any issues.
I just upgraded to a Duet Mini 5+ with a toolboard. Swapped boards and removed all the unnecessary hotend wiring. So the stepper motor wiring is not modified in any way.
I can not run my x/y motors above 500 mA. It starts to resonate very badly and display errors:
Error: short-to-ground reported by driver(s) 3
Error: over temperature shutdown reported by driver(s) 1
Warning: high temperature reported by driver(s) 1 3Driver 1 and 3 are my X / Y motors.
I also have not managed to get the sensor less homing to work reliable again.
At 500 mA it runs smoothly and quiet and prints ok, if it was not for loosing steps sometimes. So I need to use higher current ( I assume).
What could be wrong?
Faulty board?
Incorrect configuration? (I also moved from firmware 2 -> 3 and may have missed something)/fotomas
config.g
; Configuration file for Duet 3 Mini 5+ (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Mon Jul 05 2021 16:50:46 GMT+0200 (Central European Summer Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M669 K1 ; select CoreXY mode ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; X/Y Drives M569 P0.1 S1 V50 ; physical drive 0.1 M569 P0.3 S0 V50 ; physical drive 0.3 M584 X0.1 Y0.3 ; set drive mapping ; Z Drives M569 P0.0 S0 ; physical drive 0.0 M569 P0.4 S0 ; physical drive 0.4 M584 Z0.0:0.4 ; set drive mapping M671 X-12:323 Y150:150 S10.0 ; bedtild probe positions ; Extruder drive M569 P121.0 S0 ; physical drive 121.0 Extruder M584 E121.0 ; set drive mapping M92 X80 Y80 Z400.00 E420.00 ; set steps per mm M350 X128 Y128 Z256 E64 I1 ; microstepping M566 X350.00 Y350.00 Z120.00 E600.0 ; set jerk (maximum instantaneous speed changes (mm/min)) M203 X30000.00 Y30000.00 Z250.00 E1200.00 ; set maximum speeds (mm/min) M201 X300.00 Y300.00 Z500.00 E350.00 ; set accelerations (mm/s^2) DEFAULT 500 M906 X800 Y800 Z700 E800 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout M915 X Y R0 F0 S2 ; motor stall detection S = Detection sensitivity ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X290 Y290 Z290 S0 ; set axis maxim ; Endstops M574 X1 Y1 S3 ; set endstops controlled by motor stall detection ; Z-Probe M950 S0 C"^121.io0.out" ; create servo pin 0 for BLTouch M558 P9 C"^121.io0.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X0 Y-40 Z1.75 ; set Z probe trigger value, offset and trigger height M557 X5:280 Y5:280 S15 ; define mesh grid ; Heaters ;Bed M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"out0" T0 ; create bed heater output on out0 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 ;Hotend M308 S1 P"121.temp0" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin 121.temp0 M950 H1 C"121.out0" T1 ; create nozzle heater output on 121.out0 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"121.out2" Q500 ; create fan 0 on pin 121.out2 and set its frequency M106 P0 S0 H1 T45 ; set fan 0 value. Thermostatic control is turned on M950 F1 C"121.out1" Q25 ; create fan 1 on pin 121.out1 and set its frequency M106 P1 S0 H-1 ; set fan 1 value. Thermostatic control is turned off ; Tools M563 P0 D0 H1 F0 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C ; Accelerometer M955 P121.0 I16 R12 ; Custom settings are not defined ; Miscellaneous M575 P1 S1 B57600 ; enable support for PanelDue; 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 T0 ; select first tool homeall.g
; homeall.g ; called to home all axes M400 M913 X18 Y18 ; drop motor current ;M906 X176 Y176 M400 G91; relative positioning G1 H2 Z5 F4000 ; lower Z relative to current position G1 H1 X-320 F6000 ; move quickly to Y axis endstop and stop G1 X60 M400 G1 H1 Y-320 F6000 ; move quickly to Y axis endstop and stop G90 ; absolute positioning M400 M913 X100 Y100 ;M906 X800 Y800 G1 X162 Y150 F6000 ; go to first probe point G30 ; home Z by probing the bed G29 S1 **undefined** -
@fotomas said in Duet 3 Mini 5+ Error: short-to-ground reported by driver(s):
M569 P0.1 S1 V50 ; physical drive 0.1 M569 P0.3 S0 V50 ; physical drive 0.3
Do you get the same if you run in spreadcycle the entire time?
Have you tried running x16 microsteps across the board yet?
What firmware version are you running? Should be 3.3.
What PSU voltage?
Can you share the results of M122 and M98 P"config.g"?
-
With spreadcycle all the time, D2 as in for eg. M569 P0.1 S1 D2
homing just makes it stand still and buzz. I hope I have understood M569 correctly.x16 microstepping (D2 removed and V50 back) makes things better, but the resonance increases as it picks up speed until it detects a false sensor less endstopp. It is like some kind of vibration that counteracts the movement.
Video of homing @ 500 mA https://youtu.be/Kg_PY0-1OhE (works fine)
Video of homing @ 800 mA https://youtu.be/myc5rtT7meU (problems...)
Firmware
M115 FIRMWARE_NAME: RepRapFirmware for Duet 3 Mini 5+ FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet 3 Mini5plus WiFi FIRMWARE_DATE: 2021-06-15 21:46:20 PSU voltage ~24.5
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: DL70G-S396U-D65J0-40KMW-2303Z-HP9WR Used output buffers: 3 of 40 (25 max) === RTOS === Static ram: 102724 Dynamic ram: 106072 of which 60 recycled Never used RAM 34848, free system stack 136 words Tasks: NETWORK(ready,16.2%,258) HEAT(delaying,0.0%,373) Move(notifyWait,0.1%,305) CanReceiv(notifyWait,0.0%,798) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.0%,347) TMC(notifyWait,0.7%,115) MAIN(running,82.1%,426) IDLE(ready,0.1%,29) AIN(delaying,0.8%,264), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:03:16 ago, cause: software Last software reset at 2021-07-12 09:11, reason: User, GCodes spinning, available RAM 34848, 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 Aux0 errors 0,0,0 MCU revision 3, ADC conversions started 196361, completed 196360, timed out 0, errs 0 Step timer max interval 752 MCU temperature: min 25.3, current 26.4, max 27.1 Supply voltage: min 24.2, current 24.6, max 24.8, 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 24960, standstill, SG min/max 0/4, read errors 0, write errors 1, ifcnt 35, reads 10306, writes 12, timeouts 0, DMA errors 0 Driver 1: position 960, short-to-ground, standstill, SG min/max 2/336, read errors 0, write errors 1, ifcnt 40, reads 10304, writes 14, timeouts 0, DMA errors 0 Driver 2: position 2700, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 29, reads 10308, writes 9, timeouts 0, DMA errors 0 Driver 3: position 0, short-to-ground, standstill, SG min/max 2/340, read errors 0, write errors 1, ifcnt 39, reads 10303, writes 14, timeouts 0, DMA errors 0 Driver 4: position 0, standstill, SG min/max 0/2, read errors 0, write errors 1, ifcnt 35, reads 10306, writes 12, timeouts 0, DMA errors 0 Driver 5: position 0, assumed not present Driver 6: position 0, assumed not present Date/time: 2021-07-12 09:15:11 Cache data hit count 371153997 Slowest loop: 7.32ms; fastest: 0.10ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 3.2ms, write time 0.0ms, max retries 0 === Move === DMs created 83, maxWait 23259ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 7, completed moves 7, 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 = 0 -1, chamberHeaters = -1 -1 Heater 1 is on, I-accum = 0.0 === 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 1795, received 2380, lost 0, longest wait 2ms for reply type 6031, peak Tx sync delay 177, free buffers 17 (min 16), ts 982/981/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 10.80ms; 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:ef:4b WiFi Vcc 3.41, reset reason Power up WiFi flash size 2097152, free heap 26664 WiFi IP address 192.168.0.117 WiFi signal strength -51dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 M98 P"config.g" HTTP is enabled on port 80 FTP is disabled TELNET is disabled Accelerometer 121:0 with orientation 16 samples at 1344Hz with 12-bit resolution Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 827C -
What are the specs of the motors? Do they have high back emf by chance?
Also take a look at this page.
-
Check your motor winding specs on the manufacturer page. I had the same problem. Bought LDO steppers but the harness came from somewhere else. I just released the pins from the plug on the stepper side and reconfigured them correctly according to the manufacturers diagram.
-
@tony449777 If your experience should apply in thiss case the pin out for the stepper motors has to differ between the duet WiFi and the mini 5. Which I highly doubt.
(Away from printer will investigate more when I get hold of stepper motor model no)
-
@fotomas It wasn’t the pin out of the driver that was wrong. It was how the output of the driver was actually connected to the coils of the motor. They were physically in the motor plug in the wrong configuration.
-
@tony449777 said in Duet 3 Mini 5+ Error: short-to-ground reported by driver(s):
@fotomas It wasn’t the pin out of the driver that was wrong. It was how the output of the driver was actually connected to the coils of the motor. They were physically in the motor plug in the wrong configuration.
This is a common issue because different manufacturers of stepper motors use different pinouts. When using motors with a built-in socket and separate cable, ALWAYS check the phases.
-
@dc42 Exactly. That’s what I’m trying to say,
-
@tony449777 said in Duet 3 Mini 5+ Error: short-to-ground reported by driver(s):
Check your motor winding specs on the manufacturer page. I had the same problem. Bought LDO steppers but the harness came from somewhere else. I just released the pins from the plug on the stepper side and reconfigured them correctly according to the manufacturers diagram.
If this were the case here and the phases not paired correctly there would be no movement at all, but if you want the videos it's clear there is motion, but at a certain speed there is a lot of vibration and noise.
-
I got things working.
I checked wiring, everything was ok (as exprected since wiring was not modified since working ok on a Duet Wifi)
I increased the acceleration (M201) on X/Y from 300 to 800 this made it possible to increase the motor currents on X/Y to 800.
As an effect of this I had to tweak the sensorless homing to use less current.
So increased acceleration seems to be the solution, the problem may still be there but pushed out of bounds for my usage/speeds by increased acceleration.
I do not understand how increased acceleration have effected things. Maybe someone can explain this? It would be nice to know if I run into more trouble.
-
That's an interesting result. I don't understand why higher acceleration would solve it either. You've made the motor/stepper combo happy at least.