open questions: DUTY_RING saturation is active at beacon rates, guard fails open
This commit is contained in:
@@ -42,8 +42,10 @@
|
|||||||
|
|
||||||
## Duty ledger ring capacity (noted 2026-09-01, loc3)
|
## Duty ledger ring capacity (noted 2026-09-01, loc3)
|
||||||
|
|
||||||
DUTY_RING=384 entries; at minimum C1 frame airtimes (~6 ms) a full legal
|
DUTY_RING=384 entries saturates at ~2.7 s of history at ~7 ms mean
|
||||||
budget (3.6 s/h at 1000 ppm) needs ~600 entries, so the rolling-hour sum
|
airtimes -- BELOW the 3.6 s budget, so the guard silently never triggers
|
||||||
can under-count at maximum legal rate with small frames. Not reachable in
|
at high TX rates. OBSERVED ACTIVE during the 2026-09-01 beacon soak
|
||||||
normal repeater traffic (mean airtime >=10 ms); bump to 1024 at next
|
(duty_used_us plateaued at ~3.46 s while true hourly airtime was ~20 s;
|
||||||
firmware change.
|
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.
|
||||||
|
|||||||
Reference in New Issue
Block a user