Using DETECTOR_SAFE_DISTANCE instead ot ROBOT_MIN_DISTANCE #394
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.
Vestigial ROBOT_MIN_DISTANCE and ROBOT_DISTANCE_TOLERANCE config variables removed.
First config variable used only in
runDCQueue()to set the detz_out governor value which in other places in the codebase is set by DETECTOR_SAFE_DISTANCE. It was noticed because AMX has 180 mm as safe distance but ROBOT_MIN_DISTANCE would override that under certain conditionsROBOT_DISTANCE_TOLERANCE is not used anywhere in the code