beacon mode + meter-anchored verification; discovery: intermittent post-chip TX RF death; withdraw single-burst confirmations

This commit is contained in:
Lars Nolden
2026-09-01 17:52:18 +02:00
parent ee76269d31
commit d5aa9bcc8e
6 changed files with 259 additions and 0 deletions
+33
View File
@@ -85,3 +85,36 @@ because the sequence of wrong theories is itself a finding.
identical geometry, cable in vs out (LiPo), antenna close.
- Proper antenna A/B (e.g. quarter-wave with radials vs stock whip) --
directly relevant to the gateway RF architecture.
## Location 3 (evening session) -- the beacon, and the real fault
Coordinating physical actions with an async agent kept failing (missed
timestamps, tuner deaths mid-capture), so we changed instruments: a
firmware **beacon mode** (`set beacon_period_ms N`) transmits a synthetic
OMS frame (manufacturer SLN, ID 00000001, access_nr = sequence) every N ms.
No meter traffic, no serial coordination, dense uniform sampling.
The beacon caught what two days of repeat-chasing could not:
- **TX radiated power is intermittent at minute scale.** One 90 s window:
0/25 beacons produced ANY RF (max +0.5 dB over floor) while 27 ambient
meter frames in the same IQ showed median +26.8 dB (observer healthy) and
the chip reported TX_DONE, mode 6, device_errors 0 for every beacon.
Thirty minutes later, same boot, same config: repeats, test_tx and
beacons all radiated at a constant ~+10 dB.
- RX stayed healthy through dead TX windows. Chip-side diagnostics are
identical in dead and live states. The fault therefore sits between the
SX1262 PA output and the antenna: KCT8103L PA path (CPS/DIO2, CTX, PA
supply) or a mechanical/thermal TX-chain fault. Firmware cannot observe
it -- exactly the RADIO_VDD_SENSE / conducted-test-port gap in
docs/devboard_signals.csv.
- **Methodology bug found and fixed:** verify_repeats_iq's single-burst
clock fit can lock at -repeat_delay and "confirm" every repeat with its
own original's burst. The "7/7 at +37 dB" laptop confirmations were this
artifact. Trustworthy methods: structural same-duration pairs at the
configured delay, content decodes (duplicate payloads), and
hil/meter_anchored.py (clock fitted on strong meter receptions; ambient
meter levels double as per-capture observer health).
- Positive control: with a healthy observer, 30 structural pairs at
137 ms and 35 duplicate decoded payloads in 90 s -- the repeater
function itself is solid whenever the TX chain is in its live state.
+24
View File
@@ -147,6 +147,30 @@
- Long-run stability at >=100 and >=500 verified repeat events.
- Early-stop RX (poll GetRxBufferStatus) to cut the ~20 ms deaf tail.
## Location 3 follow-up (2026-09-01 evening): intermittent TX RF death
- CONFIRMED: the DUT's radiated TX output is intermittent on minute scales
-- genuinely zero (not weak) for >=10 min windows, then a stable ~+10 dB
at the SDR. Verified with beacon mode against in-capture ambient-meter
controls (observer healthy: meters +26.8 dB median while 25/25 beacons
produced <= +0.5 dB). RX unaffected; chip reports TX_DONE/mode 6/no
errors in both states => fault is post-chip (KCT8103L PA path or TX
chain), invisible to firmware. Hardware follow-up required; strengthens
the RADIO_VDD_SENSE and conducted-RF-test-port devboard requirements.
- WITHDRAWN: every single-burst "TX aligned to IQ" confirmation (e.g.
"7/7 at +37 dB", "33/41 at +19.3 dB"). verify_repeats_iq's clock fit on
TX events can lock at -repeat_delay and match each repeat to its own
original's burst. Borrow-immune evidence only: structural same-duration
pairs at the configured delay, duplicate content decodes, or
hil/meter_anchored.py (meter-anchored clock, exact TX windows).
- CONFIRMED: observer health must be judged per capture from ambient meter
levels inside the same IQ (meter median >= +15 dB over floor). The
Nooelec went deaf mid-session again; runs without this control are void.
- CORRECTION to yesterday's "placement dominates": placement governs
whether PAIRS are detectable (originals must be SDR-visible), but the
standalone invisibility episodes are better explained by the intermittent
TX death now that it has been directly observed under controls.
## Field test 2026-09-01 (onsite standalone deployment)
Full narrative with the evidence table: docs/FIELD_TEST_2026-09-01.md.