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

AP_NavEKF3: ignore VelZ of body odometry if SRCn_VELZ is set to None #28548

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Williangalvani
Copy link
Contributor

@Williangalvani Williangalvani commented Nov 7, 2024

This was found by using a dvl which was outputting bad VISION_POSITION_DELTA messages. it was losing locks and outputting bogus (0,0,0) readings fox xyz speed.
Cosuming the bad data caused the baro depth to be somewhat ignored and the vehicle to bounce a lot.

I'm actually not sure of how right this is. is the time of stateStrct the same of bodyOdmDelayed?

Copy link
Contributor

@rmackay9 rmackay9 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for finding this and having the courage to dig into the EKF.

I think though that it would be better to add some arguments to the FuseBodyVel() method which specifies whether XY and/or Z velocities are fused. The reason is that I think there will be some effects on the EKF's estimate fusing the Z-axis even if it is exactly the same as its current estimate. It will probably result in the EKF becoming overly confident of its estimate

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

Successfully merging this pull request may close these issues.

2 participants