-
-
Notifications
You must be signed in to change notification settings - Fork 530
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.
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
Provide Autopilot/Server functionality for MAVLink services #1445
Comments
Here is a big list of messages used by MAVSDK in action, telemetry & mission plugins. Parameters required to set health OK in Telemetry:
|
@julianoes: About CAL_GYRO0_ID, CAL_ACC0_ID and CAL_MAG0_ID: wasn't that supposed to be replaced by the so-called "events interface" at some point? Do you know anything about that? |
@JonasVautherin I think the calibration check and the telemetry health flags should be covered by SYS_STATUS. |
It would be exceptionally useful to have MAVSDK provide server functionality for MAVLink microservices.
There is currently a gap missing in MAVLink, the raw data types are provided by the MAVLink headers but the implementation of the microservices (Command, Mission, Heartbeat, Parameters etc) is still up to the user to implement. This can easily lead to fragmentation of the standard with the services. It also makes MAVLink integration into existing systems difficult.
MAVSDK does a good job of tackling this from a GCS/Companion side, but API is not currently suitable for the autopilot side as it was built on the assumption we're communicating with a MAVLink autopilot that implements the services we require. MAVSDK connects as a client.
There is a real case for server implementation in MAVSDK along these lines and MAVSDK could be used as a basis for a MAVLink autopilot. While obviously not for embedded platforms, there are certainly use-cases for this on non-PX4/Ardupilot autopilot systems but also in testing frameworks. In addition MAVSDK could bridge existing autopilot systems with MAVLink.
I propose MAVSDK implement the following plugins:
MISSION_REQUEST_INT
workflow from autopilot side)MAV_CMD_REQUEST_MESSAGE
?MAV_CMD_SET_MESSAGE_INTERVAL
support?)I've recently documented what MAVLink messages + parameters MAVSDK requires in order to function, I can list these as it would probably be a useful starting point for these services.
The text was updated successfully, but these errors were encountered: