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

    Automatically Deselecting Tools When Homing

    Scheduled Pinned Locked Moved Solved
    Firmware developers
    4
    7
    260
    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.
    • ProbiusSCundefined
      ProbiusSC
      last edited by

      On the Jubilee X and Z homing fails if a tool is currently selected for mechanical reasons. It would be convenient to be able to deposit the tool if the axes were sufficiently homed before issuing the command.

      My question is, is it possible to issue a home#.g command without having the axes automatically forgotten.

      1 Reply Last reply Reply Quote 0
      • OwenDundefined
        OwenD
        last edited by

        I'm not sure if an axis is marked as not homed as soon as you call any home*.g file but I would suspect so.
        However it's relatively easy to check if a tool is currently selected within any of the home*.g files and if so run a macro to drop the tool before carrying out the remainder of the macro, or cancel out.
        The macro to drop the tool may need to search for an end stop and use relative moves to find the docking station (assuming the axis is no longer homed)
        Naturally it would have to issue M564 H0 if it is no longer homed.

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

          @OwenD said in Automatically Deselecting Tools When Homing:

          I'm not sure if an axis is marked as not homed as soon as you call any home*.g file but I would suspect so,,..........

          Not quite. Axes get marked as homed when the relevant end stop triggers doing a G1 H move.

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

          OwenDundefined 1 Reply Last reply Reply Quote 0
          • OwenDundefined
            OwenD @deckingman
            last edited by

            @deckingman said in Automatically Deselecting Tools When Homing:

            @OwenD said in Automatically Deselecting Tools When Homing:

            I'm not sure if an axis is marked as not homed as soon as you call any home*.g file but I would suspect so,,..........

            Not quite. Axes get marked as homed when the relevant end stop triggers doing a G1 H move.

            That's true, however you've misread my statement.
            I was saying that even a previously homed axis will be marked as unhomed as soon as you call G28 X or Y.
            Therefore to do what the OP wants he would need ensure all moves to unload the tool take that into account.

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

              on my tool changer I have the endstops for x and y positioned so I can home them with and without a tool fitted.
              I then have a switch installed on each tool and as part of the start up of the machine, I check whether any of them are activated. If they are, the homes in x and y and then docks the appropriate tool.

              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
              • deckingmanundefined
                deckingman @OwenD
                last edited by

                @OwenD You are quite right - I did misread your statement - apologies.

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

                1 Reply Last reply Reply Quote 0
                • ProbiusSCundefined
                  ProbiusSC
                  last edited by

                  So the problem was fixable using meta commands. Specifically

                  if state.ccurrentTool != -1
                  G92 X{move.axes[0].userPosition}
                  T-1

                  The userPosition doesn't get reset when G28 is called, so it can be used to restore position.

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