FLIR Duo - Appendix B - Mavlink Implementation

FLI R Duo User Guide
436-0100-01-10, Rev. 200 Duo User Guide
Information on this page is subject to change without notice
40
Appendix B - MAVLink Implementation
CMD ID
Field Name
Data
Type
Description (MAVlink published data)
FLIR Implementation
Device Implementation
FLIR Duo / R
0
HEARTBEAT
Shows the system is present and responding.
System ID
MAVlink packet Byte 3
Standard
1
Component ID
MAVlink packet Byte 4
Standard
100
Type
uint8_t
MAV_TYPE_GENERIC - Generic micro air vehicle.
Standard
0
Autopilot
uint8_t
MAV_AUTOPILOT_INVALID - No valid autopilot,
e.g. a GCS or other MAVLink component
Standard
8
Base Mode
uint8_t
MAV_MODE_FLAG_MANUAL_INPUT_ENABLED
- 0b01000000 remote control input is enabled.
Standard
64
Custom Mode
uint32_t
A bitfield for use for autopilot-specific flags.
Standard
0
System Status
uint8_t
MAV_STATE_ACTIVE - System is active and
might be already airborne. Motors are engaged.
Standard
4
MAVLink Version
uint8_t
MAVLink version, not writable by user
Standard
Standard
2
SYSTEM_TIME
System master clock time.
Time Unix
uint64_t
Timestamp of the master clock in microseconds
since UNIX epoch.
Standard
If time is valid, it will be set to the
device.
Time Boot
uint32_t
Timestamp of the component clock since boot time
in milliseconds.
Standard
Ignored