You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 8, 2024. It is now read-only.
Today, a probing move is defined in the path planner as a move that terminates early when all moving axes are blocked. To enable more probe-like scenarios, the path planner API needs to include...
which axes need to be blocked to stop the move
whether all axes being blocked or any one axis being blocked will stop the move
reporting back which axis/axes actually stopped the move
This will enable scenarios like probing to check the correctness of a bed leveling matrix (probe moves are XYZ-moves, but any one axis from XYZ should stop them) or probing on any single axis (not necessarily Z).
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Today, a probing move is defined in the path planner as a move that terminates early when all moving axes are blocked. To enable more probe-like scenarios, the path planner API needs to include...
This will enable scenarios like probing to check the correctness of a bed leveling matrix (probe moves are XYZ-moves, but any one axis from XYZ should stop them) or probing on any single axis (not necessarily Z).
The text was updated successfully, but these errors were encountered: