Enumeration Config_PositionConfig_PositionFlags

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 Config.PositionConfig.PositionFlags

Enumeration Members

POS_ALTITUDE: 1

Include an altitude value (if available)

Generated

from protobuf enum value: POS_ALTITUDE = 1;

POS_ALT_MSL: 2

Altitude value is MSL

Generated

from protobuf enum value: POS_ALT_MSL = 2;

POS_DOP: 8

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

Generated

from protobuf enum value: POS_DOP = 8;

POS_GEO_SEP: 4

Include geoidal separation

Generated

from protobuf enum value: POS_GEO_SEP = 4;

POS_HEADING: 256

Include positional heading Intended for use with vehicle not walking speeds walking speeds are likely to be error prone like the compass

Generated

from protobuf enum value: POS_HEADING = 256;

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: 32

Include number of "satellites in view"

Generated

from protobuf enum value: POS_SATINVIEW = 32;

POS_SEQ_NOS: 64

Include a sequence number incremented per packet

Generated

from protobuf enum value: POS_SEQ_NOS = 64;

POS_SPEED: 512

Include positional speed Intended for use with vehicle not walking speeds walking speeds are likely to be error prone like the compass

Generated

from protobuf enum value: POS_SPEED = 512;

POS_TIMESTAMP: 128

Include positional timestamp (from GPS solution)

Generated

from protobuf enum value: POS_TIMESTAMP = 128;

POS_UNDEFINED: 0

Required for compilation

Generated

from protobuf enum value: POS_UNDEFINED = 0;

Generated using TypeDoc