Skip to main content

DP — GNSS DOP Thresholds

Configures up to ten GNSS dilution-of-precision thresholds. Each slot drives one read-only signal, DP0–DP9, from HDOP, PDOP, or VDOP.

Format​

  • Query: >QDP{NN}<
  • Set: >SDP{NN}{TYPE}{DDD}<
  • Delete: >SDP{NN}U<
  • Configured response: >RDP{NN}{TYPE}{DDD}<
  • Unset response: >RDP{NN}U<
FieldDescription
NNSlot index (00–09), corresponding to signal DP0–DP9
TYPEDOP value to monitor: H = HDOP, P = PDOP, or V = VDOP
DDDThreshold from 000 to 999 in hundredths; 150 represents 1.50

Behavior​

  • A signal activates when its selected DOP value is greater than the threshold.
  • A signal clears when its selected DOP value is less than the threshold.
  • If the value equals the threshold, the signal keeps its current state.
  • Each slot has its own source and threshold. Configuration is retained in nonvolatile storage across restarts.
  • DOP values are read from the GNSS information supplied to the evaluator and compared in hundredths.

Defaults and Limits​

  • Slots: 00–09 (DP0–DP9); slots are unset until configured.
  • Threshold: 000–999 (0.00–9.99).
  • Each slot monitors exactly one DOP source: HDOP, PDOP, or VDOP.
  • Configuration is stored in nonvolatile memory and restored after restart.

Examples​

Configure DP0 to monitor HDOP above 1.50:

>SDP00H150<
>RDP00H150<

Query DP0:

>QDP00<
>RDP00H150<

Configure DP1 to monitor PDOP above 2.25:

>SDP01P225<
>RDP01P225<

Delete DP0:

>SDP00U<
>RDP00U<
  • DP0–DP9 — read-only signals generated by this command.
  • See Signal List for the full signal catalog.

The command processor may append device identification fields to responses.