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: Improved Alignment Control #4554

Merged
merged 9 commits into from
May 19, 2016
Merged

EKF2: Improved Alignment Control #4554

merged 9 commits into from
May 19, 2016

Conversation

priseborough
Copy link
Contributor

Improves control over the initial alignment process. Required to take advantage of PX4/PX4-ECL#134.

Addresses #128 if combined with following tuning parameter changes to take advantage of 'ideal' SITL environment:

EKF2_GBIAS_INIT = 0.01
EKF2_ANGERR_INIT = 0.01

@julianoes
Copy link
Contributor

julianoes commented May 17, 2016

Thanks @priseborough. I tested this with two added commits. The first is to switch back to EKF2 in SITL and the second to use the param values you suggested.

I got the home position init after around 15s which is not instantly but already a big improvement.

@priseborough
Copy link
Contributor Author

priseborough commented May 18, 2016

Was 15sec with the default parameters? That is about how much time it takes to be confident in the angular accuracy given the large switch-on gyro bias uncertainty we allow for (5.7 deg/sec 1-sigma).

priseborough and others added 7 commits May 18, 2016 12:44
adds ability to set initial tilt alignment uncertainty
…le workflow with EKF2 init lag"

This reverts commit 5039661.
The sensors in the SITL environment are near ideal, so the
initialization in ekf2 can happen quicker.
fixes bug that can cause alignment to fail for pitch angles near +-90 deg
Further updates to improve angular alignment consistency
Incorporates big fixes for use of external vision data
@LorenzMeier LorenzMeier merged commit fee5e87 into master May 19, 2016
@LorenzMeier LorenzMeier deleted the pr-ekf2Alignment branch May 19, 2016 07:52
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.

3 participants