FP wMBus User manual

Wireless M-bus Adapter
Wireless M-bus to wired M-bus Gateway
from FP-InovoLabs
Operating Manual

51.0077.0004.01 Rev.03 FP wMBusConf - Operating Manual
2
Operating Manual
© 2019 -2021 FP InovoLabs GmbH
www.inovolabs.com
Publication date: 23/02/2021
This manual is protected by copyright. Any further dissemination is only permitted with permission from the issuer. This also
applies to copies, microfilms, translations, and storing and processing in electronic systems.
Trade and brand names used in this manual are registered trademarks of the applicable companies even if they are not
designated as such explicitly.

51.0077.0004.01 Rev.03 FP wMBusConf - Operating Manual
3
Operating Manual
Table of contents
SAFETY INSTRUCTIONS ...................................................................................................... 4
1DESCRIPTION OF THE WMBUS ADAPTER............................................................. 5
2INSTALLATION AND START-UP ............................................................................... 6
2.1 Assembly and cabling ................................................................................................................ 6
2.2 Setting parameters and starting up....................................................................................... 7
3M-BUS TELEGRAMS FOR REGISTERED METERS .................................................. 8
4APPENDIX...................................................................................................................... 12
4.1 General technical data ............................................................................................................ 12
4.2 Housing........................................................................................................................................ 12
4.3 Power supply .............................................................................................................................. 12
4.4 Wireless M-bus interface......................................................................................................... 12
4.5 Wired M-bus interface ............................................................................................................. 13
4.6 USB stick supplied as standard ............................................................................................. 13
4.7 Bibliography............................................................................................................................... 13
4.8 Illustrations................................................................................................................................. 13
4.9 Version information.................................................................................................................. 14
4.10 EU Declaration of Conformity ................................................................................................. 15

51.0077.0004.01 Rev.03 FP wMBusConf - Operating Manual
4
Safety instructions Operating Manual
Safety instructions
Target group Electricians
This manual is intended exclusively for qualified electricians who are familiar with the safety standards
of electrical and automation engineering. Project planning, installation, start-up, maintenance and
testing of the devices may only be carried out by a recognised qualified electrician.
Any interventions in the hardware and software of our products, unless they are described in this or
other manuals, may only be carried out by our qualified personnel.
Intended use
Only use FP InovoLabs IoT gateways for the applications intended, as described in this manual. Ensure
that all specifications in the manual are observed. Unqualified interventions in the hardware or
software, or a failure to observe the warnings in this manual can cause serious personal injury or
damage to property. In this case, no liability is accepted and all warranty claims become invalid.
Safety-relevant regulations
When project planning, installing, starting up, maintaining and testing the devices, the safety and
accident prevention regulations applicable for the specific application must be observed.
This manual provides instructions that are important for proper and safe use of the device. The
individual instructions have the following meanings:
DANGER
Means that there is a risk to the user’s life if the corresponding preventive
measures are not taken.
CAUTION
Means that there is a risk of injury for the user if the corresponding preventive
measures are not taken.
ATTENTION
Means that there is a risk of damage to the device, the software or other material
assets if the corresponding preventive measures are not taken.
Please also refer to the further literature specified in section 4.7.

51.0077.0004.01 Rev.03 FP wMBusConf - Operating Manual
5
Operating Manual Description of the wMBus adapter
1Description of the wMBus adapter
The following illustration shows the FP wireless M-bus adapter.
Figure 1: FP wireless M-bus adapter
The FP wireless M-bus adapter (subsequently referred to as wMBus adapter) enables up to 63 wireless
M-bus meters to be integrated into your existing M-bus installation. To do this, the wMBus adapter
that conforms to OMS saves the data received from the meters and transfers the last response
telegram to the master when the M-bus is queried. The wMBus adapter receives devices with wireless
M-bus interfaces in accordance with the EN13757-4 standard, with 868 MHz in mode S1, T1 or C1.
The data can be received and decoded unencrypted or AES- encrypted according to mode 5 or 7.
Figure 2: Wireless M-bus system with wMBus adapter and FP S-ENGuard IoT gateway
Thanks to the configurable white list, several wMBus adapters can also be operated in an M-bus
network. Furthermore, the wMBus adapter can also be used as a fully-fledged wireless M-bus master
thanks to the mini USB interface, which enables reading out in conjunction with the MBSheet software
from Relay. The wMBus adapter can manage without an external power supply and is either supplied
by the M-bus (5 standard loads) or via the USB interface.
ATTENTION
Never connect an M-bus master and a USB cable simultaneously to the wMBus adapter!
Configuring the white list and the reception mode (C1, S1, T1, C1+T1) is essential. The free PC
software wMBusConf makes setting the parameters, the key and the white list very convenient.

51.0077.0004.01 Rev.03 FP wMBusConf - Operating Manual
6
Installation and start-up Operating Manual
2Installation and start-up
2.1 Assembly and cabling
The back of the wMBus adapter’s housing is screwed onto the wall with the terminals pointing
downwards. There are two wall brackets on the outside of the housing for this purpose.
The following drawings show the dimensions and the required dimensions for wall installation:
Figure 3: wMBus adapter dimensions
In order to wire the wMBus adapter, use a suitable flat-head screwdriver to open the cover’s housing
screws. There are three connections on the printed circuit board inside:
Figure 4: wMBus adapter connections
-(1): Two screw terminals to connect a wired M-bus master
-(2): Two screw terminals for transmission to further M-bus participants (optional)
-(3): USB mini port for setting parameters

51.0077.0004.01 Rev.03 FP wMBusConf - Operating Manual
7
Operating Manual Installation and start-up
Guide the cable to the M-bus master through one of the self-sealing cable feedthrough membranes in
the housing. You can connect a transmission cable to the next M-bus participant to the second M-bus
terminal.
You can use a small screwdriver to push through the membranes for flexible lines. In order to
guarantee protection class IP65, the opening must be significantly smaller than the cable’s outer
diameter. If you remove the plug-in terminals and guide the corresponding cable sufficiently through
the membrane, you can establish the connection conveniently outside the housing. Then pull the
cable back and plug the terminals into the corresponding strips on the circuit board.
ATTENTION
Ensure that the cables are not laid at the top left close to the antenna, as this could have a
negative effect on the radio signals.
Tension is relieved by looping the cable ties provided around the cable.
Once you have completed all assembly and parameter setting work, secure the device with an
adhesive seal on the housing cover’s screws to protect against manipulation.
2.2 Setting parameters and starting up
The wireless M-bus adapter’s parameters are set using the free Windows software wMBusConf, that is
available on the USB stick provided or on our website at www.inovolabs.com. To communicate with
the PC, you can either use the USB interface with a mini USB cable or use the M-bus interface directly
via a level converter.
Configuration is described in detail in the special manual for the wMBusConf software (see section
4.6).
ATTENTION
Note that the wireless M-bus adapter cannot be used until parameters have been set.

51.0077.0004.01 Rev.03 FP wMBusConf - Operating Manual
8
M-bus telegrams for registered meters Operating Manual
3M-bus telegrams for registered meters
The wMBus adapter simulates all meters registered in the while list. They can either be selected and
read out using their primary address (if assigned using the RelAirConf parameter setting software) or
their secondary address. The wMBus adapter always keeps the last wM-bus telegram received from
the registered meters to hand. If required, the telegram is decrypted and packed in a telegram that
conforms to M-bus.
Example (addressing directly via primary address 0x05):
REQ_UD2: 10 7B 05 80 16
Note:
If you wish to use primary addressing, you must use the RelAirConf to program a unique address for
each sender.
Example (addressing via secondary address 00h 11h 22h 33h ACh 48h B8h 07h):
Selection: 68 0B 0B 68 53 FD 52 00 11 22 33 AC 48 B8 07 BB 16
REQ_UD2: 10 7B FD 78 16
Note:
The secondary address is transferred directly from the wireless M-bus telegram that is received.
There are a total of 4 response telegrams that are described on the following pages:
a) Blank telegram
If no telegram has yet been received from the registered meter after registration in the white
list, the device returns a telegram without data records. The data records with RSSI (DR1) and
age (DR2) are optional and are only transmitted if these options are activated in the wMBus
adapter (possible as of firmware V1.5.0).
RSP_UD: M-bus blank telegram
Example
Layer
Byte no.
Name
Contents
Bytes [hex]
1
Start
Start byte
68h
Data Link Layer (DLL)
2
L-field
Telegram length
17h
3
L-field
Telegram length
17h
4
Start
Start byte
68h
5
C-field
SND_UD
08h
6
A-field
Primary address (meter)
00h
7
CI-field
72h (long header)
72h
Transport Layer (TPL)
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

51.0077.0004.01 Rev.03 FP wMBusConf - Operating Manual
9
Operating Manual M-bus telegrams for registered meters
RSP_UD: M-bus blank telegram
Example
Layer
Byte no.
Name
Contents
Bytes [hex]
19
Config.
Configuration field (e.g. encryption)
00h
20
DR1
DIF (integer 8Bit)
01h
Application Layer (APL)
21
DR1
VIF (linear extension)
FDh
22
DR1
VIFE (RSSI / reception level dBm)
71h
23
DR1
Value
00h
24
DR2
DIF (integer 16Bit)
02h
25
DR2
VIF (age / currentness duration)
74h
26
DR2
LSB value (900s)
84h
27
DR2
MSB value
03h
Checksum
??h
DLL
Stop
Stop byte
16h
b) Telegram with wM-bus container
If the telegram cannot be decrypted despite a registered or due to a missing AES key, the
telegram is packed into a wM-bus container data record and made available. The data records
with RSSI (DR2) and age (DR3) are optional and are only transmitted if these options are
activated in the wMBus adapter (possible as of firmware V1.5.0).
RSP_UD:
Example
Layer
Byte no.
Name
Contents
Bytes [hex]
1
Start
Start byte
68h
Data Link Layer (DLL)
2
L-field
Telegram length
??h
3
L-field
Telegram length
??h
4
Start
Start byte
68h
5
C-field
SND_UD
08h
6
A-field
Primary address (meter)
00h
7
CI-field
72h (long header)
72h
Transport Layer (TPL)
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
DR1
DIF (variable length)
0Dh
Application Layer (APL)
21
DR1
VIF (linear extension)
FDh
22
DR1
VIFE (Wireless M-bus-protocol data container)
3Bh
23
DR1
LVAR
32h
24
DR1
Telegram contents as of the L-field
8Ch
…
…
…
DR1
Last byte in the telegram
06

51.0077.0004.01 Rev.03 FP wMBusConf - Operating Manual
10
M-bus telegrams for registered meters Operating Manual
RSP_UD:
Example
Layer
Byte no.
Name
Contents
Bytes [hex]
DR2
DIF (integer 8Bit)
01h
DR2
VIF (linear extension)
FDh
DR2
VIFE (RSSI / reception level dBm)
71h
DR2
Value (-96dBm)
A0h
DR3
DIF (integer 16Bit)
02h
DR3
VIF (age / currentness duration)
74h
DR3
LSB value (900s)
84h
DR3
MSB value
03h
Checksum
??h
DLL
Stop
Stop byte
16h
c) Decrypted telegram
If a registered meter sends an unencrypted telegram or the correct AES128 key is stored, the
data records contained in the telegram are simply copied into the telegram. However, all
clearly identifiable idle fillers (2Fh) are removed. The data records with RSSI (DR2) and age
(DR3) are optional and are only transmitted if these options are activated in the wMBus
adapter (possible as of firmware V1.5.0).
RSP_UD:
Example
Layer
Byte no.
Name
Contents
Bytes [hex]
1
Start
Start byte
68h
Data Link Layer (DLL)
2
L-field
Telegram length (from the C-field checksum)
1Dh
3
L-field
Telegram length (from the C-field checksum)
1Dh
4
Start
Start byte
68h
5
C-field
SND_UD
08h
6
A-field
Primary address (meter)
00h
7
CI-field
72h (long header)
72h
Transport Layer (TPL)
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
DR1
DIF (BCD 8 characters)
0Ch
Application Layer (APL)
21
DR1
VIF (Volume [l])
13h
22
DR1
LSB value
15h
23
DR1
Value
08h
24
DR1
Value (00000815 [l])
00h
25
DR1
MSB value
00h
26
DR2
DIF (integer 8Bit)
01h

51.0077.0004.01 Rev.03 FP wMBusConf - Operating Manual
11
Operating Manual M-bus telegrams for registered meters
RSP_UD:
Example
Layer
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
DLL
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
Layer
Byte no
Name
Contents
Bytes [hex]
1
Start
Start byte
68h
Data Link Layer (DLL)
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
Transport Layer (TPL)
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
APL
21
Checksum
??h
DLL
22
Stop
Stop byte
16h

51.0077.0004.01 Rev.03 FP wMBusConf - Operating Manual
12
Appendix Operating Manual
4Appendix
4.1 General technical data
Operating temperature
0 - 40 °C (32 °F to 104 °F)
Storage temperature
-20 - 70 °C (-4 °F to 158 °F)
Humidity
10 % - 70% (non-condensing)
Cable terminals
Rigid: 0.14 - 1.5 mm2(AWG 26 to AWG 16) /
flexible: 0.14 - 1.0 mm
2
(AWG 26 to AWG 18)
4.2 Housing
Installation
Wall installation
Material
Polystyrene, light grey
W x L x H
93 × 93 x 55 mm (3.66" × 3.66" × 2.17")
Protection class
IP54; IP65 possible if the cable is fed through carefully
Antenna
Internal
4.3 Power supply
With an M-bus
connection
Supply from M-bus with max. 5 standard loads (current: <= 7.5 mA)
With a USB connection
Supply from the USB (current <= 90 mA)
4.4 Wireless M-bus interface
Standard
EN13757-4 and EN13757-3, OMS-compatible
Reception modes
S1, T1, C1, T1+C1 / unidirectional / frame format A and B
Encryption
Mode 0 (unencrypted, mode 5 or mode 7
Radio scan list
Up to 488 devices
White list
Up to 63 devices can be configured

51.0077.0004.01 Rev.03 FP wMBusConf - Operating Manual
13
Operating Manual Appendix
4.5 Wired M-bus interface
Standard
EN13757-2 and EN13757-3
Current
consumption
5 standard loads; max 7.5 mA
Addressing
- Primary addressing: by default = 0, can be adjusted using the wMBusConf
software
- Secondary addressing: ID = 2xxxxxxx, with xxxxxxx = serial number
4.6 USB stick supplied as standard
A USB stick is enclosed with the wMBus adapter. Additional software and manuals are saved on it.
USB stick contents
Directory
Meaning
USB
FTDI driver software for configuration via the USB interface
wMBusConf
wMBusConf configurations software for Windows
Documentation
FP-wMBusAdapter-operating-manual_Rev1.0.pdf (this manual)
Documentation
FP-wMBusConf-operating-manual_Rev1.0.pdf (wMBusConf software)
4.7 Bibliography
[1]
FP S-OTGuard Hardware Manual: “510071900601_XX_FP_S-OTGuard_HW-Manual_EN.pdf”.
[2]
FP-TiXML-Reference (EN): “510058920001_XX_FP-TiXML-Reference_EN.pdf”.
[3]
FP PLC-TiXML Manual: “510058920101_XX_FP-PLC-TiXML-Manual_EN.pdf”.
[4]
FP SCADA / GLT Manual “510058920601_XX_FP-SCADA-GLT_EN.pdf”.
[5]
FP OpenVPN Toolkit Quick Guide “510058921201_XX_FP-OpenVPN-Toolkit_Docu_EN.pdf”.
[6]
FP XP-Modules Hardware Manual “510072900101_XX_FP-MAN-XP_EN.pdf”.
xx = Revision of the document, starting with 00
Further manuals and data sheets are available on our website at:
https://www.inovolabs.com/infobereich/downloads/handbucher-datenblatter
4.8 Illustrations
Figure 1: FP wireless M-bus adapter.......................................................................................................... 5
Figure 2: Wireless M-bus system with wMBus adapter and FP S-ENGuard IoT gateway ......................... 5
Figure 3: wMBus adapter dimensions........................................................................................................ 6
Figure 4: wMBus adapter connections ...................................................................................................... 6

51.0077.0004.01 Rev.03 FP wMBusConf - Operating Manual
14
Appendix Operating Manual
4.9 Version information
Version
Date
Author
Changes
Person responsible
03
23/02/2021
First English Issue
IVH
02
27/10/2020
Code number, layout
Ortmann
01
16/12/2019
Henze
First issue
Henze

51.0077.0004.01 Rev.03 FP wMBusConf - Operating Manual
15
Operating Manual Appendix
4.10 EU Declaration of Conformity