expose hidden BLTOUCH setting changes #22069
Merged
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.
Description
When you enable BLTOUCH, Marlin quietly resets DEACTIVATE_SERVOS_AFTER_MOVE, Z_MIN_PROBE_ENDSTOP_INVERTING and Z_MIN_ENDSTOP_INVERTING to what is needed by the BLTOUCH.
This leads to many user arguments along the lines of "I have Z_MIN_ENDSTOP_INVERTING set true, and BLTOUCH works for me" Immediately followed by a second user says the opposite "I have Z_MIN_ENDSTOP_INVERTING set false, and BLTOUCH works for me" and on and on...
This exposes that Marlin is resetting these defines to what is actually needed by BLTOUCH
Requirements
BLTOUCH and various combinations of DEACTIVATE_SERVOS_AFTER_MOVE, Z_MIN_ENDSTOP_INVERTING and Z_MIN_PROBE_ENDSTOP_INVERTING
Benefits
Less confused users, cleaner Config files that have correct settings.