-
-
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
Probe offset wizard: STOW probe and loosen endstops when using PROBE_OFFSET_WIZARD_XY_POS #20414
Merged
sjasonsmith
merged 2 commits into
MarlinFirmware:bugfix-2.0.x
from
FanDjango:PROBE_OFFSET_WIZARD
Dec 11, 2020
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PullRequest #20344 was in draft when merged. So i think it was not tested.
The Idea of PROBE_PT_RAISE was, that there should be a z rise after probing. I didn't realize that PROBE_PT_RAISE excludes a STOW (but it's logic 🙃 ).
I think we should add the following after probing:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Too bad there is no
PROBE_PT_RAISE_STOW
as a combination.I wonder what the tradeoff is in terms of code bytes to create that in
probe.cpp
(couple of bytes only I think). But that code increase would hit everyone that has a probe, and in here it only hits those that activate this functionality. Your thoughts?Also I don't really want to mess around with
probe.cpp
any more in this lifetime.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Z_CLEARANCE_DEPLOY_PROBE
will be used along withPROBE_PT_RAISE_STOW
.Other commands that probe multiple times/points only stow the probe at the end of the entire sequence. They only raise between points. They then provide an argument such as
G29 E
if your probe needs to stow after each probe. This is useful for probes such as solenoids which may overheat if deployed for too long.Some probes require a slow or manual deploy/stow process, so you don't want to actually deploy/stow multiple times.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is an ideal though. This PR doesn't have to wait for a larger rework.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nevermind, I was confusing this with G35. Always looking at code out of context 😉
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@swissnorp I think that capability could make sense. I don't know if it belongs as part of the probe code itself or simply as a move at the end of the wizard. I can imagine there will be someone annoyed and reporting bugs if it were made the behavior after every probe.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@FanDjango I was thinking about the same even before you had posted it. 😄
But I finaly think its not needed.
I realy like the solution you provided in #20439
@sjasonsmith I didn't realize that it was a private function and do_z_clearance would be a better solution because do_z_raise does lift the nozzle even higher with a negative
probe_offset.z
. But I think #20439 is the way to go!Marlin/Marlin/src/module/probe.cpp
Lines 259 to 267 in e817773