Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

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

    Scheduled Pinned Locked Moved Solved
    Duet Hardware and wiring
    2
    3
    109
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Sharousundefined
      Sharous
      last edited by

      Been building the RatRig Core v3 kit, pretty much finished with everything: successful offset calibration; mesh compensation; pid tuning of hotend and bed; everything else works except the extruder which is on Driver 5 (extension board).

      I get the error by trying to initiate extrude/retract command: Error: short-to-ground reported by driver(s) 5

      Triple checked the wiring, everything seems to be in the correct places.

      Did I miss something?

      Duet 3 Mini 5+ with dual stepper expansion board.

      *Error: short-to-ground reported by driver(s) 5
      12/8/2021, 2:03:43 PM m122
      === Diagnostics ===
      RepRapFirmware for Duet 3 Mini 5+ version 3.2.2 running on Duet 3 Mini5plus WiFi (standalone mode)
      Board ID: G2SXS-Y296U-D65J0-40KM0-2313Z-RX229
      Used output buffers: 3 of 40 (11 max)
      === RTOS ===
      Static ram: 98732
      Dynamic ram: 107976 of which 52 recycled
      Never used RAM 38456, free system stack 120 words
      Tasks: NETWORK(ready,198) HEAT(blocked,315) CanReceiv(blocked,947) CanSender(blocked,358) CanClock(blocked,363) TMC(blocked,106) MAIN(running,402) IDLE(ready,20) AIN(blocked,264)
      Owned mutexes: WiFi(NETWORK)
      === Platform ===
      Last reset 00:05:27 ago, cause: power up
      Last software reset at 2021-12-08 13:18, reason: User, GCodes spinning, available RAM 38664, slot 1
      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
      Aux1 errors 0,0,0
      Supply voltage: min 0.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
      Driver 0: position 32000, standstill, SG min/max 0/14, read errors 0, write errors 0, ifcnt 13, reads 65284, writes 13, timeouts 34, DMA errors 0, failedOp 0x41
      Driver 1: position 0, standstill, SG min/max 0/22, read errors 0, write errors 0, ifcnt 13, reads 65249, writes 13, timeouts 69, DMA errors 0, failedOp 0x71
      Driver 2: position 8719, standstill, SG min/max 0/14, read errors 0, write errors 0, ifcnt 13, reads 65294, writes 13, timeouts 24, DMA errors 0, failedOp 0x72
      Driver 3: position 0, standstill, SG min/max 0/20, read errors 0, write errors 0, ifcnt 13, reads 65166, writes 13, timeouts 151, DMA errors 0, failedOp 0x6a
      Driver 4: position 0, standstill, SG min/max 0/2, read errors 0, write errors 0, ifcnt 13, reads 65318, writes 13, timeouts 0, DMA errors 0
      Driver 5: position 0, short-to-ground, standstill, SG min/max 0/4, read errors 0, write errors 0, ifcnt 13, reads 65318, writes 13, timeouts 0, DMA errors 0
      Driver 6: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 65322, writes 9, timeouts 0, DMA errors 0
      Date/time: 2021-12-08 14:03:42
      Cache data hit count 661292756
      Slowest loop: 17.41ms; fastest: 0.12ms
      === Storage ===
      Free file entries: 10
      SD card 0 detected, interface speed: 22.5MBytes/sec
      SD card longest read time 3.9ms, write time 0.0ms, max retries 0
      === Move ===
      DMs created 83, maxWait 158409ms, bed compensation in use: mesh, comp offset -0.044
      === MainDDARing ===
      Scheduled moves 16, completed moves 16, 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, chamberHeaters = -1 -1
      Heater 1 is on, I-accum = 0.8
      === 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: 14.65ms; 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.25
        WiFi MAC address d8:bf:c0:14:e9:9f
        WiFi Vcc 3.36, reset reason Power up
        WiFi flash size 2097152, free heap 23680
        WiFi IP address 192.168.1.91
        WiFi signal strength -65dBm, mode 802.11n, reconnections 0, sleep mode modem
        Clock register 00002002
        Socket states: 0 0 0 0 0 0 0 0
        === CAN ===
        Messages queued 2950, send timeouts 2947, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 16*
      1 Reply Last reply Reply Quote 0
      • Sharousundefined
        Sharous
        last edited by

        False alarm. The fact that E3D Hemera stepper motor has a bit different pairing than usual Nema 17 motors lead to the error. Simply switching wires to have correct pairs solved the problem.

        1 Reply Last reply Reply Quote 0
        • Phaedruxundefined Phaedrux marked this topic as a question
        • Phaedruxundefined Phaedrux has marked this topic as solved
        • Phaedruxundefined
          Phaedrux Moderator
          last edited by

          Always a good idea to test and identify the motor phases before connecting them as there are no standards or color codings. Even the motor spec sheets can be incorrect.

          https://duet3d.dozuki.com/Wiki/Choosing_and_connecting_stepper_motors#Section_Identifying_the_stepper_motor_phases

          Z-Bot CoreXY Build | Thingiverse Profile

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Unless otherwise noted, all forum content is licensed under CC-BY-SA