Document repeater validation and operating limits
This commit is contained in:
+102
-51
@@ -19,14 +19,15 @@
|
||||
- TX proof of life: SDR decoded our synthetic C1 format-A frame as valid
|
||||
(crc_ok=1, mfr 0x4D8E "SLN", ID 00000001) at configured -9 dBm, and the
|
||||
wM-Bus CRC blocks computed by firmware matched rtl_wmbus's checks.
|
||||
- First real repeat observed: 100-byte Techem frame received, repeated
|
||||
after 50.002 ms (configured 50 ms).
|
||||
- Nooelec NESDR SMArt v5 R820T PLL wedges ("PLL not locked"), producing
|
||||
gain-independent white noise on all frequencies until USB reset.
|
||||
`usbreset 0bda:2838` reliably restores operation. Trigger correlated
|
||||
with `rtl_test -t` direct-sampling probe.
|
||||
- rtl-sdr-blog and osmocom rtl_sdr builds behave identically w.r.t. the
|
||||
wedge; not a driver-fork issue.
|
||||
- First real repeat observed: a 100-byte Techem frame was received and the
|
||||
firmware entered its TX routine 50.002 ms after the reconstructed frame
|
||||
end (configured 50 ms). This timestamp precedes radio preparation; it is
|
||||
not the exact on-air start time.
|
||||
- The Nooelec NESDR SMArt v5 can enter gain-independent, railed-noise
|
||||
states until USB reset or physical replug. The tune-time
|
||||
`[R82XX] PLL not locked!` message is benign and `rtl_test -t` was not the
|
||||
cause. `hil/sdr_health.py` diagnoses the actual failure from gain response
|
||||
and spectral structure.
|
||||
- Real C1 traffic exists at this site: 8 meters in 10 min baseline
|
||||
(docs/SDR_BASELINE.md); one strong plaintext meter (61471660), several
|
||||
marginal encrypted Techem meters.
|
||||
@@ -41,6 +42,18 @@
|
||||
called) -> no notifications despite correct radio-side IRQ config.
|
||||
3. `timeout bash -c "rtl_sdr | rtl_wmbus"` orphans the pipeline children
|
||||
on timeout (device stays claimed). Apply timeout to rtl_sdr directly.
|
||||
4. The `pa_low` diagnostic selected SetPaConfig
|
||||
`(0x01,0x00,0x00,0x01)`, documented in code as a low SX1262 row. Its
|
||||
first two parameters came from the SX1261 +10 dBm row, but
|
||||
`deviceSel=0x00` selected SX1262, creating an undocumented hybrid.
|
||||
Same-capture A/B testing showed about 32 dB less RF than the valid
|
||||
SX1262 row `(0x02,0x02,0x00,0x01)`. Fix: remove the invalid row
|
||||
and diagnostic toggle; always use a valid SX1262 row.
|
||||
5. The rolling-hour duty ledger retained only 384 individual events. At
|
||||
beacon rates it wrapped after about 2.7 s of airtime and silently
|
||||
under-counted the hour. Fix: 61 keyed minute buckets retain all airtime
|
||||
in the overlapping hour; host tests cover high event counts, expiry,
|
||||
boundary overlap, and invalid timestamps.
|
||||
|
||||
## LIKELY
|
||||
|
||||
@@ -61,20 +74,23 @@
|
||||
docs/RF_FRONTEND_TESTS.md.
|
||||
- Repeat payloads are byte-exact: 63/63 logged `tx_payload` values equalled
|
||||
mode bytes + the received raw frame. No corruption in the RX->TX path.
|
||||
- Real repeats are emitted as correct RF: aligning firmware TX timestamps
|
||||
to bursts in the same stream's IQ confirmed 48 of 57 TX events (84 %),
|
||||
with alignment error median 1.3 ms (max 3.6 ms) and burst duration within
|
||||
0.5 ms (median) of the computed airtime. Firmware repeat delay measured
|
||||
200.0 ms min/median/max against a 200 ms setting.
|
||||
- Real repeats are emitted as correct RF: aligning firmware TX-operation
|
||||
timestamps to bursts in the same stream's IQ confirmed 48 of 57 TX
|
||||
events (84 %), with alignment error median 1.3 ms (max 3.6 ms) and
|
||||
burst duration within 0.5 ms (median) of computed airtime. Firmware
|
||||
entered the TX routine at 200.0 ms against a 200 ms setting; radio
|
||||
preparation shifts actual RF onset later.
|
||||
- Firmware TX reliability: 58/58 TX success over 600 s and 72/72 over
|
||||
1200 s; tx_timeout 0, tx_failures 0, radio recoveries 0, MCU resets 0.
|
||||
- The KCT8103L RX path is essential: holding CSD low in RX costs ~41 dB of
|
||||
chip-referred level and drops the visible meter population from 18 to 1
|
||||
(600 s per arm, docs/RF_FRONTEND_TESTS.md). No evidence of excessive
|
||||
front-end gain hurting at this site.
|
||||
- Repeat-delay accuracy: +1 to +8 us against a 200 ms setting across 72
|
||||
repeats. RX deaf time per repeat ~225.7 ms median, of which 12.2 ms is
|
||||
the fixed-255-byte RX tail and 13.4 ms the TX airtime (docs/TIMING.md).
|
||||
- Repeat-operation scheduling: +1 to +8 us against a 200 ms setting across
|
||||
72 repeats. This is accuracy at entry to the TX routine, not RF onset.
|
||||
The historical 13.4 ms value called “TX airtime” was operation latency
|
||||
through observed TxDone; computed channel occupancy was 8.8 ms for the
|
||||
representative 102-byte radio payload (docs/TIMING.md).
|
||||
- The SX1262 GFSK engine cannot express wM-Bus length semantics, so RX uses
|
||||
a fixed 255-byte capture; RxDone therefore fires 9.4-17.1 ms after the
|
||||
real end of frame and the firmware reconstructs the true timestamp.
|
||||
@@ -147,36 +163,38 @@
|
||||
- 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
|
||||
## Location 3 follow-up (2026-09-01 evening): PA configuration postmortem
|
||||
|
||||
- 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.
|
||||
- UPDATE (same evening): antenna + IPEX pigtail EXCLUDED -- after a full
|
||||
antenna swap and pigtail reseat the fault recurred (soak segment 13:
|
||||
106 TX attempts at median +0.5 dB with observer verified healthy).
|
||||
The fault is ON-BOARD. Decay signature before death (+8 -> +6 -> dead
|
||||
over ~10 min under ~50 TX/min load) points at thermal in the FEM PA
|
||||
path; a 90 s breath-cooling attempt did not revive it (inconclusive --
|
||||
needs real thermal provocation or conducted measurement).
|
||||
- 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.
|
||||
- **WITHDRAWN:** the conclusion that this board had an intermittent
|
||||
post-SX1262 hardware TX death. The canonical “0/25 beacons produced any
|
||||
RF” capture was judged only by total energy in 1 ms windows. Reanalysis
|
||||
of the retained IQ finds a repeatable event-correlated FSK signature:
|
||||
TX median +1.5 dB over floor, nearby controls +0.2 dB, and FSK-selective
|
||||
excess +7.6 dB across 25/25 windows. It was weak RF, not zero RF.
|
||||
- Root cause in firmware: the `pa_low` diagnostic combined the SX1261
|
||||
+10 dBm PA-duty/hpMax values with SX1262 `deviceSel=0x00`:
|
||||
`(0x01,0x00,0x00,0x01)`. In a same-stream A/B test, documented SX1262
|
||||
`(0x02,0x02,0x00,0x01)` raised the event envelope by about 32 dB. The
|
||||
invalid toggle and row are now deleted. Configured power
|
||||
is restricted to -9..+2 dBm; the external KCT8103L still follows.
|
||||
- The old logs recorded configured SetTxParams power but not which PA row
|
||||
the diagnostic had selected. Exact row state cannot be reconstructed for
|
||||
every old soak segment, and the old soak deleted each IQ file after its
|
||||
scalar verdict. Therefore its claimed +8 -> +6 -> zero thermal decay is
|
||||
not auditable and is not evidence of a board fault.
|
||||
- Fixed-firmware RF smoke test at configured -9 dBm: 9/9 scheduled beacons,
|
||||
median +27.81 dB over floor (range +27.02..+27.90), nearby controls
|
||||
+0.00 dB, FSK-selective excess +40.73 dB, and no ADC clipping at 0.9 dB
|
||||
SDR gain. Firmware also reported 9/9 TxDone and exactly 24,480 us of
|
||||
computed airtime (9 x 2,720 us).
|
||||
- `hil/meter_anchored.py` now requires event-correlated FSK spectral excess
|
||||
before calling RF present and reports `strong`, `weak`, or
|
||||
`not_observed`. The historical weak capture classifies `weak`; a known
|
||||
live repeat capture classifies `strong`. `hil/beacon_soak.sh` deletes IQ
|
||||
only for `strong` segments and retains every anomaly.
|
||||
- Observer health must still be judged per capture from ambient meter
|
||||
levels. TxDone remains only chip-level evidence. Neither fact supports a
|
||||
board-fault conclusion without the RF signature and retained raw IQ.
|
||||
|
||||
## Field test 2026-09-01 (onsite standalone deployment)
|
||||
|
||||
@@ -192,12 +210,14 @@ Full narrative with the evidence table: docs/FIELD_TEST_2026-09-01.md.
|
||||
~20 cm of the free-hanging, wall-powered board, same-duration burst pairs
|
||||
appeared at the 50 ms repeat delay (10-10, 17-17, 16-16 ms; received
|
||||
+14..+24 dB over floor).
|
||||
- CONFIRMED: the laptop-connected "+37 dB at ~50 cm" reference overstates
|
||||
standalone radiated field -- the USB cable/host ground contributes
|
||||
counterpoise (and possibly conducted coupling into the shared-ground
|
||||
dongle). Radiated performance is dominated by antenna geometry:
|
||||
orientation, surroundings, and the LiPo pack's position relative to the
|
||||
antenna. Placement, not power, ruled the day.
|
||||
- **WITHDRAWN:** the claimed laptop-connected “+37 dB at ~50 cm”
|
||||
reference and the inferred USB-cable/counterpoise delta. The +37 dB
|
||||
number came from the repeat-borrowing clock-fit bug, so it cannot support
|
||||
a cable contribution estimate.
|
||||
- **NOT ESTABLISHED:** that the stock whip itself explains the weak
|
||||
standalone results. Antenna geometry unquestionably changes an
|
||||
over-the-air measurement, but the invalid SX1261-derived PA configuration is sufficient to
|
||||
explain a roughly 32 dB deficit and was not controlled in those runs.
|
||||
- CONFIRMED: TxDone (and therefore the LED double-blink) proves chip-level
|
||||
packet completion only. It is indistinguishable between a well-matched
|
||||
antenna and a shadowed/mismatched one -- §36's lesson extended to
|
||||
@@ -206,3 +226,34 @@ Full narrative with the evidence table: docs/FIELD_TEST_2026-09-01.md.
|
||||
singletons", 23-24 ms trains at ~30 ms spacing) are a neighbouring meter
|
||||
railing the dongle: rate invariant across firmware versions, reboots and
|
||||
power sources. Excluded from pair detection by fingerprint.
|
||||
|
||||
## T-mode + long-frame support (2026-09-02)
|
||||
|
||||
- CONFIRMED: T1 transmit works end to end. Synthetic T1 frames (3-of-6
|
||||
coded in software, 50 kHz TX deviation via lazy SetModulationParams
|
||||
swap, same 0x543D sync) were decoded by rtl_wmbus as valid `T1;...`
|
||||
telegrams, including a long L=140 frame (12 decode lines over 6
|
||||
airings, `captures/2026-09-02T-t1-verify`).
|
||||
- CONFIRMED: the T1 receive path decodes standard on-air chips. With no
|
||||
ambient T1 available (below), the proof is: our own T1 airings --
|
||||
independently accepted by rtl_wmbus -- were FSK-demodulated from raw IQ
|
||||
by a separate host tool, and the post-sync byte stream was fed through
|
||||
the unmodified firmware decode code (`wmbus_3of6_first_byte` ->
|
||||
`wmbus_3of6_decode` -> `wmbus_check_crc`): 5/5 CRC-OK with the exact
|
||||
transmitted content. A C1 burst pushed through the same path is
|
||||
correctly rejected at the first coded byte.
|
||||
- CONFIRMED (site): there is NO ambient T-mode traffic at this site --
|
||||
every ambient rtl_wmbus decode is C1. **Correction to earlier belief:**
|
||||
the large `rx_not_c1` bucket (44 % of sync matches overnight) is NOT
|
||||
T1 meters; it is C1 frames whose two NRZ mode bytes were corrupted by
|
||||
bit errors, plus false syncs from the deliberately short 8-bit preamble
|
||||
detector. The Techem meters here are C-mode.
|
||||
- Long frames: format B >128-byte CRC chunking and format A up to L=200
|
||||
are host-tested (sanitizers) and the L=200 format A frame was decoded
|
||||
CRC-OK over the air by rtl_wmbus.
|
||||
- T1 length cap: the fixed 255-byte capture holds ceil(total * 1.5) coded
|
||||
bytes, so T1 receive/repeat covers format A total <= 170 (L <= ~150).
|
||||
Long C1 covers total <= 253.
|
||||
- 3-of-6 tables verified against rtl-wmbus t1_c1_packet_decoder.h; codes
|
||||
are constant weight 3, so every single-chip corruption is detected
|
||||
(host test flips all 384 chip positions of a 32-byte payload).
|
||||
|
||||
Reference in New Issue
Block a user