Get desktop application:
View/edit binary Protocol Buffers messages
Enable direct MAVLink communication using libmav from a server component. Unlike MavlinkDirect, this does not require a discovered system: it sends from the local server component, which makes it suitable for broadcasting messages (e.g. as an autopilot or custom component) without a connected counterpart.
Load custom MAVLink message definitions from XML. This allows loading custom MAVLink message definitions at runtime, extending the available message types beyond the built-in definitions.
The custom MAVLink XML definition content
Send a MAVLink message directly. This allows sending any MAVLink message with full control over the message content. Leave target_system_id and target_component_id at 0 to broadcast.
The MAVLink message to send
Subscribe to incoming commands with a given command ID. Delivers COMMAND_LONG and COMMAND_INT messages with this command ID that are addressed to this server component; check message_name to see which one it is. While subscribed, MAVSDK does not ack the command itself, so every command received must be answered by sending a COMMAND_ACK with SendMessage, addressed to the sender (system_id/component_id of the received command) and with "command" set to the command ID. For a command that takes a while, send acks with MAV_RESULT_IN_PROGRESS and "progress" in percent (255 if unknown) about once per second while it runs, so the sender knows it is still going, then the final result. The sender may retransmit the command if the ack is lost, so the same command can arrive more than once.
MAV_CMD to subscribe to
The received COMMAND_LONG or COMMAND_INT
Subscribe to incoming MAVLink messages. This provides direct access to incoming MAVLink messages. Use an empty string in message_name to subscribe to all messages, or specify a message name (e.g., "HEARTBEAT") to filter for specific message types. Unlike the MavlinkDirect (client) plugin, this is not scoped to a single system: it receives matching messages from all systems.
MAVLink message name to filter for (e.g., "HEARTBEAT"), empty string = all messages
The received MAVLink message
Result type.
Used in: ,
Result enum value
Human-readable English string describing the result
Possible results returned for action requests.
Used in:
Unknown result
Request succeeded
Error
Invalid MAVLink message
Invalid field name or value
Connection error
No system connected
Request timed out
A complete MAVLink message with all header information and fields
Used in: , ,
MAVLink message name (e.g., "HEARTBEAT", "GLOBAL_POSITION_INT")
System ID of the sender (for received messages)
Component ID of the sender (for received messages)
Target system ID (for sending, 0 for broadcast)
Target component ID (for sending, 0 for broadcast)
All message fields as single JSON object