-
Notifications
You must be signed in to change notification settings - Fork 509
EKF allow initializing without baro or mag depending on configuration #931
Conversation
Conflicts resolved and rebased on current master. |
e7060fe
to
791b5c5
Compare
EKF/ekf.cpp
Outdated
} | ||
|
||
// we use baro height initially and switch to GPS/range/EV finder later when it passes checks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What happens if those other sensors are not providing data at the time of alignment, eg delayed GPS lock? i on't think the EKF will handle this well. We cannot merge this until the implications of these sensor not being available at alignment has been tested. We should be delaying alignment until the nominated height sensor is returning data that passes quality checks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That makes sense, I'll see if that's a viable change.
ab3f532
to
7b2e495
Compare
- reduce initial number of required mag and baro samples before init
Let's start with reducing the baro and mag samples and skipping the mag requirement depending on MAG_TYPE. We can come back to |
baro only required if EKF2_HGT_MODE barometric pressureLATER