Rover: 4.3 navigation tuning advice #4679
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
yuri-rage
reviewed
Oct 20, 2022
yuri-rage
reviewed
Oct 20, 2022
rmackay9
force-pushed
the
rover-nav-tune
branch
from
303e2c7
to
a0b3856
Compare
|
Updated with fixes after peer review, thanks! |
|
very nice....will try this weekend...merging |
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.
This moves the existing navigation page (for 4.2 and earlier) to a new page and replaces the existing page with updated advice for 4.3's S-Curves and Position Controller based navigation
I've tested this on my local machine and it seems OK.