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 @fcwilt
      last edited by

      @fcwilt https://de.nanotec.com/produkte/1604-pd4-c-schrittmotor-mit-integriertem-controller-nema-23-24

      this is the motor. It is a closed loop motor.

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

        @phaedrux The setup is a Duet3 6HC and 3 1XD boards. I want to use 3 motors from Nanotec. I posted the link in my previous reply. i will post the responses from the mainboard in my next reply

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

          @phaedrux these are the responses from the Mainboard

          M122

          === Diagnostics ===<LF>RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v1.01 or later (standalone mode)<LF>Board ID: 08DJM-956BA-NA3TJ-6J1DG-3SJ6P-TUAUU<LF>Used output buffers: 1 of 40 (10 max)<LF>=== RTOS ===<LF>Static ram: 150904<LF>Dynamic ram: 90984 of which 0 recycled<LF>Never used RAM 112304, free system stack 190 words<LF>Tasks: NETWORK(ready,11.6%,548) HEAT(delaying,0.0%,405) Move(notifyWait,0.0%,254) CanReceiv(notifyWait,0.0%,908) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.2%,93) MAIN(running,77.0%,1206) IDLE(ready,4.1%,29), total 100.0%<LF>Owned mutexes: USB(MAIN)<LF>=== Platform ===<LF>Last reset 00:04:03 ago, cause: power up<LF>Last software reset details not available<LF>Error status: 0x00<LF>Aux0 errors 0,0,0<LF>Step timer max interval 126<LF>MCU temperature: min 20.0, current 29.2, max 101.8<LF>Supply voltage: min 0.0, current 23.6, max 30.3, under voltage events: 0, over voltage events: 0, power good: yes<LF>12V rail voltage: min 0.1, current 12.0, [Warning: Maximal number of characters per line exceeded! Check the line break settings in Terminal > Settings > Text or increase the limit in Terminal > Settings > Advanced.]
          

          M98 P"config.g"

          Warning: Discarded std reply src=123 RID=32 exp 33 "Setting not available for external drivers"<LF>Error: Response timeout: CAN addr 122, req type 6018, RID=34<LF>Warning: Discarded std reply src=123 RID=35 exp 36 "Boar<DLE>[Warning: "80h 22h" is a byte sequence outside the Unicode basic multilingual plane (plane 0)! Only Unicode plane 0 is supported by .NET Framework and thus YAT (yet).]<LF>Error: Response timeout: CAN addr 122, req type 6042, RID=37<LF>Warning: Discarded std reply src=123 RID=38 exp 39 "Boar<DLE>[Warning: "80h 22h" is a byte sequence outside the Unicode basic multilingual plane (plane 0)! Only Unicode plane 0 is supported by .NET Framework and thus YAT (yet).]<LF>Error: Response timeout: CAN addr 122, req type 6042, RID=40<LF>Warning: Discarded std reply src=123 RID=41 exp 42 ""<LF>Error: Response timeout: CAN addr 122, req type 6042, RID=43<LF>Warning: Discarded std reply src=123 RID=44 exp 45 "Sett<DLE>[Warning: "80h 22h" is a byte sequence outside the Unicode basic multilingual plane (plane 0)! Only Unicode plane 0 is supported by .NET Framework and thus YAT (yet).]<LF>Warning: Discarded std reply src=123 RID=47 exp 48 "Setting
          
          dc42undefined 1 Reply Last reply Reply Quote 0
          • dc42undefined
            dc42 administrators @Hammad
            last edited by

            @hammad do you have a M291 command in your homing files? There is a known bug in firmware 3.3 that causes the homing failed message when you do that. It is fixed in firmware 3.4.0.

            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

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

              PS - I see that you have posted your homeall.g file and it doesn't include a M291 command. Nevertheless, please upgrade to firmware 3.4.0 because it includes fixes to bugs that affect 1XD boards.

              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

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

                @dc42 I misunderstood the instructions and bridged erase. now i cant flash the firmware because BOSSA isnt detecting the board at all. How can I solve this issue?

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

                  @hammad The Status LED is slightly on. I can't figure out why Bossa doesn't want to connect to the board. I've followed the instructions on how to upload the firmware if the firmware was erased. It doesn't work for me. I keep getting the error "could not connect to device on COM 22".

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

                    @dc42 I measured the 5V to make sure I'm getting a stable 5V. I'm measuring just a few mV. The board is only connected to the PC using a high quality USB cable from ANKER.

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

                      @hammad said in Duet3 Homing failed:

                      The board is only connected to the PC using a high quality USB cable from ANKER.

                      The Duet3 can be quite particular about USB cable and port. Please try some different combinations. Also make sure you remove the jumper after the erase.

                      Z-Bot CoreXY Build | Thingiverse Profile

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

                        @phaedrux 3 different laptops and over 15 cables and still nothing. I removed the bridge from erase before resetting the board. I'm not sure what to do now. nothing seems to be working.

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

                          @hammad do you have a powered hub you can try with?

                          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

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

                            @jay_s_uk Do you think this will solve the problem?

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

                              @hammad it has for people in the past. i've seen instances where standard USB doesn't provide enough power, especially laptops

                              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

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

                                @jay_s_uk Thank you for the idea. Ill let you know in few minutes if this actually works.

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

                                  @jay_s_uk Thank you so much! this actually worked. It is writing the Firmware right now. It's been at 34% for a while now. I'm just glad that it connected!

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

                                    @hammad one step forwards and all that

                                    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

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

                                      @jay_s_uk Do you think it is normal, that it's taking that long?

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

                                        @hammad no, its not normal for it to take very long. last time I flashed one the increase in % was fairly uniform and only took a minute or so.
                                        maybe try again?

                                        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

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

                                          @jay_s_uk Same thing. it gets stuck at 35%. I've tried it from a different Laptop.

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

                                            @hammad not a good sign. hopefully @Phaedrux or @dc42 can comment

                                            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

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