Short to ground on driver 2



  • Hello,

    I picked up a Duet 2 Ethernet for my build and it was working fine for the first few minutes of running the steppers.

    When testing my z-axis I started to get Short to Ground on driver 2 errors after it running fine for a while. I checked my wiring and tried different known good cables but still the same error. I also tried the driver on different steppers (also known good) and still got the same error. Both the wires and the steppers work on the other drivers.

    The board was also kept in a printed box and I made sure there was no way there could have been a short caused by a rouge screw or something.

    Any help would be MUCH appreciated.
    Thank you!



  • Sounds like a driver has failed unfortunately. Posting the full output of M122 might help the duet people diagnose

    It could be just one of those things, but I'd examine the wiring and motor in question for potential flaws in insulation or loose strands of wire that could cause a short.



  • Wires and steppers have been cleared as good but I'll test again tonight for my own sanity.

    I'll post the M122 output when I can get to the printer.



  • Here's what my output looks like after another test. Still no movement.

    I also cam confirm that the driver got very hot during this test.

    9:38:37 AMError: short-to-ground reported by driver(s) 2
    Warning: high temperature reported by driver(s) 2
    9:38:33 AMError: short-to-ground reported by driver(s) 2
    Warning: high temperature reported by driver(s) 2
    9:38:28 AMError: short-to-ground reported by driver(s) 2
    Warning: high temperature reported by driver(s) 2
    9:38:24 AMError: short-to-ground reported by driver(s) 2
    Warning: high temperature reported by driver(s) 2
    9:38:19 AMError: short-to-ground reported by driver(s) 2
    Warning: high temperature reported by driver(s) 2
    9:38:15 AMError: short-to-ground reported by driver(s) 2
    Warning: high temperature reported by driver(s) 2
    9:38:13 AMM122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet Ethernet 1.02 or later
    Board ID: 08DLM-996RU-N8PS4-7JKD6-3S06R-TABHP
    Used output buffers: 1 of 24 (16 max)
    === RTOS ===
    Static ram: 25680
    Dynamic ram: 93220 of which 0 recycled
    Exception stack ram used: 348
    Never used ram: 11824
    Tasks: NETWORK(ready,648) HEAT(blocked,1188) MAIN(running,3744) IDLE(ready,160)
    Owned mutexes:
    === Platform ===
    Last reset 00:03:44 ago, cause: power up
    Last software reset at 2020-08-15 18:48, reason: User, spinning module GCodes, available RAM 11824 bytes (slot 3)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    Error status: 0
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 0.0ms, max retries 0
    MCU temperature: min 27.1, current 27.6, max 27.6
    Supply voltage: min 24.2, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
    Driver 0: standstill, SG min/max not available
    Driver 1: standstill, SG min/max not available
    Driver 2: temperature-warning short-to-ground standstill, SG min/max not available
    Driver 3: standstill, SG min/max not available
    Driver 4: standstill, SG min/max not available
    Date/time: 2020-08-19 09:38:13
    Cache data hit count 571417917
    Slowest loop: 1.11ms; fastest: 0.08ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
    === Move ===
    Hiccups: 0, FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
    Bed compensation in use: none, comp offset 0.000
    === DDARing ===
    Scheduled moves: 6, completed moves: 6, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
    === Heat ===
    Bed heaters = -1 -1 -1 -1, chamberHeaters = -1 -1
    === GCodes ===
    Segments left: 0
    Stack records: 1 allocated, 0 in use
    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
    serial is idle in state(s) 0
    aux is idle in state(s) 0
    daemon is idle in state(s) 0
    queue is idle in state(s) 0
    autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Slowest loop: 4.02ms; fastest: 0.03ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 1 of 8
    Interface state 5, link 100Mbps full duplex
    9:38:10 AMError: short-to-ground reported by driver(s) 2
    Warning: high temperature reported by driver(s) 2
    9:38:06 AMError: short-to-ground reported by driver(s) 2
    Warning: high temperature reported by driver(s) 2
    9:38:01 AMError: short-to-ground reported by driver(s) 2
    Warning: high temperature reported by driver(s) 2


  • Moderator

    @RincewindBoi This does sound like a failed driver. Is the board under 6 months old? Where did you buy it? If it's a genuine Duet3D board bought through an authorised reseller, I authorise a warranty replacement. Follow the vendors warranty process, and use this thread as a warranty authorisation.

    For reference, this is our warranty: https://www.duet3d.com/warranty

    If it's a clone board, then it's up to whoever you bought it from as to whether they'll replace it. If you're not using one of the other drivers on the board, you could connect the Z motor(s) to that, and remap the axes with M584.

    Ian



  • It's genuine from Printed Solid and only a month old.
    Thank you


Log in to reply