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

    Duet 2 cant get any stepper motor to run

    Scheduled Pinned Locked Moved Solved
    Duet Hardware and wiring
    stepper wiring
    2
    7
    234
    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.
    • Jukkaundefined
      Jukka
      last edited by Jukka

      Got an old unused Duet2 1.04c and wanted to tinker around a bit.
      Thought i can convert my old but running Anet A8 (on ramps) to Duet.

      If i connect any stepper and select home it starts moving for 1-2 seconds and than stops and the motor is noisy. Thought i had to swap the wires for phases but thats looks fine - its the same as on my old RAMPS board. Also checked different steppers and wires i have here to see if the motors or wires are broke but its on every stepper+wire i have.

      Played around with the currents and steprates but no success the error is always the same:

      G28 X
      Warning: Driver 2 warning: phase A may be disconnected, phase B may be disconnected
      

      some infos:

      M115
      FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.4.6 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2023-07-21 14:08:28
      M122
      === Diagnostics ===
      RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.6 (2023-07-21 14:08:28) running on Duet WiFi 1.02 or later
      Board ID: 08DGM-917NK-F2MS4-7J1F2-3S06N-TYSSD
      Used output buffers: 2 of 26 (12 max)
      === RTOS ===
      Static ram: 23896
      Dynamic ram: 74896 of which 0 recycled
      Never used RAM 13288, free system stack 184 words
      Tasks: NETWORK(notifyWait,13.5%,242) HEAT(notifyWait,0.0%,349) Move(notifyWait,0.0%,363) MAIN(running,86.3%,460) IDLE(ready,0.2%,30), total 100.0%
      Owned mutexes: WiFi(NETWORK)
      === Platform ===
      Last reset 00:09:26 ago, cause: software
      Last software reset at 2023-11-08 21:47, reason: User, GCodes spinning, available RAM 13144, slot 1
      Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
      Error status: 0x00
      Step timer max interval 0
      MCU temperature: min 24.5, current 25.1, max 25.7
      Supply voltage: min 11.9, current 12.0, max 12.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
      Events: 0 queued, 0 completed
      Driver 0: standstill, SG min n/a
      Driver 1: standstill, SG min n/a
      Driver 2: standstill, SG min n/a
      Driver 3: standstill, SG min n/a
      Driver 4: standstill, SG min n/a
      Driver 5: 
      Driver 6: 
      Driver 7: 
      Driver 8: 
      Driver 9: 
      Driver 10: 
      Driver 11: 
      Date/time: 2023-11-08 21:57:24
      Cache data hit count 4294967295
      Slowest loop: 5.57ms; fastest: 0.18ms
      I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
      === Storage ===
      Free file entries: 10
      SD card 0 detected, interface speed: 20.0MBytes/sec
      SD card longest read time 3.1ms, write time 0.0ms, max retries 0
      === Move ===
      DMs created 83, 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, 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
      Daemon is idle in state(s) 0
      Autopause is idle in state(s) 0
      Code queue is empty
      === Network ===
      Slowest loop: 12.76ms; fastest: 0.00ms
      Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
      HTTP sessions: 1 of 8
      = WiFi =
      Interface state: active
      Module is connected to access point 
      Failed messages: pending 0, notready 0, noresp 0
      WiFi firmware version 1.27
      WiFi MAC address 60:01:94:2e:9b:22
      WiFi Vcc 3.37, reset reason Turned on by main processor
      WiFi flash size 4194304, free heap 21512
      WiFi IP address 10.0.2.10
      WiFi signal strength -54dBm, mode 802.11n, reconnections 0, sleep mode modem
      Clock register 00002002
      Socket states: 0 0 0 0 0 0 0 0
      

      Tested on X Y and Z. Am im doing something stupidly wrong? I basically used config tool and selected Anet A8 as preset. Current config is attached. Steppers on the printer are 42SHDC3025-24B.

      Kind regards.

      config.g

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

        What are the motors rated current? 500ma may be too low.

        M906 X500 Y500 Z500 E500 I30

        Carefully double check the motor phases and ensure they are wired correctly.
        https://docs.duet3d.com/en/User_manual/Connecting_hardware/Motors_connecting

        Z-Bot CoreXY Build | Thingiverse Profile

        Jukkaundefined 1 Reply Last reply Reply Quote 0
        • Jukkaundefined
          Jukka @Phaedrux
          last edited by Jukka

          42SHDC3025-24B are rated 900ma and i tried it with the default of 800ma or even 1400ma just for testing.
          on the other steppers i tested i aimed for 80% of the current rating.
          it just changed how fast the motor stopped but still the same error.

          also checked the wiring on every stepper to have both wires of one phase next to each other and not crossed.

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

            Do you have other motors to test with?

            Z-Bot CoreXY Build | Thingiverse Profile

            1 Reply Last reply Reply Quote 0
            • Jukkaundefined
              Jukka
              last edited by

              Yes, as i wrote, i tested different stepper. for example a 17HS4417L20P1-X2 next to me rated at 1.7A.
              Tried them with 1.2A current and the same happens. (checked phases ofc)

              If i put the the steppers on my ramps board they are running fine.

              I think i play around with it later today again but i currently really think - if i dont did something stupidly wrong - the drivers on the duet are wrong.

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

                It's possible that the stepper drivers have been damaged.

                The motor and cabling works correctly on another board, but not this Duet2, then it could be the driver.

                Is it possible the phases were wired incorrectly when you first tried? That could have damaged the driver.

                Z-Bot CoreXY Build | Thingiverse Profile

                1 Reply Last reply Reply Quote 0
                • Jukkaundefined
                  Jukka
                  last edited by

                  Found the issue.
                  First the warning "phase A may be disconnected" which i was thinking its the motors is caused by not connecting the Z Motor. I only had X and Y connected for testing and saw the homescripts lift Z.

                  The main issue actually was the endstop switches. I have microswitches which are most likely worn or the cables are broke but they when i just wiggle the table they trigger like 10 times.

                  After replacing them all runs fine 🙂 The motor noise i thought was part of the problem is actually the normal idle sound i tweaked with M569 F. I was used to stealthChop from my old 2130 haha

                  Thanks for the help!

                  1 Reply Last reply Reply Quote 1
                  • Jukkaundefined Jukka has marked this topic as solved
                  • First post
                    Last post
                  Unless otherwise noted, all forum content is licensed under CC-BY-SA