@aircast-4g/mavlink 1.1.3 → 1.1.6

package/dist/dialects/ardupilotmega/types.d.ts

@@ -1,2833 +0,0 @@
-// Auto-generated TypeScript types for ardupilotmega dialect
-// Generated from MAVLink XML definitions
-
-export interface MAVLinkMessage<Content = unknown> {
-  timestamp: number;
-  system_id: number;
-  component_id: number;
-  type: string;
-  payload: Content;
-}
-
-// Micro air vehicle / autopilot classes. This identifies the individual model.
-export type MAV_AUTOPILOT =
-  | 0 // MAV_AUTOPILOT_GENERIC - Generic autopilot, full support for everything
-  | 1 // MAV_AUTOPILOT_RESERVED - Reserved for future use.
-  | 2 // MAV_AUTOPILOT_SLUGS - SLUGS autopilot, http://slugsuav.soe.ucsc.edu
-  | 3 // MAV_AUTOPILOT_ARDUPILOTMEGA - ArduPilot - Plane/Copter/Rover/Sub/Tracker, https://ardupilot.org
-  | 4 // MAV_AUTOPILOT_OPENPILOT - OpenPilot, http://openpilot.org
-  | 5 // MAV_AUTOPILOT_GENERIC_WAYPOINTS_ONLY - Generic autopilot only supporting simple waypoints
-  | 6 // MAV_AUTOPILOT_GENERIC_WAYPOINTS_AND_SIMPLE_NAVIGATION_ONLY - Generic autopilot supporting waypoints and other simple navigation commands
-  | 7 // MAV_AUTOPILOT_GENERIC_MISSION_FULL - Generic autopilot supporting the full mission command set
-  | 8 // MAV_AUTOPILOT_INVALID - No valid autopilot, e.g. a GCS or other MAVLink component
-  | 9 // MAV_AUTOPILOT_PPZ - PPZ UAV - http://nongnu.org/paparazzi
-  | 10 // MAV_AUTOPILOT_UDB - UAV Dev Board
-  | 11 // MAV_AUTOPILOT_FP - FlexiPilot
-  | 12 // MAV_AUTOPILOT_PX4 - PX4 Autopilot - http://px4.io/
-  | 13 // MAV_AUTOPILOT_SMACCMPILOT - SMACCMPilot - http://smaccmpilot.org
-  | 14 // MAV_AUTOPILOT_AUTOQUAD - AutoQuad -- http://autoquad.org
-  | 15 // MAV_AUTOPILOT_ARMAZILA - Armazila -- http://armazila.com
-  | 16 // MAV_AUTOPILOT_AEROB - Aerob -- http://aerob.ru
-  | 17 // MAV_AUTOPILOT_ASLUAV - ASLUAV autopilot -- http://www.asl.ethz.ch
-  | 18 // MAV_AUTOPILOT_SMARTAP - SmartAP Autopilot - http://sky-drones.com
-  | 19 // MAV_AUTOPILOT_AIRRAILS - AirRails - http://uaventure.com
-  | 20 // MAV_AUTOPILOT_REFLEX - Fusion Reflex - https://fusion.engineering
-  | number;
-
-// 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).
-export type MAV_TYPE =
-  | 0 // MAV_TYPE_GENERIC - Generic micro air vehicle
-  | 1 // MAV_TYPE_FIXED_WING - Fixed wing aircraft.
-  | 2 // MAV_TYPE_QUADROTOR - Quadrotor
-  | 3 // MAV_TYPE_COAXIAL - Coaxial helicopter
-  | 4 // MAV_TYPE_HELICOPTER - Normal helicopter with tail rotor.
-  | 5 // MAV_TYPE_ANTENNA_TRACKER - Ground installation
-  | 6 // MAV_TYPE_GCS - Operator control unit / ground control station
-  | 7 // MAV_TYPE_AIRSHIP - Airship, controlled
-  | 8 // MAV_TYPE_FREE_BALLOON - Free balloon, uncontrolled
-  | 9 // MAV_TYPE_ROCKET - Rocket
-  | 10 // MAV_TYPE_GROUND_ROVER - Ground rover
-  | 11 // MAV_TYPE_SURFACE_BOAT - Surface vessel, boat, ship
-  | 12 // MAV_TYPE_SUBMARINE - Submarine
-  | 13 // MAV_TYPE_HEXAROTOR - Hexarotor
-  | 14 // MAV_TYPE_OCTOROTOR - Octorotor
-  | 15 // MAV_TYPE_TRICOPTER - Tricopter
-  | 16 // MAV_TYPE_FLAPPING_WING - Flapping wing
-  | 17 // MAV_TYPE_KITE - Kite
-  | 18 // MAV_TYPE_ONBOARD_CONTROLLER - Onboard companion controller
-  | 19 // MAV_TYPE_VTOL_TAILSITTER_DUOROTOR - Two-rotor Tailsitter VTOL that additionally uses control surfaces in vertical operation. Note, value previously named MAV_TYPE_VTOL_DUOROTOR.
-  | 20 // MAV_TYPE_VTOL_TAILSITTER_QUADROTOR - Quad-rotor Tailsitter VTOL using a V-shaped quad config in vertical operation. Note: value previously named MAV_TYPE_VTOL_QUADROTOR.
-  | 21 // MAV_TYPE_VTOL_TILTROTOR - Tiltrotor VTOL. Fuselage and wings stay (nominally) horizontal in all flight phases. It able to tilt (some) rotors to provide thrust in cruise flight.
-  | 22 // MAV_TYPE_VTOL_FIXEDROTOR - VTOL with separate fixed rotors for hover and cruise flight. Fuselage and wings stay (nominally) horizontal in all flight phases.
-  | 23 // MAV_TYPE_VTOL_TAILSITTER - Tailsitter VTOL. Fuselage and wings orientation changes depending on flight phase: vertical for hover, horizontal for cruise. Use more specific VTOL MAV_TYPE_VTOL_TAILSITTER_DUOROTOR or MAV_TYPE_VTOL_TAILSITTER_QUADROTOR if appropriate.
-  | 24 // MAV_TYPE_VTOL_TILTWING - Tiltwing VTOL. Fuselage stays horizontal in all flight phases. The whole wing, along with any attached engine, can tilt between vertical and horizontal mode.
-  | 25 // MAV_TYPE_VTOL_RESERVED5 - VTOL reserved 5
-  | 26 // MAV_TYPE_GIMBAL - Gimbal
-  | 27 // MAV_TYPE_ADSB - ADSB system
-  | 28 // MAV_TYPE_PARAFOIL - Steerable, nonrigid airfoil
-  | 29 // MAV_TYPE_DODECAROTOR - Dodecarotor
-  | 30 // MAV_TYPE_CAMERA - Camera
-  | 31 // MAV_TYPE_CHARGING_STATION - Charging station
-  | 32 // MAV_TYPE_FLARM - FLARM collision avoidance system
-  | 33 // MAV_TYPE_SERVO - Servo
-  | 34 // MAV_TYPE_ODID - Open Drone ID. See https://mavlink.io/en/services/opendroneid.html.
-  | 35 // MAV_TYPE_DECAROTOR - Decarotor
-  | 36 // MAV_TYPE_BATTERY - Battery
-  | 37 // MAV_TYPE_PARACHUTE - Parachute
-  | 38 // MAV_TYPE_LOG - Log
-  | 39 // MAV_TYPE_OSD - OSD
-  | 40 // MAV_TYPE_IMU - IMU
-  | 41 // MAV_TYPE_GPS - GPS
-  | 42 // MAV_TYPE_WINCH - Winch
-  | 43 // MAV_TYPE_GENERIC_MULTIROTOR - Generic multirotor that does not fit into a specific type or whose type is unknown
-  | 44 // MAV_TYPE_ILLUMINATOR - Illuminator. An illuminator is a light source that is used for lighting up dark areas external to the system: e.g. a torch or searchlight (as opposed to a light source for illuminating the system itself, e.g. an indicator light).
-  | 45 // MAV_TYPE_SPACECRAFT_ORBITER - Orbiter spacecraft. Includes satellites orbiting terrestrial and extra-terrestrial bodies. Follows NASA Spacecraft Classification.
-  | 46 // MAV_TYPE_GROUND_QUADRUPED - A generic four-legged ground vehicle (e.g., a robot dog).
-  | 47 // MAV_TYPE_VTOL_GYRODYNE - VTOL hybrid of helicopter and autogyro. It has a main rotor for lift and separate propellers for forward flight. The rotor must be powered for hover but can autorotate in cruise flight. See: https://en.wikipedia.org/wiki/Gyrodyne
-  | 48 // MAV_TYPE_GRIPPER - Gripper
-  | number;
-
-// These flags encode the MAV mode, see MAV_MODE enum for useful combinations.
-export type MAV_MODE_FLAG =
-  | 128 // MAV_MODE_FLAG_SAFETY_ARMED - 0b10000000 MAV safety set to armed. Motors are enabled / running / can start. Ready to fly. Additional note: this flag is to be ignore when sent in the command MAV_CMD_DO_SET_MODE and MAV_CMD_COMPONENT_ARM_DISARM shall be used instead. The flag can still be used to report the armed state.
-  | 64 // MAV_MODE_FLAG_MANUAL_INPUT_ENABLED - 0b01000000 remote control input is enabled.
-  | 32 // MAV_MODE_FLAG_HIL_ENABLED - 0b00100000 hardware in the loop simulation. All motors / actuators are blocked, but internal software is full operational.
-  | 16 // MAV_MODE_FLAG_STABILIZE_ENABLED - 0b00010000 system stabilizes electronically its attitude (and optionally position). It needs however further control inputs to move around.
-  | 8 // MAV_MODE_FLAG_GUIDED_ENABLED - 0b00001000 guided mode enabled, system flies waypoints / mission items.
-  | 4 // MAV_MODE_FLAG_AUTO_ENABLED - 0b00000100 autonomous mode enabled, system finds its own goal positions. Guided flag can be set or not, depends on the actual implementation.
-  | 2 // MAV_MODE_FLAG_TEST_ENABLED - 0b00000010 system has a test mode enabled. This flag is intended for temporary system tests and should not be used for stable implementations.
-  | 1 // MAV_MODE_FLAG_CUSTOM_MODE_ENABLED - 0b00000001 system-specific custom mode is enabled. When using this flag to enable a custom mode all other flags should be ignored.
-  | number;
-
-// These values encode the bit positions of the decode position. These values can be used to read the value of a flag bit by combining the base_mode variable with AND with the flag position value. The result will be either 0 or 1, depending on if the flag is set or not.
-export type MAV_MODE_FLAG_DECODE_POSITION =
-  | 128 // MAV_MODE_FLAG_DECODE_POSITION_SAFETY - First bit:  10000000
-  | 64 // MAV_MODE_FLAG_DECODE_POSITION_MANUAL - Second bit: 01000000
-  | 32 // MAV_MODE_FLAG_DECODE_POSITION_HIL - Third bit:  00100000
-  | 16 // MAV_MODE_FLAG_DECODE_POSITION_STABILIZE - Fourth bit: 00010000
-  | 8 // MAV_MODE_FLAG_DECODE_POSITION_GUIDED - Fifth bit:  00001000
-  | 4 // MAV_MODE_FLAG_DECODE_POSITION_AUTO - Sixth bit:   00000100
-  | 2 // MAV_MODE_FLAG_DECODE_POSITION_TEST - Seventh bit: 00000010
-  | 1 // MAV_MODE_FLAG_DECODE_POSITION_CUSTOM_MODE - Eighth bit: 00000001
-  | number;
-
-export type MAV_STATE =
-  | 0 // MAV_STATE_UNINIT - Uninitialized system, state is unknown.
-  | 1 // MAV_STATE_BOOT - System is booting up.
-  | 2 // MAV_STATE_CALIBRATING - System is calibrating and not flight-ready.
-  | 3 // MAV_STATE_STANDBY - System is grounded and on standby. It can be launched any time.
-  | 4 // MAV_STATE_ACTIVE - System is active and might be already airborne. Motors are engaged.
-  | 5 // MAV_STATE_CRITICAL - System is in a non-normal flight mode (failsafe). It can however still navigate.
-  | 6 // MAV_STATE_EMERGENCY - System is in a non-normal flight mode (failsafe). It lost control over parts or over the whole airframe. It is in mayday and going down.
-  | 7 // MAV_STATE_POWEROFF - System just initialized its power-down sequence, will shut down now.
-  | 8 // MAV_STATE_FLIGHT_TERMINATION - System is terminating itself (failsafe or commanded).
-  | number;
-
-// Legacy component ID values for particular types of hardware/software that might make up a MAVLink system (autopilot, cameras, servos, avoidance systems etc.).
-// Components are not required or expected to use IDs with names that correspond to their type or function, but may choose to do so.
-// Using an ID that matches the type may slightly reduce the chances of component id clashes, as, for historical reasons, it is less likely to be used by some other type of component.
-// System integration will still need to ensure that all components have unique IDs.
-// Component IDs are used for addressing messages to a particular component within a system.
-// A component can use any unique ID between 1 and 255 (MAV_COMP_ID_ALL value is the broadcast address, used to send to all components).
-// Historically component ID were also used for identifying the type of component.
-// New code must not use component IDs to infer the component type, but instead check the MAV_TYPE in the HEARTBEAT message!
-export type MAV_COMPONENT =
-  | 0 // MAV_COMP_ID_ALL - Target id (target_component) 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. Note: This is not a valid *source* component id for a message.
-  | 1 // MAV_COMP_ID_AUTOPILOT1 - System flight controller component (&quot;autopilot&quot;). Only one autopilot is expected in a particular system.
-  | 25 // MAV_COMP_ID_USER1 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 26 // MAV_COMP_ID_USER2 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 27 // MAV_COMP_ID_USER3 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 28 // MAV_COMP_ID_USER4 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 29 // MAV_COMP_ID_USER5 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 30 // MAV_COMP_ID_USER6 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 31 // MAV_COMP_ID_USER7 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 32 // MAV_COMP_ID_USER8 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 33 // MAV_COMP_ID_USER9 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 34 // MAV_COMP_ID_USER10 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 35 // MAV_COMP_ID_USER11 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 36 // MAV_COMP_ID_USER12 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 37 // MAV_COMP_ID_USER13 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 38 // MAV_COMP_ID_USER14 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 39 // MAV_COMP_ID_USER15 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 40 // MAV_COMP_ID_USER16 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 41 // MAV_COMP_ID_USER17 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 42 // MAV_COMP_ID_USER18 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 43 // MAV_COMP_ID_USER19 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 44 // MAV_COMP_ID_USER20 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 45 // MAV_COMP_ID_USER21 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 46 // MAV_COMP_ID_USER22 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 47 // MAV_COMP_ID_USER23 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 48 // MAV_COMP_ID_USER24 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 49 // MAV_COMP_ID_USER25 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 50 // MAV_COMP_ID_USER26 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 51 // MAV_COMP_ID_USER27 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 52 // MAV_COMP_ID_USER28 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 53 // MAV_COMP_ID_USER29 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 54 // MAV_COMP_ID_USER30 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 55 // MAV_COMP_ID_USER31 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 56 // MAV_COMP_ID_USER32 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 57 // MAV_COMP_ID_USER33 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 58 // MAV_COMP_ID_USER34 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 59 // MAV_COMP_ID_USER35 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 60 // MAV_COMP_ID_USER36 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 61 // MAV_COMP_ID_USER37 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 62 // MAV_COMP_ID_USER38 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 63 // MAV_COMP_ID_USER39 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 64 // MAV_COMP_ID_USER40 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 65 // MAV_COMP_ID_USER41 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 66 // MAV_COMP_ID_USER42 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 67 // MAV_COMP_ID_USER43 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 68 // MAV_COMP_ID_TELEMETRY_RADIO - Telemetry radio (e.g. SiK radio, or other component that emits RADIO_STATUS messages).
-  | 69 // MAV_COMP_ID_USER45 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 70 // MAV_COMP_ID_USER46 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 71 // MAV_COMP_ID_USER47 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 72 // MAV_COMP_ID_USER48 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 73 // MAV_COMP_ID_USER49 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 74 // MAV_COMP_ID_USER50 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 75 // MAV_COMP_ID_USER51 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 76 // MAV_COMP_ID_USER52 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 77 // MAV_COMP_ID_USER53 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 78 // MAV_COMP_ID_USER54 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 79 // MAV_COMP_ID_USER55 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 80 // MAV_COMP_ID_USER56 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 81 // MAV_COMP_ID_USER57 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 82 // MAV_COMP_ID_USER58 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 83 // MAV_COMP_ID_USER59 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 84 // MAV_COMP_ID_USER60 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 85 // MAV_COMP_ID_USER61 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 86 // MAV_COMP_ID_USER62 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 87 // MAV_COMP_ID_USER63 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 88 // MAV_COMP_ID_USER64 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 89 // MAV_COMP_ID_USER65 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 90 // MAV_COMP_ID_USER66 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 91 // MAV_COMP_ID_USER67 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 92 // MAV_COMP_ID_USER68 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 93 // MAV_COMP_ID_USER69 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 94 // MAV_COMP_ID_USER70 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 95 // MAV_COMP_ID_USER71 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 96 // MAV_COMP_ID_USER72 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 97 // MAV_COMP_ID_USER73 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 98 // MAV_COMP_ID_USER74 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 99 // MAV_COMP_ID_USER75 - Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.
-  | 100 // MAV_COMP_ID_CAMERA - Camera #1.
-  | 101 // MAV_COMP_ID_CAMERA2 - Camera #2.
-  | 102 // MAV_COMP_ID_CAMERA3 - Camera #3.
-  | 103 // MAV_COMP_ID_CAMERA4 - Camera #4.
-  | 104 // MAV_COMP_ID_CAMERA5 - Camera #5.
-  | 105 // MAV_COMP_ID_CAMERA6 - Camera #6.
-  | 140 // MAV_COMP_ID_SERVO1 - Servo #1.
-  | 141 // MAV_COMP_ID_SERVO2 - Servo #2.
-  | 142 // MAV_COMP_ID_SERVO3 - Servo #3.
-  | 143 // MAV_COMP_ID_SERVO4 - Servo #4.
-  | 144 // MAV_COMP_ID_SERVO5 - Servo #5.
-  | 145 // MAV_COMP_ID_SERVO6 - Servo #6.
-  | 146 // MAV_COMP_ID_SERVO7 - Servo #7.
-  | 147 // MAV_COMP_ID_SERVO8 - Servo #8.
-  | 148 // MAV_COMP_ID_SERVO9 - Servo #9.
-  | 149 // MAV_COMP_ID_SERVO10 - Servo #10.
-  | 150 // MAV_COMP_ID_SERVO11 - Servo #11.
-  | 151 // MAV_COMP_ID_SERVO12 - Servo #12.
-  | 152 // MAV_COMP_ID_SERVO13 - Servo #13.
-  | 153 // MAV_COMP_ID_SERVO14 - Servo #14.
-  | 154 // MAV_COMP_ID_GIMBAL - Gimbal #1.
-  | 155 // MAV_COMP_ID_LOG - Logging component.
-  | 156 // MAV_COMP_ID_ADSB - Automatic Dependent Surveillance-Broadcast (ADS-B) component.
-  | 157 // MAV_COMP_ID_OSD - On Screen Display (OSD) devices for video links.
-  | 158 // MAV_COMP_ID_PERIPHERAL - Generic autopilot peripheral component ID. Meant for devices that do not implement the parameter microservice.
-  | 159 // MAV_COMP_ID_QX1_GIMBAL - Gimbal ID for QX1.
-  | 160 // MAV_COMP_ID_FLARM - FLARM collision alert component.
-  | 161 // MAV_COMP_ID_PARACHUTE - Parachute component.
-  | 169 // MAV_COMP_ID_WINCH - Winch component.
-  | 171 // MAV_COMP_ID_GIMBAL2 - Gimbal #2.
-  | 172 // MAV_COMP_ID_GIMBAL3 - Gimbal #3.
-  | 173 // MAV_COMP_ID_GIMBAL4 - Gimbal #4
-  | 174 // MAV_COMP_ID_GIMBAL5 - Gimbal #5.
-  | 175 // MAV_COMP_ID_GIMBAL6 - Gimbal #6.
-  | 180 // MAV_COMP_ID_BATTERY - Battery #1.
-  | 181 // MAV_COMP_ID_BATTERY2 - Battery #2.
-  | 189 // MAV_COMP_ID_MAVCAN - CAN over MAVLink client.
-  | 190 // MAV_COMP_ID_MISSIONPLANNER - Component that can generate/supply a mission flight plan (e.g. GCS or developer API).
-  | 191 // MAV_COMP_ID_ONBOARD_COMPUTER - Component that lives on the onboard computer (companion computer) and has some generic functionalities, such as settings system parameters and monitoring the status of some processes that don&#x27;t directly speak mavlink and so on.
-  | 192 // MAV_COMP_ID_ONBOARD_COMPUTER2 - Component that lives on the onboard computer (companion computer) and has some generic functionalities, such as settings system parameters and monitoring the status of some processes that don&#x27;t directly speak mavlink and so on.
-  | 193 // MAV_COMP_ID_ONBOARD_COMPUTER3 - Component that lives on the onboard computer (companion computer) and has some generic functionalities, such as settings system parameters and monitoring the status of some processes that don&#x27;t directly speak mavlink and so on.
-  | 194 // MAV_COMP_ID_ONBOARD_COMPUTER4 - Component that lives on the onboard computer (companion computer) and has some generic functionalities, such as settings system parameters and monitoring the status of some processes that don&#x27;t directly speak mavlink and so on.
-  | 195 // MAV_COMP_ID_PATHPLANNER - Component that finds an optimal path between points based on a certain constraint (e.g. minimum snap, shortest path, cost, etc.).
-  | 196 // MAV_COMP_ID_OBSTACLE_AVOIDANCE - Component that plans a collision free path between two points.
-  | 197 // MAV_COMP_ID_VISUAL_INERTIAL_ODOMETRY - Component that provides position estimates using VIO techniques.
-  | 198 // MAV_COMP_ID_PAIRING_MANAGER - Component that manages pairing of vehicle and GCS.
-  | 200 // MAV_COMP_ID_IMU - Inertial Measurement Unit (IMU) #1.
-  | 201 // MAV_COMP_ID_IMU_2 - Inertial Measurement Unit (IMU) #2.
-  | 202 // MAV_COMP_ID_IMU_3 - Inertial Measurement Unit (IMU) #3.
-  | 220 // MAV_COMP_ID_GPS - GPS #1.
-  | 221 // MAV_COMP_ID_GPS2 - GPS #2.
-  | 236 // MAV_COMP_ID_ODID_TXRX_1 - Open Drone ID transmitter/receiver (Bluetooth/WiFi/Internet).
-  | 237 // MAV_COMP_ID_ODID_TXRX_2 - Open Drone ID transmitter/receiver (Bluetooth/WiFi/Internet).
-  | 238 // MAV_COMP_ID_ODID_TXRX_3 - Open Drone ID transmitter/receiver (Bluetooth/WiFi/Internet).
-  | 240 // MAV_COMP_ID_UDP_BRIDGE - Component to bridge MAVLink to UDP (i.e. from a UART).
-  | 241 // MAV_COMP_ID_UART_BRIDGE - Component to bridge to UART (i.e. from UDP).
-  | 242 // MAV_COMP_ID_TUNNEL_NODE - Component handling TUNNEL messages (e.g. vendor specific GUI of a component).
-  | 243 // MAV_COMP_ID_ILLUMINATOR - Illuminator
-  | 250 // MAV_COMP_ID_SYSTEM_CONTROL - Deprecated, don&#x27;t use. Component for handling system messages (e.g. to ARM, takeoff, etc.).
-  | number;
-
-// Enum used to indicate true or false (also: success or failure, enabled or disabled, active or inactive).
-export type BOOL =
-  | 0 // BOOL_FALSE - False.
-  | 1 // BOOL_TRUE - True.
-  | number;
-
-// These values define the type of firmware release.  These values indicate the first version or release of this type.  For example the first alpha release would be 64, the second would be 65.
-export type FIRMWARE_VERSION_TYPE =
-  | 0 // FIRMWARE_VERSION_TYPE_DEV - development release
-  | 64 // FIRMWARE_VERSION_TYPE_ALPHA - alpha release
-  | 128 // FIRMWARE_VERSION_TYPE_BETA - beta release
-  | 192 // FIRMWARE_VERSION_TYPE_RC - release candidate
-  | 255 // FIRMWARE_VERSION_TYPE_OFFICIAL - official stable release
-  | number;
-
-// Flags to report failure cases over the high latency telemetry.
-export type HL_FAILURE_FLAG =
-  | 1 // HL_FAILURE_FLAG_GPS - GPS failure.
-  | 2 // HL_FAILURE_FLAG_DIFFERENTIAL_PRESSURE - Differential pressure sensor failure.
-  | 4 // HL_FAILURE_FLAG_ABSOLUTE_PRESSURE - Absolute pressure sensor failure.
-  | 8 // HL_FAILURE_FLAG_3D_ACCEL - Accelerometer sensor failure.
-  | 16 // HL_FAILURE_FLAG_3D_GYRO - Gyroscope sensor failure.
-  | 32 // HL_FAILURE_FLAG_3D_MAG - Magnetometer sensor failure.
-  | 64 // HL_FAILURE_FLAG_TERRAIN - Terrain subsystem failure.
-  | 128 // HL_FAILURE_FLAG_BATTERY - Battery failure/critical low battery.
-  | 256 // HL_FAILURE_FLAG_RC_RECEIVER - RC receiver failure/no RC connection.
-  | 512 // HL_FAILURE_FLAG_OFFBOARD_LINK - Offboard link failure.
-  | 1024 // HL_FAILURE_FLAG_ENGINE - Engine failure.
-  | 2048 // HL_FAILURE_FLAG_GEOFENCE - Geofence violation.
-  | 4096 // HL_FAILURE_FLAG_ESTIMATOR - Estimator failure, for example measurement rejection or large variances.
-  | 8192 // HL_FAILURE_FLAG_MISSION - Mission failure.
-  | number;
-
-// Actions that may be specified in MAV_CMD_OVERRIDE_GOTO to override mission execution.
-export type MAV_GOTO =
-  | 0 // MAV_GOTO_DO_HOLD - Hold at the current position.
-  | 1 // MAV_GOTO_DO_CONTINUE - Continue with the next item in mission execution.
-  | 2 // MAV_GOTO_HOLD_AT_CURRENT_POSITION - Hold at the current position of the system
-  | 3 // MAV_GOTO_HOLD_AT_SPECIFIED_POSITION - Hold at the position specified in the parameters of the DO_HOLD action
-  | number;
-
-// Predefined OR-combined MAV_MODE_FLAG values. These can simplify using the flags when setting modes. Note that manual input is enabled in all modes as a safety override.
-export type MAV_MODE =
-  | 0 // MAV_MODE_PREFLIGHT - System is not ready to fly, booting, calibrating, etc. No flag is set.
-  | 80 // MAV_MODE_STABILIZE_DISARMED - System is allowed to be active, under assisted RC control (MAV_MODE_FLAG_SAFETY_ARMED, MAV_MODE_FLAG_STABILIZE_ENABLED)
-  | 208 // MAV_MODE_STABILIZE_ARMED - System is allowed to be active, under assisted RC control (MAV_MODE_FLAG_SAFETY_ARMED, MAV_MODE_FLAG_MANUAL_INPUT_ENABLED, MAV_MODE_FLAG_STABILIZE_ENABLED)
-  | 64 // MAV_MODE_MANUAL_DISARMED - System is allowed to be active, under manual (RC) control, no stabilization (MAV_MODE_FLAG_MANUAL_INPUT_ENABLED)
-  | 192 // MAV_MODE_MANUAL_ARMED - System is allowed to be active, under manual (RC) control, no stabilization (MAV_MODE_FLAG_SAFETY_ARMED, MAV_MODE_FLAG_MANUAL_INPUT_ENABLED)
-  | 88 // MAV_MODE_GUIDED_DISARMED - System is allowed to be active, under autonomous control, manual setpoint (MAV_MODE_FLAG_SAFETY_ARMED, MAV_MODE_FLAG_STABILIZE_ENABLED, MAV_MODE_FLAG_GUIDED_ENABLED)
-  | 216 // MAV_MODE_GUIDED_ARMED - System is allowed to be active, under autonomous control, manual setpoint (MAV_MODE_FLAG_SAFETY_ARMED, MAV_MODE_FLAG_MANUAL_INPUT_ENABLED, MAV_MODE_FLAG_STABILIZE_ENABLED, MAV_MODE_FLAG_GUIDED_ENABLED)
-  | 92 // MAV_MODE_AUTO_DISARMED - System is allowed to be active, under autonomous control and navigation (the trajectory is decided onboard and not pre-programmed by waypoints). (MAV_MODE_FLAG_SAFETY_ARMED, MAV_MODE_FLAG_STABILIZE_ENABLED, MAV_MODE_FLAG_GUIDED_ENABLED, MAV_MODE_FLAG_AUTO_ENABLED).
-  | 220 // MAV_MODE_AUTO_ARMED - System is allowed to be active, under autonomous control and navigation (the trajectory is decided onboard and not pre-programmed by waypoints). (MAV_MODE_FLAG_SAFETY_ARMED, MAV_MODE_FLAG_MANUAL_INPUT_ENABLED, MAV_MODE_FLAG_STABILIZE_ENABLED, MAV_MODE_FLAG_GUIDED_ENABLED,MAV_MODE_FLAG_AUTO_ENABLED).
-  | 66 // MAV_MODE_TEST_DISARMED - UNDEFINED mode. This solely depends on the autopilot - use with caution, intended for developers only. (MAV_MODE_FLAG_MANUAL_INPUT_ENABLED, MAV_MODE_FLAG_TEST_ENABLED).
-  | 194 // MAV_MODE_TEST_ARMED - UNDEFINED mode. This solely depends on the autopilot - use with caution, intended for developers only (MAV_MODE_FLAG_SAFETY_ARMED, MAV_MODE_FLAG_MANUAL_INPUT_ENABLED, MAV_MODE_FLAG_TEST_ENABLED)
-  | number;
-
-// These encode the sensors whose status is sent as part of the SYS_STATUS message.
-export type MAV_SYS_STATUS_SENSOR =
-  | 1 // MAV_SYS_STATUS_SENSOR_3D_GYRO - 0x01 3D gyro
-  | 2 // MAV_SYS_STATUS_SENSOR_3D_ACCEL - 0x02 3D accelerometer
-  | 4 // MAV_SYS_STATUS_SENSOR_3D_MAG - 0x04 3D magnetometer
-  | 8 // MAV_SYS_STATUS_SENSOR_ABSOLUTE_PRESSURE - 0x08 absolute pressure
-  | 16 // MAV_SYS_STATUS_SENSOR_DIFFERENTIAL_PRESSURE - 0x10 differential pressure
-  | 32 // MAV_SYS_STATUS_SENSOR_GPS - 0x20 GPS
-  | 64 // MAV_SYS_STATUS_SENSOR_OPTICAL_FLOW - 0x40 optical flow
-  | 128 // MAV_SYS_STATUS_SENSOR_VISION_POSITION - 0x80 computer vision position
-  | 256 // MAV_SYS_STATUS_SENSOR_LASER_POSITION - 0x100 laser based position
-  | 512 // MAV_SYS_STATUS_SENSOR_EXTERNAL_GROUND_TRUTH - 0x200 external ground truth (Vicon or Leica)
-  | 1024 // MAV_SYS_STATUS_SENSOR_ANGULAR_RATE_CONTROL - 0x400 3D angular rate control
-  | 2048 // MAV_SYS_STATUS_SENSOR_ATTITUDE_STABILIZATION - 0x800 attitude stabilization
-  | 4096 // MAV_SYS_STATUS_SENSOR_YAW_POSITION - 0x1000 yaw position
-  | 8192 // MAV_SYS_STATUS_SENSOR_Z_ALTITUDE_CONTROL - 0x2000 z/altitude control
-  | 16384 // MAV_SYS_STATUS_SENSOR_XY_POSITION_CONTROL - 0x4000 x/y position control
-  | 32768 // MAV_SYS_STATUS_SENSOR_MOTOR_OUTPUTS - 0x8000 motor outputs / control
-  | 65536 // MAV_SYS_STATUS_SENSOR_RC_RECEIVER - 0x10000 RC receiver
-  | 131072 // MAV_SYS_STATUS_SENSOR_3D_GYRO2 - 0x20000 2nd 3D gyro
-  | 262144 // MAV_SYS_STATUS_SENSOR_3D_ACCEL2 - 0x40000 2nd 3D accelerometer
-  | 524288 // MAV_SYS_STATUS_SENSOR_3D_MAG2 - 0x80000 2nd 3D magnetometer
-  | 1048576 // MAV_SYS_STATUS_GEOFENCE - 0x100000 geofence
-  | 2097152 // MAV_SYS_STATUS_AHRS - 0x200000 AHRS subsystem health
-  | 4194304 // MAV_SYS_STATUS_TERRAIN - 0x400000 Terrain subsystem health
-  | 8388608 // MAV_SYS_STATUS_REVERSE_MOTOR - 0x800000 Motors are reversed
-  | 16777216 // MAV_SYS_STATUS_LOGGING - 0x1000000 Logging
-  | 33554432 // MAV_SYS_STATUS_SENSOR_BATTERY - 0x2000000 Battery
-  | 67108864 // MAV_SYS_STATUS_SENSOR_PROXIMITY - 0x4000000 Proximity
-  | 134217728 // MAV_SYS_STATUS_SENSOR_SATCOM - 0x8000000 Satellite Communication
-  | 268435456 // MAV_SYS_STATUS_PREARM_CHECK - 0x10000000 pre-arm check status. Always healthy when armed
-  | 536870912 // MAV_SYS_STATUS_OBSTACLE_AVOIDANCE - 0x20000000 Avoidance/collision prevention
-  | 1073741824 // MAV_SYS_STATUS_SENSOR_PROPULSION - 0x40000000 propulsion (actuator, esc, motor or propellor)
-  | 2147483648 // MAV_SYS_STATUS_EXTENSION_USED - 0x80000000 Extended bit-field are used for further sensor status bits (needs to be set in onboard_control_sensors_present only)
-  | number;
-
-// These encode the sensors whose status is sent as part of the SYS_STATUS message in the extended fields.
-export type MAV_SYS_STATUS_SENSOR_EXTENDED =
-  | 1 // MAV_SYS_STATUS_RECOVERY_SYSTEM - 0x01 Recovery system (parachute, balloon, retracts etc)
-  | number;
-
-// Coordinate frames used by MAVLink. Not all frames are supported by all commands, messages, or vehicles.
-// Global frames use the following naming conventions:
-// - &quot;GLOBAL&quot;: Global coordinate frame with WGS84 latitude/longitude and altitude positive over mean sea level (MSL) by default.
-// The following modifiers may be used with &quot;GLOBAL&quot;:
-// - &quot;RELATIVE_ALT&quot;: Altitude is relative to the vehicle home position rather than MSL.
-// - &quot;TERRAIN_ALT&quot;: Altitude is relative to ground level rather than MSL.
-// - &quot;INT&quot;: Latitude/longitude (in degrees) are scaled by multiplying by 1E7.
-// Local frames use the following naming conventions:
-// - &quot;LOCAL&quot;: Origin of local frame is fixed relative to earth. Unless otherwise specified this origin is the origin of the vehicle position-estimator (&quot;EKF&quot;).
-// - &quot;BODY&quot;: Origin of local frame travels with the vehicle. NOTE, &quot;BODY&quot; does NOT indicate alignment of frame axis with vehicle attitude.
-// - &quot;OFFSET&quot;: Deprecated synonym for &quot;BODY&quot; (origin travels with the vehicle). Not to be used for new frames.
-// Some deprecated frames do not follow these conventions (e.g. MAV_FRAME_BODY_NED and MAV_FRAME_BODY_OFFSET_NED).
-export type MAV_FRAME =
-  | 0 // MAV_FRAME_GLOBAL - Global (WGS84) coordinate frame + altitude relative to mean sea level (MSL).
-  | 1 // MAV_FRAME_LOCAL_NED - NED local tangent frame (x: North, y: East, z: Down) with origin fixed relative to earth.
-  | 2 // MAV_FRAME_MISSION - NOT a coordinate frame, indicates a mission command.
-  | 3 // MAV_FRAME_GLOBAL_RELATIVE_ALT - Global (WGS84) coordinate frame + altitude relative to the home position.
-  | 4 // MAV_FRAME_LOCAL_ENU - ENU local tangent frame (x: East, y: North, z: Up) with origin fixed relative to earth.
-  | 5 // MAV_FRAME_GLOBAL_INT - Global (WGS84) coordinate frame (scaled) + altitude relative to mean sea level (MSL).
-  | 6 // MAV_FRAME_GLOBAL_RELATIVE_ALT_INT - Global (WGS84) coordinate frame (scaled) + altitude relative to the home position.
-  | 7 // MAV_FRAME_LOCAL_OFFSET_NED - NED local tangent frame (x: North, y: East, z: Down) with origin that travels with the vehicle.
-  | 8 // MAV_FRAME_BODY_NED - Same as MAV_FRAME_LOCAL_NED when used to represent position values. Same as MAV_FRAME_BODY_FRD when used with velocity/acceleration values.
-  | 9 // MAV_FRAME_BODY_OFFSET_NED - This is the same as MAV_FRAME_BODY_FRD.
-  | 10 // MAV_FRAME_GLOBAL_TERRAIN_ALT - Global (WGS84) coordinate frame with AGL altitude (altitude at ground level).
-  | 11 // MAV_FRAME_GLOBAL_TERRAIN_ALT_INT - Global (WGS84) coordinate frame (scaled) with AGL altitude (altitude at ground level).
-  | 12 // MAV_FRAME_BODY_FRD - FRD local frame aligned to the vehicle&#x27;s attitude (x: Forward, y: Right, z: Down) with an origin that travels with vehicle.
-  | 13 // MAV_FRAME_RESERVED_13 - MAV_FRAME_BODY_FLU - Body fixed frame of reference, Z-up (x: Forward, y: Left, z: Up).
-  | 14 // MAV_FRAME_RESERVED_14 - MAV_FRAME_MOCAP_NED - Odometry local coordinate frame of data given by a motion capture system, Z-down (x: North, y: East, z: Down).
-  | 15 // MAV_FRAME_RESERVED_15 - MAV_FRAME_MOCAP_ENU - Odometry local coordinate frame of data given by a motion capture system, Z-up (x: East, y: North, z: Up).
-  | 16 // MAV_FRAME_RESERVED_16 - MAV_FRAME_VISION_NED - Odometry local coordinate frame of data given by a vision estimation system, Z-down (x: North, y: East, z: Down).
-  | 17 // MAV_FRAME_RESERVED_17 - MAV_FRAME_VISION_ENU - Odometry local coordinate frame of data given by a vision estimation system, Z-up (x: East, y: North, z: Up).
-  | 18 // MAV_FRAME_RESERVED_18 - MAV_FRAME_ESTIM_NED - Odometry local coordinate frame of data given by an estimator running onboard the vehicle, Z-down (x: North, y: East, z: Down).
-  | 19 // MAV_FRAME_RESERVED_19 - MAV_FRAME_ESTIM_ENU - Odometry local coordinate frame of data given by an estimator running onboard the vehicle, Z-up (x: East, y: North, z: Up).
-  | 20 // MAV_FRAME_LOCAL_FRD - FRD local tangent frame (x: Forward, y: Right, z: Down) with origin fixed relative to earth. The forward axis is aligned to the front of the vehicle in the horizontal plane.
-  | 21 // MAV_FRAME_LOCAL_FLU - FLU local tangent frame (x: Forward, y: Left, z: Up) with origin fixed relative to earth. The forward axis is aligned to the front of the vehicle in the horizontal plane.
-  | number;
-
-export type MAVLINK_DATA_STREAM_TYPE =
-  | 0
-  | 1
-  | 2
-  | 3
-  | 4
-  | 5
-  | number;
-
-export type FENCE_BREACH =
-  | 0 // FENCE_BREACH_NONE - No last fence breach
-  | 1 // FENCE_BREACH_MINALT - Breached minimum altitude
-  | 2 // FENCE_BREACH_MAXALT - Breached maximum altitude
-  | 3 // FENCE_BREACH_BOUNDARY - Breached fence boundary
-  | number;
-
-// Actions being taken to mitigate/prevent fence breach
-export type FENCE_MITIGATE =
-  | 0 // FENCE_MITIGATE_UNKNOWN - Unknown
-  | 1 // FENCE_MITIGATE_NONE - No actions being taken
-  | 2 // FENCE_MITIGATE_VEL_LIMIT - Velocity limiting active to prevent breach
-  | number;
-
-// Fence types to enable or disable when using MAV_CMD_DO_FENCE_ENABLE.
-// Note that at least one of these flags must be set in MAV_CMD_DO_FENCE_ENABLE.param2.
-// If none are set, the flight stack will ignore the field and enable/disable its default set of fences (usually all of them).
-export type FENCE_TYPE =
-  | 1 // FENCE_TYPE_ALT_MAX - Maximum altitude fence
-  | 2 // FENCE_TYPE_CIRCLE - Circle fence
-  | 4 // FENCE_TYPE_POLYGON - Polygon fence
-  | 8 // FENCE_TYPE_ALT_MIN - Minimum altitude fence
-  | number;
-
-// Enumeration of possible mount operation modes. This message is used by obsolete/deprecated gimbal messages.
-export type MAV_MOUNT_MODE =
-  | 0 // MAV_MOUNT_MODE_RETRACT - Load and keep safe position (Roll,Pitch,Yaw) from permanent memory and stop stabilization
-  | 1 // MAV_MOUNT_MODE_NEUTRAL - Load and keep neutral position (Roll,Pitch,Yaw) from permanent memory.
-  | 2 // MAV_MOUNT_MODE_MAVLINK_TARGETING - Load neutral position and start MAVLink Roll,Pitch,Yaw control with stabilization
-  | 3 // MAV_MOUNT_MODE_RC_TARGETING - Load neutral position and start RC Roll,Pitch,Yaw control with stabilization
-  | 4 // MAV_MOUNT_MODE_GPS_POINT - Load neutral position and start to point to Lat,Lon,Alt
-  | 5 // MAV_MOUNT_MODE_SYSID_TARGET - Gimbal tracks system with specified system ID
-  | 6 // MAV_MOUNT_MODE_HOME_LOCATION - Gimbal tracks home position
-  | number;
-
-// Gimbal device (low level) capability flags (bitmap).
-export type GIMBAL_DEVICE_CAP_FLAGS =
-  | 1 // GIMBAL_DEVICE_CAP_FLAGS_HAS_RETRACT - Gimbal device supports a retracted position.
-  | 2 // GIMBAL_DEVICE_CAP_FLAGS_HAS_NEUTRAL - Gimbal device supports a horizontal, forward looking position, stabilized.
-  | 4 // GIMBAL_DEVICE_CAP_FLAGS_HAS_ROLL_AXIS - Gimbal device supports rotating around roll axis.
-  | 8 // GIMBAL_DEVICE_CAP_FLAGS_HAS_ROLL_FOLLOW - Gimbal device supports to follow a roll angle relative to the vehicle.
-  | 16 // GIMBAL_DEVICE_CAP_FLAGS_HAS_ROLL_LOCK - Gimbal device supports locking to a roll angle (generally that&#x27;s the default with roll stabilized).
-  | 32 // GIMBAL_DEVICE_CAP_FLAGS_HAS_PITCH_AXIS - Gimbal device supports rotating around pitch axis.
-  | 64 // GIMBAL_DEVICE_CAP_FLAGS_HAS_PITCH_FOLLOW - Gimbal device supports to follow a pitch angle relative to the vehicle.
-  | 128 // GIMBAL_DEVICE_CAP_FLAGS_HAS_PITCH_LOCK - Gimbal device supports locking to a pitch angle (generally that&#x27;s the default with pitch stabilized).
-  | 256 // GIMBAL_DEVICE_CAP_FLAGS_HAS_YAW_AXIS - Gimbal device supports rotating around yaw axis.
-  | 512 // GIMBAL_DEVICE_CAP_FLAGS_HAS_YAW_FOLLOW - Gimbal device supports to follow a yaw angle relative to the vehicle (generally that&#x27;s the default).
-  | 1024 // GIMBAL_DEVICE_CAP_FLAGS_HAS_YAW_LOCK - Gimbal device supports locking to an absolute heading, i.e., yaw angle relative to North (earth frame, often this is an option available).
-  | 2048 // GIMBAL_DEVICE_CAP_FLAGS_SUPPORTS_INFINITE_YAW - Gimbal device supports yawing/panning infinitely (e.g. using slip disk).
-  | 4096 // GIMBAL_DEVICE_CAP_FLAGS_SUPPORTS_YAW_IN_EARTH_FRAME - Gimbal device supports yaw angles and angular velocities relative to North (earth frame). This usually requires support by an autopilot via AUTOPILOT_STATE_FOR_GIMBAL_DEVICE. Support can go on and off during runtime, which is reported by the flag GIMBAL_DEVICE_FLAGS_CAN_ACCEPT_YAW_IN_EARTH_FRAME.
-  | 8192 // GIMBAL_DEVICE_CAP_FLAGS_HAS_RC_INPUTS - Gimbal device supports radio control inputs as an alternative input for controlling the gimbal orientation.
-  | number;
-
-// Gimbal manager high level capability flags (bitmap). The first 16 bits are identical to the GIMBAL_DEVICE_CAP_FLAGS. However, the gimbal manager does not need to copy the flags from the gimbal but can also enhance the capabilities and thus add flags.
-export type GIMBAL_MANAGER_CAP_FLAGS =
-  | 1 // GIMBAL_MANAGER_CAP_FLAGS_HAS_RETRACT - Based on GIMBAL_DEVICE_CAP_FLAGS_HAS_RETRACT.
-  | 2 // GIMBAL_MANAGER_CAP_FLAGS_HAS_NEUTRAL - Based on GIMBAL_DEVICE_CAP_FLAGS_HAS_NEUTRAL.
-  | 4 // GIMBAL_MANAGER_CAP_FLAGS_HAS_ROLL_AXIS - Based on GIMBAL_DEVICE_CAP_FLAGS_HAS_ROLL_AXIS.
-  | 8 // GIMBAL_MANAGER_CAP_FLAGS_HAS_ROLL_FOLLOW - Based on GIMBAL_DEVICE_CAP_FLAGS_HAS_ROLL_FOLLOW.
-  | 16 // GIMBAL_MANAGER_CAP_FLAGS_HAS_ROLL_LOCK - Based on GIMBAL_DEVICE_CAP_FLAGS_HAS_ROLL_LOCK.
-  | 32 // GIMBAL_MANAGER_CAP_FLAGS_HAS_PITCH_AXIS - Based on GIMBAL_DEVICE_CAP_FLAGS_HAS_PITCH_AXIS.
-  | 64 // GIMBAL_MANAGER_CAP_FLAGS_HAS_PITCH_FOLLOW - Based on GIMBAL_DEVICE_CAP_FLAGS_HAS_PITCH_FOLLOW.
-  | 128 // GIMBAL_MANAGER_CAP_FLAGS_HAS_PITCH_LOCK - Based on GIMBAL_DEVICE_CAP_FLAGS_HAS_PITCH_LOCK.
-  | 256 // GIMBAL_MANAGER_CAP_FLAGS_HAS_YAW_AXIS - Based on GIMBAL_DEVICE_CAP_FLAGS_HAS_YAW_AXIS.
-  | 512 // GIMBAL_MANAGER_CAP_FLAGS_HAS_YAW_FOLLOW - Based on GIMBAL_DEVICE_CAP_FLAGS_HAS_YAW_FOLLOW.
-  | 1024 // GIMBAL_MANAGER_CAP_FLAGS_HAS_YAW_LOCK - Based on GIMBAL_DEVICE_CAP_FLAGS_HAS_YAW_LOCK.
-  | 2048 // GIMBAL_MANAGER_CAP_FLAGS_SUPPORTS_INFINITE_YAW - Based on GIMBAL_DEVICE_CAP_FLAGS_SUPPORTS_INFINITE_YAW.
-  | 4096 // GIMBAL_MANAGER_CAP_FLAGS_SUPPORTS_YAW_IN_EARTH_FRAME - Based on GIMBAL_DEVICE_CAP_FLAGS_SUPPORTS_YAW_IN_EARTH_FRAME.
-  | 8192 // GIMBAL_MANAGER_CAP_FLAGS_HAS_RC_INPUTS - Based on GIMBAL_DEVICE_CAP_FLAGS_HAS_RC_INPUTS.
-  | 65536 // GIMBAL_MANAGER_CAP_FLAGS_CAN_POINT_LOCATION_LOCAL - Gimbal manager supports to point to a local position.
-  | 131072 // GIMBAL_MANAGER_CAP_FLAGS_CAN_POINT_LOCATION_GLOBAL - Gimbal manager supports to point to a global latitude, longitude, altitude position.
-  | number;
-
-// Flags for gimbal device (lower level) operation.
-export type GIMBAL_DEVICE_FLAGS =
-  | 1 // GIMBAL_DEVICE_FLAGS_RETRACT - Set to retracted safe position (no stabilization), takes precedence over all other flags.
-  | 2 // GIMBAL_DEVICE_FLAGS_NEUTRAL - Set to neutral/default position, taking precedence over all other flags except RETRACT. Neutral is commonly forward-facing and horizontal (roll&#x3D;pitch&#x3D;yaw&#x3D;0) but may be any orientation.
-  | 4 // GIMBAL_DEVICE_FLAGS_ROLL_LOCK - Lock roll angle to absolute angle relative to horizon (not relative to vehicle). This is generally the default with a stabilizing gimbal.
-  | 8 // GIMBAL_DEVICE_FLAGS_PITCH_LOCK - Lock pitch angle to absolute angle relative to horizon (not relative to vehicle). This is generally the default with a stabilizing gimbal.
-  | 16 // GIMBAL_DEVICE_FLAGS_YAW_LOCK - Lock yaw angle to absolute angle relative to North (not relative to vehicle). If this flag is set, the yaw angle and z component of angular velocity are relative to North (earth frame, x-axis pointing North), else they are relative to the vehicle heading (vehicle frame, earth frame rotated so that the x-axis is pointing forward).
-  | 32 // GIMBAL_DEVICE_FLAGS_YAW_IN_VEHICLE_FRAME - Yaw angle and z component of angular velocity are relative to the vehicle heading (vehicle frame, earth frame rotated such that the x-axis is pointing forward).
-  | 64 // GIMBAL_DEVICE_FLAGS_YAW_IN_EARTH_FRAME - Yaw angle and z component of angular velocity are relative to North (earth frame, x-axis is pointing North).
-  | 128 // GIMBAL_DEVICE_FLAGS_ACCEPTS_YAW_IN_EARTH_FRAME - Gimbal device can accept yaw angle inputs relative to North (earth frame). This flag is only for reporting (attempts to set this flag are ignored).
-  | 256 // GIMBAL_DEVICE_FLAGS_RC_EXCLUSIVE - The gimbal orientation is set exclusively by the RC signals feed to the gimbal&#x27;s radio control inputs. MAVLink messages for setting the gimbal orientation (GIMBAL_DEVICE_SET_ATTITUDE) are ignored.
-  | 512 // GIMBAL_DEVICE_FLAGS_RC_MIXED - The gimbal orientation is determined by combining/mixing the RC signals feed to the gimbal&#x27;s radio control inputs and the MAVLink messages for setting the gimbal orientation (GIMBAL_DEVICE_SET_ATTITUDE). How these two controls are combined or mixed is not defined by the protocol but is up to the implementation.
-  | number;
-
-// Flags for high level gimbal manager operation The first 16 bits are identical to the GIMBAL_DEVICE_FLAGS.
-export type GIMBAL_MANAGER_FLAGS =
-  | 1 // GIMBAL_MANAGER_FLAGS_RETRACT - Based on GIMBAL_DEVICE_FLAGS_RETRACT.
-  | 2 // GIMBAL_MANAGER_FLAGS_NEUTRAL - Based on GIMBAL_DEVICE_FLAGS_NEUTRAL.
-  | 4 // GIMBAL_MANAGER_FLAGS_ROLL_LOCK - Based on GIMBAL_DEVICE_FLAGS_ROLL_LOCK.
-  | 8 // GIMBAL_MANAGER_FLAGS_PITCH_LOCK - Based on GIMBAL_DEVICE_FLAGS_PITCH_LOCK.
-  | 16 // GIMBAL_MANAGER_FLAGS_YAW_LOCK - Based on GIMBAL_DEVICE_FLAGS_YAW_LOCK.
-  | 32 // GIMBAL_MANAGER_FLAGS_YAW_IN_VEHICLE_FRAME - Based on GIMBAL_DEVICE_FLAGS_YAW_IN_VEHICLE_FRAME.
-  | 64 // GIMBAL_MANAGER_FLAGS_YAW_IN_EARTH_FRAME - Based on GIMBAL_DEVICE_FLAGS_YAW_IN_EARTH_FRAME.
-  | 128 // GIMBAL_MANAGER_FLAGS_ACCEPTS_YAW_IN_EARTH_FRAME - Based on GIMBAL_DEVICE_FLAGS_ACCEPTS_YAW_IN_EARTH_FRAME.
-  | 256 // GIMBAL_MANAGER_FLAGS_RC_EXCLUSIVE - Based on GIMBAL_DEVICE_FLAGS_RC_EXCLUSIVE.
-  | 512 // GIMBAL_MANAGER_FLAGS_RC_MIXED - Based on GIMBAL_DEVICE_FLAGS_RC_MIXED.
-  | number;
-
-// Gimbal device (low level) error flags (bitmap, 0 means no error)
-export type GIMBAL_DEVICE_ERROR_FLAGS =
-  | 1 // GIMBAL_DEVICE_ERROR_FLAGS_AT_ROLL_LIMIT - Gimbal device is limited by hardware roll limit.
-  | 2 // GIMBAL_DEVICE_ERROR_FLAGS_AT_PITCH_LIMIT - Gimbal device is limited by hardware pitch limit.
-  | 4 // GIMBAL_DEVICE_ERROR_FLAGS_AT_YAW_LIMIT - Gimbal device is limited by hardware yaw limit.
-  | 8 // GIMBAL_DEVICE_ERROR_FLAGS_ENCODER_ERROR - There is an error with the gimbal encoders.
-  | 16 // GIMBAL_DEVICE_ERROR_FLAGS_POWER_ERROR - There is an error with the gimbal power source.
-  | 32 // GIMBAL_DEVICE_ERROR_FLAGS_MOTOR_ERROR - There is an error with the gimbal motors.
-  | 64 // GIMBAL_DEVICE_ERROR_FLAGS_SOFTWARE_ERROR - There is an error with the gimbal&#x27;s software.
-  | 128 // GIMBAL_DEVICE_ERROR_FLAGS_COMMS_ERROR - There is an error with the gimbal&#x27;s communication.
-  | 256 // GIMBAL_DEVICE_ERROR_FLAGS_CALIBRATION_RUNNING - Gimbal device is currently calibrating.
-  | 512 // GIMBAL_DEVICE_ERROR_FLAGS_NO_MANAGER - Gimbal device is not assigned to a gimbal manager.
-  | number;
-
-// Gripper actions.
-export type GRIPPER_ACTIONS =
-  | 0 // GRIPPER_ACTION_RELEASE - Gripper release cargo.
-  | 1 // GRIPPER_ACTION_GRAB - Gripper grab onto cargo.
-  | number;
-
-// Winch actions.
-export type WINCH_ACTIONS =
-  | 0 // WINCH_RELAXED - Allow motor to freewheel.
-  | 1 // WINCH_RELATIVE_LENGTH_CONTROL - Wind or unwind specified length of line, optionally using specified rate.
-  | 2 // WINCH_RATE_CONTROL - Wind or unwind line at specified rate.
-  | 3 // WINCH_LOCK - Perform the locking sequence to relieve motor while in the fully retracted position. Only action and instance command parameters are used, others are ignored.
-  | 4 // WINCH_DELIVER - Sequence of drop, slow down, touch down, reel up, lock. Only action and instance command parameters are used, others are ignored.
-  | 5 // WINCH_HOLD - Engage motor and hold current position. Only action and instance command parameters are used, others are ignored.
-  | 6 // WINCH_RETRACT - Return the reel to the fully retracted position. Only action and instance command parameters are used, others are ignored.
-  | 7 // WINCH_LOAD_LINE - Load the reel with line. The winch will calculate the total loaded length and stop when the tension exceeds a threshold. Only action and instance command parameters are used, others are ignored.
-  | 8 // WINCH_ABANDON_LINE - Spool out the entire length of the line. Only action and instance command parameters are used, others are ignored.
-  | 9 // WINCH_LOAD_PAYLOAD - Spools out just enough to present the hook to the user to load the payload. Only action and instance command parameters are used, others are ignored
-  | number;
-
-// Generalized UAVCAN node health
-export type UAVCAN_NODE_HEALTH =
-  | 0 // UAVCAN_NODE_HEALTH_OK - The node is functioning properly.
-  | 1 // UAVCAN_NODE_HEALTH_WARNING - A critical parameter went out of range or the node has encountered a minor failure.
-  | 2 // UAVCAN_NODE_HEALTH_ERROR - The node has encountered a major failure.
-  | 3 // UAVCAN_NODE_HEALTH_CRITICAL - The node has suffered a fatal malfunction.
-  | number;
-
-// Generalized UAVCAN node mode
-export type UAVCAN_NODE_MODE =
-  | 0 // UAVCAN_NODE_MODE_OPERATIONAL - The node is performing its primary functions.
-  | 1 // UAVCAN_NODE_MODE_INITIALIZATION - The node is initializing; this mode is entered immediately after startup.
-  | 2 // UAVCAN_NODE_MODE_MAINTENANCE - The node is under maintenance.
-  | 3 // UAVCAN_NODE_MODE_SOFTWARE_UPDATE - The node is in the process of updating its software.
-  | 7 // UAVCAN_NODE_MODE_OFFLINE - The node is no longer available online.
-  | number;
-
-// Indicates the ESC connection type.
-export type ESC_CONNECTION_TYPE =
-  | 0 // ESC_CONNECTION_TYPE_PPM - Traditional PPM ESC.
-  | 1 // ESC_CONNECTION_TYPE_SERIAL - Serial Bus connected ESC.
-  | 2 // ESC_CONNECTION_TYPE_ONESHOT - One Shot PPM ESC.
-  | 3 // ESC_CONNECTION_TYPE_I2C - I2C ESC.
-  | 4 // ESC_CONNECTION_TYPE_CAN - CAN-Bus ESC.
-  | 5 // ESC_CONNECTION_TYPE_DSHOT - DShot ESC.
-  | number;
-
-// Flags to report ESC failures.
-export type ESC_FAILURE_FLAGS =
-  | 1 // ESC_FAILURE_OVER_CURRENT - Over current failure.
-  | 2 // ESC_FAILURE_OVER_VOLTAGE - Over voltage failure.
-  | 4 // ESC_FAILURE_OVER_TEMPERATURE - Over temperature failure.
-  | 8 // ESC_FAILURE_OVER_RPM - Over RPM failure.
-  | 16 // ESC_FAILURE_INCONSISTENT_CMD - Inconsistent command failure i.e. out of bounds.
-  | 32 // ESC_FAILURE_MOTOR_STUCK - Motor stuck failure.
-  | 64 // ESC_FAILURE_GENERIC - Generic ESC failure.
-  | number;
-
-// Flags to indicate the status of camera storage.
-export type STORAGE_STATUS =
-  | 0 // STORAGE_STATUS_EMPTY - Storage is missing (no microSD card loaded for example.)
-  | 1 // STORAGE_STATUS_UNFORMATTED - Storage present but unformatted.
-  | 2 // STORAGE_STATUS_READY - Storage present and ready.
-  | 3 // STORAGE_STATUS_NOT_SUPPORTED - Camera does not supply storage status information. Capacity information in STORAGE_INFORMATION fields will be ignored.
-  | number;
-
-// Flags to indicate the type of storage.
-export type STORAGE_TYPE =
-  | 0 // STORAGE_TYPE_UNKNOWN - Storage type is not known.
-  | 1 // STORAGE_TYPE_USB_STICK - Storage type is USB device.
-  | 2 // STORAGE_TYPE_SD - Storage type is SD card.
-  | 3 // STORAGE_TYPE_MICROSD - Storage type is microSD card.
-  | 4 // STORAGE_TYPE_CF - Storage type is CFast.
-  | 5 // STORAGE_TYPE_CFE - Storage type is CFexpress.
-  | 6 // STORAGE_TYPE_XQD - Storage type is XQD.
-  | 7 // STORAGE_TYPE_HD - Storage type is HD mass storage type.
-  | 254 // STORAGE_TYPE_OTHER - Storage type is other, not listed type.
-  | number;
-
-// Flags to indicate usage for a particular storage (see STORAGE_INFORMATION.storage_usage and MAV_CMD_SET_STORAGE_USAGE).
-export type STORAGE_USAGE_FLAG =
-  | 1 // STORAGE_USAGE_FLAG_SET - Always set to 1 (indicates STORAGE_INFORMATION.storage_usage is supported).
-  | 2 // STORAGE_USAGE_FLAG_PHOTO - Storage for saving photos.
-  | 4 // STORAGE_USAGE_FLAG_VIDEO - Storage for saving videos.
-  | 8 // STORAGE_USAGE_FLAG_LOGS - Storage for saving logs.
-  | number;
-
-// Yaw behaviour during orbit flight.
-export type ORBIT_YAW_BEHAVIOUR =
-  | 0 // ORBIT_YAW_BEHAVIOUR_HOLD_FRONT_TO_CIRCLE_CENTER - Vehicle front points to the center (default).
-  | 1 // ORBIT_YAW_BEHAVIOUR_HOLD_INITIAL_HEADING - Vehicle front holds heading when message received.
-  | 2 // ORBIT_YAW_BEHAVIOUR_UNCONTROLLED - Yaw uncontrolled.
-  | 3 // ORBIT_YAW_BEHAVIOUR_HOLD_FRONT_TANGENT_TO_CIRCLE - Vehicle front follows flight path (tangential to circle).
-  | 4 // ORBIT_YAW_BEHAVIOUR_RC_CONTROLLED - Yaw controlled by RC input.
-  | 5 // ORBIT_YAW_BEHAVIOUR_UNCHANGED - Vehicle uses current yaw behaviour (unchanged). The vehicle-default yaw behaviour is used if this value is specified when orbit is first commanded.
-  | number;
-
-// Possible responses from a WIFI_CONFIG_AP message.
-export type WIFI_CONFIG_AP_RESPONSE =
-  | 0 // WIFI_CONFIG_AP_RESPONSE_UNDEFINED - Undefined response. Likely an indicative of a system that doesn&#x27;t support this request.
-  | 1 // WIFI_CONFIG_AP_RESPONSE_ACCEPTED - Changes accepted.
-  | 2 // WIFI_CONFIG_AP_RESPONSE_REJECTED - Changes rejected.
-  | 3 // WIFI_CONFIG_AP_RESPONSE_MODE_ERROR - Invalid Mode.
-  | 4 // WIFI_CONFIG_AP_RESPONSE_SSID_ERROR - Invalid SSID.
-  | 5 // WIFI_CONFIG_AP_RESPONSE_PASSWORD_ERROR - Invalid Password.
-  | number;
-
-// Possible responses from a CELLULAR_CONFIG message.
-export type CELLULAR_CONFIG_RESPONSE =
-  | 0 // CELLULAR_CONFIG_RESPONSE_ACCEPTED - Changes accepted.
-  | 1 // CELLULAR_CONFIG_RESPONSE_APN_ERROR - Invalid APN.
-  | 2 // CELLULAR_CONFIG_RESPONSE_PIN_ERROR - Invalid PIN.
-  | 3 // CELLULAR_CONFIG_RESPONSE_REJECTED - Changes rejected.
-  | 4 // CELLULAR_CONFIG_BLOCKED_PUK_REQUIRED - PUK is required to unblock SIM card.
-  | number;
-
-// WiFi Mode.
-export type WIFI_CONFIG_AP_MODE =
-  | 0 // WIFI_CONFIG_AP_MODE_UNDEFINED - WiFi mode is undefined.
-  | 1 // WIFI_CONFIG_AP_MODE_AP - WiFi configured as an access point.
-  | 2 // WIFI_CONFIG_AP_MODE_STATION - WiFi configured as a station connected to an existing local WiFi network.
-  | 3 // WIFI_CONFIG_AP_MODE_DISABLED - WiFi disabled.
-  | number;
-
-// Supported component metadata types. These are used in the &quot;general&quot; metadata file returned by COMPONENT_METADATA to provide information about supported metadata types. The types are not used directly in MAVLink messages.
-export type COMP_METADATA_TYPE =
-  | 0 // COMP_METADATA_TYPE_GENERAL - General information about the component. General metadata includes information about other metadata types supported by the component. Files of this type must be supported, and must be downloadable from vehicle using a MAVLink FTP URI.
-  | 1 // COMP_METADATA_TYPE_PARAMETER - Parameter meta data.
-  | 2 // COMP_METADATA_TYPE_COMMANDS - Meta data that specifies which commands and command parameters the vehicle supports. (WIP)
-  | 3 // COMP_METADATA_TYPE_PERIPHERALS - Meta data that specifies external non-MAVLink peripherals.
-  | 4 // COMP_METADATA_TYPE_EVENTS - Meta data for the events interface.
-  | 5 // COMP_METADATA_TYPE_ACTUATORS - Meta data for actuator configuration (motors, servos and vehicle geometry) and testing.
-  | number;
-
-// Actuator configuration, used to change a setting on an actuator. Component information metadata can be used to know which outputs support which commands.
-export type ACTUATOR_CONFIGURATION =
-  | 0 // ACTUATOR_CONFIGURATION_NONE - Do nothing.
-  | 1 // ACTUATOR_CONFIGURATION_BEEP - Command the actuator to beep now.
-  | 2 // ACTUATOR_CONFIGURATION_3D_MODE_ON - Permanently set the actuator (ESC) to 3D mode (reversible thrust).
-  | 3 // ACTUATOR_CONFIGURATION_3D_MODE_OFF - Permanently set the actuator (ESC) to non 3D mode (non-reversible thrust).
-  | 4 // ACTUATOR_CONFIGURATION_SPIN_DIRECTION1 - Permanently set the actuator (ESC) to spin direction 1 (which can be clockwise or counter-clockwise).
-  | 5 // ACTUATOR_CONFIGURATION_SPIN_DIRECTION2 - Permanently set the actuator (ESC) to spin direction 2 (opposite of direction 1).
-  | number;
-
-// Actuator output function. Values greater or equal to 1000 are autopilot-specific.
-export type ACTUATOR_OUTPUT_FUNCTION =
-  | 0 // ACTUATOR_OUTPUT_FUNCTION_NONE - No function (disabled).
-  | 1 // ACTUATOR_OUTPUT_FUNCTION_MOTOR1 - Motor 1
-  | 2 // ACTUATOR_OUTPUT_FUNCTION_MOTOR2 - Motor 2
-  | 3 // ACTUATOR_OUTPUT_FUNCTION_MOTOR3 - Motor 3
-  | 4 // ACTUATOR_OUTPUT_FUNCTION_MOTOR4 - Motor 4
-  | 5 // ACTUATOR_OUTPUT_FUNCTION_MOTOR5 - Motor 5
-  | 6 // ACTUATOR_OUTPUT_FUNCTION_MOTOR6 - Motor 6
-  | 7 // ACTUATOR_OUTPUT_FUNCTION_MOTOR7 - Motor 7
-  | 8 // ACTUATOR_OUTPUT_FUNCTION_MOTOR8 - Motor 8
-  | 9 // ACTUATOR_OUTPUT_FUNCTION_MOTOR9 - Motor 9
-  | 10 // ACTUATOR_OUTPUT_FUNCTION_MOTOR10 - Motor 10
-  | 11 // ACTUATOR_OUTPUT_FUNCTION_MOTOR11 - Motor 11
-  | 12 // ACTUATOR_OUTPUT_FUNCTION_MOTOR12 - Motor 12
-  | 13 // ACTUATOR_OUTPUT_FUNCTION_MOTOR13 - Motor 13
-  | 14 // ACTUATOR_OUTPUT_FUNCTION_MOTOR14 - Motor 14
-  | 15 // ACTUATOR_OUTPUT_FUNCTION_MOTOR15 - Motor 15
-  | 16 // ACTUATOR_OUTPUT_FUNCTION_MOTOR16 - Motor 16
-  | 33 // ACTUATOR_OUTPUT_FUNCTION_SERVO1 - Servo 1
-  | 34 // ACTUATOR_OUTPUT_FUNCTION_SERVO2 - Servo 2
-  | 35 // ACTUATOR_OUTPUT_FUNCTION_SERVO3 - Servo 3
-  | 36 // ACTUATOR_OUTPUT_FUNCTION_SERVO4 - Servo 4
-  | 37 // ACTUATOR_OUTPUT_FUNCTION_SERVO5 - Servo 5
-  | 38 // ACTUATOR_OUTPUT_FUNCTION_SERVO6 - Servo 6
-  | 39 // ACTUATOR_OUTPUT_FUNCTION_SERVO7 - Servo 7
-  | 40 // ACTUATOR_OUTPUT_FUNCTION_SERVO8 - Servo 8
-  | 41 // ACTUATOR_OUTPUT_FUNCTION_SERVO9 - Servo 9
-  | 42 // ACTUATOR_OUTPUT_FUNCTION_SERVO10 - Servo 10
-  | 43 // ACTUATOR_OUTPUT_FUNCTION_SERVO11 - Servo 11
-  | 44 // ACTUATOR_OUTPUT_FUNCTION_SERVO12 - Servo 12
-  | 45 // ACTUATOR_OUTPUT_FUNCTION_SERVO13 - Servo 13
-  | 46 // ACTUATOR_OUTPUT_FUNCTION_SERVO14 - Servo 14
-  | 47 // ACTUATOR_OUTPUT_FUNCTION_SERVO15 - Servo 15
-  | 48 // ACTUATOR_OUTPUT_FUNCTION_SERVO16 - Servo 16
-  | number;
-
-// Axes that will be autotuned by MAV_CMD_DO_AUTOTUNE_ENABLE.
-// Note that at least one flag must be set in MAV_CMD_DO_AUTOTUNE_ENABLE.param2: if none are set, the flight stack will tune its default set of axes.
-export type AUTOTUNE_AXIS =
-  | 1 // AUTOTUNE_AXIS_ROLL - Autotune roll axis.
-  | 2 // AUTOTUNE_AXIS_PITCH - Autotune pitch axis.
-  | 4 // AUTOTUNE_AXIS_YAW - Autotune yaw axis.
-  | number;
-
-// Actions for reading/writing parameters between persistent and volatile storage when using MAV_CMD_PREFLIGHT_STORAGE.
-// (Commonly parameters are loaded from persistent storage (flash/EEPROM) into volatile storage (RAM) on startup and written back when they are changed.)
-export type PREFLIGHT_STORAGE_PARAMETER_ACTION =
-  | 0 // PARAM_READ_PERSISTENT - Read all parameters from persistent storage. Replaces values in volatile storage.
-  | 1 // PARAM_WRITE_PERSISTENT - Write all parameter values to persistent storage (flash/EEPROM)
-  | 2 // PARAM_RESET_CONFIG_DEFAULT - Reset all user configurable parameters to their default value (including airframe selection, sensor calibration data, safety settings, and so on). Does not reset values that contain operation counters and vehicle computed statistics.
-  | 3 // PARAM_RESET_SENSOR_DEFAULT - Reset only sensor calibration parameters to factory defaults (or firmware default if not available)
-  | 4 // PARAM_RESET_ALL_DEFAULT - Reset all parameters, including operation counters, to default values
-  | number;
-
-// Actions for reading and writing plan information (mission, rally points, geofence) between persistent and volatile storage when using MAV_CMD_PREFLIGHT_STORAGE.
-// (Commonly missions are loaded from persistent storage (flash/EEPROM) into volatile storage (RAM) on startup and written back when they are changed.)
-export type PREFLIGHT_STORAGE_MISSION_ACTION =
-  | 0 // MISSION_READ_PERSISTENT - Read current mission data from persistent storage
-  | 1 // MISSION_WRITE_PERSISTENT - Write current mission data to persistent storage
-  | 2 // MISSION_RESET_DEFAULT - Erase all mission data stored on the vehicle (both persistent and volatile storage)
-  | number;
-
-// Specifies the conditions under which the MAV_CMD_PREFLIGHT_REBOOT_SHUTDOWN command should be accepted.
-export type REBOOT_SHUTDOWN_CONDITIONS =
-  | 0 // REBOOT_SHUTDOWN_CONDITIONS_SAFETY_INTERLOCKED - Reboot/Shutdown only if allowed by safety checks, such as being landed.
-  | 20190226 // REBOOT_SHUTDOWN_CONDITIONS_FORCE - Force reboot/shutdown of the autopilot/component regardless of system state.
-  | number;
-
-// Commands to be executed by the MAV. They can be executed on user request, or as part of a mission script. If the action is used in a mission, the parameter mapping to the waypoint/mission message is as follows: Param 1, Param 2, Param 3, Param 4, X: Param 5, Y:Param 6, Z:Param 7. This command list is similar what ARINC 424 is for commercial aircraft: A data format how to interpret waypoint/mission data. NaN and INT32_MAX may be used in float/integer params (respectively) to indicate optional/default values (e.g. to use the component&#x27;s current yaw or latitude rather than a specific value). See https://mavlink.io/en/guide/xml_schema.html#MAV_CMD for information about the structure of the MAV_CMD entries
-export type MAV_CMD =
-  | 16 // MAV_CMD_NAV_WAYPOINT - Navigate to waypoint. This is intended for use in missions (for guided commands outside of missions use MAV_CMD_DO_REPOSITION).
-  | 17 // MAV_CMD_NAV_LOITER_UNLIM - Loiter around this waypoint an unlimited amount of time
-  | 18 // MAV_CMD_NAV_LOITER_TURNS - Loiter around this waypoint for X turns
-  | 19 // MAV_CMD_NAV_LOITER_TIME - Loiter at the specified latitude, longitude and altitude for a certain amount of time. Multicopter vehicles stop at the point (within a vehicle-specific acceptance radius). Forward-only moving vehicles (e.g. fixed-wing) circle the point with the specified radius/direction. If the Heading Required parameter (2) is non-zero forward moving aircraft will only leave the loiter circle once heading towards the next waypoint.
-  | 20 // MAV_CMD_NAV_RETURN_TO_LAUNCH - Return to launch location
-  | 21 // MAV_CMD_NAV_LAND - Land at location.
-  | 22 // MAV_CMD_NAV_TAKEOFF - Takeoff from ground / hand. Vehicles that support multiple takeoff modes (e.g. VTOL quadplane) should take off using the currently configured mode.
-  | 23 // MAV_CMD_NAV_LAND_LOCAL - Land at local position (local frame only)
-  | 24 // MAV_CMD_NAV_TAKEOFF_LOCAL - Takeoff from local position (local frame only)
-  | 25 // MAV_CMD_NAV_FOLLOW - Vehicle following, i.e. this waypoint represents the position of a moving vehicle
-  | 30 // MAV_CMD_NAV_CONTINUE_AND_CHANGE_ALT - Continue on the current course and climb/descend to specified altitude.  When the altitude is reached continue to the next command (i.e., don&#x27;t proceed to the next command until the desired altitude is reached.
-  | 31 // MAV_CMD_NAV_LOITER_TO_ALT - Begin loiter at the specified Latitude and Longitude.  If Lat&#x3D;Lon&#x3D;0, then loiter at the current position.  Don&#x27;t consider the navigation command complete (don&#x27;t leave loiter) until the altitude has been reached. Additionally, if the Heading Required parameter is non-zero the aircraft will not leave the loiter until heading toward the next waypoint.
-  | 32 // MAV_CMD_DO_FOLLOW - Begin following a target
-  | 33 // MAV_CMD_DO_FOLLOW_REPOSITION - Reposition the MAV after a follow target command has been sent
-  | 34 // MAV_CMD_DO_ORBIT - Start orbiting on the circumference of a circle defined by the parameters. Setting values to NaN/INT32_MAX (as appropriate) results in using defaults.
-  | 80 // MAV_CMD_NAV_ROI - Sets the region of interest (ROI) for a sensor set or the vehicle itself. This can then be used by the vehicle&#x27;s control system to control the vehicle attitude and the attitude of various sensors such as cameras.
-  | 81 // MAV_CMD_NAV_PATHPLANNING - Control autonomous path planning on the MAV.
-  | 82 // MAV_CMD_NAV_SPLINE_WAYPOINT - Navigate to waypoint using a spline path.
-  | 84 // MAV_CMD_NAV_VTOL_TAKEOFF - Takeoff from ground using VTOL mode, and transition to forward flight with specified heading. The command should be ignored by vehicles that dont support both VTOL and fixed-wing flight (multicopters, boats,etc.).
-  | 85 // MAV_CMD_NAV_VTOL_LAND - Land using VTOL mode
-  | 92 // MAV_CMD_NAV_GUIDED_ENABLE - Hand control over to an external controller
-  | 93 // MAV_CMD_NAV_DELAY - Delay the next navigation command a number of seconds or until a specified time
-  | 94 // MAV_CMD_NAV_PAYLOAD_PLACE - Descend and place payload. Vehicle moves to specified location, descends until it detects a hanging payload has reached the ground, and then releases the payload. If ground is not detected before the reaching the maximum descent value (param1), the command will complete without releasing the payload.
-  | 95 // MAV_CMD_NAV_LAST - NOP - This command is only used to mark the upper limit of the NAV/ACTION commands in the enumeration
-  | 112 // MAV_CMD_CONDITION_DELAY - Delay mission state machine.
-  | 113 // MAV_CMD_CONDITION_CHANGE_ALT - Ascend/descend to target altitude at specified rate. Delay mission state machine until desired altitude reached.
-  | 114 // MAV_CMD_CONDITION_DISTANCE - Delay mission state machine until within desired distance of next NAV point.
-  | 115 // MAV_CMD_CONDITION_YAW - Reach a certain target angle.
-  | 159 // MAV_CMD_CONDITION_LAST - NOP - This command is only used to mark the upper limit of the CONDITION commands in the enumeration
-  | 176 // MAV_CMD_DO_SET_MODE - Set system mode.
-  | 177 // MAV_CMD_DO_JUMP - Jump to the desired command in the mission list.  Repeat this action only the specified number of times
-  | 178 // MAV_CMD_DO_CHANGE_SPEED - Change speed and/or throttle set points. The value persists until it is overridden or there is a mode change
-  | 179 // MAV_CMD_DO_SET_HOME - Sets the home position to either to the current position or a specified position. The home position is the default position that the system will return to and land on. The position is set automatically by the system during the takeoff (and may also be set using this command). Note: the current home position may be emitted in a HOME_POSITION message on request (using MAV_CMD_REQUEST_MESSAGE with param1&#x3D;242).
-  | 180 // MAV_CMD_DO_SET_PARAMETER - Set a system parameter.  Caution!  Use of this command requires knowledge of the numeric enumeration value of the parameter.
-  | 181 // MAV_CMD_DO_SET_RELAY - Set a relay to a condition.
-  | 182 // MAV_CMD_DO_REPEAT_RELAY - Cycle a relay on and off for a desired number of cycles with a desired period.
-  | 183 // MAV_CMD_DO_SET_SERVO - Set a servo to a desired PWM value.
-  | 184 // MAV_CMD_DO_REPEAT_SERVO - Cycle a between its nominal setting and a desired PWM for a desired number of cycles with a desired period.
-  | 185 // MAV_CMD_DO_FLIGHTTERMINATION - Terminate flight immediately. Flight termination immediately and irreversibly terminates the current flight, returning the vehicle to ground. The vehicle will ignore RC or other input until it has been power-cycled. Termination may trigger safety measures, including: disabling motors and deployment of parachute on multicopters, and setting flight surfaces to initiate a landing pattern on fixed-wing). On multicopters without a parachute it may trigger a crash landing. Support for this command can be tested using the protocol bit: MAV_PROTOCOL_CAPABILITY_FLIGHT_TERMINATION. Support for this command can also be tested by sending the command with param1&#x3D;0 (&lt; 0.5); the ACK should be either MAV_RESULT_FAILED or MAV_RESULT_UNSUPPORTED.
-  | 186 // MAV_CMD_DO_CHANGE_ALTITUDE - Change altitude set point.
-  | 187 // MAV_CMD_DO_SET_ACTUATOR - Sets actuators (e.g. servos) to a desired value. The actuator numbers are mapped to specific outputs (e.g. on any MAIN or AUX PWM or UAVCAN) using a flight-stack specific mechanism (i.e. a parameter).
-  | 188 // MAV_CMD_DO_RETURN_PATH_START - Mission item to specify the start of a failsafe/landing return-path segment (the end of the segment is the next MAV_CMD_DO_LAND_START item). A vehicle that is using missions for landing (e.g. in a return mode) will join the mission on the closest path of the return-path segment (instead of MAV_CMD_DO_LAND_START or the nearest waypoint). The main use case is to minimize the failsafe flight path in corridor missions, where the inbound/outbound paths are constrained (by geofences) to the same particular path. The MAV_CMD_NAV_RETURN_PATH_START would be placed at the start of the return path. If a failsafe occurs on the outbound path the vehicle will move to the nearest point on the return path (which is parallel for this kind of mission), effectively turning round and following the shortest path to landing. If a failsafe occurs on the inbound path the vehicle is already on the return segment and will continue to landing. The Latitude/Longitude/Altitude are optional, and may be set to 0 if not needed. If specified, the item defines the waypoint at which the return segment starts. If sent using as a command, the vehicle will perform a mission landing (using the land segment if defined) or reject the command if mission landings are not supported, or no mission landing is defined. When used as a command any position information in the command is ignored.
-  | 189 // MAV_CMD_DO_LAND_START - Mission item to mark the start of a mission landing pattern, or a command to land with a mission landing pattern. When used in a mission, this is a marker for the start of a sequence of mission items that represent a landing pattern. It should be followed by a navigation item that defines the first waypoint of the landing sequence. The start marker positional params are used only for selecting what landing pattern to use if several are defined in the mission (the selected pattern will be the one with the marker position that is closest to the vehicle when a landing is commanded). If the marker item position has zero-values for latitude, longitude, and altitude, then landing pattern selection is instead based on the position of the first waypoint in the landing sequence. When sent as a command it triggers a landing using a mission landing pattern. The location parameters are not used in this case, and should be set to 0.
-  | 190 // MAV_CMD_DO_RALLY_LAND - Mission command to perform a landing from a rally point.
-  | 191 // MAV_CMD_DO_GO_AROUND - Mission command to safely abort an autonomous landing.
-  | 192 // MAV_CMD_DO_REPOSITION - Reposition the vehicle to a specific WGS84 global position. This command is intended for guided commands (for missions use MAV_CMD_NAV_WAYPOINT instead).
-  | 193 // MAV_CMD_DO_PAUSE_CONTINUE - If in a GPS controlled position mode, hold the current position or continue.
-  | 194 // MAV_CMD_DO_SET_REVERSE - Set moving direction to forward or reverse.
-  | 195 // MAV_CMD_DO_SET_ROI_LOCATION - Sets the region of interest (ROI) to a location. This can then be used by the vehicle&#x27;s control system to control the vehicle attitude and the attitude of various sensors such as cameras. This command can be sent to a gimbal manager but not to a gimbal device. A gimbal is not to react to this message.
-  | 196 // MAV_CMD_DO_SET_ROI_WPNEXT_OFFSET - Sets the region of interest (ROI) to be toward next waypoint, with optional pitch/roll/yaw offset. This can then be used by the vehicle&#x27;s control system to control the vehicle attitude and the attitude of various sensors such as cameras. This command can be sent to a gimbal manager but not to a gimbal device. A gimbal device is not to react to this message.
-  | 197 // MAV_CMD_DO_SET_ROI_NONE - Cancels any previous ROI command returning the vehicle/sensors to default flight characteristics. This can then be used by the vehicle&#x27;s control system to control the vehicle attitude and the attitude of various sensors such as cameras. This command can be sent to a gimbal manager but not to a gimbal device. A gimbal device is not to react to this message. After this command the gimbal manager should go back to manual input if available, and otherwise assume a neutral position.
-  | 198 // MAV_CMD_DO_SET_ROI_SYSID - Mount tracks system with specified system ID. Determination of target vehicle position may be done with GLOBAL_POSITION_INT or any other means. This command can be sent to a gimbal manager but not to a gimbal device. A gimbal device is not to react to this message.
-  | 200 // MAV_CMD_DO_CONTROL_VIDEO - Control onboard camera system.
-  | 201 // MAV_CMD_DO_SET_ROI - Sets the region of interest (ROI) for a sensor set or the vehicle itself. This can then be used by the vehicle&#x27;s control system to control the vehicle attitude and the attitude of various sensors such as cameras.
-  | 202 // MAV_CMD_DO_DIGICAM_CONFIGURE - Configure digital camera. This is a fallback message for systems that have not yet implemented PARAM_EXT_XXX messages and camera definition files (see https://mavlink.io/en/services/camera_def.html ).
-  | 203 // MAV_CMD_DO_DIGICAM_CONTROL - Control digital camera. This is a fallback message for systems that have not yet implemented PARAM_EXT_XXX messages and camera definition files (see https://mavlink.io/en/services/camera_def.html ).
-  | 204 // MAV_CMD_DO_MOUNT_CONFIGURE - Mission command to configure a camera or antenna mount
-  | 205 // MAV_CMD_DO_MOUNT_CONTROL - Mission command to control a camera or antenna mount
-  | 206 // MAV_CMD_DO_SET_CAM_TRIGG_DIST - Mission command to set camera trigger distance for this flight. The camera is triggered each time this distance is exceeded. This command can also be used to set the shutter integration time for the camera.
-  | 207 // MAV_CMD_DO_FENCE_ENABLE - Enable the geofence. This can be used in a mission or via the command protocol. The persistence/lifetime of the setting is undefined. Depending on flight stack implementation it may persist until superseded, or it may revert to a system default at the end of a mission. Flight stacks typically reset the setting to system defaults on reboot.
-  | 208 // MAV_CMD_DO_PARACHUTE - Mission item/command to release a parachute or enable/disable auto release.
-  | 209 // MAV_CMD_DO_MOTOR_TEST - Command to perform motor test.
-  | 210 // MAV_CMD_DO_INVERTED_FLIGHT - Change to/from inverted flight.
-  | 211 // MAV_CMD_DO_GRIPPER - Mission command to operate a gripper.
-  | 212 // MAV_CMD_DO_AUTOTUNE_ENABLE - Enable/disable autotune.
-  | 213 // MAV_CMD_NAV_SET_YAW_SPEED - Sets a desired vehicle turn angle and speed change.
-  | 214 // MAV_CMD_DO_SET_CAM_TRIGG_INTERVAL - Mission command to set camera trigger interval for this flight. If triggering is enabled, the camera is triggered each time this interval expires. This command can also be used to set the shutter integration time for the camera.
-  | 220 // MAV_CMD_DO_MOUNT_CONTROL_QUAT - Mission command to control a camera or antenna mount, using a quaternion as reference.
-  | 221 // MAV_CMD_DO_GUIDED_MASTER - set id of master controller
-  | 222 // MAV_CMD_DO_GUIDED_LIMITS - Set limits for external control
-  | 223 // MAV_CMD_DO_ENGINE_CONTROL - Control vehicle engine. This is interpreted by the vehicles engine controller to change the target engine state. It is intended for vehicles with internal combustion engines
-  | 224 // MAV_CMD_DO_SET_MISSION_CURRENT - Set the mission item with sequence number seq as the current item and emit MISSION_CURRENT (whether or not the mission number changed). If a mission is currently being executed, the system will continue to this new mission item on the shortest path, skipping any intermediate mission items. Note that mission jump repeat counters are not reset unless param2 is set (see MAV_CMD_DO_JUMP param2). This command may trigger a mission state-machine change on some systems: for example from MISSION_STATE_NOT_STARTED or MISSION_STATE_PAUSED to MISSION_STATE_ACTIVE. If the system is in mission mode, on those systems this command might therefore start, restart or resume the mission. If the system is not in mission mode this command must not trigger a switch to mission mode. The mission may be &quot;reset&quot; using param2. Resetting sets jump counters to initial values (to reset counters without changing the current mission item set the param1 to &#x60;-1&#x60;). Resetting also explicitly changes a mission state of MISSION_STATE_COMPLETE to MISSION_STATE_PAUSED or MISSION_STATE_ACTIVE, potentially allowing it to resume when it is (next) in a mission mode. The command will ACK with MAV_RESULT_FAILED if the sequence number is out of range (including if there is no mission item).
-  | 240 // MAV_CMD_DO_LAST - NOP - This command is only used to mark the upper limit of the DO commands in the enumeration
-  | 241 // MAV_CMD_PREFLIGHT_CALIBRATION - Trigger calibration. This command will be only accepted if in pre-flight mode. Except for Temperature Calibration, only one sensor should be set in a single message and all others should be zero.
-  | 242 // MAV_CMD_PREFLIGHT_SET_SENSOR_OFFSETS - Set sensor offsets. This command will be only accepted if in pre-flight mode.
-  | 243 // MAV_CMD_PREFLIGHT_UAVCAN - Trigger UAVCAN configuration (actuator ID assignment and direction mapping). Note that this maps to the legacy UAVCAN v0 function UAVCAN_ENUMERATE, which is intended to be executed just once during initial vehicle configuration (it is not a normal pre-flight command and has been poorly named).
-  | 245 // MAV_CMD_PREFLIGHT_STORAGE - Request storage of different parameter values and logs. This command will be only accepted if in pre-flight mode.
-  | 246 // MAV_CMD_PREFLIGHT_REBOOT_SHUTDOWN - Request the reboot or shutdown of system components.
-  | 252 // MAV_CMD_OVERRIDE_GOTO - Override current mission with command to pause mission, pause mission and move to position, continue/resume mission. When param 1 indicates that the mission is paused (MAV_GOTO_DO_HOLD), param 2 defines whether it holds in place or moves to another position.
-  | 260 // MAV_CMD_OBLIQUE_SURVEY - Mission command to set a Camera Auto Mount Pivoting Oblique Survey (Replaces CAM_TRIGG_DIST for this purpose). The camera is triggered each time this distance is exceeded, then the mount moves to the next position. Params 4~6 set-up the angle limits and number of positions for oblique survey, where mount-enabled vehicles automatically roll the camera between shots to emulate an oblique camera setup (providing an increased HFOV). This command can also be used to set the shutter integration time for the camera.
-  | 262 // MAV_CMD_DO_SET_STANDARD_MODE - Enable the specified standard MAVLink mode. If the specified mode is not supported, the vehicle should ACK with MAV_RESULT_FAILED. See https://mavlink.io/en/services/standard_modes.html
-  | 300 // MAV_CMD_MISSION_START - start running a mission
-  | 310 // MAV_CMD_ACTUATOR_TEST - Actuator testing command. This is similar to MAV_CMD_DO_MOTOR_TEST but operates on the level of output functions, i.e. it is possible to test Motor1 independent from which output it is configured on. Autopilots must NACK this command with MAV_RESULT_TEMPORARILY_REJECTED while armed.
-  | 311 // MAV_CMD_CONFIGURE_ACTUATOR - Actuator configuration command.
-  | 400 // MAV_CMD_COMPONENT_ARM_DISARM - Arms / Disarms a component
-  | 401 // MAV_CMD_RUN_PREARM_CHECKS - Instructs a target system to run pre-arm checks. This allows preflight checks to be run on demand, which may be useful on systems that normally run them at low rate, or which do not trigger checks when the armable state might have changed. This command should return MAV_RESULT_ACCEPTED if it will run the checks. The results of the checks are usually then reported in SYS_STATUS messages (this is system-specific). The command should return MAV_RESULT_TEMPORARILY_REJECTED if the system is already armed.
-  | 405 // MAV_CMD_ILLUMINATOR_ON_OFF - Turns illuminators ON/OFF. An illuminator is a light source that is used for lighting up dark areas external to the system: e.g. a torch or searchlight (as opposed to a light source for illuminating the system itself, e.g. an indicator light).
-  | 406 // MAV_CMD_DO_ILLUMINATOR_CONFIGURE - Configures illuminator settings. An illuminator is a light source that is used for lighting up dark areas external to the system: e.g. a torch or searchlight (as opposed to a light source for illuminating the system itself, e.g. an indicator light).
-  | 410 // MAV_CMD_GET_HOME_POSITION - Request the home position from the vehicle. The vehicle will ACK the command and then emit the HOME_POSITION message.
-  | 420 // MAV_CMD_INJECT_FAILURE - Inject artificial failure for testing purposes. Note that autopilots should implement an additional protection before accepting this command such as a specific param setting.
-  | 500 // MAV_CMD_START_RX_PAIR - Starts receiver pairing.
-  | 510 // MAV_CMD_GET_MESSAGE_INTERVAL - Request the interval between messages for a particular MAVLink message ID. The receiver should ACK the command and then emit its response in a MESSAGE_INTERVAL message.
-  | 511 // MAV_CMD_SET_MESSAGE_INTERVAL - Set the interval between messages for a particular MAVLink message ID. This interface replaces REQUEST_DATA_STREAM.
-  | 512 // MAV_CMD_REQUEST_MESSAGE - Request the target system(s) emit a single instance of a specified message (i.e. a &quot;one-shot&quot; version of MAV_CMD_SET_MESSAGE_INTERVAL).
-  | 519 // MAV_CMD_REQUEST_PROTOCOL_VERSION - Request MAVLink protocol version compatibility. All receivers should ACK the command and then emit their capabilities in an PROTOCOL_VERSION message
-  | 520 // MAV_CMD_REQUEST_AUTOPILOT_CAPABILITIES - Request autopilot capabilities. The receiver should ACK the command and then emit its capabilities in an AUTOPILOT_VERSION message
-  | 521 // MAV_CMD_REQUEST_CAMERA_INFORMATION - Request camera information (CAMERA_INFORMATION).
-  | 522 // MAV_CMD_REQUEST_CAMERA_SETTINGS - Request camera settings (CAMERA_SETTINGS).
-  | 525 // MAV_CMD_REQUEST_STORAGE_INFORMATION - Request storage information (STORAGE_INFORMATION). Use the command&#x27;s target_component to target a specific component&#x27;s storage.
-  | 526 // MAV_CMD_STORAGE_FORMAT - Format a storage medium. Once format is complete, a STORAGE_INFORMATION message is sent. Use the command&#x27;s target_component to target a specific component&#x27;s storage.
-  | 527 // MAV_CMD_REQUEST_CAMERA_CAPTURE_STATUS - Request camera capture status (CAMERA_CAPTURE_STATUS)
-  | 528 // MAV_CMD_REQUEST_FLIGHT_INFORMATION - Request flight information (FLIGHT_INFORMATION)
-  | 529 // MAV_CMD_RESET_CAMERA_SETTINGS - Reset all camera settings to Factory Default
-  | 530 // MAV_CMD_SET_CAMERA_MODE - Set camera running mode. Use NaN for reserved values. GCS will send a MAV_CMD_REQUEST_VIDEO_STREAM_STATUS command after a mode change if the camera supports video streaming.
-  | 531 // MAV_CMD_SET_CAMERA_ZOOM - Set camera zoom. Camera must respond with a CAMERA_SETTINGS message (on success).
-  | 532 // MAV_CMD_SET_CAMERA_FOCUS - Set camera focus. Camera must respond with a CAMERA_SETTINGS message (on success).
-  | 533 // MAV_CMD_SET_STORAGE_USAGE - Set that a particular storage is the preferred location for saving photos, videos, and/or other media (e.g. to set that an SD card is used for storing videos). There can only be one preferred save location for each particular media type: setting a media usage flag will clear/reset that same flag if set on any other storage. If no flag is set the system should use its default storage. A target system can choose to always use default storage, in which case it should ACK the command with MAV_RESULT_UNSUPPORTED. A target system can choose to not allow a particular storage to be set as preferred storage, in which case it should ACK the command with MAV_RESULT_DENIED.
-  | 534 // MAV_CMD_SET_CAMERA_SOURCE - Set camera source. Changes the camera&#x27;s active sources on cameras with multiple image sensors.
-  | 600 // MAV_CMD_JUMP_TAG - Tagged jump target. Can be jumped to with MAV_CMD_DO_JUMP_TAG.
-  | 601 // MAV_CMD_DO_JUMP_TAG - Jump to the matching tag in the mission list. Repeat this action for the specified number of times. A mission should contain a single matching tag for each jump. If this is not the case then a jump to a missing tag should complete the mission, and a jump where there are multiple matching tags should always select the one with the lowest mission sequence number.
-  | 1000 // MAV_CMD_DO_GIMBAL_MANAGER_PITCHYAW - Set gimbal manager pitch/yaw setpoints (low rate command). It is possible to set combinations of the values below. E.g. an angle as well as a desired angular rate can be used to get to this angle at a certain angular rate, or an angular rate only will result in continuous turning. NaN is to be used to signal unset. Note: only the gimbal manager will react to this command - it will be ignored by a gimbal device. Use GIMBAL_MANAGER_SET_PITCHYAW if you need to stream pitch/yaw setpoints at higher rate.
-  | 1001 // MAV_CMD_DO_GIMBAL_MANAGER_CONFIGURE - Gimbal configuration to set which sysid/compid is in primary and secondary control.
-  | 2000 // MAV_CMD_IMAGE_START_CAPTURE - Start image capture sequence. CAMERA_IMAGE_CAPTURED must be emitted after each capture. Param1 (id) may be used to specify the target camera: 0: all cameras, 1 to 6: autopilot-connected cameras, 7-255: MAVLink camera component ID. It is needed in order to target specific cameras connected to the autopilot, or specific sensors in a multi-sensor camera (neither of which have a distinct MAVLink component ID). It is also needed to specify the target camera in missions. When used in a mission, an autopilot should execute the MAV_CMD for a specified local camera (param1 &#x3D; 1-6), or resend it as a command if it is intended for a MAVLink camera (param1 &#x3D; 7 - 255), setting the command&#x27;s target_component as the param1 value (and setting param1 in the command to zero). If the param1 is 0 the autopilot should do both. When sent in a command the target MAVLink address is set using target_component. If addressed specifically to an autopilot: param1 should be used in the same way as it is for missions (though command should NACK with MAV_RESULT_DENIED if a specified local camera does not exist). If addressed to a MAVLink camera, param 1 can be used to address all cameras (0), or to separately address 1 to 7 individual sensors. Other values should be NACKed with MAV_RESULT_DENIED. If the command is broadcast (target_component is 0) then param 1 should be set to 0 (any other value should be NACKED with MAV_RESULT_DENIED). An autopilot would trigger any local cameras and forward the command to all channels.
-  | 2001 // MAV_CMD_IMAGE_STOP_CAPTURE - Stop image capture sequence. Param1 (id) may be used to specify the target camera: 0: all cameras, 1 to 6: autopilot-connected cameras, 7-255: MAVLink camera component ID. It is needed in order to target specific cameras connected to the autopilot, or specific sensors in a multi-sensor camera (neither of which have a distinct MAVLink component ID). It is also needed to specify the target camera in missions. When used in a mission, an autopilot should execute the MAV_CMD for a specified local camera (param1 &#x3D; 1-6), or resend it as a command if it is intended for a MAVLink camera (param1 &#x3D; 7 - 255), setting the command&#x27;s target_component as the param1 value (and setting param1 in the command to zero). If the param1 is 0 the autopilot should do both. When sent in a command the target MAVLink address is set using target_component. If addressed specifically to an autopilot: param1 should be used in the same way as it is for missions (though command should NACK with MAV_RESULT_DENIED if a specified local camera does not exist). If addressed to a MAVLink camera, param1 can be used to address all cameras (0), or to separately address 1 to 7 individual sensors. Other values should be NACKed with MAV_RESULT_DENIED. If the command is broadcast (target_component is 0) then param 1 should be set to 0 (any other value should be NACKED with MAV_RESULT_DENIED). An autopilot would trigger any local cameras and forward the command to all channels.
-  | 2002 // MAV_CMD_REQUEST_CAMERA_IMAGE_CAPTURE - Re-request a CAMERA_IMAGE_CAPTURED message.
-  | 2003 // MAV_CMD_DO_TRIGGER_CONTROL - Enable or disable on-board camera triggering system.
-  | 2004 // MAV_CMD_CAMERA_TRACK_POINT - If the camera supports point visual tracking (CAMERA_CAP_FLAGS_HAS_TRACKING_POINT is set), this command allows to initiate the tracking.
-  | 2005 // MAV_CMD_CAMERA_TRACK_RECTANGLE - If the camera supports rectangle visual tracking (CAMERA_CAP_FLAGS_HAS_TRACKING_RECTANGLE is set), this command allows to initiate the tracking.
-  | 2010 // MAV_CMD_CAMERA_STOP_TRACKING - Stops ongoing tracking.
-  | 2500 // MAV_CMD_VIDEO_START_CAPTURE - Starts video capture (recording).
-  | 2501 // MAV_CMD_VIDEO_STOP_CAPTURE - Stop the current video capture (recording).
-  | 2502 // MAV_CMD_VIDEO_START_STREAMING - Start video streaming
-  | 2503 // MAV_CMD_VIDEO_STOP_STREAMING - Stop the given video stream
-  | 2504 // MAV_CMD_REQUEST_VIDEO_STREAM_INFORMATION - Request video stream information (VIDEO_STREAM_INFORMATION)
-  | 2505 // MAV_CMD_REQUEST_VIDEO_STREAM_STATUS - Request video stream status (VIDEO_STREAM_STATUS)
-  | 2510 // MAV_CMD_LOGGING_START - Request to start streaming logging data over MAVLink (see also LOGGING_DATA message)
-  | 2511 // MAV_CMD_LOGGING_STOP - Request to stop streaming log data over MAVLink
-  | 2520
-  | 2600 // MAV_CMD_CONTROL_HIGH_LATENCY - Request to start/stop transmitting over the high latency telemetry
-  | 2800 // MAV_CMD_PANORAMA_CREATE - Create a panorama at the current position
-  | 3000 // MAV_CMD_DO_VTOL_TRANSITION - Request VTOL transition
-  | 3001 // MAV_CMD_ARM_AUTHORIZATION_REQUEST - Request authorization to arm the vehicle to a external entity, the arm authorizer is responsible to request all data that is needs from the vehicle before authorize or deny the request. If approved the COMMAND_ACK message progress field should be set with period of time that this authorization is valid in seconds. If the authorization is denied COMMAND_ACK.result_param2 should be set with one of the reasons in ARM_AUTH_DENIED_REASON.
-  | 4000 // MAV_CMD_SET_GUIDED_SUBMODE_STANDARD - This command sets the submode to standard guided when vehicle is in guided mode. The vehicle holds position and altitude and the user can input the desired velocities along all three axes.
-  | 4001 // MAV_CMD_SET_GUIDED_SUBMODE_CIRCLE - This command sets submode circle when vehicle is in guided mode. Vehicle flies along a circle facing the center of the circle. The user can input the velocity along the circle and change the radius. If no input is given the vehicle will hold position.
-  | 4501 // MAV_CMD_CONDITION_GATE - Delay mission state machine until gate has been reached.
-  | 5000 // MAV_CMD_NAV_FENCE_RETURN_POINT - Fence return point (there can only be one such point in a geofence definition). If rally points are supported they should be used instead.
-  | 5001 // MAV_CMD_NAV_FENCE_POLYGON_VERTEX_INCLUSION - Fence vertex for an inclusion polygon (the polygon must not be self-intersecting). The vehicle must stay within this area. Minimum of 3 vertices required. The vertices for a polygon must be sent sequentially, each with param1 set to the total number of vertices in the polygon.
-  | 5002 // MAV_CMD_NAV_FENCE_POLYGON_VERTEX_EXCLUSION - Fence vertex for an exclusion polygon (the polygon must not be self-intersecting). The vehicle must stay outside this area. Minimum of 3 vertices required. The vertices for a polygon must be sent sequentially, each with param1 set to the total number of vertices in the polygon.
-  | 5003 // MAV_CMD_NAV_FENCE_CIRCLE_INCLUSION - Circular fence area. The vehicle must stay inside this area.
-  | 5004 // MAV_CMD_NAV_FENCE_CIRCLE_EXCLUSION - Circular fence area. The vehicle must stay outside this area.
-  | 5100 // MAV_CMD_NAV_RALLY_POINT - Rally point. You can have multiple rally points defined.
-  | 5200 // MAV_CMD_UAVCAN_GET_NODE_INFO - Commands the vehicle to respond with a sequence of messages UAVCAN_NODE_INFO, one message per every UAVCAN node that is online. Note that some of the response messages can be lost, which the receiver can detect easily by checking whether every received UAVCAN_NODE_STATUS has a matching message UAVCAN_NODE_INFO received earlier; if not, this command should be sent again in order to request re-transmission of the node information messages.
-  | 5300 // MAV_CMD_DO_SET_SAFETY_SWITCH_STATE - Change state of safety switch.
-  | 10001 // MAV_CMD_DO_ADSB_OUT_IDENT - Trigger the start of an ADSB-out IDENT. This should only be used when requested to do so by an Air Traffic Controller in controlled airspace. This starts the IDENT which is then typically held for 18 seconds by the hardware per the Mode A, C, and S transponder spec.
-  | 30001 // MAV_CMD_PAYLOAD_PREPARE_DEPLOY - Deploy payload on a Lat / Lon / Alt position. This includes the navigation to reach the required release position and velocity.
-  | 30002 // MAV_CMD_PAYLOAD_CONTROL_DEPLOY - Control the payload deployment.
-  | 42006 // MAV_CMD_FIXED_MAG_CAL_YAW - Magnetometer calibration based on provided known yaw. This allows for fast calibration using WMM field tables in the vehicle, given only the known yaw of the vehicle. If Latitude and longitude are both zero then use the current vehicle location.
-  | 42600 // MAV_CMD_DO_WINCH - Command to operate winch.
-  | 43003 // MAV_CMD_EXTERNAL_POSITION_ESTIMATE - Provide an external position estimate for use when dead-reckoning. This is meant to be used for occasional position resets that may be provided by a external system such as a remote pilot using landmarks over a video link.
-  | 31000 // MAV_CMD_WAYPOINT_USER_1 - User defined waypoint item. Ground Station will show the Vehicle as flying through this item.
-  | 31001 // MAV_CMD_WAYPOINT_USER_2 - User defined waypoint item. Ground Station will show the Vehicle as flying through this item.
-  | 31002 // MAV_CMD_WAYPOINT_USER_3 - User defined waypoint item. Ground Station will show the Vehicle as flying through this item.
-  | 31003 // MAV_CMD_WAYPOINT_USER_4 - User defined waypoint item. Ground Station will show the Vehicle as flying through this item.
-  | 31004 // MAV_CMD_WAYPOINT_USER_5 - User defined waypoint item. Ground Station will show the Vehicle as flying through this item.
-  | 31005 // MAV_CMD_SPATIAL_USER_1 - User defined spatial item. Ground Station will not show the Vehicle as flying through this item. Example: ROI item.
-  | 31006 // MAV_CMD_SPATIAL_USER_2 - User defined spatial item. Ground Station will not show the Vehicle as flying through this item. Example: ROI item.
-  | 31007 // MAV_CMD_SPATIAL_USER_3 - User defined spatial item. Ground Station will not show the Vehicle as flying through this item. Example: ROI item.
-  | 31008 // MAV_CMD_SPATIAL_USER_4 - User defined spatial item. Ground Station will not show the Vehicle as flying through this item. Example: ROI item.
-  | 31009 // MAV_CMD_SPATIAL_USER_5 - User defined spatial item. Ground Station will not show the Vehicle as flying through this item. Example: ROI item.
-  | 31010 // MAV_CMD_USER_1 - User defined command. Ground Station will not show the Vehicle as flying through this item. Example: MAV_CMD_DO_SET_PARAMETER item.
-  | 31011 // MAV_CMD_USER_2 - User defined command. Ground Station will not show the Vehicle as flying through this item. Example: MAV_CMD_DO_SET_PARAMETER item.
-  | 31012 // MAV_CMD_USER_3 - User defined command. Ground Station will not show the Vehicle as flying through this item. Example: MAV_CMD_DO_SET_PARAMETER item.
-  | 31013 // MAV_CMD_USER_4 - User defined command. Ground Station will not show the Vehicle as flying through this item. Example: MAV_CMD_DO_SET_PARAMETER item.
-  | 31014 // MAV_CMD_USER_5 - User defined command. Ground Station will not show the Vehicle as flying through this item. Example: MAV_CMD_DO_SET_PARAMETER item.
-  | 32000 // MAV_CMD_CAN_FORWARD - Request forwarding of CAN packets from the given CAN bus to this component. CAN Frames are sent using CAN_FRAME and CANFD_FRAME messages
-  | number;
-
-// A data stream is not a fixed set of messages, but rather a
-// recommendation to the autopilot software. Individual autopilots may or may not obey
-// the recommended messages.
-export type MAV_DATA_STREAM =
-  | 0 // MAV_DATA_STREAM_ALL - Enable all data streams
-  | 1 // MAV_DATA_STREAM_RAW_SENSORS - Enable IMU_RAW, GPS_RAW, GPS_STATUS packets.
-  | 2 // MAV_DATA_STREAM_EXTENDED_STATUS - Enable GPS_STATUS, CONTROL_STATUS, AUX_STATUS
-  | 3 // MAV_DATA_STREAM_RC_CHANNELS - Enable RC_CHANNELS_SCALED, RC_CHANNELS_RAW, SERVO_OUTPUT_RAW
-  | 4 // MAV_DATA_STREAM_RAW_CONTROLLER - Enable ATTITUDE_CONTROLLER_OUTPUT, POSITION_CONTROLLER_OUTPUT, NAV_CONTROLLER_OUTPUT.
-  | 6 // MAV_DATA_STREAM_POSITION - Enable LOCAL_POSITION, GLOBAL_POSITION_INT messages.
-  | 10 // MAV_DATA_STREAM_EXTRA1 - Dependent on the autopilot
-  | 11 // MAV_DATA_STREAM_EXTRA2 - Dependent on the autopilot
-  | 12 // MAV_DATA_STREAM_EXTRA3 - Dependent on the autopilot
-  | number;
-
-// The ROI (region of interest) for the vehicle. This can be
-// be used by the vehicle for camera/vehicle attitude alignment (see
-// MAV_CMD_NAV_ROI).
-export type MAV_ROI =
-  | 0 // MAV_ROI_NONE - No region of interest.
-  | 1 // MAV_ROI_WPNEXT - Point toward next waypoint, with optional pitch/roll/yaw offset.
-  | 2 // MAV_ROI_WPINDEX - Point toward given waypoint.
-  | 3 // MAV_ROI_LOCATION - Point toward fixed location.
-  | 4 // MAV_ROI_TARGET - Point toward of given id.
-  | number;
-
-// Specifies the datatype of a MAVLink parameter.
-export type MAV_PARAM_TYPE =
-  | 1 // MAV_PARAM_TYPE_UINT8 - 8-bit unsigned integer
-  | 2 // MAV_PARAM_TYPE_INT8 - 8-bit signed integer
-  | 3 // MAV_PARAM_TYPE_UINT16 - 16-bit unsigned integer
-  | 4 // MAV_PARAM_TYPE_INT16 - 16-bit signed integer
-  | 5 // MAV_PARAM_TYPE_UINT32 - 32-bit unsigned integer
-  | 6 // MAV_PARAM_TYPE_INT32 - 32-bit signed integer
-  | 7 // MAV_PARAM_TYPE_UINT64 - 64-bit unsigned integer
-  | 8 // MAV_PARAM_TYPE_INT64 - 64-bit signed integer
-  | 9 // MAV_PARAM_TYPE_REAL32 - 32-bit floating-point
-  | 10 // MAV_PARAM_TYPE_REAL64 - 64-bit floating-point
-  | number;
-
-// Specifies the datatype of a MAVLink extended parameter.
-export type MAV_PARAM_EXT_TYPE =
-  | 1 // MAV_PARAM_EXT_TYPE_UINT8 - 8-bit unsigned integer
-  | 2 // MAV_PARAM_EXT_TYPE_INT8 - 8-bit signed integer
-  | 3 // MAV_PARAM_EXT_TYPE_UINT16 - 16-bit unsigned integer
-  | 4 // MAV_PARAM_EXT_TYPE_INT16 - 16-bit signed integer
-  | 5 // MAV_PARAM_EXT_TYPE_UINT32 - 32-bit unsigned integer
-  | 6 // MAV_PARAM_EXT_TYPE_INT32 - 32-bit signed integer
-  | 7 // MAV_PARAM_EXT_TYPE_UINT64 - 64-bit unsigned integer
-  | 8 // MAV_PARAM_EXT_TYPE_INT64 - 64-bit signed integer
-  | 9 // MAV_PARAM_EXT_TYPE_REAL32 - 32-bit floating-point
-  | 10 // MAV_PARAM_EXT_TYPE_REAL64 - 64-bit floating-point
-  | 11 // MAV_PARAM_EXT_TYPE_CUSTOM - Custom Type
-  | number;
-
-// Result from a MAVLink command (MAV_CMD)
-export type MAV_RESULT =
-  | 0 // MAV_RESULT_ACCEPTED - Command is valid (is supported and has valid parameters), and was executed.
-  | 1 // MAV_RESULT_TEMPORARILY_REJECTED - Command is valid, but cannot be executed at this time. This is used to indicate a problem that should be fixed just by waiting (e.g. a state machine is busy, can&#x27;t arm because have not got GPS lock, etc.). Retrying later should work.
-  | 2 // MAV_RESULT_DENIED - Command is invalid (is supported but has invalid parameters). Retrying same command and parameters will not work.
-  | 3 // MAV_RESULT_UNSUPPORTED - Command is not supported (unknown).
-  | 4 // MAV_RESULT_FAILED - Command is valid, but execution has failed. This is used to indicate any non-temporary or unexpected problem, i.e. any problem that must be fixed before the command can succeed/be retried. For example, attempting to write a file when out of memory, attempting to arm when sensors are not calibrated, etc.
-  | 5 // MAV_RESULT_IN_PROGRESS - Command is valid and is being executed. This will be followed by further progress updates, i.e. the component may send further COMMAND_ACK messages with result MAV_RESULT_IN_PROGRESS (at a rate decided by the implementation), and must terminate by sending a COMMAND_ACK message with final result of the operation. The COMMAND_ACK.progress field can be used to indicate the progress of the operation.
-  | 6 // MAV_RESULT_CANCELLED - Command has been cancelled (as a result of receiving a COMMAND_CANCEL message).
-  | 7 // MAV_RESULT_COMMAND_LONG_ONLY - Command is only accepted when sent as a COMMAND_LONG.
-  | 8 // MAV_RESULT_COMMAND_INT_ONLY - Command is only accepted when sent as a COMMAND_INT.
-  | 9 // MAV_RESULT_COMMAND_UNSUPPORTED_MAV_FRAME - Command is invalid because a frame is required and the specified frame is not supported.
-  | number;
-
-// Result of mission operation (in a MISSION_ACK message).
-export type MAV_MISSION_RESULT =
-  | 0 // MAV_MISSION_ACCEPTED - mission accepted OK
-  | 1 // MAV_MISSION_ERROR - Generic error / not accepting mission commands at all right now.
-  | 2 // MAV_MISSION_UNSUPPORTED_FRAME - Coordinate frame is not supported.
-  | 3 // MAV_MISSION_UNSUPPORTED - Command is not supported.
-  | 4 // MAV_MISSION_NO_SPACE - Mission items exceed storage space.
-  | 5 // MAV_MISSION_INVALID - One of the parameters has an invalid value.
-  | 6 // MAV_MISSION_INVALID_PARAM1 - param1 has an invalid value.
-  | 7 // MAV_MISSION_INVALID_PARAM2 - param2 has an invalid value.
-  | 8 // MAV_MISSION_INVALID_PARAM3 - param3 has an invalid value.
-  | 9 // MAV_MISSION_INVALID_PARAM4 - param4 has an invalid value.
-  | 10 // MAV_MISSION_INVALID_PARAM5_X - x / param5 has an invalid value.
-  | 11 // MAV_MISSION_INVALID_PARAM6_Y - y / param6 has an invalid value.
-  | 12 // MAV_MISSION_INVALID_PARAM7 - z / param7 has an invalid value.
-  | 13 // MAV_MISSION_INVALID_SEQUENCE - Mission item received out of sequence
-  | 14 // MAV_MISSION_DENIED - Not accepting any mission commands from this communication partner.
-  | 15 // MAV_MISSION_OPERATION_CANCELLED - Current mission operation cancelled (e.g. mission upload, mission download).
-  | number;
-
-// Indicates the severity level, generally used for status messages to indicate their relative urgency. Based on RFC-5424 using expanded definitions at: http://www.kiwisyslog.com/kb/info:-syslog-message-levels/.
-export type MAV_SEVERITY =
-  | 0 // MAV_SEVERITY_EMERGENCY - System is unusable. This is a &quot;panic&quot; condition.
-  | 1 // MAV_SEVERITY_ALERT - Action should be taken immediately. Indicates error in non-critical systems.
-  | 2 // MAV_SEVERITY_CRITICAL - Action must be taken immediately. Indicates failure in a primary system.
-  | 3 // MAV_SEVERITY_ERROR - Indicates an error in secondary/redundant systems.
-  | 4 // MAV_SEVERITY_WARNING - Indicates about a possible future error if this is not resolved within a given timeframe. Example would be a low battery warning.
-  | 5 // MAV_SEVERITY_NOTICE - An unusual event has occurred, though not an error condition. This should be investigated for the root cause.
-  | 6 // MAV_SEVERITY_INFO - Normal operational messages. Useful for logging. No action is required for these messages.
-  | 7 // MAV_SEVERITY_DEBUG - Useful non-operational messages that can assist in debugging. These should not occur during normal operation.
-  | number;
-
-// Power supply status flags (bitmask)
-export type MAV_POWER_STATUS =
-  | 1 // MAV_POWER_STATUS_BRICK_VALID - main brick power supply valid
-  | 2 // MAV_POWER_STATUS_SERVO_VALID - main servo power supply valid for FMU
-  | 4 // MAV_POWER_STATUS_USB_CONNECTED - USB power is connected
-  | 8 // MAV_POWER_STATUS_PERIPH_OVERCURRENT - peripheral supply is in over-current state
-  | 16 // MAV_POWER_STATUS_PERIPH_HIPOWER_OVERCURRENT - hi-power peripheral supply is in over-current state
-  | 32 // MAV_POWER_STATUS_CHANGED - Power status has changed since boot
-  | number;
-
-// SERIAL_CONTROL device types
-export type SERIAL_CONTROL_DEV =
-  | 0 // SERIAL_CONTROL_DEV_TELEM1 - First telemetry port
-  | 1 // SERIAL_CONTROL_DEV_TELEM2 - Second telemetry port
-  | 2 // SERIAL_CONTROL_DEV_GPS1 - First GPS port
-  | 3 // SERIAL_CONTROL_DEV_GPS2 - Second GPS port
-  | 10 // SERIAL_CONTROL_DEV_SHELL - system shell
-  | 100 // SERIAL_CONTROL_SERIAL0 - SERIAL0
-  | 101 // SERIAL_CONTROL_SERIAL1 - SERIAL1
-  | 102 // SERIAL_CONTROL_SERIAL2 - SERIAL2
-  | 103 // SERIAL_CONTROL_SERIAL3 - SERIAL3
-  | 104 // SERIAL_CONTROL_SERIAL4 - SERIAL4
-  | 105 // SERIAL_CONTROL_SERIAL5 - SERIAL5
-  | 106 // SERIAL_CONTROL_SERIAL6 - SERIAL6
-  | 107 // SERIAL_CONTROL_SERIAL7 - SERIAL7
-  | 108 // SERIAL_CONTROL_SERIAL8 - SERIAL8
-  | 109 // SERIAL_CONTROL_SERIAL9 - SERIAL9
-  | number;
-
-// SERIAL_CONTROL flags (bitmask)
-export type SERIAL_CONTROL_FLAG =
-  | 1 // SERIAL_CONTROL_FLAG_REPLY - Set if this is a reply
-  | 2 // SERIAL_CONTROL_FLAG_RESPOND - Set if the sender wants the receiver to send a response as another SERIAL_CONTROL message
-  | 4 // SERIAL_CONTROL_FLAG_EXCLUSIVE - Set if access to the serial port should be removed from whatever driver is currently using it, giving exclusive access to the SERIAL_CONTROL protocol. The port can be handed back by sending a request without this flag set
-  | 8 // SERIAL_CONTROL_FLAG_BLOCKING - Block on writes to the serial port
-  | 16 // SERIAL_CONTROL_FLAG_MULTI - Send multiple replies until port is drained
-  | number;
-
-// Enumeration of distance sensor types
-export type MAV_DISTANCE_SENSOR =
-  | 0 // MAV_DISTANCE_SENSOR_LASER - Laser rangefinder, e.g. LightWare SF02/F or PulsedLight units
-  | 1 // MAV_DISTANCE_SENSOR_ULTRASOUND - Ultrasound rangefinder, e.g. MaxBotix units
-  | 2 // MAV_DISTANCE_SENSOR_INFRARED - Infrared rangefinder, e.g. Sharp units
-  | 3 // MAV_DISTANCE_SENSOR_RADAR - Radar type, e.g. uLanding units
-  | 4 // MAV_DISTANCE_SENSOR_UNKNOWN - Broken or unknown type, e.g. analog units
-  | number;
-
-// Enumeration of sensor orientation, according to its rotations
-export type MAV_SENSOR_ORIENTATION =
-  | 0 // MAV_SENSOR_ROTATION_NONE - Roll: 0, Pitch: 0, Yaw: 0
-  | 1 // MAV_SENSOR_ROTATION_YAW_45 - Roll: 0, Pitch: 0, Yaw: 45
-  | 2 // MAV_SENSOR_ROTATION_YAW_90 - Roll: 0, Pitch: 0, Yaw: 90
-  | 3 // MAV_SENSOR_ROTATION_YAW_135 - Roll: 0, Pitch: 0, Yaw: 135
-  | 4 // MAV_SENSOR_ROTATION_YAW_180 - Roll: 0, Pitch: 0, Yaw: 180
-  | 5 // MAV_SENSOR_ROTATION_YAW_225 - Roll: 0, Pitch: 0, Yaw: 225
-  | 6 // MAV_SENSOR_ROTATION_YAW_270 - Roll: 0, Pitch: 0, Yaw: 270
-  | 7 // MAV_SENSOR_ROTATION_YAW_315 - Roll: 0, Pitch: 0, Yaw: 315
-  | 8 // MAV_SENSOR_ROTATION_ROLL_180 - Roll: 180, Pitch: 0, Yaw: 0
-  | 9 // MAV_SENSOR_ROTATION_ROLL_180_YAW_45 - Roll: 180, Pitch: 0, Yaw: 45
-  | 10 // MAV_SENSOR_ROTATION_ROLL_180_YAW_90 - Roll: 180, Pitch: 0, Yaw: 90
-  | 11 // MAV_SENSOR_ROTATION_ROLL_180_YAW_135 - Roll: 180, Pitch: 0, Yaw: 135
-  | 12 // MAV_SENSOR_ROTATION_PITCH_180 - Roll: 0, Pitch: 180, Yaw: 0
-  | 13 // MAV_SENSOR_ROTATION_ROLL_180_YAW_225 - Roll: 180, Pitch: 0, Yaw: 225
-  | 14 // MAV_SENSOR_ROTATION_ROLL_180_YAW_270 - Roll: 180, Pitch: 0, Yaw: 270
-  | 15 // MAV_SENSOR_ROTATION_ROLL_180_YAW_315 - Roll: 180, Pitch: 0, Yaw: 315
-  | 16 // MAV_SENSOR_ROTATION_ROLL_90 - Roll: 90, Pitch: 0, Yaw: 0
-  | 17 // MAV_SENSOR_ROTATION_ROLL_90_YAW_45 - Roll: 90, Pitch: 0, Yaw: 45
-  | 18 // MAV_SENSOR_ROTATION_ROLL_90_YAW_90 - Roll: 90, Pitch: 0, Yaw: 90
-  | 19 // MAV_SENSOR_ROTATION_ROLL_90_YAW_135 - Roll: 90, Pitch: 0, Yaw: 135
-  | 20 // MAV_SENSOR_ROTATION_ROLL_270 - Roll: 270, Pitch: 0, Yaw: 0
-  | 21 // MAV_SENSOR_ROTATION_ROLL_270_YAW_45 - Roll: 270, Pitch: 0, Yaw: 45
-  | 22 // MAV_SENSOR_ROTATION_ROLL_270_YAW_90 - Roll: 270, Pitch: 0, Yaw: 90
-  | 23 // MAV_SENSOR_ROTATION_ROLL_270_YAW_135 - Roll: 270, Pitch: 0, Yaw: 135
-  | 24 // MAV_SENSOR_ROTATION_PITCH_90 - Roll: 0, Pitch: 90, Yaw: 0
-  | 25 // MAV_SENSOR_ROTATION_PITCH_270 - Roll: 0, Pitch: 270, Yaw: 0
-  | 26 // MAV_SENSOR_ROTATION_PITCH_180_YAW_90 - Roll: 0, Pitch: 180, Yaw: 90
-  | 27 // MAV_SENSOR_ROTATION_PITCH_180_YAW_270 - Roll: 0, Pitch: 180, Yaw: 270
-  | 28 // MAV_SENSOR_ROTATION_ROLL_90_PITCH_90 - Roll: 90, Pitch: 90, Yaw: 0
-  | 29 // MAV_SENSOR_ROTATION_ROLL_180_PITCH_90 - Roll: 180, Pitch: 90, Yaw: 0
-  | 30 // MAV_SENSOR_ROTATION_ROLL_270_PITCH_90 - Roll: 270, Pitch: 90, Yaw: 0
-  | 31 // MAV_SENSOR_ROTATION_ROLL_90_PITCH_180 - Roll: 90, Pitch: 180, Yaw: 0
-  | 32 // MAV_SENSOR_ROTATION_ROLL_270_PITCH_180 - Roll: 270, Pitch: 180, Yaw: 0
-  | 33 // MAV_SENSOR_ROTATION_ROLL_90_PITCH_270 - Roll: 90, Pitch: 270, Yaw: 0
-  | 34 // MAV_SENSOR_ROTATION_ROLL_180_PITCH_270 - Roll: 180, Pitch: 270, Yaw: 0
-  | 35 // MAV_SENSOR_ROTATION_ROLL_270_PITCH_270 - Roll: 270, Pitch: 270, Yaw: 0
-  | 36 // MAV_SENSOR_ROTATION_ROLL_90_PITCH_180_YAW_90 - Roll: 90, Pitch: 180, Yaw: 90
-  | 37 // MAV_SENSOR_ROTATION_ROLL_90_YAW_270 - Roll: 90, Pitch: 0, Yaw: 270
-  | 38 // MAV_SENSOR_ROTATION_ROLL_90_PITCH_68_YAW_293 - Roll: 90, Pitch: 68, Yaw: 293
-  | 39 // MAV_SENSOR_ROTATION_PITCH_315 - Pitch: 315
-  | 40 // MAV_SENSOR_ROTATION_ROLL_90_PITCH_315 - Roll: 90, Pitch: 315
-  | 100 // MAV_SENSOR_ROTATION_CUSTOM - Custom orientation
-  | number;
-
-// Bitmask of (optional) autopilot capabilities (64 bit). If a bit is set, the autopilot supports this capability.
-export type MAV_PROTOCOL_CAPABILITY =
-  | 1 // MAV_PROTOCOL_CAPABILITY_MISSION_FLOAT - Autopilot supports the MISSION_ITEM float message type. Note that MISSION_ITEM is deprecated, and autopilots should use MISSION_INT instead.
-  | 2 // MAV_PROTOCOL_CAPABILITY_PARAM_FLOAT - Autopilot supports the new param float message type.
-  | 4 // MAV_PROTOCOL_CAPABILITY_MISSION_INT - Autopilot supports MISSION_ITEM_INT scaled integer message type. Note that this flag must always be set if missions are supported, because missions must always use MISSION_ITEM_INT (rather than MISSION_ITEM, which is deprecated).
-  | 8 // MAV_PROTOCOL_CAPABILITY_COMMAND_INT - Autopilot supports COMMAND_INT scaled integer message type.
-  | 16 // MAV_PROTOCOL_CAPABILITY_PARAM_ENCODE_BYTEWISE - Parameter protocol uses byte-wise encoding of parameter values into param_value (float) fields: https://mavlink.io/en/services/parameter.html#parameter-encoding. Note that either this flag or MAV_PROTOCOL_CAPABILITY_PARAM_ENCODE_C_CAST should be set if the parameter protocol is supported.
-  | 32 // MAV_PROTOCOL_CAPABILITY_FTP - Autopilot supports the File Transfer Protocol v1: https://mavlink.io/en/services/ftp.html.
-  | 64 // MAV_PROTOCOL_CAPABILITY_SET_ATTITUDE_TARGET - Autopilot supports commanding attitude offboard.
-  | 128 // MAV_PROTOCOL_CAPABILITY_SET_POSITION_TARGET_LOCAL_NED - Autopilot supports commanding position and velocity targets in local NED frame.
-  | 256 // MAV_PROTOCOL_CAPABILITY_SET_POSITION_TARGET_GLOBAL_INT - Autopilot supports commanding position and velocity targets in global scaled integers.
-  | 512 // MAV_PROTOCOL_CAPABILITY_TERRAIN - Autopilot supports terrain protocol / data handling.
-  | 1024 // MAV_PROTOCOL_CAPABILITY_RESERVED3 - Reserved for future use.
-  | 2048 // MAV_PROTOCOL_CAPABILITY_FLIGHT_TERMINATION - Autopilot supports the MAV_CMD_DO_FLIGHTTERMINATION command (flight termination).
-  | 4096 // MAV_PROTOCOL_CAPABILITY_COMPASS_CALIBRATION - Autopilot supports onboard compass calibration.
-  | 8192 // MAV_PROTOCOL_CAPABILITY_MAVLINK2 - Autopilot supports MAVLink version 2.
-  | 16384 // MAV_PROTOCOL_CAPABILITY_MISSION_FENCE - Autopilot supports mission fence protocol.
-  | 32768 // MAV_PROTOCOL_CAPABILITY_MISSION_RALLY - Autopilot supports mission rally point protocol.
-  | 65536 // MAV_PROTOCOL_CAPABILITY_RESERVED2 - Reserved for future use.
-  | 131072 // MAV_PROTOCOL_CAPABILITY_PARAM_ENCODE_C_CAST - Parameter protocol uses C-cast of parameter values to set the param_value (float) fields: https://mavlink.io/en/services/parameter.html#parameter-encoding. Note that either this flag or MAV_PROTOCOL_CAPABILITY_PARAM_ENCODE_BYTEWISE should be set if the parameter protocol is supported.
-  | 262144 // MAV_PROTOCOL_CAPABILITY_COMPONENT_IMPLEMENTS_GIMBAL_MANAGER - This component implements/is a gimbal manager. This means the GIMBAL_MANAGER_INFORMATION, and other messages can be requested.
-  | 524288 // MAV_PROTOCOL_CAPABILITY_COMPONENT_ACCEPTS_GCS_CONTROL - Component supports locking control to a particular GCS independent of its system (via MAV_CMD_REQUEST_OPERATOR_CONTROL).
-  | 1048576 // MAV_PROTOCOL_CAPABILITY_GRIPPER - Autopilot has a connected gripper. MAVLink Grippers would set MAV_TYPE_GRIPPER instead.
-  | number;
-
-// Type of mission items being requested/sent in mission protocol.
-export type MAV_MISSION_TYPE =
-  | 0 // MAV_MISSION_TYPE_MISSION - Items are mission commands for main mission.
-  | 1 // MAV_MISSION_TYPE_FENCE - Specifies GeoFence area(s). Items are MAV_CMD_NAV_FENCE_ GeoFence items.
-  | 2 // MAV_MISSION_TYPE_RALLY - Specifies the rally points for the vehicle. Rally points are alternative RTL points. Items are MAV_CMD_NAV_RALLY_POINT rally point items.
-  | 255 // MAV_MISSION_TYPE_ALL - Only used in MISSION_CLEAR_ALL to clear all mission types.
-  | number;
-
-// Enumeration of estimator types
-export type MAV_ESTIMATOR_TYPE =
-  | 0 // MAV_ESTIMATOR_TYPE_UNKNOWN - Unknown type of the estimator.
-  | 1 // MAV_ESTIMATOR_TYPE_NAIVE - This is a naive estimator without any real covariance feedback.
-  | 2 // MAV_ESTIMATOR_TYPE_VISION - Computer vision based estimate. Might be up to scale.
-  | 3 // MAV_ESTIMATOR_TYPE_VIO - Visual-inertial estimate.
-  | 4 // MAV_ESTIMATOR_TYPE_GPS - Plain GPS estimate.
-  | 5 // MAV_ESTIMATOR_TYPE_GPS_INS - Estimator integrating GPS and inertial sensing.
-  | 6 // MAV_ESTIMATOR_TYPE_MOCAP - Estimate from external motion capturing system.
-  | 7 // MAV_ESTIMATOR_TYPE_LIDAR - Estimator based on lidar sensor input.
-  | 8 // MAV_ESTIMATOR_TYPE_AUTOPILOT - Estimator on autopilot.
-  | number;
-
-// Enumeration of battery types
-export type MAV_BATTERY_TYPE =
-  | 0 // MAV_BATTERY_TYPE_UNKNOWN - Not specified.
-  | 1 // MAV_BATTERY_TYPE_LIPO - Lithium polymer battery
-  | 2 // MAV_BATTERY_TYPE_LIFE - Lithium-iron-phosphate battery
-  | 3 // MAV_BATTERY_TYPE_LION - Lithium-ION battery
-  | 4 // MAV_BATTERY_TYPE_NIMH - Nickel metal hydride battery
-  | number;
-
-// Enumeration of battery functions
-export type MAV_BATTERY_FUNCTION =
-  | 0 // MAV_BATTERY_FUNCTION_UNKNOWN - Battery function is unknown
-  | 1 // MAV_BATTERY_FUNCTION_ALL - Battery supports all flight systems
-  | 2 // MAV_BATTERY_FUNCTION_PROPULSION - Battery for the propulsion system
-  | 3 // MAV_BATTERY_FUNCTION_AVIONICS - Avionics battery
-  | 4 // MAV_BATTERY_FUNCTION_PAYLOAD - Payload battery
-  | number;
-
-// Enumeration for battery charge states.
-export type MAV_BATTERY_CHARGE_STATE =
-  | 0 // MAV_BATTERY_CHARGE_STATE_UNDEFINED - Low battery state is not provided
-  | 1 // MAV_BATTERY_CHARGE_STATE_OK - Battery is not in low state. Normal operation.
-  | 2 // MAV_BATTERY_CHARGE_STATE_LOW - Battery state is low, warn and monitor close.
-  | 3 // MAV_BATTERY_CHARGE_STATE_CRITICAL - Battery state is critical, return or abort immediately.
-  | 4 // MAV_BATTERY_CHARGE_STATE_EMERGENCY - Battery state is too low for ordinary abort sequence. Perform fastest possible emergency stop to prevent damage.
-  | 5 // MAV_BATTERY_CHARGE_STATE_FAILED - Battery failed, damage unavoidable. Possible causes (faults) are listed in MAV_BATTERY_FAULT.
-  | 6 // MAV_BATTERY_CHARGE_STATE_UNHEALTHY - Battery is diagnosed to be defective or an error occurred, usage is discouraged / prohibited. Possible causes (faults) are listed in MAV_BATTERY_FAULT.
-  | 7 // MAV_BATTERY_CHARGE_STATE_CHARGING - Battery is charging.
-  | number;
-
-// Battery mode. Note, the normal operation mode (i.e. when flying) should be reported as MAV_BATTERY_MODE_UNKNOWN to allow message trimming in normal flight.
-export type MAV_BATTERY_MODE =
-  | 0 // MAV_BATTERY_MODE_UNKNOWN - Battery mode not supported/unknown battery mode/normal operation.
-  | 1 // MAV_BATTERY_MODE_AUTO_DISCHARGING - Battery is auto discharging (towards storage level).
-  | 2 // MAV_BATTERY_MODE_HOT_SWAP - Battery in hot-swap mode (current limited to prevent spikes that might damage sensitive electrical circuits).
-  | number;
-
-// Smart battery supply status/fault flags (bitmask) for health indication. The battery must also report either MAV_BATTERY_CHARGE_STATE_FAILED or MAV_BATTERY_CHARGE_STATE_UNHEALTHY if any of these are set.
-export type MAV_BATTERY_FAULT =
-  | 1 // MAV_BATTERY_FAULT_DEEP_DISCHARGE - Battery has deep discharged.
-  | 2 // MAV_BATTERY_FAULT_SPIKES - Voltage spikes.
-  | 4 // MAV_BATTERY_FAULT_CELL_FAIL - One or more cells have failed. Battery should also report MAV_BATTERY_CHARGE_STATE_FAILE (and should not be used).
-  | 8 // MAV_BATTERY_FAULT_OVER_CURRENT - Over-current fault.
-  | 16 // MAV_BATTERY_FAULT_OVER_TEMPERATURE - Over-temperature fault.
-  | 32 // MAV_BATTERY_FAULT_UNDER_TEMPERATURE - Under-temperature fault.
-  | 64 // MAV_BATTERY_FAULT_INCOMPATIBLE_VOLTAGE - Vehicle voltage is not compatible with this battery (batteries on same power rail should have similar voltage).
-  | 128 // MAV_BATTERY_FAULT_INCOMPATIBLE_FIRMWARE - Battery firmware is not compatible with current autopilot firmware.
-  | 256 // BATTERY_FAULT_INCOMPATIBLE_CELLS_CONFIGURATION - Battery is not compatible due to cell configuration (e.g. 5s1p when vehicle requires 6s).
-  | number;
-
-// Fuel types for use in FUEL_TYPE. Fuel types specify the units for the maximum, available and consumed fuel, and for the flow rates.
-export type MAV_FUEL_TYPE =
-  | 0 // MAV_FUEL_TYPE_UNKNOWN - Not specified. Fuel levels are normalized (i.e. maximum is 1, and other levels are relative to 1).
-  | 1 // MAV_FUEL_TYPE_LIQUID - A generic liquid fuel. Fuel levels are in millilitres (ml). Fuel rates are in millilitres/second.
-  | 2 // MAV_FUEL_TYPE_GAS - A gas tank. Fuel levels are in kilo-Pascal (kPa), and flow rates are in milliliters per second (ml/s).
-  | number;
-
-// Flags to report status/failure cases for a power generator (used in GENERATOR_STATUS). Note that FAULTS are conditions that cause the generator to fail. Warnings are conditions that require attention before the next use (they indicate the system is not operating properly).
-export type MAV_GENERATOR_STATUS_FLAG =
-  | 1 // MAV_GENERATOR_STATUS_FLAG_OFF - Generator is off.
-  | 2 // MAV_GENERATOR_STATUS_FLAG_READY - Generator is ready to start generating power.
-  | 4 // MAV_GENERATOR_STATUS_FLAG_GENERATING - Generator is generating power.
-  | 8 // MAV_GENERATOR_STATUS_FLAG_CHARGING - Generator is charging the batteries (generating enough power to charge and provide the load).
-  | 16 // MAV_GENERATOR_STATUS_FLAG_REDUCED_POWER - Generator is operating at a reduced maximum power.
-  | 32 // MAV_GENERATOR_STATUS_FLAG_MAXPOWER - Generator is providing the maximum output.
-  | 64 // MAV_GENERATOR_STATUS_FLAG_OVERTEMP_WARNING - Generator is near the maximum operating temperature, cooling is insufficient.
-  | 128 // MAV_GENERATOR_STATUS_FLAG_OVERTEMP_FAULT - Generator hit the maximum operating temperature and shutdown.
-  | 256 // MAV_GENERATOR_STATUS_FLAG_ELECTRONICS_OVERTEMP_WARNING - Power electronics are near the maximum operating temperature, cooling is insufficient.
-  | 512 // MAV_GENERATOR_STATUS_FLAG_ELECTRONICS_OVERTEMP_FAULT - Power electronics hit the maximum operating temperature and shutdown.
-  | 1024 // MAV_GENERATOR_STATUS_FLAG_ELECTRONICS_FAULT - Power electronics experienced a fault and shutdown.
-  | 2048 // MAV_GENERATOR_STATUS_FLAG_POWERSOURCE_FAULT - The power source supplying the generator failed e.g. mechanical generator stopped, tether is no longer providing power, solar cell is in shade, hydrogen reaction no longer happening.
-  | 4096 // MAV_GENERATOR_STATUS_FLAG_COMMUNICATION_WARNING - Generator controller having communication problems.
-  | 8192 // MAV_GENERATOR_STATUS_FLAG_COOLING_WARNING - Power electronic or generator cooling system error.
-  | 16384 // MAV_GENERATOR_STATUS_FLAG_POWER_RAIL_FAULT - Generator controller power rail experienced a fault.
-  | 32768 // MAV_GENERATOR_STATUS_FLAG_OVERCURRENT_FAULT - Generator controller exceeded the overcurrent threshold and shutdown to prevent damage.
-  | 65536 // MAV_GENERATOR_STATUS_FLAG_BATTERY_OVERCHARGE_CURRENT_FAULT - Generator controller detected a high current going into the batteries and shutdown to prevent battery damage.
-  | 131072 // MAV_GENERATOR_STATUS_FLAG_OVERVOLTAGE_FAULT - Generator controller exceeded it&#x27;s overvoltage threshold and shutdown to prevent it exceeding the voltage rating.
-  | 262144 // MAV_GENERATOR_STATUS_FLAG_BATTERY_UNDERVOLT_FAULT - Batteries are under voltage (generator will not start).
-  | 524288 // MAV_GENERATOR_STATUS_FLAG_START_INHIBITED - Generator start is inhibited by e.g. a safety switch.
-  | 1048576 // MAV_GENERATOR_STATUS_FLAG_MAINTENANCE_REQUIRED - Generator requires maintenance.
-  | 2097152 // MAV_GENERATOR_STATUS_FLAG_WARMING_UP - Generator is not ready to generate yet.
-  | 4194304 // MAV_GENERATOR_STATUS_FLAG_IDLE - Generator is idle.
-  | number;
-
-// Enumeration of VTOL states
-export type MAV_VTOL_STATE =
-  | 0 // MAV_VTOL_STATE_UNDEFINED - MAV is not configured as VTOL
-  | 1 // MAV_VTOL_STATE_TRANSITION_TO_FW - VTOL is in transition from multicopter to fixed-wing
-  | 2 // MAV_VTOL_STATE_TRANSITION_TO_MC - VTOL is in transition from fixed-wing to multicopter
-  | 3 // MAV_VTOL_STATE_MC - VTOL is in multicopter state
-  | 4 // MAV_VTOL_STATE_FW - VTOL is in fixed-wing state
-  | number;
-
-// Enumeration of landed detector states
-export type MAV_LANDED_STATE =
-  | 0 // MAV_LANDED_STATE_UNDEFINED - MAV landed state is unknown
-  | 1 // MAV_LANDED_STATE_ON_GROUND - MAV is landed (on ground)
-  | 2 // MAV_LANDED_STATE_IN_AIR - MAV is in air
-  | 3 // MAV_LANDED_STATE_TAKEOFF - MAV currently taking off
-  | 4 // MAV_LANDED_STATE_LANDING - MAV currently landing
-  | number;
-
-// Enumeration of the ADSB altimeter types
-export type ADSB_ALTITUDE_TYPE =
-  | 0 // ADSB_ALTITUDE_TYPE_PRESSURE_QNH - Altitude reported from a Baro source using QNH reference
-  | 1 // ADSB_ALTITUDE_TYPE_GEOMETRIC - Altitude reported from a GNSS source
-  | number;
-
-// ADSB classification for the type of vehicle emitting the transponder signal
-export type ADSB_EMITTER_TYPE =
-  | 0
-  | 1
-  | 2
-  | 3
-  | 4
-  | 5
-  | 6
-  | 7
-  | 8
-  | 9
-  | 10
-  | 11
-  | 12
-  | 13
-  | 14
-  | 15
-  | 16
-  | 17
-  | 18
-  | 19
-  | number;
-
-// These flags indicate status such as data validity of each data source. Set &#x3D; data valid
-export type ADSB_FLAGS =
-  | 1
-  | 2
-  | 4
-  | 8
-  | 16
-  | 32
-  | 64
-  | 128
-  | 256
-  | 32768
-  | number;
-
-// Bitmap of options for the MAV_CMD_DO_REPOSITION
-export type MAV_DO_REPOSITION_FLAGS =
-  | 1 // MAV_DO_REPOSITION_FLAGS_CHANGE_MODE - The aircraft should immediately transition into guided. This should not be set for follow me applications
-  | 2 // MAV_DO_REPOSITION_FLAGS_RELATIVE_YAW - Yaw relative to the vehicle current heading (if not set, relative to North).
-  | number;
-
-// Speed setpoint types used in MAV_CMD_DO_CHANGE_SPEED
-export type SPEED_TYPE =
-  | 0 // SPEED_TYPE_AIRSPEED - Airspeed
-  | 1 // SPEED_TYPE_GROUNDSPEED - Groundspeed
-  | 2 // SPEED_TYPE_CLIMB_SPEED - Climb speed
-  | 3 // SPEED_TYPE_DESCENT_SPEED - Descent speed
-  | number;
-
-// Flags in ESTIMATOR_STATUS message
-export type ESTIMATOR_STATUS_FLAGS =
-  | 1 // ESTIMATOR_ATTITUDE - True if the attitude estimate is good
-  | 2 // ESTIMATOR_VELOCITY_HORIZ - True if the horizontal velocity estimate is good
-  | 4 // ESTIMATOR_VELOCITY_VERT - True if the  vertical velocity estimate is good
-  | 8 // ESTIMATOR_POS_HORIZ_REL - True if the horizontal position (relative) estimate is good
-  | 16 // ESTIMATOR_POS_HORIZ_ABS - True if the horizontal position (absolute) estimate is good
-  | 32 // ESTIMATOR_POS_VERT_ABS - True if the vertical position (absolute) estimate is good
-  | 64 // ESTIMATOR_POS_VERT_AGL - True if the vertical position (above ground) estimate is good
-  | 128 // ESTIMATOR_CONST_POS_MODE - True if the EKF is in a constant position mode and is not using external measurements (eg GPS or optical flow)
-  | 256 // ESTIMATOR_PRED_POS_HORIZ_REL - True if the EKF has sufficient data to enter a mode that will provide a (relative) position estimate
-  | 512 // ESTIMATOR_PRED_POS_HORIZ_ABS - True if the EKF has sufficient data to enter a mode that will provide a (absolute) position estimate
-  | 1024 // ESTIMATOR_GPS_GLITCH - True if the EKF has detected a GPS glitch
-  | 2048 // ESTIMATOR_ACCEL_ERROR - True if the EKF has detected bad accelerometer data
-  | number;
-
-// Sequence that motors are tested when using MAV_CMD_DO_MOTOR_TEST.
-export type MOTOR_TEST_ORDER =
-  | 0 // MOTOR_TEST_ORDER_DEFAULT - Default autopilot motor test method.
-  | 1 // MOTOR_TEST_ORDER_SEQUENCE - Motor numbers are specified as their index in a predefined vehicle-specific sequence.
-  | 2 // MOTOR_TEST_ORDER_BOARD - Motor numbers are specified as the output as labeled on the board.
-  | number;
-
-// Defines how throttle value is represented in MAV_CMD_DO_MOTOR_TEST.
-export type MOTOR_TEST_THROTTLE_TYPE =
-  | 0 // MOTOR_TEST_THROTTLE_PERCENT - Throttle as a percentage (0 ~ 100)
-  | 1 // MOTOR_TEST_THROTTLE_PWM - Throttle as an absolute PWM value (normally in range of 1000~2000).
-  | 2 // MOTOR_TEST_THROTTLE_PILOT - Throttle pass-through from pilot&#x27;s transmitter.
-  | 3 // MOTOR_TEST_COMPASS_CAL - Per-motor compass calibration test.
-  | number;
-
-export type GPS_INPUT_IGNORE_FLAGS =
-  | 1 // GPS_INPUT_IGNORE_FLAG_ALT - ignore altitude field
-  | 2 // GPS_INPUT_IGNORE_FLAG_HDOP - ignore hdop field
-  | 4 // GPS_INPUT_IGNORE_FLAG_VDOP - ignore vdop field
-  | 8 // GPS_INPUT_IGNORE_FLAG_VEL_HORIZ - ignore horizontal velocity field (vn and ve)
-  | 16 // GPS_INPUT_IGNORE_FLAG_VEL_VERT - ignore vertical velocity field (vd)
-  | 32 // GPS_INPUT_IGNORE_FLAG_SPEED_ACCURACY - ignore speed accuracy field
-  | 64 // GPS_INPUT_IGNORE_FLAG_HORIZONTAL_ACCURACY - ignore horizontal accuracy field
-  | 128 // GPS_INPUT_IGNORE_FLAG_VERTICAL_ACCURACY - ignore vertical accuracy field
-  | number;
-
-// Possible actions an aircraft can take to avoid a collision.
-export type MAV_COLLISION_ACTION =
-  | 0 // MAV_COLLISION_ACTION_NONE - Ignore any potential collisions
-  | 1 // MAV_COLLISION_ACTION_REPORT - Report potential collision
-  | 2 // MAV_COLLISION_ACTION_ASCEND_OR_DESCEND - Ascend or Descend to avoid threat
-  | 3 // MAV_COLLISION_ACTION_MOVE_HORIZONTALLY - Move horizontally to avoid threat
-  | 4 // MAV_COLLISION_ACTION_MOVE_PERPENDICULAR - Aircraft to move perpendicular to the collision&#x27;s velocity vector
-  | 5 // MAV_COLLISION_ACTION_RTL - Aircraft to fly directly back to its launch point
-  | 6 // MAV_COLLISION_ACTION_HOVER - Aircraft to stop in place
-  | number;
-
-// Aircraft-rated danger from this threat.
-export type MAV_COLLISION_THREAT_LEVEL =
-  | 0 // MAV_COLLISION_THREAT_LEVEL_NONE - Not a threat
-  | 1 // MAV_COLLISION_THREAT_LEVEL_LOW - Craft is mildly concerned about this threat
-  | 2 // MAV_COLLISION_THREAT_LEVEL_HIGH - Craft is panicking, and may take actions to avoid threat
-  | number;
-
-// Source of information about this collision.
-export type MAV_COLLISION_SRC =
-  | 0 // MAV_COLLISION_SRC_ADSB - ID field references ADSB_VEHICLE packets
-  | 1 // MAV_COLLISION_SRC_MAVLINK_GPS_GLOBAL_INT - ID field references MAVLink SRC ID
-  | number;
-
-// Type of GPS fix
-export type GPS_FIX_TYPE =
-  | 0 // GPS_FIX_TYPE_NO_GPS - No GPS connected
-  | 1 // GPS_FIX_TYPE_NO_FIX - No position information, GPS is connected
-  | 2 // GPS_FIX_TYPE_2D_FIX - 2D position
-  | 3 // GPS_FIX_TYPE_3D_FIX - 3D position
-  | 4 // GPS_FIX_TYPE_DGPS - DGPS/SBAS aided 3D position
-  | 5 // GPS_FIX_TYPE_RTK_FLOAT - RTK float, 3D position
-  | 6 // GPS_FIX_TYPE_RTK_FIXED - RTK Fixed, 3D position
-  | 7 // GPS_FIX_TYPE_STATIC - Static fixed, typically used for base stations
-  | 8 // GPS_FIX_TYPE_PPP - PPP, 3D position.
-  | number;
-
-// RTK GPS baseline coordinate system, used for RTK corrections
-export type RTK_BASELINE_COORDINATE_SYSTEM =
-  | 0 // RTK_BASELINE_COORDINATE_SYSTEM_ECEF - Earth-centered, Earth-fixed
-  | 1 // RTK_BASELINE_COORDINATE_SYSTEM_NED - RTK basestation centered, north, east, down
-  | number;
-
-// Type of landing target
-export type LANDING_TARGET_TYPE =
-  | 0 // LANDING_TARGET_TYPE_LIGHT_BEACON - Landing target signaled by light beacon (ex: IR-LOCK)
-  | 1 // LANDING_TARGET_TYPE_RADIO_BEACON - Landing target signaled by radio beacon (ex: ILS, NDB)
-  | 2 // LANDING_TARGET_TYPE_VISION_FIDUCIAL - Landing target represented by a fiducial marker (ex: ARTag)
-  | 3 // LANDING_TARGET_TYPE_VISION_OTHER - Landing target represented by a pre-defined visual shape/feature (ex: X-marker, H-marker, square)
-  | number;
-
-// Direction of VTOL transition
-export type VTOL_TRANSITION_HEADING =
-  | 0 // VTOL_TRANSITION_HEADING_VEHICLE_DEFAULT - Respect the heading configuration of the vehicle.
-  | 1 // VTOL_TRANSITION_HEADING_NEXT_WAYPOINT - Use the heading pointing towards the next waypoint.
-  | 2 // VTOL_TRANSITION_HEADING_TAKEOFF - Use the heading on takeoff (while sitting on the ground).
-  | 3 // VTOL_TRANSITION_HEADING_SPECIFIED - Use the specified heading in parameter 4.
-  | 4 // VTOL_TRANSITION_HEADING_ANY - Use the current heading when reaching takeoff altitude (potentially facing the wind when weather-vaning is active).
-  | number;
-
-// Camera capability flags (Bitmap)
-export type CAMERA_CAP_FLAGS =
-  | 1 // CAMERA_CAP_FLAGS_CAPTURE_VIDEO - Camera is able to record video
-  | 2 // CAMERA_CAP_FLAGS_CAPTURE_IMAGE - Camera is able to capture images
-  | 4 // CAMERA_CAP_FLAGS_HAS_MODES - Camera has separate Video and Image/Photo modes (MAV_CMD_SET_CAMERA_MODE)
-  | 8 // CAMERA_CAP_FLAGS_CAN_CAPTURE_IMAGE_IN_VIDEO_MODE - Camera can capture images while in video mode
-  | 16 // CAMERA_CAP_FLAGS_CAN_CAPTURE_VIDEO_IN_IMAGE_MODE - Camera can capture videos while in Photo/Image mode
-  | 32 // CAMERA_CAP_FLAGS_HAS_IMAGE_SURVEY_MODE - Camera has image survey mode (MAV_CMD_SET_CAMERA_MODE)
-  | 64 // CAMERA_CAP_FLAGS_HAS_BASIC_ZOOM - Camera has basic zoom control (MAV_CMD_SET_CAMERA_ZOOM)
-  | 128 // CAMERA_CAP_FLAGS_HAS_BASIC_FOCUS - Camera has basic focus control (MAV_CMD_SET_CAMERA_FOCUS)
-  | 256 // CAMERA_CAP_FLAGS_HAS_VIDEO_STREAM - Camera has video streaming capabilities (request VIDEO_STREAM_INFORMATION with MAV_CMD_REQUEST_MESSAGE for video streaming info)
-  | 512 // CAMERA_CAP_FLAGS_HAS_TRACKING_POINT - Camera supports tracking of a point on the camera view.
-  | 1024 // CAMERA_CAP_FLAGS_HAS_TRACKING_RECTANGLE - Camera supports tracking of a selection rectangle on the camera view.
-  | 2048 // CAMERA_CAP_FLAGS_HAS_TRACKING_GEO_STATUS - Camera supports tracking geo status (CAMERA_TRACKING_GEO_STATUS).
-  | 4096 // CAMERA_CAP_FLAGS_HAS_THERMAL_RANGE - Camera supports absolute thermal range (request CAMERA_THERMAL_RANGE with MAV_CMD_REQUEST_MESSAGE).
-  | number;
-
-// Stream status flags (Bitmap)
-export type VIDEO_STREAM_STATUS_FLAGS =
-  | 1 // VIDEO_STREAM_STATUS_FLAGS_RUNNING - Stream is active (running)
-  | 2 // VIDEO_STREAM_STATUS_FLAGS_THERMAL - Stream is thermal imaging
-  | 4 // VIDEO_STREAM_STATUS_FLAGS_THERMAL_RANGE_ENABLED - Stream can report absolute thermal range (see CAMERA_THERMAL_RANGE).
-  | number;
-
-// Video stream types
-export type VIDEO_STREAM_TYPE =
-  | 0 // VIDEO_STREAM_TYPE_RTSP - Stream is RTSP
-  | 1 // VIDEO_STREAM_TYPE_RTPUDP - Stream is RTP UDP (URI gives the port number)
-  | 2 // VIDEO_STREAM_TYPE_TCP_MPEG - Stream is MPEG on TCP
-  | 3 // VIDEO_STREAM_TYPE_MPEG_TS - Stream is MPEG TS (URI gives the port number)
-  | number;
-
-// Video stream encodings
-export type VIDEO_STREAM_ENCODING =
-  | 0 // VIDEO_STREAM_ENCODING_UNKNOWN - Stream encoding is unknown
-  | 1 // VIDEO_STREAM_ENCODING_H264 - Stream encoding is H.264
-  | 2 // VIDEO_STREAM_ENCODING_H265 - Stream encoding is H.265
-  | number;
-
-// Camera tracking status flags
-export type CAMERA_TRACKING_STATUS_FLAGS =
-  | 0 // CAMERA_TRACKING_STATUS_FLAGS_IDLE - Camera is not tracking
-  | 1 // CAMERA_TRACKING_STATUS_FLAGS_ACTIVE - Camera is tracking
-  | 2 // CAMERA_TRACKING_STATUS_FLAGS_ERROR - Camera tracking in error state
-  | number;
-
-// Camera tracking modes
-export type CAMERA_TRACKING_MODE =
-  | 0 // CAMERA_TRACKING_MODE_NONE - Not tracking
-  | 1 // CAMERA_TRACKING_MODE_POINT - Target is a point
-  | 2 // CAMERA_TRACKING_MODE_RECTANGLE - Target is a rectangle
-  | number;
-
-// Camera tracking target data (shows where tracked target is within image)
-export type CAMERA_TRACKING_TARGET_DATA =
-  | 1 // CAMERA_TRACKING_TARGET_DATA_EMBEDDED - Target data embedded in image data (proprietary)
-  | 2 // CAMERA_TRACKING_TARGET_DATA_RENDERED - Target data rendered in image
-  | 4 // CAMERA_TRACKING_TARGET_DATA_IN_STATUS - Target data within status message (Point or Rectangle)
-  | number;
-
-// Zoom types for MAV_CMD_SET_CAMERA_ZOOM
-export type CAMERA_ZOOM_TYPE =
-  | 0 // ZOOM_TYPE_STEP - Zoom one step increment (-1 for wide, 1 for tele)
-  | 1 // ZOOM_TYPE_CONTINUOUS - Continuous normalized zoom in/out rate until stopped. Range -1..1, negative: wide, positive: narrow/tele, 0 to stop zooming. Other values should be clipped to the range.
-  | 2 // ZOOM_TYPE_RANGE - Zoom value as proportion of full camera range (a percentage value between 0.0 and 100.0)
-  | 3 // ZOOM_TYPE_FOCAL_LENGTH - Zoom value/variable focal length in millimetres. Note that there is no message to get the valid zoom range of the camera, so this can type can only be used for cameras where the zoom range is known (implying that this cannot reliably be used in a GCS for an arbitrary camera)
-  | 4 // ZOOM_TYPE_HORIZONTAL_FOV - Zoom value as horizontal field of view in degrees.
-  | number;
-
-// Focus types for MAV_CMD_SET_CAMERA_FOCUS
-export type SET_FOCUS_TYPE =
-  | 0 // FOCUS_TYPE_STEP - Focus one step increment (-1 for focusing in, 1 for focusing out towards infinity).
-  | 1 // FOCUS_TYPE_CONTINUOUS - Continuous normalized focus in/out rate until stopped. Range -1..1, negative: in, positive: out towards infinity, 0 to stop focusing. Other values should be clipped to the range.
-  | 2 // FOCUS_TYPE_RANGE - Focus value as proportion of full camera focus range (a value between 0.0 and 100.0)
-  | 3 // FOCUS_TYPE_METERS - Focus value in metres. Note that there is no message to get the valid focus range of the camera, so this can type can only be used for cameras where the range is known (implying that this cannot reliably be used in a GCS for an arbitrary camera).
-  | 4 // FOCUS_TYPE_AUTO - Focus automatically.
-  | 5 // FOCUS_TYPE_AUTO_SINGLE - Single auto focus. Mainly used for still pictures. Usually abbreviated as AF-S.
-  | 6 // FOCUS_TYPE_AUTO_CONTINUOUS - Continuous auto focus. Mainly used for dynamic scenes. Abbreviated as AF-C.
-  | number;
-
-// Camera sources for MAV_CMD_SET_CAMERA_SOURCE
-export type CAMERA_SOURCE =
-  | 0 // CAMERA_SOURCE_DEFAULT - Default camera source.
-  | 1 // CAMERA_SOURCE_RGB - RGB camera source.
-  | 2 // CAMERA_SOURCE_IR - IR camera source.
-  | 3 // CAMERA_SOURCE_NDVI - NDVI camera source.
-  | number;
-
-// Result from PARAM_EXT_SET message.
-export type PARAM_ACK =
-  | 0 // PARAM_ACK_ACCEPTED - Parameter value ACCEPTED and SET
-  | 1 // PARAM_ACK_VALUE_UNSUPPORTED - Parameter value UNKNOWN/UNSUPPORTED
-  | 2 // PARAM_ACK_FAILED - Parameter failed to set
-  | 3 // PARAM_ACK_IN_PROGRESS - Parameter value received but not yet set/accepted. A subsequent PARAM_EXT_ACK with the final result will follow once operation is completed. This is returned immediately for parameters that take longer to set, indicating that the the parameter was received and does not need to be resent.
-  | number;
-
-// Camera Modes.
-export type CAMERA_MODE =
-  | 0 // CAMERA_MODE_IMAGE - Camera is in image/photo capture mode.
-  | 1 // CAMERA_MODE_VIDEO - Camera is in video capture mode.
-  | 2 // CAMERA_MODE_IMAGE_SURVEY - Camera is in image survey capture mode. It allows for camera controller to do specific settings for surveys.
-  | number;
-
-export type MAV_ARM_AUTH_DENIED_REASON =
-  | 0 // MAV_ARM_AUTH_DENIED_REASON_GENERIC - Not a specific reason
-  | 1 // MAV_ARM_AUTH_DENIED_REASON_NONE - Authorizer will send the error as string to GCS
-  | 2 // MAV_ARM_AUTH_DENIED_REASON_INVALID_WAYPOINT - At least one waypoint have a invalid value
-  | 3 // MAV_ARM_AUTH_DENIED_REASON_TIMEOUT - Timeout in the authorizer process(in case it depends on network)
-  | 4 // MAV_ARM_AUTH_DENIED_REASON_AIRSPACE_IN_USE - Airspace of the mission in use by another vehicle, second result parameter can have the waypoint id that caused it to be denied.
-  | 5 // MAV_ARM_AUTH_DENIED_REASON_BAD_WEATHER - Weather is not good to fly
-  | number;
-
-// RC type. Used in MAV_CMD_START_RX_PAIR.
-export type RC_TYPE =
-  | 0 // RC_TYPE_SPEKTRUM - Spektrum
-  | 1 // RC_TYPE_CRSF - CRSF
-  | number;
-
-// RC sub-type of types defined in RC_TYPE. Used in MAV_CMD_START_RX_PAIR. Ignored if value does not correspond to the set RC_TYPE.
-export type RC_SUB_TYPE =
-  | 0 // RC_SUB_TYPE_SPEKTRUM_DSM2 - Spektrum DSM2
-  | 1 // RC_SUB_TYPE_SPEKTRUM_DSMX - Spektrum DSMX
-  | 2 // RC_SUB_TYPE_SPEKTRUM_DSMX8 - Spektrum DSMX8
-  | number;
-
-// Bitmap to indicate which dimensions should be ignored by the vehicle: a value of 0b0000000000000000 or 0b0000001000000000 indicates that none of the setpoint dimensions should be ignored. If bit 9 is set the floats afx afy afz should be interpreted as force instead of acceleration.
-export type POSITION_TARGET_TYPEMASK =
-  | 1 // POSITION_TARGET_TYPEMASK_X_IGNORE - Ignore position x
-  | 2 // POSITION_TARGET_TYPEMASK_Y_IGNORE - Ignore position y
-  | 4 // POSITION_TARGET_TYPEMASK_Z_IGNORE - Ignore position z
-  | 8 // POSITION_TARGET_TYPEMASK_VX_IGNORE - Ignore velocity x
-  | 16 // POSITION_TARGET_TYPEMASK_VY_IGNORE - Ignore velocity y
-  | 32 // POSITION_TARGET_TYPEMASK_VZ_IGNORE - Ignore velocity z
-  | 64 // POSITION_TARGET_TYPEMASK_AX_IGNORE - Ignore acceleration x
-  | 128 // POSITION_TARGET_TYPEMASK_AY_IGNORE - Ignore acceleration y
-  | 256 // POSITION_TARGET_TYPEMASK_AZ_IGNORE - Ignore acceleration z
-  | 512 // POSITION_TARGET_TYPEMASK_FORCE_SET - Use force instead of acceleration
-  | 1024 // POSITION_TARGET_TYPEMASK_YAW_IGNORE - Ignore yaw
-  | 2048 // POSITION_TARGET_TYPEMASK_YAW_RATE_IGNORE - Ignore yaw rate
-  | number;
-
-// Bitmap to indicate which dimensions should be ignored by the vehicle: a value of 0b00000000 indicates that none of the setpoint dimensions should be ignored.
-export type ATTITUDE_TARGET_TYPEMASK =
-  | 1 // ATTITUDE_TARGET_TYPEMASK_BODY_ROLL_RATE_IGNORE - Ignore body roll rate
-  | 2 // ATTITUDE_TARGET_TYPEMASK_BODY_PITCH_RATE_IGNORE - Ignore body pitch rate
-  | 4 // ATTITUDE_TARGET_TYPEMASK_BODY_YAW_RATE_IGNORE - Ignore body yaw rate
-  | 32 // ATTITUDE_TARGET_TYPEMASK_THRUST_BODY_SET - Use 3D body thrust setpoint instead of throttle
-  | 64 // ATTITUDE_TARGET_TYPEMASK_THROTTLE_IGNORE - Ignore throttle
-  | 128 // ATTITUDE_TARGET_TYPEMASK_ATTITUDE_IGNORE - Ignore attitude
-  | number;
-
-// Airborne status of UAS.
-export type UTM_FLIGHT_STATE =
-  | 1 // UTM_FLIGHT_STATE_UNKNOWN - The flight state can&#x27;t be determined.
-  | 2 // UTM_FLIGHT_STATE_GROUND - UAS on ground.
-  | 3 // UTM_FLIGHT_STATE_AIRBORNE - UAS airborne.
-  | 16 // UTM_FLIGHT_STATE_EMERGENCY - UAS is in an emergency flight state.
-  | 32 // UTM_FLIGHT_STATE_NOCTRL - UAS has no active controls.
-  | number;
-
-// Flags for the global position report.
-export type UTM_DATA_AVAIL_FLAGS =
-  | 1 // UTM_DATA_AVAIL_FLAGS_TIME_VALID - The field time contains valid data.
-  | 2 // UTM_DATA_AVAIL_FLAGS_UAS_ID_AVAILABLE - The field uas_id contains valid data.
-  | 4 // UTM_DATA_AVAIL_FLAGS_POSITION_AVAILABLE - The fields lat, lon and h_acc contain valid data.
-  | 8 // UTM_DATA_AVAIL_FLAGS_ALTITUDE_AVAILABLE - The fields alt and v_acc contain valid data.
-  | 16 // UTM_DATA_AVAIL_FLAGS_RELATIVE_ALTITUDE_AVAILABLE - The field relative_alt contains valid data.
-  | 32 // UTM_DATA_AVAIL_FLAGS_HORIZONTAL_VELO_AVAILABLE - The fields vx and vy contain valid data.
-  | 64 // UTM_DATA_AVAIL_FLAGS_VERTICAL_VELO_AVAILABLE - The field vz contains valid data.
-  | 128 // UTM_DATA_AVAIL_FLAGS_NEXT_WAYPOINT_AVAILABLE - The fields next_lat, next_lon and next_alt contain valid data.
-  | number;
-
-// These flags encode the cellular network status
-export type CELLULAR_STATUS_FLAG =
-  | 0 // CELLULAR_STATUS_FLAG_UNKNOWN - State unknown or not reportable.
-  | 1 // CELLULAR_STATUS_FLAG_FAILED - Modem is unusable
-  | 2 // CELLULAR_STATUS_FLAG_INITIALIZING - Modem is being initialized
-  | 3 // CELLULAR_STATUS_FLAG_LOCKED - Modem is locked
-  | 4 // CELLULAR_STATUS_FLAG_DISABLED - Modem is not enabled and is powered down
-  | 5 // CELLULAR_STATUS_FLAG_DISABLING - Modem is currently transitioning to the CELLULAR_STATUS_FLAG_DISABLED state
-  | 6 // CELLULAR_STATUS_FLAG_ENABLING - Modem is currently transitioning to the CELLULAR_STATUS_FLAG_ENABLED state
-  | 7 // CELLULAR_STATUS_FLAG_ENABLED - Modem is enabled and powered on but not registered with a network provider and not available for data connections
-  | 8 // CELLULAR_STATUS_FLAG_SEARCHING - Modem is searching for a network provider to register
-  | 9 // CELLULAR_STATUS_FLAG_REGISTERED - Modem is registered with a network provider, and data connections and messaging may be available for use
-  | 10 // CELLULAR_STATUS_FLAG_DISCONNECTING - Modem is disconnecting and deactivating the last active packet data bearer. This state will not be entered if more than one packet data bearer is active and one of the active bearers is deactivated
-  | 11 // CELLULAR_STATUS_FLAG_CONNECTING - Modem is activating and connecting the first packet data bearer. Subsequent bearer activations when another bearer is already active do not cause this state to be entered
-  | 12 // CELLULAR_STATUS_FLAG_CONNECTED - One or more packet data bearers is active and connected
-  | number;
-
-// These flags are used to diagnose the failure state of CELLULAR_STATUS
-export type CELLULAR_NETWORK_FAILED_REASON =
-  | 0 // CELLULAR_NETWORK_FAILED_REASON_NONE - No error
-  | 1 // CELLULAR_NETWORK_FAILED_REASON_UNKNOWN - Error state is unknown
-  | 2 // CELLULAR_NETWORK_FAILED_REASON_SIM_MISSING - SIM is required for the modem but missing
-  | 3 // CELLULAR_NETWORK_FAILED_REASON_SIM_ERROR - SIM is available, but not usable for connection
-  | number;
-
-// Cellular network radio type
-export type CELLULAR_NETWORK_RADIO_TYPE =
-  | 0
-  | 1
-  | 2
-  | 3
-  | 4
-  | number;
-
-// Precision land modes (used in MAV_CMD_NAV_LAND).
-export type PRECISION_LAND_MODE =
-  | 0 // PRECISION_LAND_MODE_DISABLED - Normal (non-precision) landing.
-  | 1 // PRECISION_LAND_MODE_OPPORTUNISTIC - Use precision landing if beacon detected when land command accepted, otherwise land normally.
-  | 2 // PRECISION_LAND_MODE_REQUIRED - Use precision landing, searching for beacon if not found when land command accepted (land normally if beacon cannot be found).
-  | number;
-
-// Parachute actions. Trigger release and enable/disable auto-release.
-export type PARACHUTE_ACTION =
-  | 0 // PARACHUTE_DISABLE - Disable auto-release of parachute (i.e. release triggered by crash detectors).
-  | 1 // PARACHUTE_ENABLE - Enable auto-release of parachute.
-  | 2 // PARACHUTE_RELEASE - Release parachute and kill motors.
-  | number;
-
-export type MAV_TUNNEL_PAYLOAD_TYPE =
-  | 0 // MAV_TUNNEL_PAYLOAD_TYPE_UNKNOWN - Encoding of payload unknown.
-  | 200 // MAV_TUNNEL_PAYLOAD_TYPE_STORM32_RESERVED0 - Registered for STorM32 gimbal controller.
-  | 201 // MAV_TUNNEL_PAYLOAD_TYPE_STORM32_RESERVED1 - Registered for STorM32 gimbal controller.
-  | 202 // MAV_TUNNEL_PAYLOAD_TYPE_STORM32_RESERVED2 - Registered for STorM32 gimbal controller.
-  | 203 // MAV_TUNNEL_PAYLOAD_TYPE_STORM32_RESERVED3 - Registered for STorM32 gimbal controller.
-  | 204 // MAV_TUNNEL_PAYLOAD_TYPE_STORM32_RESERVED4 - Registered for STorM32 gimbal controller.
-  | 205 // MAV_TUNNEL_PAYLOAD_TYPE_STORM32_RESERVED5 - Registered for STorM32 gimbal controller.
-  | 206 // MAV_TUNNEL_PAYLOAD_TYPE_STORM32_RESERVED6 - Registered for STorM32 gimbal controller.
-  | 207 // MAV_TUNNEL_PAYLOAD_TYPE_STORM32_RESERVED7 - Registered for STorM32 gimbal controller.
-  | 208 // MAV_TUNNEL_PAYLOAD_TYPE_STORM32_RESERVED8 - Registered for STorM32 gimbal controller.
-  | 209 // MAV_TUNNEL_PAYLOAD_TYPE_STORM32_RESERVED9 - Registered for STorM32 gimbal controller.
-  | 210 // MAV_TUNNEL_PAYLOAD_TYPE_MODALAI_REMOTE_OSD - Registered for ModalAI remote OSD protocol.
-  | 211 // MAV_TUNNEL_PAYLOAD_TYPE_MODALAI_ESC_UART_PASSTHRU - Registered for ModalAI ESC UART passthru protocol.
-  | 212 // MAV_TUNNEL_PAYLOAD_TYPE_MODALAI_IO_UART_PASSTHRU - Registered for ModalAI vendor use.
-  | number;
-
-export type MAV_ODID_ID_TYPE =
-  | 0 // MAV_ODID_ID_TYPE_NONE - No type defined.
-  | 1 // MAV_ODID_ID_TYPE_SERIAL_NUMBER - Manufacturer Serial Number (ANSI/CTA-2063 format).
-  | 2 // MAV_ODID_ID_TYPE_CAA_REGISTRATION_ID - CAA (Civil Aviation Authority) registered ID. Format: [ICAO Country Code].[CAA Assigned ID].
-  | 3 // MAV_ODID_ID_TYPE_UTM_ASSIGNED_UUID - UTM (Unmanned Traffic Management) assigned UUID (RFC4122).
-  | 4 // MAV_ODID_ID_TYPE_SPECIFIC_SESSION_ID - A 20 byte ID for a specific flight/session. The exact ID type is indicated by the first byte of uas_id and these type values are managed by ICAO.
-  | number;
-
-export type MAV_ODID_UA_TYPE =
-  | 0 // MAV_ODID_UA_TYPE_NONE - No UA (Unmanned Aircraft) type defined.
-  | 1 // MAV_ODID_UA_TYPE_AEROPLANE - Aeroplane/Airplane. Fixed wing.
-  | 2 // MAV_ODID_UA_TYPE_HELICOPTER_OR_MULTIROTOR - Helicopter or multirotor.
-  | 3 // MAV_ODID_UA_TYPE_GYROPLANE - Gyroplane.
-  | 4 // MAV_ODID_UA_TYPE_HYBRID_LIFT - VTOL (Vertical Take-Off and Landing). Fixed wing aircraft that can take off vertically.
-  | 5 // MAV_ODID_UA_TYPE_ORNITHOPTER - Ornithopter.
-  | 6 // MAV_ODID_UA_TYPE_GLIDER - Glider.
-  | 7 // MAV_ODID_UA_TYPE_KITE - Kite.
-  | 8 // MAV_ODID_UA_TYPE_FREE_BALLOON - Free Balloon.
-  | 9 // MAV_ODID_UA_TYPE_CAPTIVE_BALLOON - Captive Balloon.
-  | 10 // MAV_ODID_UA_TYPE_AIRSHIP - Airship. E.g. a blimp.
-  | 11 // MAV_ODID_UA_TYPE_FREE_FALL_PARACHUTE - Free Fall/Parachute (unpowered).
-  | 12 // MAV_ODID_UA_TYPE_ROCKET - Rocket.
-  | 13 // MAV_ODID_UA_TYPE_TETHERED_POWERED_AIRCRAFT - Tethered powered aircraft.
-  | 14 // MAV_ODID_UA_TYPE_GROUND_OBSTACLE - Ground Obstacle.
-  | 15 // MAV_ODID_UA_TYPE_OTHER - Other type of aircraft not listed earlier.
-  | number;
-
-export type MAV_ODID_STATUS =
-  | 0 // MAV_ODID_STATUS_UNDECLARED - The status of the (UA) Unmanned Aircraft is undefined.
-  | 1 // MAV_ODID_STATUS_GROUND - The UA is on the ground.
-  | 2 // MAV_ODID_STATUS_AIRBORNE - The UA is in the air.
-  | 3 // MAV_ODID_STATUS_EMERGENCY - The UA is having an emergency.
-  | 4 // MAV_ODID_STATUS_REMOTE_ID_SYSTEM_FAILURE - The remote ID system is failing or unreliable in some way.
-  | number;
-
-export type MAV_ODID_HEIGHT_REF =
-  | 0 // MAV_ODID_HEIGHT_REF_OVER_TAKEOFF - The height field is relative to the take-off location.
-  | 1 // MAV_ODID_HEIGHT_REF_OVER_GROUND - The height field is relative to ground.
-  | number;
-
-export type MAV_ODID_HOR_ACC =
-  | 0 // MAV_ODID_HOR_ACC_UNKNOWN - The horizontal accuracy is unknown.
-  | 1 // MAV_ODID_HOR_ACC_10NM - The horizontal accuracy is smaller than 10 Nautical Miles. 18.52 km.
-  | 2 // MAV_ODID_HOR_ACC_4NM - The horizontal accuracy is smaller than 4 Nautical Miles. 7.408 km.
-  | 3 // MAV_ODID_HOR_ACC_2NM - The horizontal accuracy is smaller than 2 Nautical Miles. 3.704 km.
-  | 4 // MAV_ODID_HOR_ACC_1NM - The horizontal accuracy is smaller than 1 Nautical Miles. 1.852 km.
-  | 5 // MAV_ODID_HOR_ACC_0_5NM - The horizontal accuracy is smaller than 0.5 Nautical Miles. 926 m.
-  | 6 // MAV_ODID_HOR_ACC_0_3NM - The horizontal accuracy is smaller than 0.3 Nautical Miles. 555.6 m.
-  | 7 // MAV_ODID_HOR_ACC_0_1NM - The horizontal accuracy is smaller than 0.1 Nautical Miles. 185.2 m.
-  | 8 // MAV_ODID_HOR_ACC_0_05NM - The horizontal accuracy is smaller than 0.05 Nautical Miles. 92.6 m.
-  | 9 // MAV_ODID_HOR_ACC_30_METER - The horizontal accuracy is smaller than 30 meter.
-  | 10 // MAV_ODID_HOR_ACC_10_METER - The horizontal accuracy is smaller than 10 meter.
-  | 11 // MAV_ODID_HOR_ACC_3_METER - The horizontal accuracy is smaller than 3 meter.
-  | 12 // MAV_ODID_HOR_ACC_1_METER - The horizontal accuracy is smaller than 1 meter.
-  | number;
-
-export type MAV_ODID_VER_ACC =
-  | 0 // MAV_ODID_VER_ACC_UNKNOWN - The vertical accuracy is unknown.
-  | 1 // MAV_ODID_VER_ACC_150_METER - The vertical accuracy is smaller than 150 meter.
-  | 2 // MAV_ODID_VER_ACC_45_METER - The vertical accuracy is smaller than 45 meter.
-  | 3 // MAV_ODID_VER_ACC_25_METER - The vertical accuracy is smaller than 25 meter.
-  | 4 // MAV_ODID_VER_ACC_10_METER - The vertical accuracy is smaller than 10 meter.
-  | 5 // MAV_ODID_VER_ACC_3_METER - The vertical accuracy is smaller than 3 meter.
-  | 6 // MAV_ODID_VER_ACC_1_METER - The vertical accuracy is smaller than 1 meter.
-  | number;
-
-export type MAV_ODID_SPEED_ACC =
-  | 0 // MAV_ODID_SPEED_ACC_UNKNOWN - The speed accuracy is unknown.
-  | 1 // MAV_ODID_SPEED_ACC_10_METERS_PER_SECOND - The speed accuracy is smaller than 10 meters per second.
-  | 2 // MAV_ODID_SPEED_ACC_3_METERS_PER_SECOND - The speed accuracy is smaller than 3 meters per second.
-  | 3 // MAV_ODID_SPEED_ACC_1_METERS_PER_SECOND - The speed accuracy is smaller than 1 meters per second.
-  | 4 // MAV_ODID_SPEED_ACC_0_3_METERS_PER_SECOND - The speed accuracy is smaller than 0.3 meters per second.
-  | number;
-
-export type MAV_ODID_TIME_ACC =
-  | 0 // MAV_ODID_TIME_ACC_UNKNOWN - The timestamp accuracy is unknown.
-  | 1 // MAV_ODID_TIME_ACC_0_1_SECOND - The timestamp accuracy is smaller than or equal to 0.1 second.
-  | 2 // MAV_ODID_TIME_ACC_0_2_SECOND - The timestamp accuracy is smaller than or equal to 0.2 second.
-  | 3 // MAV_ODID_TIME_ACC_0_3_SECOND - The timestamp accuracy is smaller than or equal to 0.3 second.
-  | 4 // MAV_ODID_TIME_ACC_0_4_SECOND - The timestamp accuracy is smaller than or equal to 0.4 second.
-  | 5 // MAV_ODID_TIME_ACC_0_5_SECOND - The timestamp accuracy is smaller than or equal to 0.5 second.
-  | 6 // MAV_ODID_TIME_ACC_0_6_SECOND - The timestamp accuracy is smaller than or equal to 0.6 second.
-  | 7 // MAV_ODID_TIME_ACC_0_7_SECOND - The timestamp accuracy is smaller than or equal to 0.7 second.
-  | 8 // MAV_ODID_TIME_ACC_0_8_SECOND - The timestamp accuracy is smaller than or equal to 0.8 second.
-  | 9 // MAV_ODID_TIME_ACC_0_9_SECOND - The timestamp accuracy is smaller than or equal to 0.9 second.
-  | 10 // MAV_ODID_TIME_ACC_1_0_SECOND - The timestamp accuracy is smaller than or equal to 1.0 second.
-  | 11 // MAV_ODID_TIME_ACC_1_1_SECOND - The timestamp accuracy is smaller than or equal to 1.1 second.
-  | 12 // MAV_ODID_TIME_ACC_1_2_SECOND - The timestamp accuracy is smaller than or equal to 1.2 second.
-  | 13 // MAV_ODID_TIME_ACC_1_3_SECOND - The timestamp accuracy is smaller than or equal to 1.3 second.
-  | 14 // MAV_ODID_TIME_ACC_1_4_SECOND - The timestamp accuracy is smaller than or equal to 1.4 second.
-  | 15 // MAV_ODID_TIME_ACC_1_5_SECOND - The timestamp accuracy is smaller than or equal to 1.5 second.
-  | number;
-
-export type MAV_ODID_AUTH_TYPE =
-  | 0 // MAV_ODID_AUTH_TYPE_NONE - No authentication type is specified.
-  | 1 // MAV_ODID_AUTH_TYPE_UAS_ID_SIGNATURE - Signature for the UAS (Unmanned Aircraft System) ID.
-  | 2 // MAV_ODID_AUTH_TYPE_OPERATOR_ID_SIGNATURE - Signature for the Operator ID.
-  | 3 // MAV_ODID_AUTH_TYPE_MESSAGE_SET_SIGNATURE - Signature for the entire message set.
-  | 4 // MAV_ODID_AUTH_TYPE_NETWORK_REMOTE_ID - Authentication is provided by Network Remote ID.
-  | 5 // MAV_ODID_AUTH_TYPE_SPECIFIC_AUTHENTICATION - The exact authentication type is indicated by the first byte of authentication_data and these type values are managed by ICAO.
-  | number;
-
-export type MAV_ODID_DESC_TYPE =
-  | 0 // MAV_ODID_DESC_TYPE_TEXT - Optional free-form text description of the purpose of the flight.
-  | 1 // MAV_ODID_DESC_TYPE_EMERGENCY - Optional additional clarification when status &#x3D;&#x3D; MAV_ODID_STATUS_EMERGENCY.
-  | 2 // MAV_ODID_DESC_TYPE_EXTENDED_STATUS - Optional additional clarification when status !&#x3D; MAV_ODID_STATUS_EMERGENCY.
-  | number;
-
-export type MAV_ODID_OPERATOR_LOCATION_TYPE =
-  | 0 // MAV_ODID_OPERATOR_LOCATION_TYPE_TAKEOFF - The location/altitude of the operator is the same as the take-off location.
-  | 1 // MAV_ODID_OPERATOR_LOCATION_TYPE_LIVE_GNSS - The location/altitude of the operator is dynamic. E.g. based on live GNSS data.
-  | 2 // MAV_ODID_OPERATOR_LOCATION_TYPE_FIXED - The location/altitude of the operator are fixed values.
-  | number;
-
-export type MAV_ODID_CLASSIFICATION_TYPE =
-  | 0 // MAV_ODID_CLASSIFICATION_TYPE_UNDECLARED - The classification type for the UA is undeclared.
-  | 1 // MAV_ODID_CLASSIFICATION_TYPE_EU - The classification type for the UA follows EU (European Union) specifications.
-  | number;
-
-export type MAV_ODID_CATEGORY_EU =
-  | 0 // MAV_ODID_CATEGORY_EU_UNDECLARED - The category for the UA, according to the EU specification, is undeclared.
-  | 1 // MAV_ODID_CATEGORY_EU_OPEN - The category for the UA, according to the EU specification, is the Open category.
-  | 2 // MAV_ODID_CATEGORY_EU_SPECIFIC - The category for the UA, according to the EU specification, is the Specific category.
-  | 3 // MAV_ODID_CATEGORY_EU_CERTIFIED - The category for the UA, according to the EU specification, is the Certified category.
-  | number;
-
-export type MAV_ODID_CLASS_EU =
-  | 0 // MAV_ODID_CLASS_EU_UNDECLARED - The class for the UA, according to the EU specification, is undeclared.
-  | 1 // MAV_ODID_CLASS_EU_CLASS_0 - The class for the UA, according to the EU specification, is Class 0.
-  | 2 // MAV_ODID_CLASS_EU_CLASS_1 - The class for the UA, according to the EU specification, is Class 1.
-  | 3 // MAV_ODID_CLASS_EU_CLASS_2 - The class for the UA, according to the EU specification, is Class 2.
-  | 4 // MAV_ODID_CLASS_EU_CLASS_3 - The class for the UA, according to the EU specification, is Class 3.
-  | 5 // MAV_ODID_CLASS_EU_CLASS_4 - The class for the UA, according to the EU specification, is Class 4.
-  | 6 // MAV_ODID_CLASS_EU_CLASS_5 - The class for the UA, according to the EU specification, is Class 5.
-  | 7 // MAV_ODID_CLASS_EU_CLASS_6 - The class for the UA, according to the EU specification, is Class 6.
-  | number;
-
-export type MAV_ODID_OPERATOR_ID_TYPE =
-  | 0 // MAV_ODID_OPERATOR_ID_TYPE_CAA - CAA (Civil Aviation Authority) registered operator ID.
-  | number;
-
-export type MAV_ODID_ARM_STATUS =
-  | 0 // MAV_ODID_ARM_STATUS_GOOD_TO_ARM - Passing arming checks.
-  | 1 // MAV_ODID_ARM_STATUS_PRE_ARM_FAIL_GENERIC - Generic arming failure, see error string for details.
-  | number;
-
-// Tune formats (used for vehicle buzzer/tone generation).
-export type TUNE_FORMAT =
-  | 1 // TUNE_FORMAT_QBASIC1_1 - Format is QBasic 1.1 Play: https://www.qbasic.net/en/reference/qb11/Statement/PLAY-006.htm.
-  | 2 // TUNE_FORMAT_MML_MODERN - Format is Modern Music Markup Language (MML): https://en.wikipedia.org/wiki/Music_Macro_Language#Modern_MML.
-  | number;
-
-// Type of AIS vessel, enum duplicated from AIS standard, https://gpsd.gitlab.io/gpsd/AIVDM.html
-export type AIS_TYPE =
-  | 0 // AIS_TYPE_UNKNOWN - Not available (default).
-  | 1
-  | 2
-  | 3
-  | 4
-  | 5
-  | 6
-  | 7
-  | 8
-  | 9
-  | 10
-  | 11
-  | 12
-  | 13
-  | 14
-  | 15
-  | 16
-  | 17
-  | 18
-  | 19
-  | 20 // AIS_TYPE_WIG - Wing In Ground effect.
-  | 21
-  | 22
-  | 23
-  | 24
-  | 25
-  | 26
-  | 27
-  | 28
-  | 29
-  | 30
-  | 31
-  | 32 // AIS_TYPE_TOWING_LARGE - Towing: length exceeds 200m or breadth exceeds 25m.
-  | 33 // AIS_TYPE_DREDGING - Dredging or other underwater ops.
-  | 34
-  | 35
-  | 36
-  | 37
-  | 38
-  | 39
-  | 40 // AIS_TYPE_HSC - High Speed Craft.
-  | 41
-  | 42
-  | 43
-  | 44
-  | 45
-  | 46
-  | 47
-  | 48
-  | 49
-  | 50
-  | 51 // AIS_TYPE_SAR - Search And Rescue vessel.
-  | 52
-  | 53
-  | 54 // AIS_TYPE_ANTI_POLLUTION - Anti-pollution equipment.
-  | 55
-  | 56
-  | 57
-  | 58
-  | 59 // AIS_TYPE_NONECOMBATANT - Noncombatant ship according to RR Resolution No. 18.
-  | 60
-  | 61
-  | 62
-  | 63
-  | 64
-  | 65
-  | 66
-  | 67
-  | 68
-  | 69
-  | 70
-  | 71
-  | 72
-  | 73
-  | 74
-  | 75
-  | 76
-  | 77
-  | 78
-  | 79
-  | 80
-  | 81
-  | 82
-  | 83
-  | 84
-  | 85
-  | 86
-  | 87
-  | 88
-  | 89
-  | 90
-  | 91
-  | 92
-  | 93
-  | 94
-  | 95
-  | 96
-  | 97
-  | 98
-  | 99
-  | number;
-
-// Navigational status of AIS vessel, enum duplicated from AIS standard, https://gpsd.gitlab.io/gpsd/AIVDM.html
-export type AIS_NAV_STATUS =
-  | 0 // UNDER_WAY - Under way using engine.
-  | 1
-  | 2
-  | 3
-  | 4
-  | 5
-  | 6
-  | 7
-  | 8
-  | 9
-  | 10
-  | 11
-  | 12
-  | 13
-  | 14 // AIS_NAV_AIS_SART - Search And Rescue Transponder.
-  | 15 // AIS_NAV_UNKNOWN - Not available (default).
-  | number;
-
-// These flags are used in the AIS_VESSEL.fields bitmask to indicate validity of data in the other message fields. When set, the data is valid.
-export type AIS_FLAGS =
-  | 1 // AIS_FLAGS_POSITION_ACCURACY - 1 &#x3D; Position accuracy less than 10m, 0 &#x3D; position accuracy greater than 10m.
-  | 2
-  | 4
-  | 8 // AIS_FLAGS_HIGH_VELOCITY - 1 &#x3D; Velocity over 52.5765m/s (102.2 knots)
-  | 16
-  | 32 // AIS_FLAGS_TURN_RATE_SIGN_ONLY - Only the sign of the returned turn rate value is valid, either greater than 5deg/30s or less than -5deg/30s
-  | 64
-  | 128 // AIS_FLAGS_LARGE_BOW_DIMENSION - Distance to bow is larger than 511m
-  | 256 // AIS_FLAGS_LARGE_STERN_DIMENSION - Distance to stern is larger than 511m
-  | 512 // AIS_FLAGS_LARGE_PORT_DIMENSION - Distance to port side is larger than 63m
-  | 1024 // AIS_FLAGS_LARGE_STARBOARD_DIMENSION - Distance to starboard side is larger than 63m
-  | 2048
-  | 4096
-  | number;
-
-// List of possible units where failures can be injected.
-export type FAILURE_UNIT =
-  | 0
-  | 1
-  | 2
-  | 3
-  | 4
-  | 5
-  | 6
-  | 7
-  | 8
-  | 100
-  | 101
-  | 102
-  | 103
-  | 104
-  | 105
-  | number;
-
-// List of possible failure type to inject.
-export type FAILURE_TYPE =
-  | 0 // FAILURE_TYPE_OK - No failure injected, used to reset a previous failure.
-  | 1 // FAILURE_TYPE_OFF - Sets unit off, so completely non-responsive.
-  | 2 // FAILURE_TYPE_STUCK - Unit is stuck e.g. keeps reporting the same value.
-  | 3 // FAILURE_TYPE_GARBAGE - Unit is reporting complete garbage.
-  | 4 // FAILURE_TYPE_WRONG - Unit is consistently wrong.
-  | 5 // FAILURE_TYPE_SLOW - Unit is slow, so e.g. reporting at slower than expected rate.
-  | 6 // FAILURE_TYPE_DELAYED - Data of unit is delayed in time.
-  | 7 // FAILURE_TYPE_INTERMITTENT - Unit is sometimes working, sometimes not.
-  | number;
-
-export type NAV_VTOL_LAND_OPTIONS =
-  | 0 // NAV_VTOL_LAND_OPTIONS_DEFAULT - Default autopilot landing behaviour.
-  | 1 // NAV_VTOL_LAND_OPTIONS_FW_DESCENT - Descend in fixed wing mode, transitioning to multicopter mode for vertical landing when close to the ground. The fixed wing descent pattern is at the discretion of the vehicle (e.g. transition altitude, loiter direction, radius, and speed, etc.).
-  | 2 // NAV_VTOL_LAND_OPTIONS_HOVER_DESCENT - Land in multicopter mode on reaching the landing coordinates (the whole landing is by &quot;hover descent&quot;).
-  | number;
-
-// Winch status flags used in WINCH_STATUS
-export type MAV_WINCH_STATUS_FLAG =
-  | 1 // MAV_WINCH_STATUS_HEALTHY - Winch is healthy
-  | 2 // MAV_WINCH_STATUS_FULLY_RETRACTED - Winch line is fully retracted
-  | 4 // MAV_WINCH_STATUS_MOVING - Winch motor is moving
-  | 8 // MAV_WINCH_STATUS_CLUTCH_ENGAGED - Winch clutch is engaged allowing motor to move freely.
-  | 16 // MAV_WINCH_STATUS_LOCKED - Winch is locked by locking mechanism.
-  | 32 // MAV_WINCH_STATUS_DROPPING - Winch is gravity dropping payload.
-  | 64 // MAV_WINCH_STATUS_ARRESTING - Winch is arresting payload descent.
-  | 128 // MAV_WINCH_STATUS_GROUND_SENSE - Winch is using torque measurements to sense the ground.
-  | 256 // MAV_WINCH_STATUS_RETRACTING - Winch is returning to the fully retracted position.
-  | 512 // MAV_WINCH_STATUS_REDELIVER - Winch is redelivering the payload. This is a failover state if the line tension goes above a threshold during RETRACTING.
-  | 1024 // MAV_WINCH_STATUS_ABANDON_LINE - Winch is abandoning the line and possibly payload. Winch unspools the entire calculated line length. This is a failover state from REDELIVER if the number of attempts exceeds a threshold.
-  | 2048 // MAV_WINCH_STATUS_LOCKING - Winch is engaging the locking mechanism.
-  | 4096 // MAV_WINCH_STATUS_LOAD_LINE - Winch is spooling on line.
-  | 8192 // MAV_WINCH_STATUS_LOAD_PAYLOAD - Winch is loading a payload.
-  | number;
-
-export type MAG_CAL_STATUS =
-  | 0
-  | 1
-  | 2
-  | 3
-  | 4
-  | 5
-  | 6
-  | 7
-  | number;
-
-// Reason for an event error response.
-export type MAV_EVENT_ERROR_REASON =
-  | 0 // MAV_EVENT_ERROR_REASON_UNAVAILABLE - The requested event is not available (anymore).
-  | number;
-
-// Flags for CURRENT_EVENT_SEQUENCE.
-export type MAV_EVENT_CURRENT_SEQUENCE_FLAGS =
-  | 1 // MAV_EVENT_CURRENT_SEQUENCE_FLAGS_RESET - A sequence reset has happened (e.g. vehicle reboot).
-  | number;
-
-// Flags in the HIL_SENSOR message indicate which fields have updated since the last message
-export type HIL_SENSOR_UPDATED_FLAGS =
-  | 1 // HIL_SENSOR_UPDATED_XACC - The value in the xacc field has been updated
-  | 2 // HIL_SENSOR_UPDATED_YACC - The value in the yacc field has been updated
-  | 4 // HIL_SENSOR_UPDATED_ZACC - The value in the zacc field has been updated
-  | 8 // HIL_SENSOR_UPDATED_XGYRO - The value in the xgyro field has been updated
-  | 16 // HIL_SENSOR_UPDATED_YGYRO - The value in the ygyro field has been updated
-  | 32 // HIL_SENSOR_UPDATED_ZGYRO - The value in the zgyro field has been updated
-  | 64 // HIL_SENSOR_UPDATED_XMAG - The value in the xmag field has been updated
-  | 128 // HIL_SENSOR_UPDATED_YMAG - The value in the ymag field has been updated
-  | 256 // HIL_SENSOR_UPDATED_ZMAG - The value in the zmag field has been updated
-  | 512 // HIL_SENSOR_UPDATED_ABS_PRESSURE - The value in the abs_pressure field has been updated
-  | 1024 // HIL_SENSOR_UPDATED_DIFF_PRESSURE - The value in the diff_pressure field has been updated
-  | 2048 // HIL_SENSOR_UPDATED_PRESSURE_ALT - The value in the pressure_alt field has been updated
-  | 4096 // HIL_SENSOR_UPDATED_TEMPERATURE - The value in the temperature field has been updated
-  | 2147483648 // HIL_SENSOR_UPDATED_RESET - Full reset of attitude/position/velocities/etc was performed in sim (Bit 31).
-  | number;
-
-// Flags in the HIGHRES_IMU message indicate which fields have updated since the last message
-export type HIGHRES_IMU_UPDATED_FLAGS =
-  | 1 // HIGHRES_IMU_UPDATED_XACC - The value in the xacc field has been updated
-  | 2 // HIGHRES_IMU_UPDATED_YACC - The value in the yacc field has been updated
-  | 4 // HIGHRES_IMU_UPDATED_ZACC - The value in the zacc field has been updated since
-  | 8 // HIGHRES_IMU_UPDATED_XGYRO - The value in the xgyro field has been updated
-  | 16 // HIGHRES_IMU_UPDATED_YGYRO - The value in the ygyro field has been updated
-  | 32 // HIGHRES_IMU_UPDATED_ZGYRO - The value in the zgyro field has been updated
-  | 64 // HIGHRES_IMU_UPDATED_XMAG - The value in the xmag field has been updated
-  | 128 // HIGHRES_IMU_UPDATED_YMAG - The value in the ymag field has been updated
-  | 256 // HIGHRES_IMU_UPDATED_ZMAG - The value in the zmag field has been updated
-  | 512 // HIGHRES_IMU_UPDATED_ABS_PRESSURE - The value in the abs_pressure field has been updated
-  | 1024 // HIGHRES_IMU_UPDATED_DIFF_PRESSURE - The value in the diff_pressure field has been updated
-  | 2048 // HIGHRES_IMU_UPDATED_PRESSURE_ALT - The value in the pressure_alt field has been updated
-  | 4096 // HIGHRES_IMU_UPDATED_TEMPERATURE - The value in the temperature field has been updated
-  | number;
-
-export type CAN_FILTER_OP =
-  | 0
-  | 1
-  | 2
-  | number;
-
-// MAV FTP error codes (https://mavlink.io/en/services/ftp.html)
-export type MAV_FTP_ERR =
-  | 0 // MAV_FTP_ERR_NONE - None: No error
-  | 1 // MAV_FTP_ERR_FAIL - Fail: Unknown failure
-  | 2 // MAV_FTP_ERR_FAILERRNO - FailErrno: Command failed, Err number sent back in PayloadHeader.data[1]. This is a file-system error number understood by the server operating system.
-  | 3 // MAV_FTP_ERR_INVALIDDATASIZE - InvalidDataSize: Payload size is invalid
-  | 4 // MAV_FTP_ERR_INVALIDSESSION - InvalidSession: Session is not currently open
-  | 5 // MAV_FTP_ERR_NOSESSIONSAVAILABLE - NoSessionsAvailable: All available sessions are already in use
-  | 6 // MAV_FTP_ERR_EOF - EOF: Offset past end of file for ListDirectory and ReadFile commands
-  | 7 // MAV_FTP_ERR_UNKNOWNCOMMAND - UnknownCommand: Unknown command / opcode
-  | 8 // MAV_FTP_ERR_FILEEXISTS - FileExists: File/directory already exists
-  | 9 // MAV_FTP_ERR_FILEPROTECTED - FileProtected: File/directory is write protected
-  | 10 // MAV_FTP_ERR_FILENOTFOUND - FileNotFound: File/directory not found
-  | number;
-
-// MAV FTP opcodes: https://mavlink.io/en/services/ftp.html
-export type MAV_FTP_OPCODE =
-  | 0 // MAV_FTP_OPCODE_NONE - None. Ignored, always ACKed
-  | 1 // MAV_FTP_OPCODE_TERMINATESESSION - TerminateSession: Terminates open Read session
-  | 2 // MAV_FTP_OPCODE_RESETSESSION - ResetSessions: Terminates all open read sessions
-  | 3 // MAV_FTP_OPCODE_LISTDIRECTORY - ListDirectory. List files and directories in path from offset
-  | 4 // MAV_FTP_OPCODE_OPENFILERO - OpenFileRO: Opens file at path for reading, returns session
-  | 5 // MAV_FTP_OPCODE_READFILE - ReadFile: Reads size bytes from offset in session
-  | 6 // MAV_FTP_OPCODE_CREATEFILE - CreateFile: Creates file at path for writing, returns session
-  | 7 // MAV_FTP_OPCODE_WRITEFILE - WriteFile: Writes size bytes to offset in session
-  | 8 // MAV_FTP_OPCODE_REMOVEFILE - RemoveFile: Remove file at path
-  | 9 // MAV_FTP_OPCODE_CREATEDIRECTORY - CreateDirectory: Creates directory at path
-  | 10 // MAV_FTP_OPCODE_REMOVEDIRECTORY - RemoveDirectory: Removes directory at path. The directory must be empty.
-  | 11 // MAV_FTP_OPCODE_OPENFILEWO - OpenFileWO: Opens file at path for writing, returns session
-  | 12 // MAV_FTP_OPCODE_TRUNCATEFILE - TruncateFile: Truncate file at path to offset length
-  | 13 // MAV_FTP_OPCODE_RENAME - Rename: Rename path1 to path2
-  | 14 // MAV_FTP_OPCODE_CALCFILECRC - CalcFileCRC32: Calculate CRC32 for file at path
-  | 15 // MAV_FTP_OPCODE_BURSTREADFILE - BurstReadFile: Burst download session file
-  | 128 // MAV_FTP_OPCODE_ACK - ACK: ACK response
-  | 129 // MAV_FTP_OPCODE_NAK - NAK: NAK response
-  | number;
-
-// States of the mission state machine.
-// Note that these states are independent of whether the mission is in a mode that can execute mission items or not (is suspended).
-// They may not all be relevant on all vehicles.
-export type MISSION_STATE =
-  | 0 // MISSION_STATE_UNKNOWN - The mission status reporting is not supported.
-  | 1 // MISSION_STATE_NO_MISSION - No mission on the vehicle.
-  | 2 // MISSION_STATE_NOT_STARTED - Mission has not started. This is the case after a mission has uploaded but not yet started executing.
-  | 3 // MISSION_STATE_ACTIVE - Mission is active, and will execute mission items when in auto mode.
-  | 4 // MISSION_STATE_PAUSED - Mission is paused when in auto mode.
-  | 5 // MISSION_STATE_COMPLETE - Mission has executed all mission items.
-  | number;
-
-// Possible safety switch states.
-export type SAFETY_SWITCH_STATE =
-  | 0 // SAFETY_SWITCH_STATE_SAFE - Safety switch is engaged and vehicle should be safe to approach.
-  | 1 // SAFETY_SWITCH_STATE_DANGEROUS - Safety switch is NOT engaged and motors, propellers and other actuators should be considered active.
-  | number;
-
-// Modes of illuminator
-export type ILLUMINATOR_MODE =
-  | 0 // ILLUMINATOR_MODE_UNKNOWN - Illuminator mode is not specified/unknown
-  | 1 // ILLUMINATOR_MODE_INTERNAL_CONTROL - Illuminator behavior is controlled by MAV_CMD_DO_ILLUMINATOR_CONFIGURE settings
-  | 2 // ILLUMINATOR_MODE_EXTERNAL_SYNC - Illuminator behavior is controlled by external factors: e.g. an external hardware signal
-  | number;
-
-// Illuminator module error flags (bitmap, 0 means no error)
-export type ILLUMINATOR_ERROR_FLAGS =
-  | 1 // ILLUMINATOR_ERROR_FLAGS_THERMAL_THROTTLING - Illuminator thermal throttling error.
-  | 2 // ILLUMINATOR_ERROR_FLAGS_OVER_TEMPERATURE_SHUTDOWN - Illuminator over temperature shutdown error.
-  | 4 // ILLUMINATOR_ERROR_FLAGS_THERMISTOR_FAILURE - Illuminator thermistor failure.
-  | number;
-
-// Standard modes with a well understood meaning across flight stacks and vehicle types.
-// For example, most flight stack have the concept of a &quot;return&quot; or &quot;RTL&quot; mode that takes a vehicle to safety, even though the precise mechanics of this mode may differ.
-// The modes supported by a flight stack can be queried using AVAILABLE_MODES and set using MAV_CMD_DO_SET_STANDARD_MODE.
-// The current mode is streamed in CURRENT_MODE.
-// See https://mavlink.io/en/services/standard_modes.html
-export type MAV_STANDARD_MODE =
-  | 0 // MAV_STANDARD_MODE_NON_STANDARD - Non standard mode. This may be used when reporting the mode if the current flight mode is not a standard mode.
-  | 1 // MAV_STANDARD_MODE_POSITION_HOLD - Position mode (manual). Position-controlled and stabilized manual mode. When sticks are released vehicles return to their level-flight orientation and hold both position and altitude against wind and external forces. This mode can only be set by vehicles that can hold a fixed position. Multicopter (MC) vehicles actively brake and hold both position and altitude against wind and external forces. Hybrid MC/FW (&quot;VTOL&quot;) vehicles first transition to multicopter mode (if needed) but otherwise behave in the same way as MC vehicles. Fixed-wing (FW) vehicles must not support this mode. Other vehicle types must not support this mode (this may be revisited through the PR process).
-  | 2 // MAV_STANDARD_MODE_ORBIT - Orbit (manual). Position-controlled and stabilized manual mode. The vehicle circles around a fixed setpoint in the horizontal plane at a particular radius, altitude, and direction. Flight stacks may further allow manual control over the setpoint position, radius, direction, speed, and/or altitude of the circle, but this is not mandated. Flight stacks may support the [MAV_CMD_DO_ORBIT](https://mavlink.io/en/messages/common.html#MAV_CMD_DO_ORBIT) for changing the orbit parameters. MC and FW vehicles may support this mode. Hybrid MC/FW (&quot;VTOL&quot;) vehicles may support this mode in MC/FW or both modes; if the mode is not supported by the current configuration the vehicle should transition to the supported configuration. Other vehicle types must not support this mode (this may be revisited through the PR process).
-  | 3 // MAV_STANDARD_MODE_CRUISE - Cruise mode (manual). Position-controlled and stabilized manual mode. When sticks are released vehicles return to their level-flight orientation and hold their original track against wind and external forces. Fixed-wing (FW) vehicles level orientation and maintain current track and altitude against wind and external forces. Hybrid MC/FW (&quot;VTOL&quot;) vehicles first transition to FW mode (if needed) but otherwise behave in the same way as MC vehicles. Multicopter (MC) vehicles must not support this mode. Other vehicle types must not support this mode (this may be revisited through the PR process).
-  | 4 // MAV_STANDARD_MODE_ALTITUDE_HOLD - Altitude hold (manual). Altitude-controlled and stabilized manual mode. When sticks are released vehicles return to their level-flight orientation and hold their altitude. MC vehicles continue with existing momentum and may move with wind (or other external forces). FW vehicles continue with current heading, but may be moved off-track by wind. Hybrid MC/FW (&quot;VTOL&quot;) vehicles behave according to their current configuration/mode (FW or MC). Other vehicle types must not support this mode (this may be revisited through the PR process).
-  | 5 // MAV_STANDARD_MODE_SAFE_RECOVERY - Safe recovery mode (auto). Automatic mode that takes vehicle to a predefined safe location via a safe flight path, and may also automatically land the vehicle. This mode is more commonly referred to as RTL and/or or Smart RTL. The precise return location, flight path, and landing behaviour depend on vehicle configuration and type. For example, the vehicle might return to the home/launch location, a rally point, or the start of a mission landing, it might follow a direct path, mission path, or breadcrumb path, and land using a mission landing pattern or some other kind of descent.
-  | 6 // MAV_STANDARD_MODE_MISSION - Mission mode (automatic). Automatic mode that executes MAVLink missions. Missions are executed from the current waypoint as soon as the mode is enabled.
-  | 7 // MAV_STANDARD_MODE_LAND - Land mode (auto). Automatic mode that lands the vehicle at the current location. The precise landing behaviour depends on vehicle configuration and type.
-  | 8 // MAV_STANDARD_MODE_TAKEOFF - Takeoff mode (auto). Automatic takeoff mode. The precise takeoff behaviour depends on vehicle configuration and type.
-  | number;
-
-// Mode properties.
-export type MAV_MODE_PROPERTY =
-  | 1 // MAV_MODE_PROPERTY_ADVANCED - If set, this mode is an advanced mode. For example a rate-controlled manual mode might be advanced, whereas a position-controlled manual mode is not. A GCS can optionally use this flag to configure the UI for its intended users.
-  | 2 // MAV_MODE_PROPERTY_NOT_USER_SELECTABLE - If set, this mode should not be added to the list of selectable modes. The mode might still be selected by the FC directly (for example as part of a failsafe).
-  | 4 // MAV_MODE_PROPERTY_AUTO_MODE - If set, this mode is automatically controlled (it may use but does not require a manual controller). If unset the mode is a assumed to require user input (be a manual mode).
-  | number;
-
-// Flags used in HIL_ACTUATOR_CONTROLS message.
-export type HIL_ACTUATOR_CONTROLS_FLAGS =
-  | 1 // HIL_ACTUATOR_CONTROLS_FLAGS_LOCKSTEP - Simulation is using lockstep
-  | number;
-
-// State flags for ADS-B transponder dynamic report
-export type UAVIONIX_ADSB_OUT_DYNAMIC_STATE =
-  | 1
-  | 2
-  | 4
-  | 8
-  | 16
-  | number;
-
-// Transceiver RF control flags for ADS-B transponder dynamic reports
-export type UAVIONIX_ADSB_OUT_RF_SELECT =
-  | 1
-  | 2
-  | number;
-
-// Status for ADS-B transponder dynamic input
-export type UAVIONIX_ADSB_OUT_DYNAMIC_GPS_FIX =
-  | 0
-  | 1
-  | 2
-  | 3
-  | 4
-  | 5
-  | number;
-
-// Status flags for ADS-B transponder dynamic output
-export type UAVIONIX_ADSB_RF_HEALTH =
-  | 1
-  | 2
-  | 16
-  | number;
-
-// Definitions for aircraft size
-export type UAVIONIX_ADSB_OUT_CFG_AIRCRAFT_SIZE =
-  | 0
-  | 1
-  | 2
-  | 3
-  | 4
-  | 5
-  | 6
-  | 7
-  | 8
-  | 9
-  | 10
-  | 11
-  | 12
-  | 13
-  | 14
-  | 15
-  | number;
-
-// GPS lataral offset encoding
-export type UAVIONIX_ADSB_OUT_CFG_GPS_OFFSET_LAT =
-  | 0
-  | 1
-  | 2
-  | 3
-  | 4
-  | 5
-  | 6
-  | 7
-  | number;
-
-// GPS longitudinal offset encoding
-export type UAVIONIX_ADSB_OUT_CFG_GPS_OFFSET_LON =
-  | 0
-  | 1
-  | number;
-
-// Emergency status encoding
-export type UAVIONIX_ADSB_EMERGENCY_STATUS =
-  | 0
-  | 1
-  | 2
-  | 3
-  | 4
-  | 5
-  | 6
-  | 7
-  | number;
-
-// State flags for ADS-B transponder dynamic report
-export type UAVIONIX_ADSB_OUT_CONTROL_STATE =
-  | 1
-  | 4
-  | 8
-  | 16
-  | 32
-  | 64
-  | 128
-  | number;
-
-// State flags for X-Bit and reserved fields.
-export type UAVIONIX_ADSB_XBIT =
-  | 128
-  | number;
-
-// State flags for ADS-B transponder status report
-export type UAVIONIX_ADSB_OUT_STATUS_STATE =
-  | 1
-  | 2
-  | 4
-  | 8
-  | 16
-  | 32
-  | 64
-  | 128
-  | number;
-
-// State flags for ADS-B transponder status report
-export type UAVIONIX_ADSB_OUT_STATUS_NIC_NACP =
-  | 1
-  | 2
-  | 3
-  | 4
-  | 5
-  | 6
-  | 7
-  | 8
-  | 9
-  | 10
-  | 11
-  | 16
-  | 32
-  | 48
-  | 64
-  | 80
-  | 96
-  | 112
-  | 128
-  | 144
-  | 160
-  | 176
-  | number;
-
-// State flags for ADS-B transponder fault report
-export type UAVIONIX_ADSB_OUT_STATUS_FAULT =
-  | 8
-  | 16
-  | 32
-  | 64
-  | 128
-  | number;
-
-export type ICAROUS_TRACK_BAND_TYPES =
-  | 0
-  | 1
-  | 2
-  | number;
-
-export type ICAROUS_FMS_STATE =
-  | 0
-  | 1
-  | 2
-  | 3
-  | 4
-  | 5
-  | number;
-
-export type MAV_CMD =
-  | 10151 // MAV_CMD_LOWEHEISER_SET_STATE - Set Loweheiser desired states
-  | number;
-
-export type AIRLINK_AUTH_RESPONSE_TYPE =
-  | 0 // AIRLINK_ERROR_LOGIN_OR_PASS - Login or password error
-  | 1 // AIRLINK_AUTH_OK - Auth successful
-  | number;
-
-export type ACCELCAL_VEHICLE_POS =
-  | 1
-  | 2
-  | 3
-  | 4
-  | 5
-  | 6
-  | 16777215
-  | 16777216
-  | number;
-
-export type HEADING_TYPE =
-  | 0
-  | 1
-  | 2
-  | number;
-
-export type MAV_CMD =
-  | 215 // MAV_CMD_DO_SET_RESUME_REPEAT_DIST - Set the distance to be repeated on mission resume
-  | 216 // MAV_CMD_DO_SPRAYER - Control attached liquid sprayer
-  | 217 // MAV_CMD_DO_SEND_SCRIPT_MESSAGE - Pass instructions onto scripting, a script should be checking for a new command
-  | 218 // MAV_CMD_DO_AUX_FUNCTION - Execute auxiliary function
-  | 83 // MAV_CMD_NAV_ALTITUDE_WAIT - Mission command to wait for an altitude or downwards vertical speed. This is meant for high altitude balloon launches, allowing the aircraft to be idle until either an altitude is reached or a negative vertical speed is reached (indicating early balloon burst). The wiggle time is how often to wiggle the control surfaces to prevent them seizing up.
-  | 42000 // MAV_CMD_POWER_OFF_INITIATED - A system wide power-off event has been initiated.
-  | 42001 // MAV_CMD_SOLO_BTN_FLY_CLICK - FLY button has been clicked.
-  | 42002 // MAV_CMD_SOLO_BTN_FLY_HOLD - FLY button has been held for 1.5 seconds.
-  | 42003 // MAV_CMD_SOLO_BTN_PAUSE_CLICK - PAUSE button has been clicked.
-  | 42004 // MAV_CMD_FIXED_MAG_CAL - Magnetometer calibration based on fixed position in earth field given by inclination, declination and intensity.
-  | 42005 // MAV_CMD_FIXED_MAG_CAL_FIELD - Magnetometer calibration based on fixed expected field values.
-  | 42007 // MAV_CMD_SET_EKF_SOURCE_SET - Set EKF sensor source set.
-  | 42424 // MAV_CMD_DO_START_MAG_CAL - Initiate a magnetometer calibration.
-  | 42425 // MAV_CMD_DO_ACCEPT_MAG_CAL - Accept a magnetometer calibration.
-  | 42426 // MAV_CMD_DO_CANCEL_MAG_CAL - Cancel a running magnetometer calibration.
-  | 42429 // MAV_CMD_ACCELCAL_VEHICLE_POS - Used when doing accelerometer calibration. When sent to the GCS tells it what position to put the vehicle in. When sent to the vehicle says what position the vehicle is in.
-  | 42428 // MAV_CMD_DO_SEND_BANNER - Reply with the version banner.
-  | 42427 // MAV_CMD_SET_FACTORY_TEST_MODE - Command autopilot to get into factory test/diagnostic mode.
-  | 42501 // MAV_CMD_GIMBAL_RESET - Causes the gimbal to reset and boot as if it was just powered on.
-  | 42502 // MAV_CMD_GIMBAL_AXIS_CALIBRATION_STATUS - Reports progress and success or failure of gimbal axis calibration procedure.
-  | 42503 // MAV_CMD_GIMBAL_REQUEST_AXIS_CALIBRATION - Starts commutation calibration on the gimbal.
-  | 42505 // MAV_CMD_GIMBAL_FULL_RESET - Erases gimbal application and parameters.
-  | 42650 // MAV_CMD_FLASH_BOOTLOADER - Update the bootloader
-  | 42651 // MAV_CMD_BATTERY_RESET - Reset battery capacity for batteries that accumulate consumed battery via integration.
-  | 42700 // MAV_CMD_DEBUG_TRAP - Issue a trap signal to the autopilot process, presumably to enter the debugger.
-  | 42701 // MAV_CMD_SCRIPTING - Control onboard scripting.
-  | 42702 // MAV_CMD_NAV_SCRIPT_TIME - Scripting command as NAV command with wait for completion.
-  | 42703 // MAV_CMD_NAV_ATTITUDE_TIME - Maintain an attitude for a specified time.
-  | 43000 // MAV_CMD_GUIDED_CHANGE_SPEED - Change flight speed at a given rate. This slews the vehicle at a controllable rate between it&#x27;s previous speed and the new one. (affects GUIDED only. Outside GUIDED, aircraft ignores these commands. Designed for onboard companion-computer command-and-control, not normally operator/GCS control.)
-  | 43001 // MAV_CMD_GUIDED_CHANGE_ALTITUDE - Change target altitude at a given rate. This slews the vehicle at a controllable rate between it&#x27;s previous altitude and the new one. (affects GUIDED only. Outside GUIDED, aircraft ignores these commands. Designed for onboard companion-computer command-and-control, not normally operator/GCS control.)
-  | 43002 // MAV_CMD_GUIDED_CHANGE_HEADING - Change to target heading at a given rate, overriding previous heading/s. This slews the vehicle at a controllable rate between it&#x27;s previous heading and the new one. (affects GUIDED only. Exiting GUIDED returns aircraft to normal behaviour defined elsewhere. Designed for onboard companion-computer command-and-control, not normally operator/GCS control.)
-  | 43005 // MAV_CMD_SET_HAGL - Provide a value for height above ground level. This can be used for things like fixed wing and VTOL landing.
-  | number;
-
-export type SCRIPTING_CMD =
-  | 0 // SCRIPTING_CMD_REPL_START - Start a REPL session.
-  | 1 // SCRIPTING_CMD_REPL_STOP - End a REPL session.
-  | 2 // SCRIPTING_CMD_STOP - Stop execution of scripts.
-  | 3 // SCRIPTING_CMD_STOP_AND_RESTART - Stop execution of scripts and restart.
-  | number;
-
-export type SECURE_COMMAND_OP =
-  | 0 // SECURE_COMMAND_GET_SESSION_KEY - Get an 8 byte session key which is used for remote secure updates which operate on flight controller data such as bootloader public keys. Return data will be 8 bytes on success. The session key remains valid until either the flight controller reboots or another SECURE_COMMAND_GET_SESSION_KEY is run.
-  | 1 // SECURE_COMMAND_GET_REMOTEID_SESSION_KEY - Get an 8 byte session key which is used for remote secure updates which operate on RemoteID module data. Return data will be 8 bytes on success. The session key remains valid until either the remote ID module reboots or another SECURE_COMMAND_GET_REMOTEID_SESSION_KEY is run.
-  | 2 // SECURE_COMMAND_REMOVE_PUBLIC_KEYS - Remove range of public keys from the bootloader. Command data consists of two bytes, first byte if index of first public key to remove. Second byte is the number of keys to remove. If all keys are removed then secure boot is disabled and insecure firmware can be loaded.
-  | 3 // SECURE_COMMAND_GET_PUBLIC_KEYS - Get current public keys from the bootloader. Command data consists of two bytes, first byte is index of first public key to fetch, 2nd byte is number of keys to fetch. Total data needs to fit in data portion of reply (max 6 keys for 32 byte keys). Reply data has the index of the first key in the first byte, followed by the keys. Returned keys may be less than the number of keys requested if there are less keys installed than requested.
-  | 4 // SECURE_COMMAND_SET_PUBLIC_KEYS - Set current public keys in the bootloader. Data consists of a one byte public key index followed by the public keys. With 32 byte keys this allows for up to 6 keys to be set in one request. Keys outside of the range that is being set will remain unchanged.
-  | 5 // SECURE_COMMAND_GET_REMOTEID_CONFIG - Get config data for remote ID module. This command should be sent to the component ID of the flight controller which will forward it to the RemoteID module either over mavlink or DroneCAN. Data format is specific to the RemoteID implementation, see RemoteID firmware documentation for details.
-  | 6 // SECURE_COMMAND_SET_REMOTEID_CONFIG - Set config data for remote ID module. This command should be sent to the component ID of the flight controller which will forward it to the RemoteID module either over mavlink or DroneCAN. Data format is specific to the RemoteID implementation, see RemoteID firmware documentation for details.
-  | 7 // SECURE_COMMAND_FLASH_BOOTLOADER - Flash bootloader from local storage. Data is the filename to use for the bootloader. This is intended to be used with MAVFtp to upload a new bootloader to a microSD before flashing.
-  | number;
-
-export type LIMITS_STATE =
-  | 0 // LIMITS_INIT - Pre-initialization.
-  | 1 // LIMITS_DISABLED - Disabled.
-  | 2 // LIMITS_ENABLED - Checking limits.
-  | 3 // LIMITS_TRIGGERED - A limit has been breached.
-  | 4 // LIMITS_RECOVERING - Taking action e.g. Return/RTL.
-  | 5 // LIMITS_RECOVERED - We&#x27;re no longer in breach of a limit.
-  | number;
-
-export type LIMIT_MODULE =
-  | 1 // LIMIT_GPSLOCK - Pre-initialization.
-  | 2 // LIMIT_GEOFENCE - Disabled.
-  | 4 // LIMIT_ALTITUDE - Checking limits.
-  | number;
-
-// Flags in RALLY_POINT message.
-export type RALLY_FLAGS =
-  | 1 // FAVORABLE_WIND - Flag set when requiring favorable winds for landing.
-  | 2 // LAND_IMMEDIATELY - Flag set when plane is to immediately descend to break altitude and land without GCS intervention. Flag not set when plane is to loiter at Rally point until commanded to land.
-  | 4 // ALT_FRAME_VALID - True if the following altitude frame value is valid.
-  | 24 // ALT_FRAME - 2 bit value representing altitude frame. 0: absolute, 1: relative home, 2: relative origin, 3: relative terrain
-  | number;
-
-export type CAMERA_STATUS_TYPES =
-  | 0 // CAMERA_STATUS_TYPE_HEARTBEAT - Camera heartbeat, announce camera component ID at 1Hz.
-  | 1 // CAMERA_STATUS_TYPE_TRIGGER - Camera image triggered.
-  | 2 // CAMERA_STATUS_TYPE_DISCONNECT - Camera connection lost.
-  | 3 // CAMERA_STATUS_TYPE_ERROR - Camera unknown error.
-  | 4 // CAMERA_STATUS_TYPE_LOWBATT - Camera battery low. Parameter p1 shows reported voltage.
-  | 5 // CAMERA_STATUS_TYPE_LOWSTORE - Camera storage low. Parameter p1 shows reported shots remaining.
-  | 6 // CAMERA_STATUS_TYPE_LOWSTOREV - Camera storage low. Parameter p1 shows reported video minutes remaining.
-  | number;
-
-export type CAMERA_FEEDBACK_FLAGS =
-  | 0 // CAMERA_FEEDBACK_PHOTO - Shooting photos, not video.
-  | 1 // CAMERA_FEEDBACK_VIDEO - Shooting video, not stills.
-  | 2 // CAMERA_FEEDBACK_BADEXPOSURE - Unable to achieve requested exposure (e.g. shutter speed too low).
-  | 3 // CAMERA_FEEDBACK_CLOSEDLOOP - Closed loop feedback from camera, we know for sure it has successfully taken a picture.
-  | 4 // CAMERA_FEEDBACK_OPENLOOP - Open loop camera, an image trigger has been requested but we can&#x27;t know for sure it has successfully taken a picture.
-  | number;
-
-export type MAV_MODE_GIMBAL =
-  | 0 // MAV_MODE_GIMBAL_UNINITIALIZED - Gimbal is powered on but has not started initializing yet.
-  | 1 // MAV_MODE_GIMBAL_CALIBRATING_PITCH - Gimbal is currently running calibration on the pitch axis.
-  | 2 // MAV_MODE_GIMBAL_CALIBRATING_ROLL - Gimbal is currently running calibration on the roll axis.
-  | 3 // MAV_MODE_GIMBAL_CALIBRATING_YAW - Gimbal is currently running calibration on the yaw axis.
-  | 4 // MAV_MODE_GIMBAL_INITIALIZED - Gimbal has finished calibrating and initializing, but is relaxed pending reception of first rate command from copter.
-  | 5 // MAV_MODE_GIMBAL_ACTIVE - Gimbal is actively stabilizing.
-  | 6 // MAV_MODE_GIMBAL_RATE_CMD_TIMEOUT - Gimbal is relaxed because it missed more than 10 expected rate command messages in a row. Gimbal will move back to active mode when it receives a new rate command.
-  | number;
-
-export type GIMBAL_AXIS =
-  | 0 // GIMBAL_AXIS_YAW - Gimbal yaw axis.
-  | 1 // GIMBAL_AXIS_PITCH - Gimbal pitch axis.
-  | 2 // GIMBAL_AXIS_ROLL - Gimbal roll axis.
-  | number;
-
-export type GIMBAL_AXIS_CALIBRATION_STATUS =
-  | 0 // GIMBAL_AXIS_CALIBRATION_STATUS_IN_PROGRESS - Axis calibration is in progress.
-  | 1 // GIMBAL_AXIS_CALIBRATION_STATUS_SUCCEEDED - Axis calibration succeeded.
-  | 2 // GIMBAL_AXIS_CALIBRATION_STATUS_FAILED - Axis calibration failed.
-  | number;
-
-export type GIMBAL_AXIS_CALIBRATION_REQUIRED =
-  | 0 // GIMBAL_AXIS_CALIBRATION_REQUIRED_UNKNOWN - Whether or not this axis requires calibration is unknown at this time.
-  | 1 // GIMBAL_AXIS_CALIBRATION_REQUIRED_TRUE - This axis requires calibration.
-  | 2 // GIMBAL_AXIS_CALIBRATION_REQUIRED_FALSE - This axis does not require calibration.
-  | number;
-
-export type GOPRO_HEARTBEAT_STATUS =
-  | 0 // GOPRO_HEARTBEAT_STATUS_DISCONNECTED - No GoPro connected.
-  | 1 // GOPRO_HEARTBEAT_STATUS_INCOMPATIBLE - The detected GoPro is not HeroBus compatible.
-  | 2 // GOPRO_HEARTBEAT_STATUS_CONNECTED - A HeroBus compatible GoPro is connected.
-  | 3 // GOPRO_HEARTBEAT_STATUS_ERROR - An unrecoverable error was encountered with the connected GoPro, it may require a power cycle.
-  | number;
-
-export type GOPRO_HEARTBEAT_FLAGS =
-  | 1 // GOPRO_FLAG_RECORDING - GoPro is currently recording.
-  | number;
-
-export type GOPRO_REQUEST_STATUS =
-  | 0 // GOPRO_REQUEST_SUCCESS - The write message with ID indicated succeeded.
-  | 1 // GOPRO_REQUEST_FAILED - The write message with ID indicated failed.
-  | number;
-
-export type GOPRO_COMMAND =
-  | 0 // GOPRO_COMMAND_POWER - (Get/Set).
-  | 1 // GOPRO_COMMAND_CAPTURE_MODE - (Get/Set).
-  | 2 // GOPRO_COMMAND_SHUTTER - (___/Set).
-  | 3 // GOPRO_COMMAND_BATTERY - (Get/___).
-  | 4 // GOPRO_COMMAND_MODEL - (Get/___).
-  | 5 // GOPRO_COMMAND_VIDEO_SETTINGS - (Get/Set).
-  | 6 // GOPRO_COMMAND_LOW_LIGHT - (Get/Set).
-  | 7 // GOPRO_COMMAND_PHOTO_RESOLUTION - (Get/Set).
-  | 8 // GOPRO_COMMAND_PHOTO_BURST_RATE - (Get/Set).
-  | 9 // GOPRO_COMMAND_PROTUNE - (Get/Set).
-  | 10 // GOPRO_COMMAND_PROTUNE_WHITE_BALANCE - (Get/Set) Hero 3+ Only.
-  | 11 // GOPRO_COMMAND_PROTUNE_COLOUR - (Get/Set) Hero 3+ Only.
-  | 12 // GOPRO_COMMAND_PROTUNE_GAIN - (Get/Set) Hero 3+ Only.
-  | 13 // GOPRO_COMMAND_PROTUNE_SHARPNESS - (Get/Set) Hero 3+ Only.
-  | 14 // GOPRO_COMMAND_PROTUNE_EXPOSURE - (Get/Set) Hero 3+ Only.
-  | 15 // GOPRO_COMMAND_TIME - (Get/Set).
-  | 16 // GOPRO_COMMAND_CHARGING - (Get/Set).
-  | number;
-
-export type GOPRO_CAPTURE_MODE =
-  | 0 // GOPRO_CAPTURE_MODE_VIDEO - Video mode.
-  | 1 // GOPRO_CAPTURE_MODE_PHOTO - Photo mode.
-  | 2 // GOPRO_CAPTURE_MODE_BURST - Burst mode, Hero 3+ only.
-  | 3 // GOPRO_CAPTURE_MODE_TIME_LAPSE - Time lapse mode, Hero 3+ only.
-  | 4 // GOPRO_CAPTURE_MODE_MULTI_SHOT - Multi shot mode, Hero 4 only.
-  | 5 // GOPRO_CAPTURE_MODE_PLAYBACK - Playback mode, Hero 4 only, silver only except when LCD or HDMI is connected to black.
-  | 6 // GOPRO_CAPTURE_MODE_SETUP - Playback mode, Hero 4 only.
-  | 255 // GOPRO_CAPTURE_MODE_UNKNOWN - Mode not yet known.
-  | number;
-
-export type GOPRO_RESOLUTION =
-  | 0 // GOPRO_RESOLUTION_480p - 848 x 480 (480p).
-  | 1 // GOPRO_RESOLUTION_720p - 1280 x 720 (720p).
-  | 2 // GOPRO_RESOLUTION_960p - 1280 x 960 (960p).
-  | 3 // GOPRO_RESOLUTION_1080p - 1920 x 1080 (1080p).
-  | 4 // GOPRO_RESOLUTION_1440p - 1920 x 1440 (1440p).
-  | 5 // GOPRO_RESOLUTION_2_7k_17_9 - 2704 x 1440 (2.7k-17:9).
-  | 6 // GOPRO_RESOLUTION_2_7k_16_9 - 2704 x 1524 (2.7k-16:9).
-  | 7 // GOPRO_RESOLUTION_2_7k_4_3 - 2704 x 2028 (2.7k-4:3).
-  | 8 // GOPRO_RESOLUTION_4k_16_9 - 3840 x 2160 (4k-16:9).
-  | 9 // GOPRO_RESOLUTION_4k_17_9 - 4096 x 2160 (4k-17:9).
-  | 10 // GOPRO_RESOLUTION_720p_SUPERVIEW - 1280 x 720 (720p-SuperView).
-  | 11 // GOPRO_RESOLUTION_1080p_SUPERVIEW - 1920 x 1080 (1080p-SuperView).
-  | 12 // GOPRO_RESOLUTION_2_7k_SUPERVIEW - 2704 x 1520 (2.7k-SuperView).
-  | 13 // GOPRO_RESOLUTION_4k_SUPERVIEW - 3840 x 2160 (4k-SuperView).
-  | number;
-
-export type GOPRO_FRAME_RATE =
-  | 0 // GOPRO_FRAME_RATE_12 - 12 FPS.
-  | 1 // GOPRO_FRAME_RATE_15 - 15 FPS.
-  | 2 // GOPRO_FRAME_RATE_24 - 24 FPS.
-  | 3 // GOPRO_FRAME_RATE_25 - 25 FPS.
-  | 4 // GOPRO_FRAME_RATE_30 - 30 FPS.
-  | 5 // GOPRO_FRAME_RATE_48 - 48 FPS.
-  | 6 // GOPRO_FRAME_RATE_50 - 50 FPS.
-  | 7 // GOPRO_FRAME_RATE_60 - 60 FPS.
-  | 8 // GOPRO_FRAME_RATE_80 - 80 FPS.
-  | 9 // GOPRO_FRAME_RATE_90 - 90 FPS.
-  | 10 // GOPRO_FRAME_RATE_100 - 100 FPS.
-  | 11 // GOPRO_FRAME_RATE_120 - 120 FPS.
-  | 12 // GOPRO_FRAME_RATE_240 - 240 FPS.
-  | 13 // GOPRO_FRAME_RATE_12_5 - 12.5 FPS.
-  | number;
-
-export type GOPRO_FIELD_OF_VIEW =
-  | 0 // GOPRO_FIELD_OF_VIEW_WIDE - 0x00: Wide.
-  | 1 // GOPRO_FIELD_OF_VIEW_MEDIUM - 0x01: Medium.
-  | 2 // GOPRO_FIELD_OF_VIEW_NARROW - 0x02: Narrow.
-  | number;
-
-export type GOPRO_VIDEO_SETTINGS_FLAGS =
-  | 1 // GOPRO_VIDEO_SETTINGS_TV_MODE - 0&#x3D;NTSC, 1&#x3D;PAL.
-  | number;
-
-export type GOPRO_PHOTO_RESOLUTION =
-  | 0 // GOPRO_PHOTO_RESOLUTION_5MP_MEDIUM - 5MP Medium.
-  | 1 // GOPRO_PHOTO_RESOLUTION_7MP_MEDIUM - 7MP Medium.
-  | 2 // GOPRO_PHOTO_RESOLUTION_7MP_WIDE - 7MP Wide.
-  | 3 // GOPRO_PHOTO_RESOLUTION_10MP_WIDE - 10MP Wide.
-  | 4 // GOPRO_PHOTO_RESOLUTION_12MP_WIDE - 12MP Wide.
-  | number;
-
-export type GOPRO_PROTUNE_WHITE_BALANCE =
-  | 0 // GOPRO_PROTUNE_WHITE_BALANCE_AUTO - Auto.
-  | 1 // GOPRO_PROTUNE_WHITE_BALANCE_3000K - 3000K.
-  | 2 // GOPRO_PROTUNE_WHITE_BALANCE_5500K - 5500K.
-  | 3 // GOPRO_PROTUNE_WHITE_BALANCE_6500K - 6500K.
-  | 4 // GOPRO_PROTUNE_WHITE_BALANCE_RAW - Camera Raw.
-  | number;
-
-export type GOPRO_PROTUNE_COLOUR =
-  | 0 // GOPRO_PROTUNE_COLOUR_STANDARD - Auto.
-  | 1 // GOPRO_PROTUNE_COLOUR_NEUTRAL - Neutral.
-  | number;
-
-export type GOPRO_PROTUNE_GAIN =
-  | 0 // GOPRO_PROTUNE_GAIN_400 - ISO 400.
-  | 1 // GOPRO_PROTUNE_GAIN_800 - ISO 800 (Only Hero 4).
-  | 2 // GOPRO_PROTUNE_GAIN_1600 - ISO 1600.
-  | 3 // GOPRO_PROTUNE_GAIN_3200 - ISO 3200 (Only Hero 4).
-  | 4 // GOPRO_PROTUNE_GAIN_6400 - ISO 6400.
-  | number;
-
-export type GOPRO_PROTUNE_SHARPNESS =
-  | 0 // GOPRO_PROTUNE_SHARPNESS_LOW - Low Sharpness.
-  | 1 // GOPRO_PROTUNE_SHARPNESS_MEDIUM - Medium Sharpness.
-  | 2 // GOPRO_PROTUNE_SHARPNESS_HIGH - High Sharpness.
-  | number;
-
-export type GOPRO_PROTUNE_EXPOSURE =
-  | 0 // GOPRO_PROTUNE_EXPOSURE_NEG_5_0 - -5.0 EV (Hero 3+ Only).
-  | 1 // GOPRO_PROTUNE_EXPOSURE_NEG_4_5 - -4.5 EV (Hero 3+ Only).
-  | 2 // GOPRO_PROTUNE_EXPOSURE_NEG_4_0 - -4.0 EV (Hero 3+ Only).
-  | 3 // GOPRO_PROTUNE_EXPOSURE_NEG_3_5 - -3.5 EV (Hero 3+ Only).
-  | 4 // GOPRO_PROTUNE_EXPOSURE_NEG_3_0 - -3.0 EV (Hero 3+ Only).
-  | 5 // GOPRO_PROTUNE_EXPOSURE_NEG_2_5 - -2.5 EV (Hero 3+ Only).
-  | 6 // GOPRO_PROTUNE_EXPOSURE_NEG_2_0 - -2.0 EV.
-  | 7 // GOPRO_PROTUNE_EXPOSURE_NEG_1_5 - -1.5 EV.
-  | 8 // GOPRO_PROTUNE_EXPOSURE_NEG_1_0 - -1.0 EV.
-  | 9 // GOPRO_PROTUNE_EXPOSURE_NEG_0_5 - -0.5 EV.
-  | 10 // GOPRO_PROTUNE_EXPOSURE_ZERO - 0.0 EV.
-  | 11 // GOPRO_PROTUNE_EXPOSURE_POS_0_5 - +0.5 EV.
-  | 12 // GOPRO_PROTUNE_EXPOSURE_POS_1_0 - +1.0 EV.
-  | 13 // GOPRO_PROTUNE_EXPOSURE_POS_1_5 - +1.5 EV.
-  | 14 // GOPRO_PROTUNE_EXPOSURE_POS_2_0 - +2.0 EV.
-  | 15 // GOPRO_PROTUNE_EXPOSURE_POS_2_5 - +2.5 EV (Hero 3+ Only).
-  | 16 // GOPRO_PROTUNE_EXPOSURE_POS_3_0 - +3.0 EV (Hero 3+ Only).
-  | 17 // GOPRO_PROTUNE_EXPOSURE_POS_3_5 - +3.5 EV (Hero 3+ Only).
-  | 18 // GOPRO_PROTUNE_EXPOSURE_POS_4_0 - +4.0 EV (Hero 3+ Only).
-  | 19 // GOPRO_PROTUNE_EXPOSURE_POS_4_5 - +4.5 EV (Hero 3+ Only).
-  | 20 // GOPRO_PROTUNE_EXPOSURE_POS_5_0 - +5.0 EV (Hero 3+ Only).
-  | number;
-
-export type GOPRO_CHARGING =
-  | 0 // GOPRO_CHARGING_DISABLED - Charging disabled.
-  | 1 // GOPRO_CHARGING_ENABLED - Charging enabled.
-  | number;
-
-export type GOPRO_MODEL =
-  | 0 // GOPRO_MODEL_UNKNOWN - Unknown gopro model.
-  | 1 // GOPRO_MODEL_HERO_3_PLUS_SILVER - Hero 3+ Silver (HeroBus not supported by GoPro).
-  | 2 // GOPRO_MODEL_HERO_3_PLUS_BLACK - Hero 3+ Black.
-  | 3 // GOPRO_MODEL_HERO_4_SILVER - Hero 4 Silver.
-  | 4 // GOPRO_MODEL_HERO_4_BLACK - Hero 4 Black.
-  | number;
-
-export type GOPRO_BURST_RATE =
-  | 0 // GOPRO_BURST_RATE_3_IN_1_SECOND - 3 Shots / 1 Second.
-  | 1 // GOPRO_BURST_RATE_5_IN_1_SECOND - 5 Shots / 1 Second.
-  | 2 // GOPRO_BURST_RATE_10_IN_1_SECOND - 10 Shots / 1 Second.
-  | 3 // GOPRO_BURST_RATE_10_IN_2_SECOND - 10 Shots / 2 Second.
-  | 4 // GOPRO_BURST_RATE_10_IN_3_SECOND - 10 Shots / 3 Second (Hero 4 Only).
-  | 5 // GOPRO_BURST_RATE_30_IN_1_SECOND - 30 Shots / 1 Second.
-  | 6 // GOPRO_BURST_RATE_30_IN_2_SECOND - 30 Shots / 2 Second.
-  | 7 // GOPRO_BURST_RATE_30_IN_3_SECOND - 30 Shots / 3 Second.
-  | 8 // GOPRO_BURST_RATE_30_IN_6_SECOND - 30 Shots / 6 Second.
-  | number;
-
-export type MAV_CMD_DO_AUX_FUNCTION_SWITCH_LEVEL =
-  | 0 // MAV_CMD_DO_AUX_FUNCTION_SWITCH_LEVEL_LOW - Switch Low.
-  | 1 // MAV_CMD_DO_AUX_FUNCTION_SWITCH_LEVEL_MIDDLE - Switch Middle.
-  | 2 // MAV_CMD_DO_AUX_FUNCTION_SWITCH_LEVEL_HIGH - Switch High.
-  | number;
-
-export type LED_CONTROL_PATTERN =
-  | 0 // LED_CONTROL_PATTERN_OFF - LED patterns off (return control to regular vehicle control).
-  | 1 // LED_CONTROL_PATTERN_FIRMWAREUPDATE - LEDs show pattern during firmware update.
-  | 255 // LED_CONTROL_PATTERN_CUSTOM - Custom Pattern using custom bytes fields.
-  | number;
-
-// Flags in EKF_STATUS message.
-export type EKF_STATUS_FLAGS =
-  | 1 // EKF_ATTITUDE - Set if EKF&#x27;s attitude estimate is good.
-  | 2 // EKF_VELOCITY_HORIZ - Set if EKF&#x27;s horizontal velocity estimate is good.
-  | 4 // EKF_VELOCITY_VERT - Set if EKF&#x27;s vertical velocity estimate is good.
-  | 8 // EKF_POS_HORIZ_REL - Set if EKF&#x27;s horizontal position (relative) estimate is good.
-  | 16 // EKF_POS_HORIZ_ABS - Set if EKF&#x27;s horizontal position (absolute) estimate is good.
-  | 32 // EKF_POS_VERT_ABS - Set if EKF&#x27;s vertical position (absolute) estimate is good.
-  | 64 // EKF_POS_VERT_AGL - Set if EKF&#x27;s vertical position (above ground) estimate is good.
-  | 128 // EKF_CONST_POS_MODE - EKF is in constant position mode and does not know it&#x27;s absolute or relative position.
-  | 256 // EKF_PRED_POS_HORIZ_REL - Set if EKF&#x27;s predicted horizontal position (relative) estimate is good.
-  | 512 // EKF_PRED_POS_HORIZ_ABS - Set if EKF&#x27;s predicted horizontal position (absolute) estimate is good.
-  | 32768 // EKF_GPS_GLITCHING - Set if EKF believes the GPS input data is faulty.
-  | 1024 // EKF_UNINITIALIZED - Set if EKF has never been healthy.
-  | number;
-
-export type PID_TUNING_AXIS =
-  | 1
-  | 2
-  | 3
-  | 4
-  | 5
-  | 6
-  | number;
-
-// Special ACK block numbers control activation of dataflash log streaming.
-export type MAV_REMOTE_LOG_DATA_BLOCK_COMMANDS =
-  | 2147483645 // MAV_REMOTE_LOG_DATA_BLOCK_STOP - UAV to stop sending DataFlash blocks.
-  | 2147483646 // MAV_REMOTE_LOG_DATA_BLOCK_START - UAV to start sending DataFlash blocks.
-  | number;
-
-// Possible remote log data block statuses.
-export type MAV_REMOTE_LOG_DATA_BLOCK_STATUSES =
-  | 0 // MAV_REMOTE_LOG_DATA_BLOCK_NACK - This block has NOT been received.
-  | 1 // MAV_REMOTE_LOG_DATA_BLOCK_ACK - This block has been received.
-  | number;
-
-// Bus types for device operations.
-export type DEVICE_OP_BUSTYPE =
-  | 0 // DEVICE_OP_BUSTYPE_I2C - I2C Device operation.
-  | 1 // DEVICE_OP_BUSTYPE_SPI - SPI Device operation.
-  | number;
-
-// Deepstall flight stage.
-export type DEEPSTALL_STAGE =
-  | 0 // DEEPSTALL_STAGE_FLY_TO_LANDING - Flying to the landing point.
-  | 1 // DEEPSTALL_STAGE_ESTIMATE_WIND - Building an estimate of the wind.
-  | 2 // DEEPSTALL_STAGE_WAIT_FOR_BREAKOUT - Waiting to breakout of the loiter to fly the approach.
-  | 3 // DEEPSTALL_STAGE_FLY_TO_ARC - Flying to the first arc point to turn around to the landing point.
-  | 4 // DEEPSTALL_STAGE_ARC - Turning around back to the deepstall landing point.
-  | 5 // DEEPSTALL_STAGE_APPROACH - Approaching the landing point.
-  | 6 // DEEPSTALL_STAGE_LAND - Stalling and steering towards the land point.
-  | number;
-
-// A mapping of plane flight modes for custom_mode field of heartbeat.
-export type PLANE_MODE =
-  | 0 // PLANE_MODE_MANUAL - MANUAL
-  | 1 // PLANE_MODE_CIRCLE - CIRCLE
-  | 2 // PLANE_MODE_STABILIZE - STABILIZE
-  | 3 // PLANE_MODE_TRAINING - TRAINING
-  | 4 // PLANE_MODE_ACRO - ACRO
-  | 5 // PLANE_MODE_FLY_BY_WIRE_A - FBWA
-  | 6 // PLANE_MODE_FLY_BY_WIRE_B - FBWB
-  | 7 // PLANE_MODE_CRUISE - CRUISE
-  | 8 // PLANE_MODE_AUTOTUNE - AUTOTUNE
-  | 10 // PLANE_MODE_AUTO - AUTO
-  | 11 // PLANE_MODE_RTL - RTL
-  | 12 // PLANE_MODE_LOITER - LOITER
-  | 13 // PLANE_MODE_TAKEOFF - TAKEOFF
-  | 14 // PLANE_MODE_AVOID_ADSB - AVOID ADSB
-  | 15 // PLANE_MODE_GUIDED - GUIDED
-  | 16 // PLANE_MODE_INITIALIZING - INITIALISING
-  | 17 // PLANE_MODE_QSTABILIZE - QSTABILIZE
-  | 18 // PLANE_MODE_QHOVER - QHOVER
-  | 19 // PLANE_MODE_QLOITER - QLOITER
-  | 20 // PLANE_MODE_QLAND - QLAND
-  | 21 // PLANE_MODE_QRTL - QRTL
-  | 22 // PLANE_MODE_QAUTOTUNE - QAUTOTUNE
-  | 23 // PLANE_MODE_QACRO - QACRO
-  | 24 // PLANE_MODE_THERMAL - THERMAL
-  | 25 // PLANE_MODE_LOITER_ALT_QLAND - LOITER2QLAND
-  | 26 // PLANE_MODE_AUTOLAND - AUTOLAND
-  | number;
-
-// A mapping of copter flight modes for custom_mode field of heartbeat.
-export type COPTER_MODE =
-  | 0 // COPTER_MODE_STABILIZE - STABILIZE
-  | 1 // COPTER_MODE_ACRO - ACRO
-  | 2 // COPTER_MODE_ALT_HOLD - ALT HOLD
-  | 3 // COPTER_MODE_AUTO - AUTO
-  | 4 // COPTER_MODE_GUIDED - GUIDED
-  | 5 // COPTER_MODE_LOITER - LOITER
-  | 6 // COPTER_MODE_RTL - RTL
-  | 7 // COPTER_MODE_CIRCLE - CIRCLE
-  | 9 // COPTER_MODE_LAND - LAND
-  | 11 // COPTER_MODE_DRIFT - DRIFT
-  | 13 // COPTER_MODE_SPORT - SPORT
-  | 14 // COPTER_MODE_FLIP - FLIP
-  | 15 // COPTER_MODE_AUTOTUNE - AUTOTUNE
-  | 16 // COPTER_MODE_POSHOLD - POSHOLD
-  | 17 // COPTER_MODE_BRAKE - BRAKE
-  | 18 // COPTER_MODE_THROW - THROW
-  | 19 // COPTER_MODE_AVOID_ADSB - AVOID ADSB
-  | 20 // COPTER_MODE_GUIDED_NOGPS - GUIDED NOGPS
-  | 21 // COPTER_MODE_SMART_RTL - SMARTRTL
-  | 22 // COPTER_MODE_FLOWHOLD - FLOWHOLD
-  | 23 // COPTER_MODE_FOLLOW - FOLLOW
-  | 24 // COPTER_MODE_ZIGZAG - ZIGZAG
-  | 25 // COPTER_MODE_SYSTEMID - SYSTEMID
-  | 26 // COPTER_MODE_AUTOROTATE - AUTOROTATE
-  | 27 // COPTER_MODE_AUTO_RTL - AUTO RTL
-  | 28 // COPTER_MODE_TURTLE - TURTLE
-  | number;
-
-// A mapping of sub flight modes for custom_mode field of heartbeat.
-export type SUB_MODE =
-  | 0 // SUB_MODE_STABILIZE - STABILIZE
-  | 1 // SUB_MODE_ACRO - ACRO
-  | 2 // SUB_MODE_ALT_HOLD - ALT HOLD
-  | 3 // SUB_MODE_AUTO - AUTO
-  | 4 // SUB_MODE_GUIDED - GUIDED
-  | 7 // SUB_MODE_CIRCLE - CIRCLE
-  | 9 // SUB_MODE_SURFACE - SURFACE
-  | 16 // SUB_MODE_POSHOLD - POSHOLD
-  | 19 // SUB_MODE_MANUAL - MANUAL
-  | 20 // SUB_MODE_MOTORDETECT - MOTORDETECT
-  | 21 // SUB_MODE_SURFTRAK - SURFTRAK
-  | number;
-
-// A mapping of rover flight modes for custom_mode field of heartbeat.
-export type ROVER_MODE =
-  | 0 // ROVER_MODE_MANUAL - MANUAL
-  | 1 // ROVER_MODE_ACRO - ACRO
-  | 3 // ROVER_MODE_STEERING - STEERING
-  | 4 // ROVER_MODE_HOLD - HOLD
-  | 5 // ROVER_MODE_LOITER - LOITER
-  | 6 // ROVER_MODE_FOLLOW - FOLLOW
-  | 7 // ROVER_MODE_SIMPLE - SIMPLE
-  | 8 // ROVER_MODE_DOCK - DOCK
-  | 9 // ROVER_MODE_CIRCLE - CIRCLE
-  | 10 // ROVER_MODE_AUTO - AUTO
-  | 11 // ROVER_MODE_RTL - RTL
-  | 12 // ROVER_MODE_SMART_RTL - SMART RTL
-  | 15 // ROVER_MODE_GUIDED - GUIDED
-  | 16 // ROVER_MODE_INITIALIZING - INITIALISING
-  | number;
-
-// A mapping of antenna tracker flight modes for custom_mode field of heartbeat.
-export type TRACKER_MODE =
-  | 0 // TRACKER_MODE_MANUAL - MANUAL
-  | 1 // TRACKER_MODE_STOP - STOP
-  | 2 // TRACKER_MODE_SCAN - SCAN
-  | 3 // TRACKER_MODE_SERVO_TEST - SERVO TEST
-  | 4 // TRACKER_MODE_GUIDED - GUIDED
-  | 10 // TRACKER_MODE_AUTO - AUTO
-  | 16 // TRACKER_MODE_INITIALIZING - INITIALISING
-  | number;
-
-// The type of parameter for the OSD parameter editor.
-export type OSD_PARAM_CONFIG_TYPE =
-  | 0
-  | 1
-  | 2
-  | 3
-  | 4
-  | 5
-  | 6
-  | 7
-  | 8
-  | number;
-
-// The error type for the OSD parameter editor.
-export type OSD_PARAM_CONFIG_ERROR =
-  | 0
-  | 1
-  | 2
-  | 3
-  | number;
-