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

    Method to disable homing during print

    Scheduled Pinned Locked Moved
    Gcode meta commands
    3
    7
    448
    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.
    • Stephen6309undefined
      Stephen6309
      last edited by Stephen6309

      Some have suggested: to check if the state.status is "processing" when homing.

      Problem: It is always "processing" the moment the print is started, so homing never occurs during the print. Which means, you start the print and then get many not homed errors.

      I set a global variable in config.g and checkit in the homing files. Call the enable/disable in the slicer's start gcode and a enabie in the end gcode.
      Note: you will get homing failed errors when homing is disabled in the homing files.

      In config.g:

      if !exists(global.DisableHoming)
       global DisableHoming=false  ;create variable for use in homing
      else
       set global.DisableHoming=false ;reset variable for use in homing
      

      In the homeing files add at the beginning:

      if global.DisableHoming
       M99
      

      EnableHoming macro:

      set global.DisableHoming=false
      

      DisableHoming macro:

      set global.DisableHoming=true
      

      In the slicer's start gcode:

      M98 P"EnableHoming"
      G28                            ; home all axes
      M98 P"DisableHoming"
      

      Add M98 P"EnableHoming" in the end gocde in the slicer

      deckingmanundefined 1 Reply Last reply Reply Quote 4
      • Phaedruxundefined Phaedrux moved this topic from Using Duet Controllers
      • deckingmanundefined
        deckingman @Stephen6309
        last edited by

        @stephen6309 said in Method to disable homing during print:

        Some have suggested: to check if the state.status is "processing" when homing.

        Problem: It is always "processing" the moment the print is started, so homing never occurs during the print. Which means, you start the print and then get many not homed errors.
        ................

        Umm - I have to ask.......a) why would you want to run homing macros during a print? and b) Why would you want to start a print if the machine had not been homed (resulting in error messages)?

        Scratch that - I think I've worked it out - I assume this is for the use case where you run homing macros as part of the slicer start code yes?

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

        Stephen6309undefined 1 Reply Last reply Reply Quote 0
        • Stephen6309undefined
          Stephen6309 @deckingman
          last edited by Stephen6309

          @deckingman Yes. I don't want to have to remember to manually home before starting a print. Slicers have been doing that as a default in the start gcode, since I started with a Prusa 2 linear kit.

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

            @stephen6309 you can test the values of moves.axes[N].homed for each axis number N that matters.

            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

            Stephen6309undefined 1 Reply Last reply Reply Quote 0
            • Stephen6309undefined
              Stephen6309 @dc42
              last edited by

              @dc42 I already test for not homed in bed.g, since they won't work without homing. Also in mesh.g if it has to make the heightmap.csv.

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

                @stephen6309 so why not test in start.g too, and home if necessary? Then change the start GCode of the slicer not to home the printer.

                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

                Stephen6309undefined 1 Reply Last reply Reply Quote 0
                • Stephen6309undefined
                  Stephen6309 @dc42
                  last edited by Stephen6309

                  @dc42 I haven't set up a start.g file. But that's a good idea.

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