Relay RelAir R2M HOME User Manual page 11

b) Telegram with wM-Bus container
If the telegram cannot be decrypted despite a registered or because of a missing AES key, the
telegram is packed into a wM-Bus container data record and made available:
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 Manufacturer code LSB (Code = REL)
13 Manufacturer Manufacturer code MSB
14 Version
15 Type
16 Acc.
17 State
18 Config.
19 Config.
20 DR1
21 DR1
22 DR1
23 DR1
24 DR1
...
DR1
Checksum
Stopp
Telegram – wM-Bus container data record
User Manual RelAir R2M · 07/2018 · VERSION 1.1
RSP_UD:
Content
Start-Byte
Telegram length
Telegram length
Start-Byte
SND_UD
Primary address (meter)
72h (long Header)
Identification number LSB
Identification number
Identification number (meter ID)
Identification number MSB
Version
Device type
Access number
M-Bus State (e.g. error, alarm)
Configuration field (e.g. encryption)
Configuration field (e.g. encryption)
DIF (variable length)
VIF (linear extension)
VIFE (data container for the Wireless-
M-Bus protocol)
LVAR
Telegram content starting from L-field
...
Last byte of the telegram
Stop-Byte
RELAIR R2M
Example
Bytes [hex]
68h
45h
45h
68h
08h
00h
72h
00h
11h
22h
33h
ACh
48h
B8h
07h
01h
00h
00h
00h
0Dh
FDh
3Bh
32h
8Ch
...
06
h
16h
11