Error: short-to-ground on driver 0

  • Hi,
    I´m currently setting up and testing my Duet Wifi board for my new printer setup.

    While starting with testing the motors one by one with the G91 followed by G1 S2 (...)10 F100, I get the message when checking the x-Driver/Motor

    Error: Short to ground on driver 0

    As this topic was already discussed in this forum several times I already checked the following ideas/solutions:

    1. Update the firmware to the latest status
    2. Check that there is no connection / shortage on the backside of the board (Board is hanging completely free currently)
    3. Checked a different motor and check the other drivers: All others are working properly
    4. Driver X (0) is also reporting the error when no motor is attached onto the board and the command is called
    5. It´s genuine board by the German reseller ""

    I already contacted the reseller with the issue but since a full week I do not get any feedback or result on how to go ahead or get a replacement.

    Maybe someone else has another idea to check but I guess the driver for the X-axis is broken/damaged?

    Thanks for responding!

  • Moderator

    @tobias3333 sorry you are having problems. Can you post your config.g? And send M115 then post the response. This will aid troubleshooting.


  • Hi Ian, no problem and thanks for the quick respond.

    The config file is attached and following is the M115 response.

    FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.05 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2019-12-13b1


  • Moderator

    @tobias3333 said in Error: short-to-ground on driver 0:


    Can you post the actual config.g from the sys directory? It's human readable and much easier to understand.

  • Moderator

    @tobias3333 Thanks for the info. The config.json is the output from the Firmware Config tool, and tells me a lot, but doesn't show how your machine is set up now. Ideally, we need to see the config.g file. If you can access the Duet through DWC, go to 'System', select 'config.g' from the file list, and copy the text from there into your reply post.

    Edit: @Phaedrux beats me to it, again!


  • Got it:

    ; Configuration file for Duet WiFi (firmware version 2.03)
    ; executed by the firmware on start-up
    ; generated by RepRapFirmware Configuration Tool v2.1.8 on Wed Feb 12 2020 19:41:41 GMT+0100 (Mitteleuropäische Normalzeit)

    ; General preferences
    G90 ; send absolute coordinates...
    M83 ; ...but relative extruder moves
    M550 P"CoreXY" ; set printer name

    M667 S1 ; select CoreXY mode

    ; Network
    M552 S1 ; enable network
    M586 P0 S1 ; enable HTTP
    M586 P1 S0 ; disable FTP
    M586 P2 S0 ; disable Telnet

    ; Drives
    M569 P0 S1 ; physical drive 0 goes forwards
    M569 P1 S1 ; physical drive 1 goes forwards
    M569 P2 S0 ; physical drive 2 goes backwards
    M569 P3 S0 ; physical drive 3 goes backwards
    M584 X0 Y1 Z2 E3 ; set drive mapping
    M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
    M92 X200.00 Y200.00 Z400.00 E418.00 ; set steps per mm
    M566 X720.00 Y720.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
    M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
    M201 X500.00 Y500.00 Z250.00 E1000.00 ; set accelerations (mm/s^2)
    M906 X1600 Y1600 Z1600 E1600 I30 ; set motor currents (mA) and motor idle factor in per cent
    M84 S30 ; Set idle timeout

    ; Axis Limits
    M208 X0 Y0 Z0 S1 ; set axis minima
    M208 X350 Y350 Z350 S0 ; set axis maxima

    ; Endstops
    M574 Z0 S0 ; set active low and disabled endstops
    M574 X1 Y1 S1 ; set active high endstops

    ; Z-Probe
    M558 P5 R0.4 H5 F1200 T6000 ; set Z probe type to effector and the dive height + speeds
    G31 P25 X28.5 Y-5 Z0 ; set Z probe trigger value, offset and trigger height
    M557 X15:285 Y15:285 S20 ; define mesh grid

    ; Heaters
    M305 P0 T100000 B4138 R4700 ; set thermistor + ADC parameters for heater 0
    M143 H0 S100 ; set temperature limit for heater 0 to 100C
    M305 P1 T100000 B4138 R4700 ; set thermistor + ADC parameters for heater 1
    M143 H1 S260 ; set temperature limit for heater 1 to 260C

    ; Fans
    M106 P0 S0 I0 F500 H-1 ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
    M106 P1 S1 I0 F500 H1 T45 ; set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
    M106 P2 S1 I0 F500 H1 T45 ; set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

    ; Tools
    M563 P0 D0 H1 F0 ; define tool 0
    G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
    G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C

    ; Custom settings are not defined

    ; Miscellaneous
    M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss

  • Moderator

    @tobias3333 Your config.g looks pretty standard, and I can't see anything obviously wrong. The X is configured the same as Y, which works. You are running in CoreXY mode, so it might be worth turning this off by commenting out the 'M667 S1 ; select CoreXY mode' with a semicolon ';' then testing the motor movement again. If X doesn't move and Y does, swap the motors and test again. Make sure you turn off power, or you can damage the stepper drivers by disconnecting/connecting motors when the driver is powered up. I think if this doesn't work, it's a damaged/failed/faulty driver chip.

    Let me know to confirm the above. If it's the chip, it's probably a warranty replacement. Sorry for the inconvenience.


  • @droftarts: I just check your suggestion and I have to reply that it is still the same result. On the Y-Side the motor is turning. Switching to the X-Side there is again the fault message with the shorted driver0

  • Moderator

    @tobias3333 okay. Is this a new Duet, or was it previously working? Where did you buy it, and when? If it’s a genuine Duet, bought from Duet3D or one of the resellers, and is within its warranty period, I’m happy to approve a warranty replacement. Contact your supplier, follow their warranty process, and refer them to this thread.

    If you could post a picture of your Duet, or at least post the information from the sticker on the main processor, that would help identify the manufacturing date and supplier. Thanks!

    As an aside, the only known causes of short-to-ground error reports are:

    1. Genuine short (to ground or across the motor)
    2. Motor phases not connected correctly
    3. On a Maestro, running in stealthChop mode at high speeds (probably possible with Duet 3 too)
    4. Failed driver
    5. Bad SPI signals (especially if ALL drivers report short-to-ground)


  • @droftarts: Thanks for the clear statement. The board was bought at the Duet´s suggested German supplier therefore it should be a genuine board?! I ordered it by the end of September 2019. Due to personel reasons there was no possibility for me to install the board since the last weeks.

    So the board wasn´t running within the printer already. I started with the step by step guide from the Dozuki site.
    When heading to the task to check the motors, the failure already appeared.

    I already contacted the support from Makerdise to solve the issue but since 10 days there is no further feedback on how to go ahead / or initate a replacement.
    Hopefully they will reply within the next days and give some feedback.

    Anyway beside the support problems thank you very much for your time and the great support!

  • Moderator

    @tobias3333 no problem, hopefully your warranty replacement will work better!

    If you could post a picture of your Duet, that would be great.

    M584 X0 Y1 Z2 E3 ; set drive mapping

    As you’re only using 4 of the 5 drivers, you could remap X to the spare one, while you wait for the replacement. Add this line after the other M569 commands:

    M569 P4 sS1 ; physical drive 4 goes forwards

    Change M584 to:

    M584 X4 Y1 Z2 E3                                   ; set drive mapping

    and connect X motor to E1 stepper driver.


  • @droftarts: The driver re-mapping seems to work for the moment.

    Replacement is still on-going.

    Attached a picture of the board as requested

Log in to reply