Relay RelAir R2M HOME User Manual page 12

c) Decrypted Telegram
In the case that a registered meter sends an unencrypted telegram or the correct AES128 key is
stored, the data records contained in the wireless telegram are simply copied to the wired
M-Bus telegram. However, all uniquely identifiable idle fillers (2Fh) are removed:
Byte No. Name
1 Start
2 L-Field
3 L-Field
4 Start
5 C-Field
6 A-Field
7 CI-Field
8 ID-Field
9 ID-Field
10 ID-Field
11 ID-Field
12 Manufacturer
13 Manufacturer
14 Version
15 Type
16 Acc.
17 State
18 Config.
19 Config.
20 DR1
21 DR1
22 DR1
23 DR1
24 DR1
25 DR1
Checksum
Stop
Telegram – RSP_UD of a registered meter
User Manual RelAir R2M · 07/2018 · VERSION 1.1
RSP_UD:
Content
Start-Byte
Telegram length
(from C-Field to checksum)
Telegram length
(from C-Field to checksum)
Start-Byte
SND_UD
Primary address (meter)
72h (long Header)
Identification number LSB
Identification number
Identification number (meter ID)
Identification number MSB
Manufacturer code LSB (Code = REL)
Manufacturer code MSB
Version
Device type
Access number
M-Bus State (e.g. error, alarm)
Configuration field (e.g. encryption)
Configuration field (e.g. encryption)
DIF (BCD 8 digits)
VIF (volume [l])
Value LSB
Value
Value (00000815 [l])
Value MSB
Stop-Byte
RELAIR R2M
Example
Bytes [hex]
68h
15h
15h
68h
08h
00h
72h
00h
11h
22h
33h
ACh
48h
B8h
07h
01h
00h
00h
00h
0Ch
13h
15h
08h
00h
00h
h
16h
12