Component ID's
Component ID’s are used to identify what different devices are, where messages come from and to send commands specific devices.
Known Component ID’s
Value | Field Name | Description | Used By Aeronavics |
|---|---|---|---|
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 ("autopilot"). Only one autopilot is expected in a particular system. | ✓ |
25-49 | MAV_COMP_ID_USER1-25 | 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-59 | MAV_COMP_ID_ANV1-10 | Used by Aeronavics for custom components | ✓ |
60-67 | MAV_COMP_ID_USER36-43 | 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-99 | MAV_COMP_ID_USER45-75 | 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-153 | MAV_COMP_ID_SERVO1-14 | Servo #1 - #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 DEPRECATED: Replaced by MAV_COMP_ID_GIMBAL (2018-11). All gimbals should use MAV_COMP_ID_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-175 | MAV_COMP_ID_GIMBAL2-6 | Gimbal #2 - #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 | The Onboard mission computer used by Aeronavics. | ✓ |
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'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'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'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). | |
250 | MAV_COMP_ID_SYSTEM_CONTROL DEPRECATED: Replaced by MAV_COMP_ID_ALL (2018-11). System control does not require a separate component ID. Instead, system commands should be sent with target_component=MAV_COMP_ID_ALL allowing the target component to use any appropriate component id. | Deprecated, don't use. Component for handling system messages (e.g. to ARM, takeoff, etc.). |