GCS_MAVLink: add support for MAV_CMD_EKF_SOURCE_SET #18345
Merged
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 support for the new MAV_CMD_EKF_SOURCE_SET command that allows external systems to set the active EKF sensor source set.
This has been tested in SITL and works. I think the only question is whether we want the mavlink command to accept the source set in the range 1 to 3 (to match the parameters) or 0 to 2 (to match the ahrs interface). Currently it is implemented in the 1 to 3 range.
MAVLink PR ArduPilot/mavlink#220 should be merged first.
This resolves the "add support for switching source via MAVLink" item in issue #15859
Below is a screen shot of the SITL test with some extra debug added.
![ekf-source-set-sitl-test](https://user-images.githubusercontent.com/1498098/129516099-b4bb8b23-2233-47fc-9993-1acc721d8c10.png)