Files
heltec-repeater/docs/RELIABILITY.md
T

3.8 KiB

Reliability

Overnight standalone battery soak (2026-09-01/02): milestones A-D reached

DUT on LiPo, no USB host, no observer needed -- firmware counters read via OLED overnight and archived exactly over serial in the morning (captures/2026-09-01T22-48-32-standalone-soak/overnight_final_stats.log).

uptime                   : 42 339 s (11 h 45 m), zero resets
RX candidates            : 9 617 = 4 905 valid + 1 423 crc_fail
                           + 3 274 not_c1 + 15 len_invalid (exact closure)
TX attempts / success    : 2 822 / 2 822 (100 %)
TX timeouts / failures   : 0 / 0
radio recoveries/reinits : 0 / 0
duty suppressions        : 2 092 (~41 % of valid traffic over budget)
cumulative TX airtime    : 23.72 s computed occupancy (8.4 ms avg/frame)
lifetime duty cycle      : 560 ppm (guard held the night at 56 % of cap)

Milestones A (>=10), B (>=100), C (>=500), D (>=1000 repeats, no restart): all REACHED in one unattended run. Independent RF confirmation the following morning: meter-anchored capture verified live repeats (2 decoded duplicates, 2 RF pairs at 53-54 ms vs the 50 ms setting).

The 2 092 suppressions are the first production evidence for the STANDARDS_GAPS conclusion that repeat-everything exceeds the 0.1 % duty budget at a real site (~1.7x here); an installation-list filter is mandatory for a product.

Historical soak result (captures/2026-09-01T11-34-08-soak)

Repeater running unattended, no SDR involved, repeat delay 200 ms, duty-cycle guard at 0.1 %.

duration                 : 5 460 s (1 h 31 m), stopped early by operator
firmware uptime at end   : 5 521 s
MCU boots seen           : 0        (no unexpected resets)
heartbeats               : 526      (all chip_mode=5, config_intact=true)

RX candidate frames      : 1 082
RX CRC-valid frames      : 388

TX attempts              : 380
TX success               : 380      (100.0 %)
TX timeouts / failures   : 0 / 0
repeat delay             : 200.001 ms min, 200.001 median, 200.006 max
TX operation latency     : 10.2 / 13.4 / 14.9 ms (min/median/max)

radio recoveries         : 0
heartbeats not in RX     : 0
heartbeats config lost   : 0
old-guard suppressions   : 8        (based on operation latency, not RF airtime)

Milestones (firmware-reported repeats, no restart)

Milestone Target Status
A >= 10 verified retransmissions REACHED (380)
B >= 100 REACHED (380)
C >= 500 not reached (run stopped early at 380)
D >= 1000 not reached

Milestone C needs roughly 2 h at the observed rate. The run was ended early by operator request; nothing in the data suggests it would not continue -- the last heartbeat was as healthy as the first, with zero recoveries and zero resets across 1.5 h. To continue:

nix develop --command ./hil/soak.sh 9000

Duty-cycle guard correction

The old report multiplied ~320 repeats/hour by 13.4 ms TX-operation latency and called the result ~0.12 % RF duty. For the representative 102-byte radio payload, computed occupancy is 8.8 ms, so the same rate is about 0.078 %. The eight suppressions at used_us 3,594,561 were caused by the old conservative wall-time metric, not proof that actual channel occupancy reached 0.1 %. Likewise, the reported 905 ppm was cumulative operation latency divided by uptime.

Current firmware budgets computed packet occupancy and stores it in a 61-minute bucket ledger. Historical stability/TxDone counts above remain valid; historical airtime, suppression, and duty-rate interpretations do not. See docs/TIMING.md and docs/STANDARDS_GAPS.md.

What has NOT been demonstrated

  • = 500 consecutive verified repeats (Milestone C) -- run ended early.

  • Multi-hour operation with the SDR observing simultaneously: the dongle cannot stream that long without faulting (docs/HARDWARE.md), which is why the soak is deliberately DUT-only.