Commit c3ba3f99 authored by PX4BuildBot's avatar PX4BuildBot

autogenerated headers for rev...

autogenerated headers for rev https://github.com/mavlink/mavlink/tree/5e539462241d8a088619e842c72e8030c134ab0c
parent 077265ae
......@@ -7,7 +7,7 @@
#ifndef MAVLINK_VERSION_H
#define MAVLINK_VERSION_H
#define MAVLINK_BUILD_DATE "Wed Nov 28 2018"
#define MAVLINK_BUILD_DATE "Thu Nov 29 2018"
#define MAVLINK_WIRE_PROTOCOL_VERSION "2.0"
#define MAVLINK_MAX_DIALECT_PAYLOAD_SIZE 255
......
......@@ -7,7 +7,7 @@
#ifndef MAVLINK_VERSION_H
#define MAVLINK_VERSION_H
#define MAVLINK_BUILD_DATE "Wed Nov 28 2018"
#define MAVLINK_BUILD_DATE "Thu Nov 29 2018"
#define MAVLINK_WIRE_PROTOCOL_VERSION "2.0"
#define MAVLINK_MAX_DIALECT_PAYLOAD_SIZE 255
......
......@@ -7,7 +7,7 @@
#ifndef MAVLINK_VERSION_H
#define MAVLINK_VERSION_H
#define MAVLINK_BUILD_DATE "Wed Nov 28 2018"
#define MAVLINK_BUILD_DATE "Thu Nov 29 2018"
#define MAVLINK_WIRE_PROTOCOL_VERSION "2.0"
#define MAVLINK_MAX_DIALECT_PAYLOAD_SIZE 255
......
......@@ -94,7 +94,7 @@ typedef enum MAV_TYPE
MAV_TYPE_VTOL_RESERVED3=23, /* VTOL reserved 3 | */
MAV_TYPE_VTOL_RESERVED4=24, /* VTOL reserved 4 | */
MAV_TYPE_VTOL_RESERVED5=25, /* VTOL reserved 5 | */
MAV_TYPE_GIMBAL=26, /* Onboard gimbal | */
MAV_TYPE_GIMBAL=26, /* Gimbal (standalone) | */
MAV_TYPE_ADSB=27, /* ADSB system (standalone) | */
MAV_TYPE_PARAFOIL=28, /* Steerable, nonrigid airfoil | */
MAV_TYPE_DODECAROTOR=29, /* Dodecarotor | */
......@@ -228,53 +228,54 @@ typedef enum MAV_STATE
} MAV_STATE;
#endif
/** @brief */
/** @brief Component ids (values) for the different types and instances of onboard hardware/software that might make up a MAVLink system (autopilot, cameras, servos, GPS systems, avoidance systems etc.).
Components must use the appropriate ID in their source address when sending messages. Components can also use IDs to determine if they are the intended recipient of an incoming message. The MAV_COMP_ID_ALL value is used to indicate messages that must be processed by all components.
When creating new entries, components that can have multiple instances (e.g. cameras, servos etc.) should be allocated sequential values. An appropriate number of values should be left free after these components to allow the number of instances to be expanded. */
#ifndef HAVE_ENUM_MAV_COMPONENT
#define HAVE_ENUM_MAV_COMPONENT
typedef enum MAV_COMPONENT
{
MAV_COMP_ID_ALL=0, /* | */
MAV_COMP_ID_AUTOPILOT1=1, /* | */
MAV_COMP_ID_CAMERA=100, /* | */
MAV_COMP_ID_CAMERA2=101, /* | */
MAV_COMP_ID_CAMERA3=102, /* | */
MAV_COMP_ID_CAMERA4=103, /* | */
MAV_COMP_ID_CAMERA5=104, /* | */
MAV_COMP_ID_CAMERA6=105, /* | */
MAV_COMP_ID_SERVO1=140, /* | */
MAV_COMP_ID_SERVO2=141, /* | */
MAV_COMP_ID_SERVO3=142, /* | */
MAV_COMP_ID_SERVO4=143, /* | */
MAV_COMP_ID_SERVO5=144, /* | */
MAV_COMP_ID_SERVO6=145, /* | */
MAV_COMP_ID_SERVO7=146, /* | */
MAV_COMP_ID_SERVO8=147, /* | */
MAV_COMP_ID_SERVO9=148, /* | */
MAV_COMP_ID_SERVO10=149, /* | */
MAV_COMP_ID_SERVO11=150, /* | */
MAV_COMP_ID_SERVO12=151, /* | */
MAV_COMP_ID_SERVO13=152, /* | */
MAV_COMP_ID_SERVO14=153, /* | */
MAV_COMP_ID_GIMBAL=154, /* | */
MAV_COMP_ID_LOG=155, /* | */
MAV_COMP_ID_ADSB=156, /* | */
MAV_COMP_ID_OSD=157, /* On Screen Display (OSD) devices for video links | */
MAV_COMP_ID_PERIPHERAL=158, /* Generic autopilot peripheral component ID. Meant for devices that do not implement the parameter sub-protocol | */
MAV_COMP_ID_QX1_GIMBAL=159, /* | */
MAV_COMP_ID_FLARM=160, /* | */
MAV_COMP_ID_MAPPER=180, /* | */
MAV_COMP_ID_MISSIONPLANNER=190, /* | */
MAV_COMP_ID_PATHPLANNER=195, /* | */
MAV_COMP_ID_OBSTACLE_AVOIDANCE=196, /* | */
MAV_COMP_ID_VISUAL_INERTIAL_ODOMETRY=197, /* | */
MAV_COMP_ID_IMU=200, /* | */
MAV_COMP_ID_IMU_2=201, /* | */
MAV_COMP_ID_IMU_3=202, /* | */
MAV_COMP_ID_GPS=220, /* | */
MAV_COMP_ID_GPS2=221, /* | */
MAV_COMP_ID_UDP_BRIDGE=240, /* | */
MAV_COMP_ID_UART_BRIDGE=241, /* | */
MAV_COMP_ID_SYSTEM_CONTROL=250, /* | */
MAV_COMP_ID_ALL=0, /* Used to broadcast messages to all components of the receiving system. Components should attempt to process messages with this component ID and forward to components on any other interfaces. | */
MAV_COMP_ID_AUTOPILOT1=1, /* System flight controller component ("autopilot"). Only one autopilot is expected in a particular system. | */
MAV_COMP_ID_CAMERA=100, /* Camera #1. | */
MAV_COMP_ID_CAMERA2=101, /* Camera #2. | */
MAV_COMP_ID_CAMERA3=102, /* Camera #3. | */
MAV_COMP_ID_CAMERA4=103, /* Camera #4. | */
MAV_COMP_ID_CAMERA5=104, /* Camera #5. | */
MAV_COMP_ID_CAMERA6=105, /* Camera #6. | */
MAV_COMP_ID_SERVO1=140, /* Servo #1. | */
MAV_COMP_ID_SERVO2=141, /* Servo #2. | */
MAV_COMP_ID_SERVO3=142, /* Servo #3. | */
MAV_COMP_ID_SERVO4=143, /* Servo #4. | */
MAV_COMP_ID_SERVO5=144, /* Servo #5. | */
MAV_COMP_ID_SERVO6=145, /* Servo #6. | */
MAV_COMP_ID_SERVO7=146, /* Servo #7. | */
MAV_COMP_ID_SERVO8=147, /* Servo #8. | */
MAV_COMP_ID_SERVO9=148, /* Servo #9. | */
MAV_COMP_ID_SERVO10=149, /* Servo #10. | */
MAV_COMP_ID_SERVO11=150, /* Servo #11. | */
MAV_COMP_ID_SERVO12=151, /* Servo #12. | */
MAV_COMP_ID_SERVO13=152, /* Servo #13. | */
MAV_COMP_ID_SERVO14=153, /* Servo #14. | */
MAV_COMP_ID_GIMBAL=154, /* Gimbal component. | */
MAV_COMP_ID_LOG=155, /* Logging component. | */
MAV_COMP_ID_ADSB=156, /* Automatic Dependent Surveillance-Broadcast (ADS-B) component. | */
MAV_COMP_ID_OSD=157, /* On Screen Display (OSD) devices for video links. | */
MAV_COMP_ID_PERIPHERAL=158, /* Generic autopilot peripheral component ID. Meant for devices that do not implement the parameter microservice. | */
MAV_COMP_ID_QX1_GIMBAL=159, /* Gimbal ID for QX1. | */
MAV_COMP_ID_FLARM=160, /* FLARM collision alert component. | */
MAV_COMP_ID_MISSIONPLANNER=190, /* Component that supports the Mission microservice. | */
MAV_COMP_ID_PATHPLANNER=195, /* Component that finds an optimal path between points based on a certain constraint (e.g. minimum snap, shortest path, cost, etc.). | */
MAV_COMP_ID_OBSTACLE_AVOIDANCE=196, /* Component that plans a collision free path between two points. | */
MAV_COMP_ID_VISUAL_INERTIAL_ODOMETRY=197, /* Component that provides position estimates using VIO techniques. | */
MAV_COMP_ID_IMU=200, /* Inertial Measurement Unit (IMU) #1. | */
MAV_COMP_ID_IMU_2=201, /* Inertial Measurement Unit (IMU) #2. | */
MAV_COMP_ID_IMU_3=202, /* Inertial Measurement Unit (IMU) #3. | */
MAV_COMP_ID_GPS=220, /* GPS #1. | */
MAV_COMP_ID_GPS2=221, /* GPS #2. | */
MAV_COMP_ID_UDP_BRIDGE=240, /* Component to bridge MAVLink to UDP (i.e. from a UART). | */
MAV_COMP_ID_UART_BRIDGE=241, /* Component to bridge to UART (i.e. from UDP). | */
MAV_COMP_ID_SYSTEM_CONTROL=250, /* Component for handling system messages (e.g. to ARM, takeoff, etc.). | */
MAV_COMPONENT_ENUM_END=251, /* | */
} MAV_COMPONENT;
#endif
......
......@@ -7,7 +7,7 @@
#ifndef MAVLINK_VERSION_H
#define MAVLINK_VERSION_H
#define MAVLINK_BUILD_DATE "Wed Nov 28 2018"
#define MAVLINK_BUILD_DATE "Thu Nov 29 2018"
#define MAVLINK_WIRE_PROTOCOL_VERSION "2.0"
#define MAVLINK_MAX_DIALECT_PAYLOAD_SIZE 255
......
......@@ -7,7 +7,7 @@
#ifndef MAVLINK_VERSION_H
#define MAVLINK_VERSION_H
#define MAVLINK_BUILD_DATE "Wed Nov 28 2018"
#define MAVLINK_BUILD_DATE "Thu Nov 29 2018"
#define MAVLINK_WIRE_PROTOCOL_VERSION "2.0"
#define MAVLINK_MAX_DIALECT_PAYLOAD_SIZE 255
......
......@@ -7,7 +7,7 @@
#ifndef MAVLINK_VERSION_H
#define MAVLINK_VERSION_H
#define MAVLINK_BUILD_DATE "Wed Nov 28 2018"
#define MAVLINK_BUILD_DATE "Thu Nov 29 2018"
#define MAVLINK_WIRE_PROTOCOL_VERSION "2.0"
#define MAVLINK_MAX_DIALECT_PAYLOAD_SIZE 255
......
......@@ -148,7 +148,7 @@
<description>VTOL reserved 5</description>
</entry>
<entry value="26" name="MAV_TYPE_GIMBAL">
<description>Onboard gimbal</description>
<description>Gimbal (standalone)</description>
</entry>
<entry value="27" name="MAV_TYPE_ADSB">
<description>ADSB system (standalone)</description>
......@@ -369,131 +369,133 @@
</entry>
</enum>
<enum name="MAV_COMPONENT">
<description>Component ids (values) for the different types and instances of onboard hardware/software that might make up a MAVLink system (autopilot, cameras, servos, GPS systems, avoidance systems etc.).
Components must use the appropriate ID in their source address when sending messages. Components can also use IDs to determine if they are the intended recipient of an incoming message. The MAV_COMP_ID_ALL value is used to indicate messages that must be processed by all components.
When creating new entries, components that can have multiple instances (e.g. cameras, servos etc.) should be allocated sequential values. An appropriate number of values should be left free after these components to allow the number of instances to be expanded.</description>
<entry value="0" name="MAV_COMP_ID_ALL">
<description/>
<description>Used to broadcast messages to all components of the receiving system. Components should attempt to process messages with this component ID and forward to components on any other interfaces.</description>
</entry>
<entry value="1" name="MAV_COMP_ID_AUTOPILOT1">
<description/>
<description>System flight controller component ("autopilot"). Only one autopilot is expected in a particular system.</description>
</entry>
<entry value="100" name="MAV_COMP_ID_CAMERA">
<description/>
<description>Camera #1.</description>
</entry>
<entry value="101" name="MAV_COMP_ID_CAMERA2">
<description/>
<description>Camera #2.</description>
</entry>
<entry value="102" name="MAV_COMP_ID_CAMERA3">
<description/>
<description>Camera #3.</description>
</entry>
<entry value="103" name="MAV_COMP_ID_CAMERA4">
<description/>
<description>Camera #4.</description>
</entry>
<entry value="104" name="MAV_COMP_ID_CAMERA5">
<description/>
<description>Camera #5.</description>
</entry>
<entry value="105" name="MAV_COMP_ID_CAMERA6">
<description/>
<description>Camera #6.</description>
</entry>
<entry value="140" name="MAV_COMP_ID_SERVO1">
<description/>
<description>Servo #1.</description>
</entry>
<entry value="141" name="MAV_COMP_ID_SERVO2">
<description/>
<description>Servo #2.</description>
</entry>
<entry value="142" name="MAV_COMP_ID_SERVO3">
<description/>
<description>Servo #3.</description>
</entry>
<entry value="143" name="MAV_COMP_ID_SERVO4">
<description/>
<description>Servo #4.</description>
</entry>
<entry value="144" name="MAV_COMP_ID_SERVO5">
<description/>
<description>Servo #5.</description>
</entry>
<entry value="145" name="MAV_COMP_ID_SERVO6">
<description/>
<description>Servo #6.</description>
</entry>
<entry value="146" name="MAV_COMP_ID_SERVO7">
<description/>
<description>Servo #7.</description>
</entry>
<entry value="147" name="MAV_COMP_ID_SERVO8">
<description/>
<description>Servo #8.</description>
</entry>
<entry value="148" name="MAV_COMP_ID_SERVO9">
<description/>
<description>Servo #9.</description>
</entry>
<entry value="149" name="MAV_COMP_ID_SERVO10">
<description/>
<description>Servo #10.</description>
</entry>
<entry value="150" name="MAV_COMP_ID_SERVO11">
<description/>
<description>Servo #11.</description>
</entry>
<entry value="151" name="MAV_COMP_ID_SERVO12">
<description/>
<description>Servo #12.</description>
</entry>
<entry value="152" name="MAV_COMP_ID_SERVO13">
<description/>
<description>Servo #13.</description>
</entry>
<entry value="153" name="MAV_COMP_ID_SERVO14">
<description/>
<description>Servo #14.</description>
</entry>
<entry value="154" name="MAV_COMP_ID_GIMBAL">
<description/>
<description>Gimbal component.</description>
</entry>
<entry value="155" name="MAV_COMP_ID_LOG">
<description/>
<description>Logging component.</description>
</entry>
<entry value="156" name="MAV_COMP_ID_ADSB">
<description/>
<description>Automatic Dependent Surveillance-Broadcast (ADS-B) component.</description>
</entry>
<entry value="157" name="MAV_COMP_ID_OSD">
<description>On Screen Display (OSD) devices for video links</description>
<description>On Screen Display (OSD) devices for video links.</description>
</entry>
<entry value="158" name="MAV_COMP_ID_PERIPHERAL">
<description>Generic autopilot peripheral component ID. Meant for devices that do not implement the parameter sub-protocol</description>
<description>Generic autopilot peripheral component ID. Meant for devices that do not implement the parameter microservice.</description>
</entry>
<entry value="159" name="MAV_COMP_ID_QX1_GIMBAL">
<description/>
<deprecated since="2018-11" replaced_by="MAV_COMP_ID_GIMBAL">All gimbals should use MAV_COMP_ID_GIMBAL.</deprecated>
<description>Gimbal ID for QX1.</description>
</entry>
<entry value="160" name="MAV_COMP_ID_FLARM">
<description/>
</entry>
<entry value="180" name="MAV_COMP_ID_MAPPER">
<description/>
<description>FLARM collision alert component.</description>
</entry>
<entry value="190" name="MAV_COMP_ID_MISSIONPLANNER">
<description/>
<description>Component that supports the Mission microservice.</description>
</entry>
<entry value="195" name="MAV_COMP_ID_PATHPLANNER">
<description/>
<description>Component that finds an optimal path between points based on a certain constraint (e.g. minimum snap, shortest path, cost, etc.).</description>
</entry>
<entry value="196" name="MAV_COMP_ID_OBSTACLE_AVOIDANCE">
<description/>
<description>Component that plans a collision free path between two points.</description>
</entry>
<entry value="197" name="MAV_COMP_ID_VISUAL_INERTIAL_ODOMETRY">
<description/>
<description>Component that provides position estimates using VIO techniques.</description>
</entry>
<entry value="200" name="MAV_COMP_ID_IMU">
<description/>
<description>Inertial Measurement Unit (IMU) #1.</description>
</entry>
<entry value="201" name="MAV_COMP_ID_IMU_2">
<description/>
<description>Inertial Measurement Unit (IMU) #2.</description>
</entry>
<entry value="202" name="MAV_COMP_ID_IMU_3">
<description/>
<description>Inertial Measurement Unit (IMU) #3.</description>
</entry>
<entry value="220" name="MAV_COMP_ID_GPS">
<description/>
<description>GPS #1.</description>
</entry>
<entry value="221" name="MAV_COMP_ID_GPS2">
<description/>
<description>GPS #2.</description>
</entry>
<entry value="240" name="MAV_COMP_ID_UDP_BRIDGE">
<description/>
<description>Component to bridge MAVLink to UDP (i.e. from a UART).</description>
</entry>
<entry value="241" name="MAV_COMP_ID_UART_BRIDGE">
<description/>
<description>Component to bridge to UART (i.e. from UDP).</description>
</entry>
<entry value="250" name="MAV_COMP_ID_SYSTEM_CONTROL">
<description/>
<deprecated since="2018-11" replaced_by="MAV_COMP_ID_ALL">System control does not require a separate component ID.</deprecated>
<description>Component for handling system messages (e.g. to ARM, takeoff, etc.).</description>
</entry>
</enum>
<enum name="MAV_SYS_STATUS_SENSOR">
......
......@@ -7,7 +7,7 @@
#ifndef MAVLINK_VERSION_H
#define MAVLINK_VERSION_H
#define MAVLINK_BUILD_DATE "Wed Nov 28 2018"
#define MAVLINK_BUILD_DATE "Thu Nov 29 2018"
#define MAVLINK_WIRE_PROTOCOL_VERSION "2.0"
#define MAVLINK_MAX_DIALECT_PAYLOAD_SIZE 9
......
......@@ -7,7 +7,7 @@
#ifndef MAVLINK_VERSION_H
#define MAVLINK_VERSION_H
#define MAVLINK_BUILD_DATE "Wed Nov 28 2018"
#define MAVLINK_BUILD_DATE "Thu Nov 29 2018"
#define MAVLINK_WIRE_PROTOCOL_VERSION "2.0"
#define MAVLINK_MAX_DIALECT_PAYLOAD_SIZE 255
......
......@@ -7,7 +7,7 @@
#ifndef MAVLINK_VERSION_H
#define MAVLINK_VERSION_H
#define MAVLINK_BUILD_DATE "Wed Nov 28 2018"
#define MAVLINK_BUILD_DATE "Thu Nov 29 2018"
#define MAVLINK_WIRE_PROTOCOL_VERSION "2.0"
#define MAVLINK_MAX_DIALECT_PAYLOAD_SIZE 255
......
......@@ -7,7 +7,7 @@
#ifndef MAVLINK_VERSION_H
#define MAVLINK_VERSION_H
#define MAVLINK_BUILD_DATE "Wed Nov 28 2018"
#define MAVLINK_BUILD_DATE "Thu Nov 29 2018"
#define MAVLINK_WIRE_PROTOCOL_VERSION "2.0"
#define MAVLINK_MAX_DIALECT_PAYLOAD_SIZE 179
......
......@@ -7,7 +7,7 @@
#ifndef MAVLINK_VERSION_H
#define MAVLINK_VERSION_H
#define MAVLINK_BUILD_DATE "Wed Nov 28 2018"
#define MAVLINK_BUILD_DATE "Thu Nov 29 2018"
#define MAVLINK_WIRE_PROTOCOL_VERSION "2.0"
#define MAVLINK_MAX_DIALECT_PAYLOAD_SIZE 255
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment