Skip to content
This repository has been archived by the owner on May 1, 2024. It is now read-only.

EKF allow initializing without baro or mag depending on configuration #931

Merged
merged 1 commit into from
Dec 17, 2020

Conversation

dagar
Copy link
Member

@dagar dagar commented Nov 2, 2020

  • baro only required if EKF2_HGT_MODE barometric pressure LATER
  • mag only required if EKF2_MAG_TYPE Automatic/Magnetic heading/3-axis
  • don't require 2 buffers worth of baro or mag data before initializing
  • relax accel norm requirements

EKF/ekf.cpp Show resolved Hide resolved
@dagar dagar changed the title [WIP]: EKF init allow initializing without baro or mag depending on configuration EKF allow initializing without baro or mag depending on configuration Nov 17, 2020
@dagar dagar marked this pull request as ready for review November 17, 2020 16:46
dagar added a commit to PX4/PX4-Autopilot that referenced this pull request Nov 17, 2020
@dagar
Copy link
Member Author

dagar commented Dec 6, 2020

Conflicts resolved and rebased on current master.

dagar added a commit to PX4/PX4-Autopilot that referenced this pull request Dec 8, 2020
dagar added a commit to PX4/PX4-Autopilot that referenced this pull request Dec 8, 2020
@dagar dagar force-pushed the pr-ekf_init branch 2 times, most recently from e7060fe to 791b5c5 Compare December 8, 2020 23:07
EKF/ekf.cpp Outdated
}

// we use baro height initially and switch to GPS/range/EV finder later when it passes checks.
Copy link
Collaborator

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.

Copy link
Member Author

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.

@dagar dagar force-pushed the pr-ekf_init branch 2 times, most recently from ab3f532 to 7b2e495 Compare December 16, 2020 15:38
 - reduce initial number of required mag and baro samples before init
@dagar
Copy link
Member Author

dagar commented Dec 16, 2020

Let's start with reducing the baro and mag samples and skipping the mag requirement depending on MAG_TYPE. We can come back to vdist_sensor_type later.

@dagar dagar requested review from bresch and priseborough December 16, 2020 15:43
@priseborough priseborough merged commit 398fe15 into master Dec 17, 2020
@priseborough priseborough deleted the pr-ekf_init branch December 17, 2020 08:55
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants