Servers by jDrones

Introducing MAVSDK

MAVSDK is the new name for the “■■■■■■■■■ SDK” (formerly “DroneCore”), the project is now under the MAVLink project umbrella.

Learn about the project and how to contribute :point_right:



I am very happy to see this appening !
I guess now you will be interested in supporting ArduPilot ?

Hello @khancyr!

I am one of the maintainers of MAVSDK. Thanks for the question :slight_smile:!

The goal for MAVSDK is to provide an easy way to interact with MAVLink flight stacks in general, and we would love to have it working with APM! As defined in this RFC, the idea is that MAVSDK would officially support the MAVLink standard set of messages, and at the same time allow specific implementations (I believe that APM has MAVLink dialects that would need to be supported, for instance).

We started an issue specifically for APM a few months ago, and would love to have your insights there!

My first understanding was that the “common” set of messages was implemented by all flight stacks, and that APM had dialects on top of that. But I came to realize that APM does not implement all of common MAVLink. Which is fine: not all stacks need to implement everything.

IMO, it would be super nice if somebody from APM could look at (some) of the features of MAVSDK (say the action, telemetry, and mission plugins) and check what would be required for them to work with APM. Some things may need to be discussed at the MAVLink level (e.g. making the specification stricter), some may need to be changed in MAVSDK (because we develop it against PX4 right now, meaning that we certainly have PX4-specific things there), and some may need to be changed in the flight stack side (be it APM or PX4).

I personally don’t have that kind of understanding yet, so I would love to get insights from the APM community!

What do you think?

What is the current status of MAVSDK with ArduPilot?
Also I am wondering is it possible to design a custom GCS using MAVSDK.

Servers by jDrones