Skip to content
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

EKF: add baro bias estimator using GNSS altitude #17944

Merged
merged 3 commits into from
Jul 19, 2021
Merged

Conversation

bresch
Copy link
Member

@bresch bresch commented Jul 19, 2021

Describe problem solved by this pull request
Barometers develop a bias over time, mainly due to a temperature or a weather change. This can be compensated by estimating the change in offset between another height source that is not affected by the same noise.

Describe your solution
In this PR, the GNSS altitude is used to estimate the bias of the magnetometer using a simple single-state KF.

Additional benefit: this is a requirement for multiple height source fusion (e.g.: GNSS alt + baro)

Test data / coverage
Used for ~1 year on many different drones without issues.

Example SITL test with drifting baro:
EKF2 is using baro as the primary height source but the drift is compensated by the bias estimator introduced in this PR.
DeepinScreenshot_select-area_20210719155037
https://logs.px4.io/plot_app?log=6a4b836d-6bb8-420d-aceb-ccee324f3f4d

@bresch bresch force-pushed the ekf-baro-bias-estimator branch 2 times, most recently from 3b9f9f4 to 885c602 Compare July 19, 2021 14:05
@dagar dagar force-pushed the ekf-baro-bias-estimator branch from 885c602 to 112a28b Compare July 19, 2021 16:15
@dagar dagar merged commit a8e3c46 into master Jul 19, 2021
@dagar dagar deleted the ekf-baro-bias-estimator branch July 19, 2021 20:53
@BazookaJoe1900
Copy link
Member

I have the issue above, but on 1.11?
any idea how to backport that issue? or another workaround on v1.11?

@bresch
Copy link
Member Author

bresch commented Jan 27, 2022

@BazookaJoe1900 You can try to cherry-pick the commits or to re-apply the changes on your code base, but we won't update the v1.11 release with this, it isn't just a bugfix. Otherwise, I would recommend to move to a newest release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants