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

    Crash with Z probe X/Y offset

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    3
    8
    639
    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.
    • Surgikillundefined
      Surgikill
      last edited by

      So I'm setting up my DC42 IR probe and I set an X/Y offset in the firmware for the probe. I run into an issue though when I am trying to probe the bed. It seems like the G32 command is taking into account the X/Y offset and disregarding endstop limits. When I run G32 it home normally, but it crashes on the first probe point (I stop it there.) The first probe point is at 6,0. The probe is offset about 31mm in the +Y direction, so it is trying to move to -31Y to probe, which obviously won't work. Any way I can fix this, or should I just leave the probe offset at 0,0?

      1 Reply Last reply Reply Quote 0
      • aidarundefined
        aidar
        last edited by

        You can ajust your probe points so probe can actually reach those points. Say, if your Y0 is physically your Y limit and probe offset is Y31, then you should probe at X6 Y35 (for example) instead of X6 Y0.

        Surgikillundefined 1 Reply Last reply Reply Quote 0
        • Surgikillundefined
          Surgikill @aidar
          last edited by

          @aidar Is there a way for it to automatically adjust that so it will go as far as it can? I kind of figured the software would do that, but I guess not.

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

            Not for G32 since you are providing the coordinates. G29 will follow the grid provided by m557 and will skip unreachable areas, but even there it's best to adjust the grid size to maximize your probable area.

            Z-Bot CoreXY Build | Thingiverse Profile

            Surgikillundefined 1 Reply Last reply Reply Quote 0
            • Surgikillundefined
              Surgikill @Phaedrux
              last edited by

              @phaedrux I'm using 4 independent lead screws. The documentation said it was best to use G32. Should I just use G29 instead?

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

                For independent lead screw leveling you should still use G32 to run bed.g. you could use G29 afterwards for mesh grip mapping of the surface and active compensation.

                Z-Bot CoreXY Build | Thingiverse Profile

                Surgikillundefined 1 Reply Last reply Reply Quote 0
                • Surgikillundefined
                  Surgikill @Phaedrux
                  last edited by

                  @phaedrux said in Crash with Z probe X/Y offset:

                  For independent lead screw leveling you should still use G32 to run bed.g. you could use G29 afterwards for mesh grip mapping of the surface and active compensation.

                  Okay cool. I'll just adjust accordingly. Any idea how accurate the lead screw positions need to be? Is there any way I can have it auto map the leadscrew positions?

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

                    @surgikill I don't think you can automate it but I think the easiest way to find the coordinates would be to manually position the print head to place the probe at the closest location to the lead screw that you can and record the X Y.

                    You can run the leveling multiple times if need be to get the leveling closer. 2 or 3 times should be enough. If it doesn't even out at that point there may be other issues.

                    Z-Bot CoreXY Build | Thingiverse Profile

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