ROMFS: Update Solo EKF2 tuning defaults to increase GPS glitch resistance #18
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.
Updates to achieve equivalent GPS velocity innovations to EKF1. This is required to ensure that equivalence in GPs glitch detection levels are achieved. The default values from upstream are set to accomodate IMU installations with increased resistance to the effects of aliasing and clipping, however this comes at the expense of increased susceptibility to GPS glitches.
These revised values have been tuned using a flight log with significant GPS glitch events. The following innovation sequences are from a replay of the flight log using both EKF1 and EKF2 + revised tuning for the section of log where the GPS glitches occurred.
With the default tuning EKF2 follows the GPS glitch more than EKF1 with innovation levels during the glitch being half.
This tuning is a compromise between handling IMU and GPS errors, however GPS glitch events have been historically much more common in support tickets than IMU data quality problems.