#include <mavlink_msg_v2_extension.h>

Data Fields
uint16_t	message_type
	A code that identifies the software component that understands this message (analogous to usb device classes or mime type strings). If this code is less than 32768, it is considered a 'registered' protocol extension and the corresponding entry should be added to https://github.com/mavlink/mavlink/extension-message-ids.xml. Software creators can register blocks of message IDs as needed (useful for GCS specific metadata, etc...). Message_types greater than 32767 are considered local experiments and should not be checked in to any widely distributed codebase. More...

uint8_t	target_network
	Network ID (0 for broadcast) More...

uint8_t	target_system
	System ID (0 for broadcast) More...

uint8_t	target_component
	Component ID (0 for broadcast) More...

uint8_t	payload [249]
	Variable length payload. The length is defined by the remaining message length when subtracting the header and other fields. The entire content of this block is opaque unless you understand any the encoding message_type. The particular encoding used can be extension specific and might not always be documented as part of the mavlink specification. More...

Field Documentation

uint16_t __mavlink_v2_extension_t::message_type

A code that identifies the software component that understands this message (analogous to usb device classes or mime type strings). If this code is less than 32768, it is considered a 'registered' protocol extension and the corresponding entry should be added to https://github.com/mavlink/mavlink/extension-message-ids.xml. Software creators can register blocks of message IDs as needed (useful for GCS specific metadata, etc...). Message_types greater than 32767 are considered local experiments and should not be checked in to any widely distributed codebase.

uint8_t __mavlink_v2_extension_t::payload[249]

Variable length payload. The length is defined by the remaining message length when subtracting the header and other fields. The entire content of this block is opaque unless you understand any the encoding message_type. The particular encoding used can be extension specific and might not always be documented as part of the mavlink specification.

uint8_t __mavlink_v2_extension_t::target_component

Component ID (0 for broadcast)

uint8_t __mavlink_v2_extension_t::target_network

Network ID (0 for broadcast)

uint8_t __mavlink_v2_extension_t::target_system

System ID (0 for broadcast)

The documentation for this struct was generated from the following file:

src/main/mavlink/common/mavlink_msg_v2_extension.h

Data Fields

Field Documentation