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

Oh oh! Bad news - Error: Short-to-ground on drivers 0

Scheduled Pinned Locked Moved
Duet Hardware and wiring
3
7
1.6k
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.
  • undefined
    nickpgre
    last edited by 21 Jan 2018, 17:23

    Hello everyone,

    Today, I installed (almost) my new DuetWifi, and accessing the Duet Web control for first time whilst being powered on a 24v power supply (350w) and got spammed with this warning:

    Warning: Error: Short-to-ground on drivers 0
    Warning: Error: Over temperature shutdown on drivers 0

    I've double checked and triple checked everything and all my wires are correct. As a matter of fact even without having anything connected to the drivers, (only power wire and heated bed) I still get this error.

    I also updated the firmware to 1.20.1
    M115
    FIRMWARE_NAME: RepRapFirmware for Duet WiFi FIRMWARE_VERSION: 1.20.1 ELECTRONICS: Duet WiFi 1.0 FIRMWARE_DATE: 2018-01-08

    Also did run diagnostics (M122) and got the following:

    And this the output I am receiving using the M112

    === Diagnostics ===
    Used output buffers: 3 of 32 (14 max)
    === Platform ===
    RepRapFirmware for Duet WiFi version 1.20.1 running on Duet WiFi 1.0
    Board ID: 08DGM-95BNL-MGPSJ-6J1FD-3S46T-KKY3X
    Static ram used: 15372
    Dynamic ram used: 98780
    Recycled dynamic ram: 536
    Stack ram used: 1336 current, 4260 maximum
    Never used ram: 12124
    Last reset 00:06:34 ago, cause: software
    Last software reset time unknown, reason: User, spinning module GCodes, available RAM 12124 bytes (slot 3)
    Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0441f000, 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 23.6, current 23.9, max 24.1
    Supply voltage: min 24.4, current 24.5, max 24.7, under voltage events: 0, over voltage events: 0
    Driver 0: temperature-shutdown! short-to-ground standstill, SG min/max not available
    Driver 1: standstill, SG min/max not available
    Driver 2: standstill, SG min/max not available
    Driver 3: standstill, SG min/max not available
    Driver 4: standstill, SG min/max not available
    Date/time: 2018-01-21 14:54:32
    Cache data hit count 2316986664
    Slowest main loop (seconds): 0.006525; fastest: 0.000108
    === Move ===
    MaxReps: 0, StepErrors: 0, LaErrors: 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 heaters = 0 -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 state is running
    WiFi module is connected to access point
    Failed messages: pending 0, notready 0, noresp 0
    WiFi firmware version 1.19
    WiFi MAC address a0:20:a6:2f:bf:f9
    WiFi Vcc 3.10, reset reason Turned on by main processor
    WiFi flash size 4194304, free heap 39560
    WiFi IP address 192.168.1.111
    WiFi signal strength -56dBm, reconnections 0, sleep mode unknown
    HTTP sessions: 1 of 8
    Socket states: 2 0 0 0 0 0 0 0
    Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
    Warning: Error: Short-to-ground on drivers 0
    Warning: Error: Over temperature shutdown on drivers 0

    Is there anything i might have missed and it is something that can be magically fixed?

    Thanks,
    Nick

    1 Reply Last reply Reply Quote 0
    • undefined
      dc42 administrators
      last edited by 21 Jan 2018, 19:01

      Sadly that suggests that the driver chip has failed. Please ask for your Duet to be repaired/replaced under warranty. See https://www.duet3d.com/warranty if you bought it direct from duet3d.

      Duet WiFi hardware designer and firmware engineer
      Please do not ask me for Duet support via PM or email, use the forum
      http://www.escher3d.com, https://miscsolutions.wordpress.com

      undefined 1 Reply Last reply 24 Apr 2018, 16:14 Reply Quote 0
      • undefined
        nickpgre
        last edited by 21 Jan 2018, 19:05

        Thanks, I'll do

        1 Reply Last reply Reply Quote 0
        • undefined
          audryhome @dc42
          last edited by 24 Apr 2018, 16:14

          @dc42

          When homing, I have an error "Short to ground on driver 1".
          If I run M122, I got the driver status : "short-to-ground standstill, SG min/max 0/0"

          If I invert drivers, I have the error on the other drive, this make me think it is related to the stepper, not the driver chip.

          I double checked for connection of this stepper, everything fine.

          This stepper is always disabled, either on drive 0 or drive 1.

          I don't have any undervoltage error on M122.

          Could it be the power supply?

          undefined 1 Reply Last reply 24 Apr 2018, 16:26 Reply Quote 0
          • undefined
            dc42 administrators @audryhome
            last edited by dc42 24 Apr 2018, 16:26

            @audryhome said in Oh oh! Bad news - Error: Short-to-ground on drivers 0:

            @dc42

            When homing, I have an error "Short to ground on driver 1".
            If I run M122, I got the driver status : "short-to-ground standstill, SG min/max 0/0"

            If I invert drivers, I have the error on the other drive, this make me think it is related to the stepper, not the driver chip.

            Please explain what you mean by that last sentence. Do you mean that the error moves to a different driver number if you plug that motor cable into a different driver output on the Duet? If so, that suggests a fault in the cabling or a short in the motor.

            Duet WiFi hardware designer and firmware engineer
            Please do not ask me for Duet support via PM or email, use the forum
            http://www.escher3d.com, https://miscsolutions.wordpress.com

            undefined 2 Replies Last reply 24 Apr 2018, 17:44 Reply Quote 0
            • undefined
              audryhome @dc42
              last edited by 24 Apr 2018, 17:44

              @dc42 Yes exactly, I have to consider changing the stepper and test again thanks.

              1 Reply Last reply Reply Quote 0
              • undefined
                audryhome @dc42
                last edited by 1 May 2018, 07:49

                @dc42 Changed the cable supplied with stepper (!) with another one and it works.
                thanks for your answer

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