Updated MAVLink C library and fixed issue with mocap#956
Merged
Conversation
irsdkv
approved these changes
Jan 16, 2020
JonasVautherin
approved these changes
Jan 16, 2020
Collaborator
|
Thanks Timmy! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
To continue my work on microservice versioning (See PX4/PX4-Autopilot#13565 and mavlink/qgroundcontrol#8065), I need to use my own custom MAVLink C library. However, the latest MAVLink message definition adds a new field to a message. I have updated MAVSDK to cope with this, and also updated to the latest MAVLink C library.