-
Notifications
You must be signed in to change notification settings - Fork 17.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plane: 4.5.2-beta1 release #26896
Closed
Closed
Plane: 4.5.2-beta1 release #26896
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
we are calling "reached_loiter_target" as part of our checks as to whether to fly home or not. We need to call update_loiter so the L1 controller can update its internal state for the new waypoint which do_RTL has set. Depending on location (but typically), that will mean that L1's reached_loiter_target() will then return false, so we fly home. This bug was affected by f8d7be5 . Any sort of altitude error greater than 10m would delay us entering the landing sequence, allowing the L1 controller to update its state.
Rolf makes a good argument for why some quadplanes need less than 2s
This leads to smoother transitions between RC and GCS control
Co-authored-by: davidsastresas <[email protected]>
Signed-off-by: Ryan Friedman <[email protected]>
* We want to support TCP and UDP in the future, so make sure we call it UDP here Signed-off-by: Ryan Friedman <[email protected]>
* This caused position quantization errors in the MicroStrain7 Signed-off-by: Ryan Friedman <[email protected]>
* Variances vs uncertainties may still be off * Requires enabling the following packets in SensorConnect: * Position Uncertainty (LLH) * Velocity Uncertainty (NED) Signed-off-by: Ryan Friedman <[email protected]>
* If the device hasn't initialized in 5 seconds, give a warning Signed-off-by: Ryan Friedman <[email protected]>
Signed-off-by: Ryan Friedman <[email protected]>
Signed-off-by: Ryan Friedman <[email protected]>
* Add generic health and time utils * Fix bug only checking first GNSS system * Use common logging struct * Improve pre-arm log checks Signed-off-by: Ryan Friedman <[email protected]>
* This allows the backend to report more detailed errors * Before this, many pre-arm errors were hidden by origin failure * If pre-arm could report multiple errors, that would be ideal Signed-off-by: Ryan Friedman <[email protected]>
Signed-off-by: Ryan Friedman <[email protected]>
rmackay9
force-pushed
the
plane-452-beta1
branch
2 times, most recently
from
April 30, 2024 03:55
78f8245
to
4c0cf83
Compare
# Conflicts: # AntennaTracker/ReleaseNotes.txt
rmackay9
force-pushed
the
plane-452-beta1
branch
from
April 30, 2024 03:56
4c0cf83
to
c98bdde
Compare
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 is the Plane equivalent of #26894
The individual PRs included can be seen in the 4.5 Backports project by checking the "Status" for "4.5.2-beta1" entries.
These PRs were not included because I bumped into merge conflicts that I was not confident I would be able to resolve correctly:
I've created this PR because there was a merge conflict in the Plane branch to do with the AntennaTracker's Release Notes.