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

    Stepper motor "Phase B Short to VIN"

    Scheduled Pinned Locked Moved
    General Discussion
    3
    5
    302
    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.
    • p8blrundefined
      p8blr
      last edited by

      I bought a couple of these steppers to build a linear actuator:

      https://www.robotdigg.com/product/644/NEMA8-Linear-Stepper-Motor-with-lead-screw-Tr4.76-or-Tr5

      but I cannot get them to spin.

      I've confirmed that the phases are wired correctly with a multimeter, however, I keep getting the an error about "Phase B Short to VIN" when I try and move it. Of course I've tried flipping a pair of wires around but still no luck. I have the issue on both of the steppers I purchased. Any ideas?

      Duet 3 6HC, actuators connected to a 3HC expansion board.

      Thanks!

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

        Can you send M122 and M122 B# where # is the canbus address of your expansions and post the results here?

        Also please post your config.g

        Do you get that error on other drivers as well? Does that driver work with other motors?

        Z-Bot CoreXY Build | Thingiverse Profile

        p8blrundefined 1 Reply Last reply Reply Quote 0
        • p8blrundefined
          p8blr @Phaedrux
          last edited by

          @phaedrux

          M122
          === Diagnostics ===
          RepRapFirmware for Duet 3 MB6HC version 3.4.2 (2022-09-13 15:17:43) running on Duet 3 MB6HC v1.01 (standalone mode)
          Board ID: 08DJM-956BA-NA3TN-6J9DJ-3SJ6S-1T8AV
          Used output buffers: 13 of 40 (36 max)
          === RTOS ===
          Static ram: 152664
          Dynamic ram: 99904 of which 0 recycled
          Never used RAM 98104, free system stack 200 words
          Tasks: NETWORK(ready,24.1%,210) ETHERNET(notifyWait,0.1%,561) HEAT(notifyWait,0.0%,369) Move(notifyWait,0.0%,351) CanReceiv(notifyWait,0.1%,799) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,339) TMC(notifyWait,8.4%,91) MAIN(running,66.9%,1083) IDLE(ready,0.4%,30), total 100.0%
          Owned mutexes:
          === Platform ===
          Last reset 00:00:38 ago, cause: power up
          Last software reset time unknown, reason: User, GCodes spinning, available RAM 12676, slot 0
          Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
          Error status: 0x00
          Aux0 errors 0,0,0
          Step timer max interval 129
          MCU temperature: min 18.6, current 28.2, max 28.2
          Supply voltage: min 24.1, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
          12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0
          Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
          Events: 5 queued, 5 completed
          Driver 0: standstill, SG min 0, mspos 128, reads 15023, writes 14 timeouts 0
          Driver 1: standstill, SG min 0, mspos 8, reads 15026, writes 11 timeouts 0
          Driver 2: standstill, SG min 0, mspos 8, reads 15026, writes 11 timeouts 0
          Driver 3: standstill, SG min 0, mspos 8, reads 15026, writes 11 timeouts 0
          Driver 4: standstill, SG min 0, mspos 8, reads 15026, writes 11 timeouts 0
          Driver 5: standstill, SG min 0, mspos 8, reads 15026, writes 11 timeouts 0
          Date/time: 2022-09-26 11:19:11
          Slowest loop: 15.31ms; fastest: 0.06ms
          === Storage ===
          Free file entries: 10
          SD card 0 detected, interface speed: 25.0MBytes/sec
          SD card longest read time 2.9ms, write time 0.0ms, max retries 0
          === Move ===
          DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
          === MainDDARing ===
          Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
          === AuxDDARing ===
          Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
          === Heat ===
          Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters 1 -1 -1 -1, ordering errs 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 416, received 4207, lost 0, boc 0
          Longest wait 2ms for reply type 6019, peak Tx sync delay 42, free buffers 50 (min 49), ts 194/193/0
          Tx timeouts 0,0,0,0,0,0
          === Network ===
          Slowest loop: 17.81ms; fastest: 0.03ms
          Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
          HTTP sessions: 1 of 8
          = Ethernet =
          State: active
          Error counts: 0 0 0 1 0 0
          Socket states: 5 2 2 2 2 0 0 0
          === Multicast handler ===
          Responder is inactive, messages processed 0
          
          M122 B3
          Diagnostics for board 3:
          Duet EXP3HC rev 1.01 or earlier firmware version 3.4.2 (2022-09-13 15:05:23)
          Bootloader ID: SAME5x bootloader version 2.3 (2021-01-26b1)
          All averaging filters OK
          Never used RAM 158352, free system stack 200 words
          Tasks: Move(notifyWait,0.0%,160) HEAT(notifyWait,0.1%,101) CanAsync(notifyWait,0.0%,69) CanRecv(notifyWait,0.0%,82) CanClock(notifyWait,0.0%,71) TMC(notifyWait,7.6%,99) MAIN(running,91.0%,344) IDLE(ready,0.0%,40) AIN(delaying,1.3%,263), total 100.0%
          Last reset 00:01:06 ago, cause: power up
          Last software reset data not available
          Driver 0: pos 0, 5.0 steps/mm,standstill, SG min 0, mspos 128, reads 58834, writes 15 timeouts 0, steps req 0 done 0
          Driver 1: pos 0, 5.0 steps/mm,standstill, SG min 0, mspos 128, reads 58834, writes 15 timeouts 0, steps req 0 done 0
          Driver 2: pos 0, 80.0 steps/mm,standstill, SG min 0, mspos 8, reads 58839, writes 11 timeouts 0, steps req 0 done 0
          Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
          Peak sync jitter 1/11, peak Rx sync delay 176, resyncs 0/0, no step interrupt scheduled
          VIN voltage: min 24.4, current 24.5, max 24.5
          V12 voltage: min 12.2, current 12.2, max 12.2
          MCU temperature: min 23.5C, current 26.4C, max 26.7C
          

          Not getting the error on any other drivers, connecting a different stepper works. I'm starting to wonder that if I can control a NEMA 17 and 23 just fine, maybe this NEMA 7 is too low of resistance for the 3HC's drivers and it's just assuming it's a short. Is that possible?

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

            @p8blr do you get the same error if you connect this particular motor to another driver output?

            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

            p8blrundefined 1 Reply Last reply Reply Quote 0
            • p8blrundefined
              p8blr @dc42
              last edited by

              @dc42 I do yes. I'm beginning to suspect the motor could be defective. I've ordered a replacement to test. Will update when I receive.

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