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

    Help with a Short to Ground that is occurring

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    3
    12
    343
    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.
    • abindarraez1undefined
      abindarraez1
      last edited by

      Hi, I just bought a Duet 5 mini + Ethernet. Then a Ground to Short occurred so I asked for a board change and got it again. I really don't want to have to send this board back as well. So I connected it and tried to move it, but a ground-to-short error occurred again. I just checked each motor and the Mechanism (The printer is a delta) moved with a simple DRV8825. Is there some config I am missing?
      The current is .850 Amps.
      Also, please indicate to me if I should change the driver. I will buy the spare and get it soldered here.
      Thanks

      abindarraez1undefined 1 Reply Last reply Reply Quote 0
      • abindarraez1undefined
        abindarraez1 @abindarraez1
        last edited by

        M122
        === Diagnostics ===
        RepRapFirmware for Duet 3 Mini 5+ version 3.3RC2 (2021-05-11 14:55:40) running on Duet 3 Mini5plus Ethernet (standalone mode)
        Board ID: K9SWG-7196U-D65J0-40KMA-LF03Z-ZGA27
        Used output buffers: 3 of 40 (11 max)
        === RTOS ===
        Static ram: 102476
        Dynamic ram: 99828 of which 60 recycled
        Never used RAM 41340, free system stack 196 words
        Tasks: NETWORK(ready,25.4%,220) ETHERNET(notifyWait,0.1%,568) HEAT(notifyWait,0.0%,338) Move(notifyWait,0.1%,362) CanReceiv(notifyWait,0.0%,943) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.0%,341) TMC(notifyWait,0.6%,115) MAIN(running,69.9%,353) IDLE(ready,3.1%,29) AIN(delaying,0.9%,274), total 100.0%
        Owned mutexes:
        === Platform ===
        Last reset 00:00:04 ago, cause: software
        Last software reset at 2023-03-30 11:57, reason: User, GCodes spinning, available RAM 41340, slot 2
        Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
        Error status: 0x00
        Aux0 errors 0,0,0
        Aux1 errors 0,0,0
        MCU revision 3, ADC conversions started 4517, completed 4517, timed out 0, errs 0
        Step timer max interval 736
        MCU temperature: min 30.8, current 31.5, max 31.5
        Supply voltage: min 23.8, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
        Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
        Driver 0: position 55034, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 29, reads 204, writes 9, timeouts 0, DMA errors 0
        Driver 1: position 55034, standstill, SG min/max 2/2, read errors 0, write errors 1, ifcnt 31, reads 204, writes 9, timeouts 0, DMA errors 0
        Driver 2: position 55034, standstill, SG min/max 270/270, read errors 0, write errors 1, ifcnt 31, reads 204, writes 9, timeouts 0, DMA errors 0
        Driver 3: position 0, standstill, SG min/max 2/2, read errors 0, write errors 1, ifcnt 31, reads 204, writes 9, timeouts 0, DMA errors 0
        Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 29, reads 204, writes 9, timeouts 0, DMA errors 0
        Driver 5: position 0, assumed not present
        Driver 6: position 0, assumed not present
        Date/time: 2023-03-30 11:57:20
        Cache data hit count 7231248
        Slowest loop: 11.20ms; fastest: 0.12ms
        === Storage ===
        Free file entries: 10
        SD card 0 detected, interface speed: 22.5MBytes/sec
        SD card longest read time 3.2ms, write time 0.0ms, max retries 0
        === Move ===
        DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
        === MainDDARing ===
        Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
        === AuxDDARing ===
        Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
        === Heat ===
        Bed heaters = 0 -1, chamberHeaters = -1 -1
        === GCodes ===
        Segments left: 0
        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
        USB is idle in state(s) 0
        Aux is idle in state(s) 0
        Trigger is idle in state(s) 0
        Queue is idle in state(s) 0
        LCD is idle in state(s) 0
        SBC is idle in state(s) 0
        Daemon is idle in state(s) 0
        Aux2 is idle in state(s) 0
        Autopause is idle in state(s) 0
        Code queue is empty.
        === CAN ===
        Messages queued 38, send timeouts 36, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17)
        Last cancelled message type 30 dest 127
        === Network ===
        Slowest loop: 3.83ms; fastest: 0.03ms
        Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
        HTTP sessions: 1 of 8

        • Ethernet -
          State: active
          Error counts: 0 0 0 0 0
          Socket states: 5 2 2 2 2 0 0 0
        jay_s_ukundefined 1 Reply Last reply Reply Quote 0
        • jay_s_ukundefined
          jay_s_uk @abindarraez1
          last edited by

          @abindarraez1 which driver is reporting a short to ground?

          Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

          abindarraez1undefined 1 Reply Last reply Reply Quote 0
          • abindarraez1undefined
            abindarraez1 @jay_s_uk
            last edited by

            @jay_s_uk 1Generally Driver 1. It also sends me a high temp alert.
            Driver 2 also sends me an error.

            jay_s_ukundefined 1 Reply Last reply Reply Quote 0
            • jay_s_ukundefined
              jay_s_uk @abindarraez1
              last edited by

              @abindarraez1 if you swap the motor on driver 1 with say driver 0, does it report the error?

              Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

              abindarraez1undefined 2 Replies Last reply Reply Quote 0
              • abindarraez1undefined
                abindarraez1 @jay_s_uk
                last edited by

                @jay_s_uk I am worried it might burn that driver as well
                But I will try it.

                1 Reply Last reply Reply Quote 0
                • abindarraez1undefined
                  abindarraez1 @jay_s_uk
                  last edited by

                  @jay_s_uk Error moved. Now it is on driver 2 and 3. Also, the printer moved but with a lot vibrations.

                  jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                  • jay_s_ukundefined
                    jay_s_uk @abindarraez1
                    last edited by

                    @abindarraez1 so you have a problem with your stepper motors and/or motor wiring. Nothing wrong with the board

                    Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                    abindarraez1undefined 1 Reply Last reply Reply Quote 0
                    • abindarraez1undefined
                      abindarraez1 @jay_s_uk
                      last edited by

                      @jay_s_uk Thanks a lot. But any clue what could be causing it? The motors seem to work well with the DRV8825

                      jay_s_ukundefined abindarraez1undefined 2 Replies Last reply Reply Quote 0
                      • jay_s_ukundefined
                        jay_s_uk @abindarraez1
                        last edited by

                        @abindarraez1 poor or failing crimps would be my guess

                        Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                        1 Reply Last reply Reply Quote 1
                        • abindarraez1undefined
                          abindarraez1 @abindarraez1
                          last edited by

                          @abindarraez1 Thanks, I will revise them.

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

                            For your review

                            https://docs.duet3d.com/en/User_manual/Connecting_hardware/Motors_connecting

                            https://docs.duet3d.com/en/How_to_guides/Commissioning#h-10-check-stepper-motors

                            Z-Bot CoreXY Build | Thingiverse Profile

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