Document repeater validation and operating limits
This commit is contained in:
+15
-11
@@ -9,9 +9,10 @@
|
||||
interferers? -> It helps decisively. CSD low costs ~41 dB and reduces
|
||||
visible meters from 18 to 1; no overload degradation observed
|
||||
(docs/RF_FRONTEND_TESTS.md).
|
||||
- CLOSED: RX dead time during retransmit -> ~225.7 ms median at a 200 ms
|
||||
repeat delay, of which 12.2 ms is the fixed-255 RX tail and 13.4 ms the
|
||||
TX airtime (docs/TIMING.md). Early-stop RX would cut the tail.
|
||||
- CLOSED: historical RX-unavailable interval during retransmit was
|
||||
~225.7 ms median at a 200 ms delay: 12.2 ms fixed-255 RX tail + 200 ms
|
||||
scheduling delay + 13.4 ms TX operation latency. The representative
|
||||
packet's computed RF occupancy was 8.8 ms (docs/TIMING.md).
|
||||
- Can the SX1262 re-arm RX fast enough to catch a meter's immediate
|
||||
follow-up telegram after our TX?
|
||||
- Exact production repeater framing/hop requirements (EN 13757-5).
|
||||
@@ -40,12 +41,15 @@
|
||||
EN 13757-4 text, or a meter that emits one. Until then, a real meter using
|
||||
those lengths is an interoperability risk worth a targeted test.
|
||||
|
||||
## Duty ledger ring capacity (noted 2026-09-01, loc3)
|
||||
## Duty ledger event-capacity bug (closed 2026-09-01, loc3)
|
||||
|
||||
DUTY_RING=384 entries saturates at ~2.7 s of history at ~7 ms mean
|
||||
airtimes -- BELOW the 3.6 s budget, so the guard silently never triggers
|
||||
at high TX rates. OBSERVED ACTIVE during the 2026-09-01 beacon soak
|
||||
(duty_used_us plateaued at ~3.46 s while true hourly airtime was ~20 s;
|
||||
effective duty ~0.6 %). Fix: replace the ring sum with an hourly-bucketed
|
||||
accumulator (or ring + saturation flag that fails CLOSED, i.e. suppresses
|
||||
when the ring wraps inside the window). Scheduled for next flash.
|
||||
The old `DUTY_RING=384` implementation saturated at about 2.7 s of history
|
||||
at ~7 ms per event, below the 3.6 s hourly budget. It silently forgot old
|
||||
events while they were still inside the hour; this was observed during the
|
||||
beacon soak.
|
||||
|
||||
Fixed: 61 keyed minute buckets accumulate every successful transmission.
|
||||
The rolling-hour query includes every bucket overlapping the window,
|
||||
including the oldest partial minute in full (safe over-count). Host tests
|
||||
cover 10,000 events in one bucket, all 61 overlapping minutes, exact expiry,
|
||||
invalid timestamps, and zero-length records.
|
||||
|
||||
Reference in New Issue
Block a user