Options
All
  • Public
  • Public/Protected
  • All
Menu

Bit field of boolean configuration options, indicating which optional fields to include when assembling POSITION messages Longitude and latitude are always included (also time if GPS-synced)

NOTE: the more fields are included, the larger the message will be - leading to longer airtime and a higher risk of packet loss

generated

from protobuf enum PositionFlags

Index

Enumeration members

POS_ALTITUDE

POS_ALTITUDE = 1

Include an altitude value (if available)

generated

from protobuf enum value: POS_ALTITUDE = 1;

POS_ALT_MSL

POS_ALT_MSL = 2

Altitude value is MSL

generated

from protobuf enum value: POS_ALT_MSL = 2;

POS_BATTERY

POS_BATTERY = 32

Include battery level

generated

from protobuf enum value: POS_BATTERY = 32;

POS_DOP

POS_DOP = 8

Include the DOP value ; PDOP used by default, see below

generated

from protobuf enum value: POS_DOP = 8;

POS_GEO_SEP

POS_GEO_SEP = 4

Include geoidal separation

generated

from protobuf enum value: POS_GEO_SEP = 4;

POS_HVDOP

POS_HVDOP = 16

If POS_DOP set, send separate HDOP / VDOP values instead of PDOP

generated

from protobuf enum value: POS_HVDOP = 16;

POS_SATINVIEW

POS_SATINVIEW = 64

Include number of "satellites in view"

generated

from protobuf enum value: POS_SATINVIEW = 64;

POS_SEQ_NOS

POS_SEQ_NOS = 128

Include a sequence number incremented per packet

generated

from protobuf enum value: POS_SEQ_NOS = 128;

POS_TIMESTAMP

POS_TIMESTAMP = 256

Include positional timestamp (from GPS solution)

generated

from protobuf enum value: POS_TIMESTAMP = 256;

POS_UNDEFINED

POS_UNDEFINED = 0

Required for compilation

generated

from protobuf enum value: POS_UNDEFINED = 0;

Generated using TypeDoc