AP_NavEKF3: ignore VelZ of body odometry if SRCn_VELZ is set to None #28548
+4
−1
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 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?