🚸 Conditional extra clearance in do_move_after_z_homing #27593
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
thinkyhead
force-pushed
the
bf2_fancy_probe_clearance_PR
branch
from
848ed5e to
caaebc9
Compare
thinkyhead
force-pushed
the
bf2_fancy_probe_clearance_PR
branch
from
caaebc9 to
f706c41
Compare
thinkyhead
force-pushed
the
bf2_fancy_probe_clearance_PR
branch
from
f706c41 to
27c4eda
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Apply probe offset clearance after
G28only when the probe is a type that moves and is known (or believed to be) deployed.Use with caution. This should do the right thing. A probe in an alarm state should be stowed, but we need to look for counter-examples.