Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

MAVLink 2.0 support #41

Open
LorenzMeier opened this issue May 20, 2017 · 2 comments
Open

MAVLink 2.0 support #41

LorenzMeier opened this issue May 20, 2017 · 2 comments

Comments

@LorenzMeier
Copy link

More and more MAVLink functions require 2.0 support, such as e.g. Geofence transfer. It would be great to have this here too.
@LorenzMeier LorenzMeier mentioned this issue May 20, 2017
Merged
@wolkesson
Copy link

Is anyone working on MAVLink 2 support? Seems to be fairly easy to upgrade the lib to the newer version. The problem now is that the latest firmware for PixRacer and QCS both assume Mavlink 2 but can't connect because the ESP module, that is oftentimes delivered with the PixRacer, does not support it.

@dogmaphobic
Copy link
Collaborator

dogmaphobic commented Feb 15, 2018 •
edited

It's been in the todo list for ever. It's not as simple as it sounds. Simple would be to make it "fixed" to V2 (not supporting V1). To support both it's a different story. With that said, I have not had the time to look at any of this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dogmaphobic @LorenzMeier @wolkesson