From f1178bd6c8832ed82c1ed09e4a795e11ef008215 Mon Sep 17 00:00:00 2001 From: Lars Nolden Date: Tue, 1 Sep 2026 18:46:53 +0200 Subject: [PATCH] open questions: DUTY_RING saturation is active at beacon rates, guard fails open --- docs/OPEN_QUESTIONS.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/docs/OPEN_QUESTIONS.md b/docs/OPEN_QUESTIONS.md index 2f23006..7846944 100644 --- a/docs/OPEN_QUESTIONS.md +++ b/docs/OPEN_QUESTIONS.md @@ -42,8 +42,10 @@ ## Duty ledger ring capacity (noted 2026-09-01, loc3) -DUTY_RING=384 entries; at minimum C1 frame airtimes (~6 ms) a full legal -budget (3.6 s/h at 1000 ppm) needs ~600 entries, so the rolling-hour sum -can under-count at maximum legal rate with small frames. Not reachable in -normal repeater traffic (mean airtime >=10 ms); bump to 1024 at next -firmware change. +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.