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

    Idex mesh leveling with T1 active

    Scheduled Pinned Locked Moved
    General Discussion
    2
    5
    263
    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.
    • jckrayundefined
      jckray
      last edited by

      My idex machine has the z probe attached to T0. If T1 is the active tool it tries to home z and probe the bed using T1, which does not have a probe attached. I realize the simple solution is to make sure T0 is active when running G28 or G29, but is there any way to ensure that if this is accidentally done with T1 active it will still probe with T0? If you're not paying attention and trying to home z or run mesh leveling with T1 active it crashes the tool into the bed.

      John
      Founder of Hydra Research LLC, developers of the open-source 3D printers and providers of 3D printing services.
      https://www.hydraresearch3d.com/

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

        @jckray said in Idex mesh leveling with T1 active:

        is there any way to ensure that if this is accidentally done with T1 active it will still probe with T0?

        Alter homeall.g and mesh.g to select T0 at the start so that when G28 or G29 get called it will switch to T0 if not already active.

        Z-Bot CoreXY Build | Thingiverse Profile

        jckrayundefined 1 Reply Last reply Reply Quote 1
        • jckrayundefined
          jckray @Phaedrux
          last edited by

          @phaedrux I had that thought, but that can interfere with the print jobs if mesh leveling is done at the beginning of each print. At least in Cura, it outputs the tool command for the first tool used during a job before it inserts the start gcode. This means if the job is supposed to start using T1 and there is a T0 command anywhere in the start gecode then the job will start using T0 rather than T1. Thus, I have been trying to avoid any use of tool commands in the start gcode. This is pretty annoying though, so I might have to look into changing how Cura outputs gcode in the back end instead.

          John
          Founder of Hydra Research LLC, developers of the open-source 3D printers and providers of 3D printing services.
          https://www.hydraresearch3d.com/

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

            If you're really worried about that use start.g to do the print prep. It takes effect before the print gcode is executed.

            T0
            G28
            G29
            ; cura code takes over and selects whatever tool it wants.

            Z-Bot CoreXY Build | Thingiverse Profile

            jckrayundefined 1 Reply Last reply Reply Quote 0
            • jckrayundefined
              jckray @Phaedrux
              last edited by

              @phaedrux I forgot about start.g, thanks for reminding me! I will give that a go.

              John
              Founder of Hydra Research LLC, developers of the open-source 3D printers and providers of 3D printing services.
              https://www.hydraresearch3d.com/

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