Add parameter support for EKF multi-rotor momentum drag model #17791
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Minor complaint from clang-tidy.
|
|
Will update when PX4/PX4-ECL#1019 is merged |
|
Rebased on master and submodule updated to ecl master. |
dagar
previously approved these changes
Jul 8, 2021
dagar
force-pushed
the
pr-ekf_momentum_drag
branch
from
ba4bbc0
to
9642a05
Compare
dagar
approved these changes
Jul 8, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds the required parameters and parameter documentation changes required for compatibility with the addition of a rotor momentum drag model to the EKF's multi-rotor wind estimator function. See PX4/PX4-ECL#1013 for details. The multi-rotor wind estimation feature remains off by default as before.
TODO: https://docs.px4.io/master/en/advanced_config/tuning_the_ecl_ekf.html#multicopter-wind-estimation-using-drag-specific-forces will also need to be updated in a separate PR