autogenerated headers for rev...

autogenerated headers for rev https://github.com/mavlink/mavlink/tree/f9398a1e230754e0dfa4b406b6a3f3b04c2a10ca

common/mavlink_msg_heartbeat.h

@@ -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 system (quadrotor, helicopter, etc.). Components use the same type as their associated system.*/
+ uint8_t type; /*<  Vehicle or component type. For a flight controller component the vehicle type (quadrotor, helicopter, etc.). For other components the component type (e.g. camera, gimbal, etc.). This should be used in preference to component id for identifying the component type.*/
  uint8_t autopilot; /*<  Autopilot type / class. Use MAV_AUTOPILOT_INVALID for components that are not flight controllers.*/
  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 system (quadrotor, helicopter, etc.). Components use the same type as their associated system.
+ * @param type  Vehicle or component type. For a flight controller component the vehicle type (quadrotor, helicopter, etc.). For other components the component type (e.g. camera, gimbal, etc.). This should be used in preference to component id for identifying the component type.
  * @param autopilot  Autopilot type / class. Use MAV_AUTOPILOT_INVALID for components that are not flight controllers.
  * @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 system (quadrotor, helicopter, etc.). Components use the same type as their associated system.
+ * @param type  Vehicle or component type. For a flight controller component the vehicle type (quadrotor, helicopter, etc.). For other components the component type (e.g. camera, gimbal, etc.). This should be used in preference to component id for identifying the component type.
  * @param autopilot  Autopilot type / class. Use MAV_AUTOPILOT_INVALID for components that are not flight controllers.
  * @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 system (quadrotor, helicopter, etc.). Components use the same type as their associated system.
+ * @param type  Vehicle or component type. For a flight controller component the vehicle type (quadrotor, helicopter, etc.). For other components the component type (e.g. camera, gimbal, etc.). This should be used in preference to component id for identifying the component type.
  * @param autopilot  Autopilot type / class. Use MAV_AUTOPILOT_INVALID for components that are not flight controllers.
  * @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 system (quadrotor, helicopter, etc.). Components use the same type as their associated system.
+ * @return  Vehicle or component type. For a flight controller component the vehicle type (quadrotor, helicopter, etc.). For other components the component type (e.g. camera, gimbal, etc.). This should be used in preference to component id for identifying the component type.
  */
 static inline uint8_t mavlink_msg_heartbeat_get_type(const mavlink_message_t* msg)
 {

message_definitions/common.xml

@@ -67,9 +67,9 @@
       </entry>
     </enum>
     <enum name="MAV_TYPE">
-      <description>MAVLINK system type. All components in a system should report this type in their HEARTBEAT.</description>
+      <description>MAVLINK component type reported in HEARTBEAT message. Flight controllers must report the type of the vehicle on which they are mounted (e.g. MAV_TYPE_OCTOROTOR). All other components must report a value appropriate for their type (e.g. a camera must use MAV_TYPE_CAMERA).</description>
       <entry value="0" name="MAV_TYPE_GENERIC">
-        <description>Generic micro air vehicle.</description>
+        <description>Generic micro air vehicle</description>
       </entry>
       <entry value="1" name="MAV_TYPE_FIXED_WING">
         <description>Fixed wing aircraft.</description>
@@ -148,10 +148,10 @@
         <description>VTOL reserved 5</description>
       </entry>
       <entry value="26" name="MAV_TYPE_GIMBAL">
-        <description>Gimbal (standalone)</description>
+        <description>Gimbal</description>
       </entry>
       <entry value="27" name="MAV_TYPE_ADSB">
-        <description>ADSB system (standalone)</description>
+        <description>ADSB system</description>
       </entry>
       <entry value="28" name="MAV_TYPE_PARAFOIL">
         <description>Steerable, nonrigid airfoil</description>
@@ -160,13 +160,16 @@
         <description>Dodecarotor</description>
       </entry>
       <entry value="30" name="MAV_TYPE_CAMERA">
-        <description>Camera (standalone)</description>
+        <description>Camera</description>
       </entry>
       <entry value="31" name="MAV_TYPE_CHARGING_STATION">
         <description>Charging station</description>
       </entry>
       <entry value="32" name="MAV_TYPE_FLARM">
-        <description>FLARM collision avoidance system (standalone)</description>
+        <description>FLARM collision avoidance system</description>
+      </entry>
+      <entry value="33" name="SERVO">
+        <description>Servo</description>
       </entry>
     </enum>
     <enum name="FIRMWARE_VERSION_TYPE">
@@ -3702,7 +3705,7 @@
   <messages>
     <message id="0" name="HEARTBEAT">
       <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). This microservice is documented at https://mavlink.io/en/services/heartbeat.html</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="type" enum="MAV_TYPE">Vehicle or component type. For a flight controller component the vehicle type (quadrotor, helicopter, etc.). For other components the component type (e.g. camera, gimbal, etc.). This should be used in preference to component id for identifying the component type.</field>
       <field type="uint8_t" name="autopilot" enum="MAV_AUTOPILOT">Autopilot type / class. Use MAV_AUTOPILOT_INVALID for components that are not flight controllers.</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>