Updated to function with the changes of MAVSDK 3.0.0 #747
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
julianoes
previously approved these changes
Jan 30, 2025
|
Just some style issues to fix before we can merge it. |
Yeah sorry. I will fix them. |
JonasVautherin
approved these changes
Jan 30, 2025
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.
The Gimbal API changed quite a bit in MAVSDK 3.0.0. This updates the example to work with the new API.
It added multi gimbal support, and almost all calls need a gimbal ID.
set_pitch_and_yaw is removed and I have replaced it with the new set_angles.
It has been test on real hardware, with a PX4 v1.15.2 orange cube and a Gremsy T3v3 and T7.