docs/power.md: rxps failed on the live mesh (fewer packets, TX stall); tickless loop sleep measured at zero
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
2e8aea5c44
commit
01d66a66ce
1 file changed
+17
-1
+17
-1
@@ -13,7 +13,7 @@ figures are.
|
||||
| **GPS running continuously** | **46.0 mA** (spread 43.7-47.5) | `gps duty` recovers 42-45 of it |
|
||||
| BLE advertising + Bluefruit's blinking LED | see below | defaults changed, LED off, 1 s interval |
|
||||
| `powersaving on` (MCU light sleep) | **~1 mA, not separable from zero** | keep it on (free), but it is not a lever |
|
||||
| RX duty cycle (`set radio.rxps`, from EasySkyMesh) | **~2.3 mA** at `max` (XIAO, 12. 11. 2026) | opt-in, off by default: worth it on a small panel, see below |
|
||||
| RX duty cycle (`set radio.rxps`, from EasySkyMesh) | **~2.3 mA** at `max` (XIAO, 12. 11. 2026) | **no** on a live node: -16 % received and a TX stall on mast-three, see below |
|
||||
| `radio.rxgain off` | ~0.7 mA | **no** — 1-3 dB of sensitivity is what a mast node is for |
|
||||
| FEM LNA control | n/a | SenseCap has no FEM, only an RXEN switch |
|
||||
|
||||
@@ -132,6 +132,17 @@ off as well, and of the three at level 3 one was on x3, which had rxps off: the
|
||||
bench shows no degradation at any level. Not measured: mixed SF/preamble senders, a busy
|
||||
live mesh. On a mast, where 2 mA of ~24 is not the problem, leave it off.
|
||||
|
||||
**On the live mesh it failed (mast-three, 14. 11. 2026, `max`).** Against ob1 as
|
||||
the reference for the hour-to-hour traffic, the node received ~16 % fewer
|
||||
packets (2.08 vs 2.47 per ob1 packet) with ~30 % more `recv_errors`, and within
|
||||
two hours of switching it on it stopped transmitting altogether: `sent` frozen,
|
||||
queue full (32), no `tx_start_fail`/`tx_timeout`, RX still counting -- so no
|
||||
adverts and no replies to an admin login, for 6+ hours. `radiostat` showed
|
||||
`irq=0x0014` (preamble + header valid, no RX done). `set radio.rxps off` did
|
||||
NOT bring TX back; a reboot did. The mechanism is not proven, and the radio
|
||||
silence watchdog cannot see it (it watches RX only). Do not enable rxps on a
|
||||
node that has to answer.
|
||||
|
||||
## MCU sleep
|
||||
|
||||
`powersaving on` makes the nRF52 wait in WFE between events (it wakes on any
|
||||
@@ -148,6 +159,11 @@ still polls the SX1262 over SPI on every pass and the SoftDevice wakes the core
|
||||
for each advertising event, so there is not much idle left to sleep through.
|
||||
Keep it on (it is free and cannot hurt), but do not budget for it.
|
||||
|
||||
Blocking the loop task instead of waiting for an event (so that FreeRTOS can
|
||||
sleep tickless) changes nothing either: `delay(10)` against `sd_app_evt_wait()`,
|
||||
XIAO x4, A/B/A/B 30 min cells (14. 11. 2026): paired difference **0.04 mA**,
|
||||
cell repeatability 0.1-0.4 mA. The tick wakeups are not where the current goes.
|
||||
|
||||
One fork-specific fix goes with it: the sleep is also held off while the BLE
|
||||
console still has queued output (`bleTxPending()`), because on the observer node
|
||||
a half-drained `rxlog`/`pktlog` page would otherwise wait for the next
|
||||
|
||||
Reference in new issue
Block a user