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

    Problems with homing the x-axis

    Scheduled Pinned Locked Moved Solved
    General Discussion
    2
    3
    178
    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.
    • heinrich.platauundefined
      heinrich.platau
      last edited by

      Hello everyone

      I have a problem with my printer / duet board.

      Suddenly (after 1,5 years working perfectly) it is not possible to home the x-axis.

      If I send the command, the printer head is moving just a small distance right and left (along the x-axis) from its position. The distance is about 1 or 2 cm. Also there is a strange noise.

      During that failed homing process, the duet shows the following message:

      G28 X
      Warning: motor phase B may be disconnected reported by driver(s) 0

      I have checked the stepper motor for a mecahnical failure. But the stepper seems to be ok.

      Can you help me and give me some advice? How can I check wether the On-Board Driver on the Duet Board is defective?

      I use a DuetBoard 2 (Ethernet) with firmware version 3.2.1

      Please tell me, if i should post any further information

      Thanks a lot for you help2022-08-23_12h50_23.png

      jay_s_ukundefined 1 Reply Last reply Reply Quote 0
      • jay_s_ukundefined
        jay_s_uk @heinrich.platau
        last edited by

        @heinrich-platau fully check the wiring for your motor.
        use a multimeter so you can verify each of the coils

        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

        heinrich.platauundefined 1 Reply Last reply Reply Quote 0
        • heinrich.platauundefined
          heinrich.platau @jay_s_uk
          last edited by

          @jay_s_uk

          You are right!! Problem solved!

          I thought about the worst case but I'd better check the most obvious error.

          Thanks.

          Thread can be closed!

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