docs: gps duty vs upstream gps period; advert.loc, not "set loc"
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
8d0b0dd164
commit
84e4136a84
2 files changed
+2
-2
No files matched your search
@@ -1141,7 +1141,7 @@ mast or solar repeater — where a receiver drawing tens of mA continuously
|
||||
dwarfs the rest of the power budget. Unlike `gps period`, every attempt is
|
||||
capped even before the first fix ever, so a node that never sees the sky does
|
||||
not keep the receiver powered. It sets `gps period` to 0. The position still
|
||||
comes from prefs (see `set loc`), so duty mode does not affect what a repeater
|
||||
comes from prefs (see `set advert.loc`), so duty mode does not affect what a repeater
|
||||
advertises. `gps on` / `gps off` leave duty mode. Build-time knobs:
|
||||
`GPS_DUTY_SYNC_INTERVAL_SECS` (1800), `GPS_DUTY_MAX_AWAKE_SECS` (300, the cap on
|
||||
one attempt) and `GPS_DUTY_RETRY_SECS` (3600, backoff after a window with no fix).
|
||||
|
||||
@@ -535,7 +535,7 @@ void CommonCLI::handleCommand(uint32_t sender_timestamp, char* command, char* re
|
||||
} else if (memcmp(command, "gps duty", 8) == 0) {
|
||||
// Power GPS only around a clock sync. For a node that runs GPS purely for
|
||||
// the (volatile) RTC this is the same service at a fraction of the power;
|
||||
// position keeps coming from prefs, see `set loc`. Duty owns the cadence,
|
||||
// position keeps coming from prefs, see `set advert.loc`. Duty owns the cadence,
|
||||
// so a `gps period` left over would fight it.
|
||||
if (_sensors->setSettingValue("gps", "2")) {
|
||||
_prefs->getGpsPrefs()->setGpsPeriod(*_sensors, 0);
|
||||
|
||||
Reference in new issue
Block a user