-
-
Notifications
You must be signed in to change notification settings - Fork 19.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] G29 is probing in the wrong position #16348
Comments
Fixed changing the file "G29.CPP" Please search for "#if ENABLED(NOZZLE_AS_PROBE)" |
Ill go over the action it takes there again, but the theory was the the inset would be honored for everything in the min / max position calculation. Prior it was possible to set points that did not honor configured limits. In reality those couple lines are a bugfix mixed with the feature extension to support lulzbot. This would be expected behavior since you have |
@InsanityAutomation, I found a problem causing MIN_PROBE_EDGE to be doubled. I'm testing a fix right now. |
@sjasonsmith for me your change works. Thanks. |
Experiencing the exact same problem, and the patch in #16367 solved it for me. |
seems this one is solved by #16367 |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Bug Description
I'm using bugfix-2.0.x and the problem seems to be in this commit: Add NOZZLE_AS_PROBE (no probe offsets) (#15929) (1c9ccce) developed by @InsanityAutomation
G29 probes the points in the wrong position.
My Configurations
Archive.zip
Steps to Reproduce
Expected behavior:
Probe the 9 points of the bed all around 30 positions from bed limits.
Actual behavior:
Is probing the 9 points much more than 30 positions from bed limits (too near the center of the bed)
The text was updated successfully, but these errors were encountered: