use Z_PROBE_SPEED instead of HOMING_FEEDRATE_Z to go up for z-probe repetitions #775
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
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.
Currently, HOMING_FEEDRATE_Z is used as speed to retract the nozzle/z-probe between multiple probing repetitions.
However, if a vibration sensitive Z probe is used (such as a piezo sensor) on a delta with a fast Z homing feedrate, the short motion can well fall within the Z_JERK limit, causing an inadvertent triggering of the z-probe at the end of the move due to the momentum of the extruder. Repetier will then trigger an error because it reports the Z probe as not having properly untriggered after moving to back to the probe rest position.
I'd suggest doing this move at Z_PROBE_SPEED instead, since the slower feed rate doesn't really matter at such short distances, and Cartesian printers have a slow Z max. speed anyway. Alternatively, another setting could be introduced, but I think this is a viable compromise.