Commit 84edc17c authored by PX4BuildBot's avatar PX4BuildBot

autogenerated headers for rev...

autogenerated headers for rev https://github.com/mavlink/mavlink/tree/0e9bb3e9af13f8b84f09ff3615bf92579b93fe7f
parent e2e18dc2
......@@ -63,7 +63,7 @@ typedef enum MAV_AUTOPILOT
} MAV_AUTOPILOT;
#endif
/** @brief */
/** @brief MAVLINK system type. All components in a system should report this type in their HEARTBEAT. */
#ifndef HAVE_ENUM_MAV_TYPE
#define HAVE_ENUM_MAV_TYPE
typedef enum MAV_TYPE
......
......@@ -6,7 +6,7 @@
MAVPACKED(
typedef struct __mavlink_heartbeat_t {
uint32_t custom_mode; /*< A bitfield for use for autopilot-specific flags*/
uint8_t type; /*< Type of the MAV (quadrotor, helicopter, etc.)*/
uint8_t type; /*< Type of the system (quadrotor, helicopter, etc.). Components use the same type as their associated system.*/
uint8_t autopilot; /*< Autopilot type / class.*/
uint8_t base_mode; /*< System mode bitmap.*/
uint8_t system_status; /*< System status flag.*/
......@@ -56,7 +56,7 @@ typedef struct __mavlink_heartbeat_t {
* @param component_id ID of this component (e.g. 200 for IMU)
* @param msg The MAVLink message to compress the data into
*
* @param type Type of the MAV (quadrotor, helicopter, etc.)
* @param type Type of the system (quadrotor, helicopter, etc.). Components use the same type as their associated system.
* @param autopilot Autopilot type / class.
* @param base_mode System mode bitmap.
* @param custom_mode A bitfield for use for autopilot-specific flags
......@@ -98,7 +98,7 @@ static inline uint16_t mavlink_msg_heartbeat_pack(uint8_t system_id, uint8_t com
* @param component_id ID of this component (e.g. 200 for IMU)
* @param chan The MAVLink channel this message will be sent over
* @param msg The MAVLink message to compress the data into
* @param type Type of the MAV (quadrotor, helicopter, etc.)
* @param type Type of the system (quadrotor, helicopter, etc.). Components use the same type as their associated system.
* @param autopilot Autopilot type / class.
* @param base_mode System mode bitmap.
* @param custom_mode A bitfield for use for autopilot-specific flags
......@@ -166,7 +166,7 @@ static inline uint16_t mavlink_msg_heartbeat_encode_chan(uint8_t system_id, uint
* @brief Send a heartbeat message
* @param chan MAVLink channel to send the message
*
* @param type Type of the MAV (quadrotor, helicopter, etc.)
* @param type Type of the system (quadrotor, helicopter, etc.). Components use the same type as their associated system.
* @param autopilot Autopilot type / class.
* @param base_mode System mode bitmap.
* @param custom_mode A bitfield for use for autopilot-specific flags
......@@ -255,7 +255,7 @@ static inline void mavlink_msg_heartbeat_send_buf(mavlink_message_t *msgbuf, mav
/**
* @brief Get field type from heartbeat message
*
* @return Type of the MAV (quadrotor, helicopter, etc.)
* @return Type of the system (quadrotor, helicopter, etc.). Components use the same type as their associated system.
*/
static inline uint8_t mavlink_msg_heartbeat_get_type(const mavlink_message_t* msg)
{
......
......@@ -67,6 +67,7 @@
</entry>
</enum>
<enum name="MAV_TYPE">
<description>MAVLINK system type. All components in a system should report this type in their HEARTBEAT.</description>
<entry value="0" name="MAV_TYPE_GENERIC">
<description>Generic micro air vehicle.</description>
</entry>
......@@ -3046,8 +3047,8 @@
</enums>
<messages>
<message id="0" name="HEARTBEAT">
<description>The heartbeat message shows that a system is present and responding. The type of the MAV and Autopilot hardware allow the receiving system to treat further messages from this system appropriate (e.g. by laying out the user interface based on the autopilot).</description>
<field type="uint8_t" name="type" enum="MAV_TYPE">Type of the MAV (quadrotor, helicopter, etc.)</field>
<description>The heartbeat message shows that a system or component is present and responding. The type and autopilot fields (along with the message component id), allow the receiving system to treat further messages from this system appropriately (e.g. by laying out the user interface based on the autopilot).</description>
<field type="uint8_t" name="type" enum="MAV_TYPE">Type of the system (quadrotor, helicopter, etc.). Components use the same type as their associated system.</field>
<field type="uint8_t" name="autopilot" enum="MAV_AUTOPILOT">Autopilot type / class.</field>
<field type="uint8_t" name="base_mode" enum="MAV_MODE_FLAG" display="bitmask">System mode bitmap.</field>
<field type="uint32_t" name="custom_mode">A bitfield for use for autopilot-specific flags</field>
......
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