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

    Error:short-to-ground/over temp shutdown reported by driver 2

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    3
    14
    834
    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.
    • UnderDoneSushiundefined
      UnderDoneSushi
      last edited by

      Hey everyone,

      I have an extra Duetwifi 2 (V1.02 board design) laying around that I have running firmware 2.03 (haven't taken the dive into 3.0 yet). I plugged it in and made a config for a COREXY printer I have been building and I am getting a constant from startup - Error:short-to-ground/over temp shutdown reported by driver 2.
      With or without steppers plugged in, tried multiple cables/steppers, drivers aren't getting hot.
      Is it potentially a coding issue like this other post? ----- https://forum.duet3d.com/topic/12953/driver-0-short-to-ground/8?_=1640877003699

      Here is my config.g and M122 report (which had no stepper motors plugged in when the gcode was sent).
      Is it possible to swap the jumpers on Drive 2? I would assume that wouldn't change anything since it is the driver itself that is having issues. Hoping it isn't a dead driver because this board has just been sitting unused for a couple of years now...

      Thanks

      ; Configuration file for Duet WiFi (firmware version 2.03)
      ; executed by the firmware on start-up
      ;
      ; generated by RepRapFirmware Configuration Tool v3.1.4 on Sat Aug 01 2020 17:18:06 GMT-0400 (Eastern Daylight Time)
      
      ; 0 - INDEX
      ; 1 - GENERAL PREFERENCES
      ; 2 - NETWORK
      ; 3 - DRIVES
      ; 4 - DRIVE SETTINGS
      ; 5 - AXIS LIMITS + ENDSTOPS + Z-PROBE
      ; 6 - HEATERS
      ; 7 - FANS
      ; 8 - TOOLS
      ; 9 - MISC
      
      ; FEEDRATE CONVERSIONS
      : Slow		10mm/s = F600 - 20mm/s = F1200 - 30mm/s = F1800
      ; Medium	40mm/s = F2400 - 50mm/s = F3000 - 60mm/s = F3600
      ; Fast		80mm/s = F4800 - 100mm/s = F6000 - 120mm/s = F7200
      
      ; 1 - GENERAL PREFERENCES ---------------------------------------------------------------------------------------------------
      M111 S0												; Debugging off
      G21													; Work in millimetres
      G90													; Send absolute coordinates...
      M83													; ...but relative extruder moves
      M555 P1												; Set firmware compatibility to look like RepRapFirmare
      M669 K1												; Select CoreXY mode
      
      ; 2 - NETWORK ---------------------------------------------------------------------------------------------------------------
      M550 P"X"									; Set machine name
      ;M551 P"X"										; Set password
      M552 S1                                  			; Enable network
      ;*** Access point is configured manually via M587
      M586 P0 S1                               			; Enable HTTP
      M586 P1 S0                               			; Disable FTP
      M586 P2 S0                               			; Disable Telnet
      
      ; 3.0 - DRIVES --------------------------------------------------------------------------------------------------------------
      M569 P0 S1											; Physical Drive 0 goes FORWARD (X_AXIS)
      M569 P1 S1											; Physical Drive 1 goes FORWARD (Y_AXIS)
      M569 P2 S1											; Physical Drive 2 goes FORWARD (Z_AXIS-1)
      M569 P3 S1											; Physical Drive 3 goes FORWARD (E_AXIS)
      M569 P4 S1											; Physical Drive 4 goes FORWARD (Z_AXIS-2)
      
      M584 X0 Y1 Z2:4 E1									; Two Z motors connected to driver outputs 2 and 4 (E1)
      M671 X20:380 Y200:200 S1 P2							; Z leadscrews are at (20,200), (380,200)
      
      ; 4 - DRIVE SETTINGS - TRAVEL SPEEDS + PRINT SPEEDS -----------------------------------------------------------------------
      M350 X16 Y16 Z16 E16 I1								; Configure microstepping with interpolation
      M92 X80.00 Y80.00 Z1600.00 E837.00					; Set steps per mm
      M566 X900.00 Y900.00 Z120.00 E120.00				; Set maximum instantaneous speed changes (mm/min)
      M203 X12000.00 Y12000.00 Z600.00 E1200.00			; Set maximum speeds (mm/min)
      M201 X800.00 Y800.00 Z100.00 E350.00				; Set accelerations (mm/s^2)
      M906 X800.00 Y800.00 Z800.00 E800.00 I30			; Set motor currents (mA) and motor idle factor in per cent
      M84 S30												; Set idle timeout
      
      ; 5 - AXIS LIMITS + ENDSTOPS + Z-PROBE --------------------------------------------------------------------------------------
      ;Axis limits
      M208 X0 Y0 Z0 S1									; Set axis minima
      M208 X400 Y400 Z600 S0								; Set axis maxima
      
      ;X/Y Endstops
      M574 X1 Y2 S1										; Set active high endstops
      
      ;Sensorless Homing
      ;M574 X1 S3 F0 R0									; Set active High endstops (S1=SENSORED) (X-MIN(1)) (S3=SENSORLESS)
      ;M574 Y0 S3 F0 R0									; Set active High endstops (S1=SENSORED) (Y-MIN(1)) (S3=SENSORLESS)
      ;M574 X1 Y1 S3										; Set endstops controlled by motor load detection
      ;M574 Z1 S2											; Use zprobe and home to min
      ;M915 X Y S7 R0 F0									; set X and Y to sensitivity 7, do nothing when stall, unfiltered
      
      ;Z-Probe --- IR PROBE
      M574 Z1 S2											; Set endstop controlled by probe
      M558 P1 H3 F120 T9000								; Set Z probe type to modulated and the dive height + speeds
      G31 P500 X0 Y13.5 Z1.00								; Set Z probe trigger value, offset and trigger height
      M557 X20:380 Y20:380 S95							; Define mesh grid
      
      ; 6 - HEATERS ---------------------------------------------------------------------------------------------------------------
      ;Heated Bed
      ;M307 H0 A46.7 C66.3 D4.5 B0 S1.00					; Disable bang-bang mode for the bed heater and set PWM limit
      M305 P0 T100000 B4092 R4700							; set thermistor + ADC parameters for heater 0
      M143 H0 S120										; set temperature limit for heater 0 to 120C
      
      ;Hotend
      ;M307 H1 A384.4 C190.7 D4.8 B0 S1.00				; Disable bang-bang mode for the bed heater and set PWM limit
      M305 P1 T100000 B4725 C7.060000e-8 R4700			; set thermistor + ADC parameters for heater 1
      M143 H1 S280										; set temperature limit for heater 1 to 280C
      
      ; 7 - FANS ------------------------------------------------------------------------------------------------------------------
      M106 P0 S1 I0 F500 H1 T45							; set fan 0 value, PWM signal inversion and frequency. (Hotend Fan) Thermostatic control. Turns on when hotend reaches 45c
      
      ;M106 P0 S0 I0 F500 H-1								; Set fan 0 (Part cooling blower) G-code controlled. Thermostatic control is turned off
      ;M106 P1 S1 I0 F500 H1 T45							; Set fan 1 (Hotend Fan) Thermostatic control. Turns on when hotend reaches 45c
      ;M106 P2 S0 I0 F500 H-1								; Set fan 2 (Duet Fan) G-code controlled. Thermostatic control is turned off
      
      ; 8 - TOOLS -----------------------------------------------------------------------------------------------------------------
      M563 P0 S"E3DV6 - 0.4mm" D0 H1						; 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
      
      ; Automatic saving after power loss is not enabled
      
      ; Custom settings are not configured
      
      ; 9 - Miscellaneous ---------------------------------------------------------------------------------------------------------
      M501 					 							; Load saved parameters from non-volatile memory
      ;T0													; Select first tool[/c]
      ;G29 S1												; Load the height map from the last time you used G29 to probe the bed.
      
      
      M122
      === Diagnostics ===
      RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later
      Board ID: 08DDM-9FAM2-LW4SD-6J9F6-3SN6M-12ZVY
      Used output buffers: 1 of 24 (17 max)
      === RTOS ===
      Static ram: 25712
      Dynamic ram: 93164 of which 392 recycled
      Exception stack ram used: 272
      Never used ram: 11532
      Tasks: NETWORK(ready,628) HEAT(blocked,1232) MAIN(running,3760) IDLE(ready,160)
      Owned mutexes:
      === Platform ===
      Last reset 00:06:58 ago, cause: power up
      Last software reset at 2021-12-30 12:10, reason: User, spinning module GCodes, available RAM 11552 bytes (slot 0)
      Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x04433000 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 25.6, current 25.6, max 26.0
      Supply voltage: min 24.1, current 24.2, max 24.4, 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-shutdown! 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: 2021-12-30 12:47:19
      Cache data hit count 1278367466
      Slowest loop: 2.04ms; fastest: 0.07ms
      I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
      === Move ===
      Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
      Bed compensation in use: none, comp offset 0.000
      === DDARing ===
      Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
      === 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 ===
      Slowest loop: 201.15ms; fastest: 0.08ms
      Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
      HTTP sessions: 2 of 8
      - WiFi -
      Network state is running
      WiFi module is connected to access point 
      Failed messages: pending 0, notready 0, noresp 2
      WiFi firmware version 1.23
      WiFi MAC address 60:01:94:34:3b:0a
      WiFi Vcc 3.40, reset reason Turned on by main processor
      WiFi flash size 4194304, free heap 22656
      WiFi IP address 192.168.1.63
      WiFi signal strength -54dBm, reconnections 0, sleep mode modem
      Socket states: 0 0 0 0 0 0 0 0
      
      Phaedruxundefined 1 Reply Last reply Reply Quote 0
      • Phaedruxundefined
        Phaedrux Moderator @UnderDoneSushi
        last edited by

        @underdonesushi said in Error:short-to-ground/over temp shutdown reported by driver 2:

        Is it possible to swap the jumpers on Drive 2?

        I'm not sure what you mean by this.

        On your Z axis driver port, the one with 2 ports together, do you have the jumpers installed on the second port?

        alt text

        Z-Bot CoreXY Build | Thingiverse Profile

        UnderDoneSushiundefined 1 Reply Last reply Reply Quote 0
        • UnderDoneSushiundefined
          UnderDoneSushi @Phaedrux
          last edited by UnderDoneSushi

          @Phaedrux I was wondering if I could switch the jumpers from the ZB to ZA. But that should solve my problem because it would still be running through Drive 2. For all of the testing I did for the error:short-to-ground, the jumpers were in option A single Z motor, and the second motor was set to run off Drive 4 E1. Hopefully that all makes sense.

          1 Reply Last reply Reply Quote 0
          • Phaedruxundefined
            Phaedrux Moderator
            last edited by

            Can you post photos of the Z driver area?

            Z-Bot CoreXY Build | Thingiverse Profile

            UnderDoneSushiundefined 1 Reply Last reply Reply Quote 0
            • UnderDoneSushiundefined
              UnderDoneSushi @Phaedrux
              last edited by UnderDoneSushi

              @phaedrux Let me know if you need some photos at different angles, I tried to get as close as possible to see the solder points. Is it crucial to mount the board with the plastic washers? I had it out of the case I had it mounted in and I still get the same driver reporting shorted. You can tell the board has been sitting unused with the dust haha. Is there someone in the US or Canada that does repairs?
              IMG_0798.jpg
              IMG_0797.jpg
              IMG_0796.jpg

              1 Reply Last reply Reply Quote 0
              • Phaedruxundefined
                Phaedrux Moderator
                last edited by

                I don't see any obvious damage.

                I think your options are to either disable the driver to silence the warning and use a single driver for the z axis by wiring the steppers up in series. Or adding an external driver. Or replacing the driver chip if that's something in your wheel house.

                You could also try contacting roland@duet3d.com to inquire about a possible discounted refurbished unit on exchange.

                Z-Bot CoreXY Build | Thingiverse Profile

                UnderDoneSushiundefined 1 Reply Last reply Reply Quote 0
                • UnderDoneSushiundefined
                  UnderDoneSushi @Phaedrux
                  last edited by

                  @phaedrux If I wired the Z motors in series though I wouldn't be able to control bed leveling correct? What would be the cheapest way to add an external driver? I personally don't have the skills to repair/solder that small but would be up for getting it repaired. I messaged two of the USA based people that were on the community repair post. I will email Roland now and see what he says. Thanks for the help!

                  Phaedruxundefined 1 Reply Last reply Reply Quote 0
                  • Phaedruxundefined
                    Phaedrux Moderator @UnderDoneSushi
                    last edited by Phaedrux

                    @underdonesushi said in Error:short-to-ground/over temp shutdown reported by driver 2:

                    If I wired the Z motors in series though I wouldn't be able to control bed leveling correct?

                    That's right, independent motor control would not work.

                    Take a look here for adding an external driver.
                    https://duet3d.dozuki.com/Wiki/Using_external_stepper_motor_drivers

                    Z-Bot CoreXY Build | Thingiverse Profile

                    UnderDoneSushiundefined 1 Reply Last reply Reply Quote 0
                    • UnderDoneSushiundefined
                      UnderDoneSushi @Phaedrux
                      last edited by

                      @phaedrux Dang didn't really want to spend another $100, yeah I might do the exchange when Roland gets back to my email. Would a Maestro expansion board work as well? Or would the pin setup not work with the Duetwifi2 - V1.02.
                      https://www.filastruder.com/collections/electronics/products/duet-maestro-expansion-board

                      Phaedruxundefined 1 Reply Last reply Reply Quote 0
                      • Phaedruxundefined
                        Phaedrux Moderator @UnderDoneSushi
                        last edited by

                        @underdonesushi said in Error:short-to-ground/over temp shutdown reported by driver 2:

                        Dang didn't really want to spend another $100

                        Do you mean for adding a Duex? That's not the only option. You can use a Pololu or stepstick style driver as well connected to the expansion header pins.

                        There's also the expansion breakout board that makes it a bit easier without requiring a full Duex.

                        https://duet3d.dozuki.com/Wiki/Duet_Expansion_Breakout_Board

                        Z-Bot CoreXY Build | Thingiverse Profile

                        UnderDoneSushiundefined 1 Reply Last reply Reply Quote 0
                        • UnderDoneSushiundefined
                          UnderDoneSushi @Phaedrux
                          last edited by

                          @phaedrux Okay that would be a much easier pill to swallow. Does the driver need to match the ones on the board or can it be a newer TMC driver? Unfortunately it looks like single stepsticks are harder to come by on amazon. Any other sources for a TMC stepstick? Thanks again for the help as usual Phaedrux.

                          Stephen6309undefined 1 Reply Last reply Reply Quote 0
                          • Stephen6309undefined
                            Stephen6309 @UnderDoneSushi
                            last edited by Stephen6309

                            @underdonesushi Filastruder has singles: https://www.filastruder.com/products/silentstepstick-tmc2209-stepper-motor-driver

                            UnderDoneSushiundefined 1 Reply Last reply Reply Quote 0
                            • UnderDoneSushiundefined
                              UnderDoneSushi @Stephen6309
                              last edited by

                              @stephen6309 Thanks, I hadn't realized filastruder had them. I assume they don't need to match the other drivers that are on the DuetWifi 2.

                              Phaedruxundefined 1 Reply Last reply Reply Quote 0
                              • Phaedruxundefined
                                Phaedrux Moderator @UnderDoneSushi
                                last edited by

                                @underdonesushi said in Error:short-to-ground/over temp shutdown reported by driver 2:

                                I assume they don't need to match the other drivers that are on the DuetWifi 2.

                                correct

                                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