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

EKF2: move handling of invalid range into ECL #12988

Merged
merged 2 commits into from
Sep 19, 2019

Conversation

nicovanduijn
Copy link
Contributor

Rebased version of #12950

The TL;DR is:

  • While the vehicle is on the ground and the distance sensor data is garbage and/or invalid, we use the value of the parameter EKF2_MIN_RNG
  • This was previously done in the EKF2, but has now been moved into ECL, as the former #todo comment suggested
  • Flight test successful, apart from issues unrelated to these changes: https://review.px4.io/plot_app?log=c5c192d0-ae47-4bbc-a8de-2c887bddaf87

priseborough and others added 2 commits September 19, 2019 09:06
The ecl library EKF is able to use vehicle motion and in-air status to better determine when the default on-ground range finder reading can be used.
The description for the EKF2_MIN_RNG parameter has been updated to make its use clearer.
Requires ecl at commit 267195a or later.
* Minimum valid range for the range finder
* Expected range finder reading when on ground.
*
* If the vehicle is on ground, is not moving as determined by the motion test controlled by EKF2_MOVE_TEST and the range finder is returning invalid or no data, then an assumed range value of EKF2_MIN_RNG will be used by the terrain estimator so that a terrain height estimate is avilable at the start of flight in situations where the range finder may be inside its minimum measurements distance when on ground.
Copy link
Contributor

Choose a reason for hiding this comment

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

FYI @hamishwillee , not sure if we have any other documentation on this parameter, but the description was misleading before.

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.

4 participants