hil: RF-only standalone repeater verification (no serial required)
This commit is contained in:
@@ -148,3 +148,24 @@ Differences are behavioural, not cosmetic:
|
||||
timing is never perturbed by debug serial traffic. Build directories are
|
||||
separate (`build-test`, `build-debug`) so profiles cannot silently reuse a
|
||||
stale sdkconfig.
|
||||
|
||||
## Verifying a standalone repeater (no serial connection)
|
||||
|
||||
When the DUT runs on external power with no USB host, firmware telemetry is
|
||||
unavailable and RF is the only evidence. Record IQ once, then derive both
|
||||
decodes and RF-level repeat pairs from the same samples:
|
||||
|
||||
```
|
||||
timeout 80 rtl_sdr -f 868950000 -s 1600000 -g 42.1 -n 96000000 iq.raw
|
||||
cat iq.raw | rtl_wmbus -f > decodes.log
|
||||
./result-py/bin/python3 hil/verify_standalone.py --iq iq.raw --decodes decodes.log
|
||||
```
|
||||
|
||||
Reports decoded repeats (same payload twice) and RF-level repeat pairs
|
||||
(burst pairs of matching duration inside the delay window). The latter
|
||||
matters because our transmission usually overloads the dongle and fails CRC
|
||||
even though the RF is correct.
|
||||
|
||||
Note: only one process can hold the RTL-SDR. If another tool (e.g. an
|
||||
oms-tui / wmbusmeters pipeline) is running, `rtl_sdr` fails with
|
||||
`usb_claim_interface error -6` and it must be stopped first.
|
||||
|
||||
Reference in New Issue
Block a user