Files

6.2 KiB

Standards Gaps — experimental shortcuts vs EN 13757 / OMS

This firmware is an RF feasibility experiment, NOT a standards-compliant repeater. Known deviations:

# Experimental behavior Standard requirement
1 Marks supported OMS uplinks with H=1 and repairs the affected CRC; unsupported layouts are skipped Full repeater behavior still requires installation handling and timing compliance; see implementation notes below
2 Fixed repeat delay 20-1000 ms (persisted; 500 ms in current field testing) OMS repeaters use randomized delays in the seconds range to avoid collisions
3 Repeats CRC-valid C1/T1 uplinks passing C-field, hop/access-bit and supported-header checks (optional dev whitelist) Real repeaters filter by installation list
4 Rolling-hour duty-cycle guard, default 0.1 % (1000 ppm), suppresses repeats over budget and counts them (tx_suppressed_duty) A production repeater needs proper duty-cycle management, or LBT+AFA, plus per-sub-band awareness
5 H=1/R=1 frames are suppressed; a 2.5 s hash ring also suppresses duplicate originals Full installation and duplicate-management policy still needs review
6 No AES, no decryption, payload treated as opaque OMS security profiles apply to end devices; a transparent repeater may pass ciphertext, but production behavior needs review
7 C1 and T1 both received and repeated in their native mode (3-of-6 codec in software, per-TX deviation swap). S-mode out of scope A production repeater still needs reviewed mode policy (e.g. never re-air T1 as C1)
8 Format B >128 bytes and format A up to L=200 host-tested and verified on air (2026-09-02) --

None of these shortcuts may be carried into the production Solenos/Gebos gateway without explicit review.

Scope decision (2026-09-02): S-mode support is explicitly OUT OF SCOPE -- no S-mode traffic observed at either test site. T-mode receive/repeat and long-frame support were implemented and RF-verified 2026-09-02. Site finding from that verification: this site has NO ambient T-mode traffic either (all ambient decodes are C1); the firmware's historical rx_not_c1 bucket is mode-byte-corrupted C1 plus false syncs, not T1 meters.

Persistence exception (2026-09-02): duty_budget_ppm and repeat_delay_ms survive power cycles (NVS), because battery-standalone testing needs settings that outlive reboots. A persisted duty_budget_ppm of 0 disables the duty guard indefinitely -- the device transmits over the ERC/REC 70-03 budget whenever traffic exceeds it, until set duty_budget_ppm 1000 is sent again. The OLED config page shows the effective values (DUTYCAP, DELAY); boot logs cfg_restore. Re-enable the guard after every guard-off test session.

OMS hop marking (2026-09-09)

wmbus_mark_repeated() in firmware/main/wmbus.c operates on a CRC-validated raw format A/B frame, before C1 framing or T1 3-of-6 encoding. It accepts only C-fields 44 (SND_NR) and 46 (SND_IR), with H=0 and R=0:

  • ELL CI 8C or 8E: set bit 4 of the Communication Control byte. ELL takes precedence over any inner Transport Layer configuration.
  • Without ELL: an explicitly recognized short/long uplink TPL header in security mode 0 or 5 uses bit 0 of the Configuration field.
  • Already-repeated/access-marked frames, truncated headers, and unsupported layouts are left unchanged and not transmitted. Unsupported includes headerless CI 78, ELL 8D/8F, and AFL without a supported outer ELL. There is no bit-exact fallback.

Only H and its enclosing block's CRC change. The helper maps logical header offsets across raw CRC boundaries; it neither decrypts nor copies the payload. Frame length, meter identity, access number and ciphertext remain unchanged. The original RX hash remains the RX/TX log correlation key; TX raw contains the actual modified physical payload. Verbose mode reports policy rejection as tx_suppressed with reason hop_policy.

H identifies a repeated copy, not a repeater ID, and does not enable multihop. Synthetic test_tx, test_tx_t1, beacons and test_burst remain unchanged PHY probes, not examples of received-frame repeater policy. Existing delay, whitelist and duty-cycle settings are unchanged.

Reference: OMS Volume 2, issue 5.0.1, sections 5.2.2.2, 5.2.5.2 and 7.2.4. Setting H alone does not establish full OMS compliance. The new marking path has not yet been verified over RF.

Duty cycle — measured, and why it matters

868.95 MHz falls in the 868.7-869.2 MHz sub-band, which ERC/REC 70-03 (annex h1.6) limits to 25 mW e.r.p. with <= 0.1 % duty cycle, unless the device implements LBT+AFA.

Absolute e.r.p. from the SX1262 plus KCT8103L and antenna has not been calibrated. The default -9 dBm SetTxParams value is the minimum chip setting, not proof of compliance with the 25 mW e.r.p. cap.

Current computed occupancy for the historical bench traffic:

RF occupancy per repeat : ~5.8-9.8 ms (8.8 ms for 102 radio bytes)
observed repeat rate     : ~5-6 repeats/min when repeating every valid telegram
resulting duty cycle     : roughly 0.07-0.09 % at the representative length

An older report used 10.4-14.6 ms TX-operation latency (median 13.4 ms) as if it were RF airtime and consequently reported 0.11-0.13 %. That was a safe overestimate but not channel occupancy. Even the corrected site rate is close to 0.1%; traffic variation, longer frames, a denser environment, or adding T-mode can exceed the budget.

Consequences for the production gateway:

  • Duty-cycle budgeting is a first-class requirement, not an afterthought. Repeating "every telegram we hear" is not a viable policy.
  • Either implement LBT+AFA (which lifts the duty-cycle restriction in this sub-band) or filter by installation list and/or rate-limit per meter.
  • Frame length matters: airtime scales with it, so long encrypted telegrams cost roughly 40 % more budget than short ones.

The experimental firmware therefore enforces a rolling-hour airtime budget (set duty_budget_ppm N, default 1000 ppm = 0.1 %, 0 disables) purely so unattended multi-hour runs cannot drift into non-compliance. This guard is an experiment-safety measure and is NOT the OMS/EN 13757-5 repeater behaviour a product would need.