Error: Short-to-ground on drivers 0 1 2 3 4 5 6 7 8 9



  • I'm encountering a new problem today for the first time. I haven't used my machine in a while, but after turning it on I am getting very strange behavior. I get the following errors:
    Error: Short-to-ground on drivers 0 1 2 3 4 5 6 7 8 9
    Error: Over temperature shutdown on drivers 0 1 2 3 4 5 6 7 8 9

    Oddly though, these errors change. Often it is only 1 or 2 drivers at a time, sometimes 4 or more. It updates with a new set of driver errors approximately every 6-10 seconds.

    I checked my supply voltage and it is consistent at 12.3 volts. I'm not sure what firmware version I have, but I'm guessing somewhere in the neighborhood of 1.18. I haven't tried updating because I am trying to figure out if the overheating is true or an error. I don't want to leave things running long.

    My z-axis motor is engaged and my extruder motor starts twitching after I turn the board on, but none of my other steppers power on. I have checked for debris and odd connections, but I haven't found anything yet. Did I short something and do permanent damage to the board?


  • administrators

    Here are some possibilities:

    • Bad power. After you get some of these errors, run M122 and check whether any under voltage events have been recorded.

    • Bad power to the DueX5. Check the feed to the VIN terminals of the DueX5.

    • Intermittent short circuit on the SPI data line from the stepper drivers. Check for metallic debris between the pins of the stepper drivers and between the pins of the main processor.

    • intermittent connection on the microcontroller pin that receives the SPI signal

    You could disconnect the ribbon cable to the DueX5, that would tell you which board the problem is on.



  • It is still happening after unplugging the extension board, but now only on drivers 1 and 2. No longer changing randomly. Power looks clean as reported by M122 and by my measurements. I'm still looking for debris, but no luck so far. Any tips for cleaning a board like this?

    M122
    === Diagnostics ===
    Used output buffers: 3 of 32 (9 max)
    === Platform ===
    RepRapFirmware for Duet Ethernet version 1.19 running on Duet Ethernet 1.0
    Board ID: 08DDM-9FAMU-JW4S4-6JKD8-3S06Q-T3WMT
    Static ram used: 17684
    Dynamic ram used: 95908
    Recycled dynamic ram: 1096
    Stack ram used: 1136 current, 4400 maximum
    Never used ram: 11984
    Last reset 00:01:50 ago, cause: power up
    Last software reset reason: User, spinning module GCodes, available RAM 11984 bytes (slot 4)
    Software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
    Error status: 0
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 0.0ms
    MCU temperature: min 32.6, current 41.7, max 41.9
    Supply voltage: min 12.3, current 12.4, max 12.5, under voltage events: 0, over voltage events: 0
    Driver 0: ok
    Driver 1: stalled temperature-shutdown! short-to-ground standstill
    Driver 2: stalled temperature-shutdown! short-to-ground standstill
    Driver 3: ok
    Driver 4: ok
    Date/time: 2018-02-14 10:15:21
    Slowest main loop (seconds): 0.607201; fastest: 0.000039
    === Move ===
    MaxReps: 0, StepErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
    Scheduled moves: 0, completed moves: 0
    Bed compensation in use: none
    Bed probe heights: 0.000 0.000 0.000 0.000 0.000
    === Heat ===
    Bed heater = 0, chamber heater = -1
    Heater 1 is on, I-accum = 0.0
    === 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 ===
    State: 5
    HTTP sessions: 1 of 8
    Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)



  • Actually, it looks like it is still changing. Typically drivers 1 and 2, but sometimes none, sometimes all 0-4.

    After running M122 again:

    RepRapFirmware for Duet Ethernet version 1.19 running on Duet Ethernet 1.0
    Board ID: 08DDM-9FAMU-JW4S4-6JKD8-3S06Q-T3WMT
    Static ram used: 17684
    Dynamic ram used: 95908
    Recycled dynamic ram: 1096
    Stack ram used: 1136 current, 4400 maximum
    Never used ram: 11984
    Last reset 00:07:13 ago, cause: power up
    Last software reset reason: User, spinning module GCodes, available RAM 11984 bytes (slot 4)
    Software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
    Error status: 0
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 0.0ms
    MCU temperature: min 41.5, current 47.1, max 47.2
    Supply voltage: min 12.3, current 12.4, max 12.4, under voltage events: 0, over voltage events: 0
    Driver 0: ok
    Driver 1: ok
    Driver 2: ok
    Driver 3: ok
    Driver 4: ok
    Date/time: 2018-02-14 10:20:44
    Slowest main loop (seconds): 0.004028; fastest: 0.000031


  • administrators

    If your Duet is under warranty, ask for it to be replaced. I suspect a bad solder joint on the microcontroller SPI1 input pin.



  • That's unfortunate. I'm not sure if any updated information will help, but I unplugged everything from the board except power. Driver 4 is getting hot to the touch, and driver 3 is warm. The others are not hot, despite the over temperature and short-to-ground warnings. I doubt it is under warranty at this point.


  • administrators

    Which country are you in?



  • USA. I believe I ordered it from Filastruder in April of last year, or thereabout.


  • administrators

    Forum user W3DRK is based in the US and does Duet repairs, so you might want to PM him.



  • Thanks for the contact. I'll try that.


Locked
 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.