51.0077.0004.01 Rev.03
FP wMBusConf - Operating Manual
11
Operating Manual
M-bus telegrams for registered meters
RSP_UD:
Example
Laye
r
Byte no. Name
Contents
Bytes [hex]
27
DR2
VIF (linear extension)
FDh
28
DR2
VIFE (RSSI / reception level dBm)
71h
29
DR2
Value (-96dBm)
A0h
30
DR3
DIF (integer 16Bit)
02h
31
DR3
VIF (age / currentness duration)
74h
32
DR3
LSB value (900s)
84h
33
DR3
MSB value
03h
Checksum
??h
DL
L
Stop
Stop byte
16h
d)
Telegram application error
If the wMBus adapter cannot decrypt a wM-bus telegram that was received, the entire
telegram is packed in a wM-bus container. The wM-bus container can have a maximum length
of 191 bytes according to standard “EN13757-3-2018”. For longer wM-bus telegrams that do
not fit into the container, the wMBus adapter therefore sends an application error:
RSP_UD:
Example
Laye
r
Byte no Name
Contents
Bytes [hex]
1
Start
Start byte
68h
Da
ta
L
in
k L
ay
er
(D
LL
)
2
L-field
Telegram length (from the C-field checksum)
10h
3
L-field
Telegram length (from the C-field checksum)
10h
4
Start
Start byte
68h
5
C-field
RSP_UD
08h
6
A-field
Primary address (meter)
00h
7
CI-field
Application error from the device (long)
6Fh
Tr
an
sp
ort
L
ay
er (
TP
L)
8
ID-field
LSB identification number
00h
9
ID-field
Identification number
11h
10
ID-field
Identification number (meter ID)
22h
11
ID-field
MSB identification number
33h
12
Manuf.
LSB manufacturer code (code = REL)
ACh
13
Manuf.
MSB manufacturer code
48h
14
Version
Version
B8h
15
Type
Device type
07h
16
Acc
Access number
01h
17
Status
M-bus status (e.g. error, alarm)
00h
18
Config.
Configuration field (e.g. encryption)
00h
19
Config.
Configuration field (e.g. encryption)
00h
20
Error
Buffer overrun
02h
AP
L
21
Checksum
??h
DL
L
22
Stop
Stop byte
16h