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

    Duet 3 Mini 5+ Error: short-to-ground reported by driver(s)

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    short-to-ground
    4
    12
    865
    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.
    • fotomasundefined
      fotomas @Phaedrux
      last edited by

      @phaedrux

      With spreadcycle all the time, D2 as in for eg. M569 P0.1 S1 D2
      homing just makes it stand still and buzz. I hope I have understood M569 correctly.

      x16 microstepping (D2 removed and V50 back) makes things better, but the resonance increases as it picks up speed until it detects a false sensor less endstopp. It is like some kind of vibration that counteracts the movement.

      Video of homing @ 500 mA https://youtu.be/Kg_PY0-1OhE (works fine)

      Video of homing @ 800 mA https://youtu.be/myc5rtT7meU (problems...)

      Firmware

      M115
      FIRMWARE_NAME: RepRapFirmware for Duet 3 Mini 5+ FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet 3 Mini5plus WiFi FIRMWARE_DATE: 2021-06-15 21:46:20
      

      PSU voltage ~24.5

      M122
      === Diagnostics ===
      RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus WiFi (standalone mode)
      Board ID: DL70G-S396U-D65J0-40KMW-2303Z-HP9WR
      Used output buffers: 3 of 40 (25 max)
      === RTOS ===
      Static ram: 102724
      Dynamic ram: 106072 of which 60 recycled
      Never used RAM 34848, free system stack 136 words
      Tasks: NETWORK(ready,16.2%,258) HEAT(delaying,0.0%,373) Move(notifyWait,0.1%,305) CanReceiv(notifyWait,0.0%,798) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.0%,347) TMC(notifyWait,0.7%,115) MAIN(running,82.1%,426) IDLE(ready,0.1%,29) AIN(delaying,0.8%,264), total 100.0%
      Owned mutexes: WiFi(NETWORK)
      === Platform ===
      Last reset 00:03:16 ago, cause: software
      Last software reset at 2021-07-12 09:11, reason: User, GCodes spinning, available RAM 34848, slot 0
      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
      MCU revision 3, ADC conversions started 196361, completed 196360, timed out 0, errs 0
      Step timer max interval 752
      MCU temperature: min 25.3, current 26.4, max 27.1
      Supply voltage: min 24.2, current 24.6, max 24.8, 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 24960, standstill, SG min/max 0/4, read errors 0, write errors 1, ifcnt 35, reads 10306, writes 12, timeouts 0, DMA errors 0
      Driver 1: position 960, short-to-ground, standstill, SG min/max 2/336, read errors 0, write errors 1, ifcnt 40, reads 10304, writes 14, timeouts 0, DMA errors 0
      Driver 2: position 2700, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 29, reads 10308, writes 9, timeouts 0, DMA errors 0
      Driver 3: position 0, short-to-ground, standstill, SG min/max 2/340, read errors 0, write errors 1, ifcnt 39, reads 10303, writes 14, timeouts 0, DMA errors 0
      Driver 4: position 0, standstill, SG min/max 0/2, read errors 0, write errors 1, ifcnt 35, reads 10306, writes 12, timeouts 0, DMA errors 0
      Driver 5: position 0, assumed not present
      Driver 6: position 0, assumed not present
      Date/time: 2021-07-12 09:15:11
      Cache data hit count 371153997
      Slowest loop: 7.32ms; fastest: 0.10ms
      === 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 23259ms, bed compensation in use: none, comp offset 0.000
      === MainDDARing ===
      Scheduled moves 7, completed moves 7, 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
      Heater 1 is on, I-accum = 0.0
      === 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 1795, received 2380, lost 0, longest wait 2ms for reply type 6031, peak Tx sync delay 177, free buffers 17 (min 16), ts 982/981/0
      Tx timeouts 0,0,0,0,0,0
      === Network ===
      Slowest loop: 10.80ms; fastest: 0.00ms
      Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
      HTTP sessions: 1 of 8
      - WiFi -
      Network state is active
      WiFi module is connected to access point 
      Failed messages: pending 0, notready 0, noresp 0
      WiFi firmware version 1.26
      WiFi MAC address f0:08:d1:02:ef:4b
      WiFi Vcc 3.41, reset reason Power up
      WiFi flash size 2097152, free heap 26664
      WiFi IP address 192.168.0.117
      WiFi signal strength -51dBm, mode 802.11n, reconnections 0, sleep mode modem
      Clock register 00002002
      Socket states: 0 0 0 0 0 0 0 0
      
      M98 P"config.g"
      HTTP is enabled on port 80
      FTP is disabled
      TELNET is disabled
      Accelerometer 121:0 with orientation 16 samples at 1344Hz with 12-bit resolution
      Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 827C
      
      1 Reply Last reply Reply Quote 0
      • Phaedruxundefined
        Phaedrux Moderator
        last edited by Phaedrux

        What are the specs of the motors? Do they have high back emf by chance?

        Also take a look at this page.

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

        Z-Bot CoreXY Build | Thingiverse Profile

        1 Reply Last reply Reply Quote 0
        • tony449777undefined
          tony449777
          last edited by

          Check your motor winding specs on the manufacturer page. I had the same problem. Bought LDO steppers but the harness came from somewhere else. I just released the pins from the plug on the stepper side and reconfigured them correctly according to the manufacturers diagram.

          fotomasundefined Phaedruxundefined 2 Replies Last reply Reply Quote 0
          • fotomasundefined
            fotomas @tony449777
            last edited by

            @tony449777 If your experience should apply in thiss case the pin out for the stepper motors has to differ between the duet WiFi and the mini 5. Which I highly doubt.

            (Away from printer will investigate more when I get hold of stepper motor model no)

            tony449777undefined 1 Reply Last reply Reply Quote 0
            • tony449777undefined
              tony449777 @fotomas
              last edited by

              @fotomas It wasn’t the pin out of the driver that was wrong. It was how the output of the driver was actually connected to the coils of the motor. They were physically in the motor plug in the wrong configuration.

              dc42undefined 1 Reply Last reply Reply Quote 0
              • dc42undefined
                dc42 administrators @tony449777
                last edited by

                @tony449777 said in Duet 3 Mini 5+ Error: short-to-ground reported by driver(s):

                @fotomas It wasn’t the pin out of the driver that was wrong. It was how the output of the driver was actually connected to the coils of the motor. They were physically in the motor plug in the wrong configuration.

                This is a common issue because different manufacturers of stepper motors use different pinouts. When using motors with a built-in socket and separate cable, ALWAYS check the phases.

                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

                tony449777undefined 1 Reply Last reply Reply Quote 0
                • tony449777undefined
                  tony449777 @dc42
                  last edited by

                  @dc42 Exactly. That’s what I’m trying to say,

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

                    @tony449777 said in Duet 3 Mini 5+ Error: short-to-ground reported by driver(s):

                    Check your motor winding specs on the manufacturer page. I had the same problem. Bought LDO steppers but the harness came from somewhere else. I just released the pins from the plug on the stepper side and reconfigured them correctly according to the manufacturers diagram.

                    If this were the case here and the phases not paired correctly there would be no movement at all, but if you want the videos it's clear there is motion, but at a certain speed there is a lot of vibration and noise.

                    Z-Bot CoreXY Build | Thingiverse Profile

                    fotomasundefined 1 Reply Last reply Reply Quote 0
                    • fotomasundefined
                      fotomas @Phaedrux
                      last edited by

                      I got things working.

                      I checked wiring, everything was ok (as exprected since wiring was not modified since working ok on a Duet Wifi)

                      I increased the acceleration (M201) on X/Y from 300 to 800 this made it possible to increase the motor currents on X/Y to 800.

                      As an effect of this I had to tweak the sensorless homing to use less current.

                      So increased acceleration seems to be the solution, the problem may still be there but pushed out of bounds for my usage/speeds by increased acceleration.

                      I do not understand how increased acceleration have effected things. Maybe someone can explain this? It would be nice to know if I run into more trouble.

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

                        That's an interesting result. I don't understand why higher acceleration would solve it either. You've made the motor/stepper combo happy at least.

                        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