56 lines
3.0 KiB
Markdown
56 lines
3.0 KiB
Markdown
# Open Questions
|
|
|
|
- Optimal SX1262 RX bandwidth for C1: 234.3 kHz chosen (signal ~190 kHz
|
|
incl. tolerances); would 156 kHz improve sensitivity without clipping
|
|
drifted meters?
|
|
- Preamble detector length: 8 bits chosen for sensitivity; false-sync rate
|
|
in the field? (false syncs cost ~20 ms deaf time each at fixed-255 RX).
|
|
- CLOSED: Does the KCT8103L LNA help or hurt with strong 868 MHz
|
|
interferers? -> It helps decisively. CSD low costs ~41 dB and reduces
|
|
visible meters from 18 to 1; no overload degradation observed
|
|
(docs/RF_FRONTEND_TESTS.md).
|
|
- CLOSED: historical RX-unavailable interval during retransmit was
|
|
~225.7 ms median at a 200 ms delay: 12.2 ms fixed-255 RX tail + 200 ms
|
|
scheduling delay + 13.4 ms TX operation latency. The representative
|
|
packet's computed RF occupancy was 8.8 ms (docs/TIMING.md).
|
|
- Can the SX1262 re-arm RX fast enough to catch a meter's immediate
|
|
follow-up telegram after our TX?
|
|
- Exact production repeater framing/hop requirements (EN 13757-5).
|
|
- Regulatory duty-cycle budget for a production repeater at 868.95 MHz.
|
|
- Modulation shaping for TX: none vs GFSK BT=0.5 — which does rtl-wmbus /
|
|
real receivers prefer? (TX currently unshaped 2-FSK.)
|
|
- Why does the R820T degrade and eventually die during streaming? Three
|
|
failure modes are characterised in docs/HARDWARE.md; `usbreset` recovers
|
|
the first two, the third needs a physical replug. Root cause unknown
|
|
(thermal suspected). The `rtl_test -t` theory was DISPROVEN.
|
|
- Can the SX1262 RX be stopped early (poll GetRxBufferStatus after
|
|
SyncWordValid) to remove the ~12 ms fixed-capture tail?
|
|
|
|
## Standards detail needing an authoritative answer
|
|
|
|
- Format A frame length for `L = 10 (mod 16)`. Two mature open-source
|
|
implementations disagree in this corner:
|
|
- rtl-wmbus computes `1 + L + 2*((L-10+15)/16 + 1)` CRC pairs, which for
|
|
L = 10, 26, 42, ... requires a 17-byte block;
|
|
- wmbusmeters does not predict the length at all; it walks greedy 16-byte
|
|
blocks and accepts a final block of 1..16 bytes.
|
|
This firmware follows the wmbusmeters decomposition
|
|
(`1 + L + 2*(1 + ceil((L-9)/16))`) because it is self-consistent with the
|
|
CRC walk actually used. No valid frame with such an L was ever captured
|
|
at this site, so the question is unresolved empirically -- it needs the
|
|
EN 13757-4 text, or a meter that emits one. Until then, a real meter using
|
|
those lengths is an interoperability risk worth a targeted test.
|
|
|
|
## Duty ledger event-capacity bug (closed 2026-09-01, loc3)
|
|
|
|
The old `DUTY_RING=384` implementation saturated at about 2.7 s of history
|
|
at ~7 ms per event, below the 3.6 s hourly budget. It silently forgot old
|
|
events while they were still inside the hour; this was observed during the
|
|
beacon soak.
|
|
|
|
Fixed: 61 keyed minute buckets accumulate every successful transmission.
|
|
The rolling-hour query includes every bucket overlapping the window,
|
|
including the oldest partial minute in full (safe over-count). Host tests
|
|
cover 10,000 events in one bucket, all 61 overlapping minutes, exact expiry,
|
|
invalid timestamps, and zero-length records.
|