Enumeration Config_PositionConfig_PositionFlags

Bit field of boolean configuration options, indicating which optional fields to include when assembling POSITION messages. Longitude, latitude, altitude, speed, heading, and DOP 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 enum meshtastic.Config.PositionConfig.PositionFlags

Enumeration Members

ALTITUDE: 1

Include an altitude value (if available)

Generated

from enum value: ALTITUDE = 1;

ALTITUDE_MSL: 2

Altitude value is MSL

Generated

from enum value: ALTITUDE_MSL = 2;

DOP: 8

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

Generated

from enum value: DOP = 8;

GEOIDAL_SEPARATION: 4

Include geoidal separation

Generated

from enum value: GEOIDAL_SEPARATION = 4;

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 enum value: HEADING = 256;

HVDOP: 16

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

Generated

from enum value: HVDOP = 16;

SATINVIEW: 32

Include number of "satellites in view"

Generated

from enum value: SATINVIEW = 32;

SEQ_NO: 64

Include a sequence number incremented per packet

Generated

from enum value: SEQ_NO = 64;

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 enum value: SPEED = 512;

TIMESTAMP: 128

Include positional timestamp (from GPS solution)

Generated

from enum value: TIMESTAMP = 128;

UNSET: 0

Required for compilation

Generated

from enum value: UNSET = 0;

Generated using TypeDoc