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

    Error: G0/G1: insufficient axes homed

    Scheduled Pinned Locked Moved
    Firmware installation
    5
    18
    682
    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.
    • gloomyandyundefined
      gloomyandy @ThreeDeeDave
      last edited by

      @ThreeDeeDave I don't see any obvious problem, what driver modules do you have installed? Have you made any changes to the board since it was working? What exactly did "installing a new toolhead" involve? I'm not really very familiar with that board/printer but I think @jay_s_uk Had one for a while so he may have some ideas.

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

        @ThreeDeeDave i can't see anything wrong with what's being reported there either.
        Best thing is detail what you've changed, include some photos of the underside of the machine or even better, join us on discord https://discord.gg/uS97Qs7

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

          @ThreeDeeDave

          You really don't need to make your homing code that complicated.

          I've been using very simple code for years on multiple printers and never had an issue with just the basic:

          ; assumes endtop is at axis high end
          G1 H1 Xaaa Fddd
          G1 X-bbb
          G1 H1 Xccc Feee
          

          You don't need to do the test to see if the endstop is already triggered at the start. If the endstop is triggered that just means the fast G1 H1 is, in essence, already done.

          --

          As to your issue - I don't see anything except for the driver report but you are using hardware that I have no experience with.

          Frederick

          Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

          jay_s_ukundefined deckingmanundefined 2 Replies Last reply Reply Quote 0
          • jay_s_ukundefined
            jay_s_uk @fcwilt
            last edited by

            @fcwilt thats the homing file we provide https://github.com/TeamGloomy/Troodon-V2/blob/improved/Config/sys/homex.g

            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

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

              @fcwilt said in Error: G0/G1: insufficient axes homed:

              You don't need to do the test to see if the endstop is already triggered at the start. If the endstop is triggered that just means the fast G1 H1 is, in essence, already done.

              It could also mean that a wire has become detached from the end stop or the switch itself is faulty. In which case, the axis will be homed even though the print head is some distance away from the switch position. Say for example on the first pass, the head was X = 50mm away from the switch but the wire had fallen off, when you home the machine it will set X=50 as X=0 so then when you travel to X max, the head will collide with the frame some 50mm before X max. So check if the switch is triggered - if so move a short distance away and check again. If it's still triggered something is amiss so flag this and abort is the best approach IMO.

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

              fcwiltundefined 1 Reply Last reply Reply Quote 0
              • fcwiltundefined
                fcwilt @deckingman
                last edited by

                @deckingman

                Yes it certainly is protection against that sort of failure but given the multiplicity of things that can fail it's protection against just one. 😀

                Frederick

                Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

                deckingmanundefined 1 Reply Last reply Reply Quote 0
                • fcwiltundefined
                  fcwilt @jay_s_uk
                  last edited by

                  @jay_s_uk

                  To each their own.

                  Frederick

                  Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

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

                    @fcwilt said in Error: G0/G1: insufficient axes homed:

                    @deckingman

                    Yes it certainly is protection against that sort of failure but given the multiplicity of things that can fail it's protection against just one. 😀

                    Frederick

                    Sure. But if you've ever slammed a couple of kgs of print head against a frame, you'll know that protection is worth having - especially as it costs nothing and takes milliseconds to check. 😄

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

                    1 Reply Last reply Reply Quote 1
                    • ThreeDeeDaveundefined
                      ThreeDeeDave @gloomyandy
                      last edited by

                      @gloomyandy @jay_s_uk

                      Thanks guys for taking a look. Please see below answers and attached images:

                      what driver modules do you have installed?
                      I have Bigtree TMC 2209 v1.2

                      Have you made any changes to the board since it was working:
                      I Have unplugged everything in the board and then put it all back together checking that there were no issues with wiring on the reverse. 99% sure things went back exactly as they should have?

                      What exactly did "installing a new toolhead" involve:
                      I installed the new stealth burner and tap upgrade from Formbot. I have updated the the firmware to the relevant team gloomy "tap" firmware.

                      Any clues?
                      Thanks
                      David

                      20231129_143320.jpg 20231129_143335.jpg

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

                        @ThreeDeeDave have you had issues in the past with the breakout board? i've not seen a repair like this before
                        daa424f3-6007-4c7b-adc2-70c84f683f24-image.png
                        In terms of the drivers, they seem to be installed fine. Have you removed any of them? Have you changed any of the jumpers before beneath them?

                        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

                        ThreeDeeDaveundefined 1 Reply Last reply Reply Quote 0
                        • ThreeDeeDaveundefined
                          ThreeDeeDave @jay_s_uk
                          last edited by

                          @jay_s_uk
                          Break out board: Yes I have, the copper channels on the other side had come loose and detached from the pin somehow. I had a local computer repair shop repair it. This was from before and the issues from this were related to the z homing switch. This all works fine now aside from the current issue of course. It is repaired like this as the copper channel was too damaged to repair with certainty so they suggested connecting from the reverse side.

                          Drivers wise, I took them out when checking the main board for damage. Honestly probably didn't put them back in exactly the same place but I assumed they are all the same so it didn't matter?

                          Haven't touched the jumpers although I do have loads of spares so could try replacing?

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

                            @ThreeDeeDave could you take a photo of one of the slots with the drivers removed? obviously with the power off

                            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

                            ThreeDeeDaveundefined 1 Reply Last reply Reply Quote 0
                            • ThreeDeeDaveundefined
                              ThreeDeeDave @jay_s_uk
                              last edited by

                              @jay_s_uk
                              No problem see below:20231130_152130.jpg

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

                                @ThreeDeeDave thats correct as well which would indicate there may be some sort of hardware issue. I can't see anything wrong with the config etc. best get in contact with Ada at formbot and they should be able to sort you out with a new board. just mention you've spoken to me

                                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

                                ThreeDeeDaveundefined 1 Reply Last reply Reply Quote 0
                                • ThreeDeeDaveundefined
                                  ThreeDeeDave @jay_s_uk
                                  last edited by

                                  @jay_s_uk Ok thanks so much for taking the time to look at it, really appreciate it.

                                  Thanks
                                  David

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