Error: short-to-ground reported by driver(s) 0 1
-
After start to try my X and Y stepper motors I get this result.
11/23/2021, 11:39:40 AM G28
Error: short-to-ground reported by driver(s) 0 1
11/23/2021, 11:37:53 AM M122
=== Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later Board ID: 0JD0M-9P6B2-NJ4S8-6JKF2-3SD6T-KU76M Used output buffers: 3 of 24 (11 max) === RTOS === Static ram: 23876 Dynamic ram: 75208 of which 52 recycled Never used RAM 15280, free system stack 184 words Tasks: NETWORK(ready,13.8%,237) HEAT(delaying,0.0%,330) Move(notifyWait,0.1%,340) MAIN(running,85.6%,411) IDLE(ready,0.5%,29), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:02:54 ago, cause: software Last software reset at 2021-11-23 11:34, reason: User, GCodes spinning, available RAM 12248, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 Step timer max interval 0 MCU temperature: min 27.6, current 28.9, max 29.1 Supply voltage: min 23.8, current 24.1, max 24.4, 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 not available Driver 1: position 0, standstill, SG min/max not available Driver 2: position 0, standstill, SG min/max not available Driver 3: position 0, standstill, SG min/max not available Driver 4: position 0, standstill, SG min/max not available Driver 5: position 0 Driver 6: position 0 Driver 7: position 0 Driver 8: position 0 Driver 9: position 0 Driver 10: position 0 Driver 11: position 0 Date/time: 2021-11-23 11:37:51 Cache data hit count 4294967295 Slowest loop: 5.01ms; fastest: 0.17ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 3.3ms, 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 = 0 -1 -1 -1, chamberHeaters = -1 -1 -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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 15.56ms; fastest: 0.00ms Responder states: HTTP(2) 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 48:3f:da:a6:c4:9e WiFi Vcc 3.43, reset reason Power up WiFi flash size 2097152, free heap 23432 WiFi IP address 192.168.178.18 WiFi signal strength -49dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0
11/23/2021, 11:35:05 AM Connection establishedIs this a defect in a driver or something else?
-
@create-at-hwbdesign-com check your wiring
https://teamgloomy.github.io/short_to_ground.html -
@jay_s_uk , Thanks, all checked the motors work perfect trough the Z drivers.
The connections are perfectly soldered.
New wiring tested.
Thanks Jay, best Joep -
@create-at-hwbdesign-com please check that you have phased the stepper motor wiring correctly. See https://duet3d.dozuki.com/Wiki/Choosing_and_connecting_stepper_motors#Section_Connecting_stepper_motors.
-
@dc42 Hello,
Is there a difference in wiring for X and Y drivers? I tested the cable's by connecting them to the Z drivers, the work perfectly there? -
@create-at-hwbdesign-com the Z driver connectors on Duet 2 are connected in series. This means that if you had the phases incorrectly wired on both motors, they might work out correctly.
DO NOT just swap wires around, because connecting the motors incorrectly can blow the drivers. Check that you have one phase connected to the pins at one end of the connector and the other phase at the other end, as described at https://duet3d.dozuki.com/Wiki/Choosing_and_connecting_stepper_motors#Section_Identifying_the_stepper_motor_phases.
-
@dc42 Hello David, You where wright! Wrong cable set. Checked the phase and had to change the connections. Motors work fine now.
Thanks a lot for showing the correct connection work.
Best Joep -
-