AP_NavEKF3: added two more EK3_OPTION bits #28750
Open
+88
−7
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
tridge
force-pushed
the
pr-ekf3-options
branch
from
80d5db1
to
d090367
Compare
timtuxworth
reviewed
Nov 27, 2024
tridge
force-pushed
the
pr-ekf3-options
branch
from
d090367
to
88c2110
Compare
these allow for easier GPS-denied testing of EKF3, and allows for replay testing without the SetLatLng code being active. Note that the gaps in the bitmask are for pending range beacon features, we don't want to fill in the gaps so that existing replay logs for that feature remain valid
tridge
force-pushed
the
pr-ekf3-options
branch
from
88c2110
to
2d052cd
Compare
|
I wonder why we couldn't just use the EK3 source switching feature? there are 3 slots and you can setup one to not use GPS |
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.
these allow for easier GPS-denied testing of EKF3, and allows for replay testing without the SetLatLng code being active.
Note that the gaps in the bitmask are for pending range beacon features, we don't want to fill in the gaps so that existing replay logs for that feature remain valid