Mount: support GIMBAL_MANAGER_INFORMATION message #23587
Merged
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
This was referenced Apr 24, 2023
rmackay9
force-pushed
the
mount-gimbal-manager-information
branch
from
0640932
to
78e0726
Compare
tridge
approved these changes
Apr 25, 2023
peterbarker
approved these changes
Apr 25, 2023
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 support for sending GIMBAL_MANAGER_INFORMATION messages to the ground station. This will allow the upcoming camera/gimbal control screen from @Davidsastresas to better display the available controls to the user.
This has been lightly tested in SITL to confirm that the message is sent in response to a MAV_CMD_REQUEST_MESSAGE. This is possible by typing, "long MAV_CMD_REQUEST_MESSAGE 280" into the MAVProxy console. The results are below.
This has been rebased on PR ArduPilot/mavlink#311