ArduPilot / ArduPilot/ardupilot

AP_NavEKF3: EKF ignores rangefinder for terrain estimates if RNGFND1/2 are not configured downward facing

Open
#25,399 1 comment 0 reactions 1 assignee Claimed by @rishabsingh3003 View on GitHub
BUG EKF
Dominant language
C++
Stars
15.9k
Forks
21.4k
Avg merge
3d 17h
Merged PRs (30d)
119

Description

**Issue details**
EKF3 (and probably 2 also) currently ignores rangefinder readings if one of RNGFND1 or 2 _ORIENT is not set to 25 (Downward facing). This means if, for example, RNGFND4_ORIENT = 25 is the first downward-facing rangefinder, the user will not be able to switch to a loiter in an optical-flow-based setup.

This is easily reproducible in SITL. The culprit code is here: https://github.com/ArduPilot/ardupilot/blob/master/libraries/AP_NavEKF3/AP_NavEKF3_Measurements.cpp#L37

**Platform**
[ x ] All
[ ] AntennaTracker
[ ] Copter
[ ] Plane
[ ] Rover
[ ] Submarine

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.