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 attempts to explain MPC_COL_PREV_ANG as introduced (and discussed in) PX4/PX4-Autopilot#12561
@jkflying and @baumanta you'll recognise the information and diagrams :-)
What has changed a bit here is that I believe that the angle MPC_COL_PREV_ANG is used for all movement, not just going backwards. So its tuning affects what happens all the time.
The other thing that I've tried to capture here is that when you go forward the distance calculated is based on the minimum distance from the whole set of included sensors. So if you're travelling along a wall and including a sensor, that is the distance, that gets included, not the empty space in front of you.
Anyway, please check I got it right. This was hard to understand and convey.