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

    Duet3 Homing failed

    Scheduled Pinned Locked Moved
    Using Duet Controllers
    6
    51
    1.8k
    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.
    • Hammadundefined
      Hammad @jay_s_uk
      last edited by

      @jay_s_uk I didn't remove the board from the housing. I just got the board and 3 1XD Modules for a big 3D printer. The board arrived like a month ago. The issue with BOSSA was just an issue because I misunderstood the Firmware process. I erased the Firmware by bridging the erase on the board. There is no wiring issues and everything is built according to the documentation.

      1 Reply Last reply Reply Quote 0
      • Hammadundefined
        Hammad @jay_s_uk
        last edited by

        @jay_s_uk I only have the CAN cables and the 24V cables. nothing else. The motors are connected to the 1XD Modules.

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

          @hammad one for @Phaedrux or @dc42 to comment on then. in the mean time use it with USB power applied

          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 0
          • dc42undefined
            dc42 administrators @jay_s_uk
            last edited by

            @jay_s_uk said in Duet3 Homing failed:

            @hammad if the 5v and 3.3v lights aren't on when powered by 24v, the onboard 5v converter has died

            Or else the jumper to enable the on-board 5V regulator is not int the correct position. @Hammad, please check it against the wiring diagram.

            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

            jay_s_ukundefined Hammadundefined 3 Replies Last reply Reply Quote 1
            • jay_s_ukundefined
              jay_s_uk @dc42
              last edited by

              @dc42 forgot about that! Good shout

              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 0
              • Hammadundefined
                Hammad @dc42
                last edited by

                @dc42 Thank you so much. This was actually the Problem.

                1 Reply Last reply Reply Quote 0
                • Hammadundefined
                  Hammad @dc42
                  last edited by

                  @dc42 @Phaedrux I'm still facing the original Problem with the Motors. The Board doesn't home or move the Motors. I reconfigured the RepRap firmware and still nothing. I bought the 1XD Modules to be able to use the motors I mentioned in my reply at the beginning. Can you suggest a solution to this problem?

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

                    @hammad said in Duet3 Homing failed:

                    Can you suggest a solution to this problem?

                    I'll ask again:

                    Have you been able to get the motors to move at all? You can force the axis to report as homed without moving at all by sending G92 X100 Y100 Z10 and then carefully testing movement by sending G1 X1 F100

                    Z-Bot CoreXY Build | Thingiverse Profile

                    Hammadundefined 1 Reply Last reply Reply Quote 0
                    • Hammadundefined
                      Hammad @Phaedrux
                      last edited by

                      @phaedrux It does home. I can see the coordinates on the Touchscreen. The Motors don't move at all. I tried moving the Motor with an external driver and it worked. Just to make sure that the Motors aren't the issue here.

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

                        I am confused by your response. Is homing working or not?

                        Can you give a more detailed restatement of the current problem situation?

                        Perhaps it would even be a good idea to start a new thread since this one has gone on for quite some time and we've gone through a number of things.

                        Z-Bot CoreXY Build | Thingiverse Profile

                        1 Reply Last reply Reply Quote 0
                        • deckingmanundefined
                          deckingman @Hammad
                          last edited by

                          @hammad Are you saying that the homing status changes from "unhomed" to homed but the motors don't move? If so, then it means that the homing switch is triggered at the start of the move. The usual cause of that is either the configuration does not match the physical NO/NC of the switch, or there is a wiring fault.

                          Ian
                          https://somei3deas.wordpress.com/
                          https://www.youtube.com/@deckingman

                          Hammadundefined 1 Reply Last reply Reply Quote 0
                          • Hammadundefined
                            Hammad @deckingman
                            last edited by

                            @deckingman The Homing status changed to the coordinates I entered with G92 X100 Y100 Z10. The Touchscreen showed X 100 Y 100 and Z 10. When I try to move the motors using the Touchscreen they don't move at all but the coordinates on the screen change. The wiring isn't the issue. I checked everything and it was built to be normally closed as recommended by the documentation. I'm going to start a new thread to make it easier for everyone to follow. I need to get this to work for a big project. I already ordered many boards for the other printers lol. I'll post a link to the new thread in a bit.

                            Hammadundefined Phaedruxundefined 2 Replies Last reply Reply Quote 0
                            • Hammadundefined
                              Hammad @Hammad
                              last edited by

                              @dc42 @deckingman @jay_s_uk @Phaedrux this is the link to the new thread.

                              new thread

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

                                @hammad said in Duet3 Homing failed:

                                @deckingman The Homing status changed to the coordinates I entered with G92 X100 Y100 Z10. The Touchscreen showed X 100 Y 100 and Z 10. When I try to move the motors using the Touchscreen they don't move at all but the coordinates on the screen change. The wiring isn't the issue. I checked everything and it was built to be normally closed as recommended by the documentation. I'm going to start a new thread to make it easier for everyone to follow. I need to get this to work for a big project. I already ordered many boards for the other printers lol. I'll post a link to the new thread in a bit.

                                Thanks, that makes more sense. I'll check your new thread.

                                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