Files
heltec-repeater/docs/STANDARDS_GAPS.md
T

1.4 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 Repeats the raw telegram bit-exact, including hop-related fields EN 13757-5 repeaters must manage the hop counter / C-field semantics so telegrams are not repeated endlessly
2 Fixed development repeat delay 20-200 ms (default 50 ms) OMS repeaters use randomized delays in the seconds range to avoid collisions
3 Repeats every CRC-valid C1 telegram (optional dev whitelist) Real repeaters filter by installation list
4 No duty-cycle accounting EU 868.95 MHz band has duty-cycle limits (1% for 868.7-869.2 sub-band per ERC 70-03); a production repeater must budget its TX time
5 Duplicate suppression is a 2.5 s hash ring Standard requires proper duplicate/loop protection semantics
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 T1 telegrams are detected (shared 0x543D sync) but dropped A combined C/T repeater would need 3-of-6 decode/encode
8 Format B frames >128 bytes CRC-checked but rare path untested --

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