2.2 KiB
Reliability
Soak result (final firmware, 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 airtime : 10.2 / 13.4 / 14.9 ms (min/median/max)
radio recoveries : 0
heartbeats not in RX : 0
heartbeats config lost : 0
duty-cycle suppressions : 8 (guard working as designed)
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, or longer once the duty-cycle guard caps output at ~268 repeats/hour. 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 behaviour
At the observed traffic rate the repeater wants ~320 repeats/hour, which at
13.4 ms measured airtime each is ~0.12 % -- above the 0.1 % ceiling for
868.7-869.2 MHz. The guard suppressed 8 repeats to stay inside the budget
(used_us 3 594 561 against budget_us 3 600 000) and reported a final
tx_duty_cycle_ppm of 905, i.e. 0.0905 %. See 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.