HMS Networks intesis INBACMEB0200100 User manual

M-BUS to BACnet/IP Server Gateway
USER MANUAL
Version 1.0.0
Publicaon date 2023-06-08
ENGLISH

Copyright © 2023 Intesis
Disclaimer
The informaon in this document is for informaonal purposes only. Please inform HMS Networks of any
inaccuracies or omissions found in this document. HMS Networks disclaims any responsibility or liability for any
errors that may appear in this document.
HMS Networks reserves the right to modify its products in line with its policy of connuous product
development. The informaon in this document shall therefore not be construed as a commitment on the
part of HMS Networks and is subject to change without noce. HMS Networks makes no commitment to update
or keep current the informaon in this document.
The data, examples and illustraons found in this document are included for illustrave purposes and are only
intended to help improve understanding of the funconality and handling of the product. In view of the wide
range of possible applicaons of the product, and because of the many variables and requirements associated
with any parcular implementaon, HMS Networks cannot assume responsibility or liability for actual use
based on the data, examples or illustraons included in this document nor for any damages incurred during
installaon of the product. Those responsible for the use of the product must acquire sucient knowledge in
order to ensure that the product is used correctly in their specic applicaon and that the applicaon meets all
performance and safety requirements including any applicable laws, regulaons, codes and standards. Further,
HMS Networks will under no circumstances assume liability or responsibility for any problems that may arise as
a result from the use of undocumented features or funconal side eects found outside the documented scope
of the product. The eects caused by any direct or indirect use of such aspects of the product are undened and
may include e.g. compability issues and stability issues.

Table of Contents
1. Descripon and Order Codes ..................................................................................................... 1
2. Gateway Capacity .................................................................................................................... 2
3. General Informaon ................................................................................................................ 3
3.1. Intended Use of the User Manual ........................................................................................ 3
3.2. General Safety Informaon ................................................................................................ 3
3.3. Admonion Messages and Symbols ..................................................................................... 3
4. Overview ............................................................................................................................... 5
4.1. Inside the Package ............................................................................................................ 5
4.2. Gateway Main Features ..................................................................................................... 5
4.3. Gateway General Funconality ........................................................................................... 6
5. Hardware ............................................................................................................................... 7
5.1. Mounng ........................................................................................................................ 7
5.2. Connecon ..................................................................................................................... 8
5.2.1. Gateway Connectors .................................................................................................. 8
5.2.2. Common Connecons ............................................................................................... 10
5.2.2.1. Connecng the Gateway to the Power Supply ........................................................ 10
5.2.3. Connecon Procedure for M-Bus ................................................................................ 10
5.2.4. Connecon Procedure for BACnet/IP ........................................................................... 11
5.3. Technical Specicaons .................................................................................................... 12
5.4. Dimensions .................................................................................................................... 13
6. M-Bus System ........................................................................................................................ 14
6.1. General Descripon ......................................................................................................... 14
6.2. M-Bus Interface .............................................................................................................. 14
6.3. M-Bus Signals ................................................................................................................. 14
7. BACnet System ....................................................................................................................... 15
7.1. General Descripon ......................................................................................................... 15
7.2. BACnet Server ................................................................................................................. 16
7.2.1. Descripon ............................................................................................................. 16
7.2.2. BACnet/IP ............................................................................................................... 17
8. Setup Process with the Conguraon Tool .................................................................................. 18
8.1. Prerequisites .................................................................................................................. 18
8.2. Intesis MAPS Conguraon and Monitoring Tool ................................................................... 18
8.2.1. Introducon ............................................................................................................ 18
8.2.2. Create a New Project from a Template ......................................................................... 19
8.2.3. Main Menu Overview ............................................................................................... 20
8.2.4. Connecon Tab ....................................................................................................... 20
8.2.5. Conguraon Tab ..................................................................................................... 20
8.2.6. Signals Tab .............................................................................................................. 21
8.2.7. Receive/Send Tab ..................................................................................................... 21
8.2.8. Diagnosc Tab ......................................................................................................... 22
M-BUS to BACnet/IP Server Gateway
USER MANUAL Version 1.0.0

1. Descripon and Order Codes
INBACMEBxxx0100 Protocol Translator Gateway
M-Bus to BACnet/IP Server Gateway
ORDER CODE LEGACY ORDER CODE
INBACMEB0200100 IBBACMEB0200100
INBACMEB0500100 IBBACMEB0500100
NOTICE
The order code may vary depending on the product seller and the buyer's locaon.
Descripon and Order Codes M-BUS to BACnet/IP Server Gateway
USER MANUAL Version 1.0.0 Page 1 of 22

2. Gateway Capacity
Element INBACMEB0200100 INBACMEB0500100 Notes
Type of BACnet devices IP Communicaon with BACnet/IP.
Number of BACnet objects 500 1250 Maximum number of points that can be dened in the virtual
BACnet device inside the gateway.
Number of BACnet subscripon
(COV) requests 1000 2500 Maximum number of BACnet subscripon (COV) requests accepted by the gateway.
Type of M-Bus devices M-Bus EIA-485 slave devices Those supporng the M-Bus EN-1434-3 Standard.
Communicaon over EIA-485.
Number of M-Bus slave devices 20 50 Number of M-Bus slave devices supported by the gateway.
Number of M-Bus signals 500 1250 Number of M-Bus signals (readings in the meters) that can be
read from the gateway.
M-BUS to BACnet/IP Server Gateway Gateway Capacity
Page 2 of 22 USER MANUAL Version 1.0.0

3. General Informaon
3.1. Intended Use of the User Manual
This manual contains the main features of this Intesis gateway and the instrucons for its appropriate
installaon, conguraon, and operaon.
The contents of this manual should be brought to the aenon of any person who installs, congures, or
operates this gateway or any associated equipment.
Keep this manual for future reference during the installaon, conguraon, and operaon.
3.2. General Safety Informaon
IMPORTANT
Follow these instrucons carefully. Improper work may seriously harm your health and damage the
gateway and/or any other equipment connected to it.
Only technical personnel, following these instrucons and the country legislaon for installing electrical
equipment, can install and manipulate this gateway.
Install this gateway indoors, in a restricted access locaon, avoiding exposure to direct solar radiaon, water, high
relave humidity, or dust.
All wires (for communicaon and power supply, if needed) must only be connected to networks with indoor
wiring. All communicaon ports are considered for indoor use and must only be connected to SELV circuits.
Disconnect all systems from their power source before manipulang and connecng them to the gateway.
Use SELV-rated NEC class 2 or limited power source (LPS) power supply.
Supply always a correct voltage to power the gateway. See Technical Specicaons (page 12).
Respect the expected polarity of power and communicaon cables when connecng them to the gateway.
3.3. Admonion Messages and Symbols
DANGER
Instrucons that must be followed to avoid an imminently hazardous situaon that, if not avoided,
will result in death or severe injury.
WARNING
Instrucons that must be followed to avoid a potenally hazardous situaon that, if not avoided,
could result in death or severe injury.
CAUTION
Instrucon that must be followed to avoid a potenally hazardous situaon that, if not avoided,
could result in minor or moderate injury.
IMPORTANT
Instrucon that must be followed to avoid a risk of reduced funconality and/or damage to the
equipment or to avoid a network security risk.
General Informaon M-BUS to BACnet/IP Server Gateway
USER MANUAL Version 1.0.0 Page 3 of 22

NOTE
Addional informaon which may facilitate installaon and/or operaon.
TIP
Helpful advice and suggesons.
NOTICE
Remarkable Informaon.
M-BUS to BACnet/IP Server Gateway Admonion Messages and Symbols
Page 4 of 22 USER MANUAL Version 1.0.0

4. Overview
This Intesis® gateway allows to integrate M-Bus devices into BACnet/IP systems easily.
The aim of this integraon is to make M-Bus devices accessible from a BACnet control system or device to get the
same behavior as if the M-Bus device was part of the BACnet installaon.
For this, the Intesis gateway acts as a BACnet/IP client device in its BACnet interface, allowing it to read/write
points from the BACnet Server device(s). From the M-Bus point of view, the gateway acts as an M-Bus level
converter and Master device (EN-1434-3). The gateway performs the readings of the M-Bus slave device(s) by
automac connuous polling, or on demand (to reduce baery consumpon).
The gateway conguraon is carried out through the Intesis MAPS conguraon tool.
Figure 1. Integraon of M-Bus devices into BACnet/IP installaons
IMPORTANT
This document assumes that the user is familiar with BACnet and M-Bus technologies and their
technical terms.
4.1. Inside the Package
Items included:
• Intesis INBACMEBxxx0100 Protocol Translator Gateway
•Installaon sheet
4.2. Gateway Main Features
• Embedded level converter. Direct connecon to M-Bus devices with no extra hardware required.
• Scan funcon: detect M-Bus devices and their available registers automacally.
• Import/Export of M-Bus device templates.
• Baud rate congurable within the M-Bus allowed range (300 to 9600 bps. The devices are normally congured
at 2400 bps).
•Specic parameters and meouts are available to maximize compability with any possible peculiarity
between dierent meter manufacturers.
• Availability of variables for communicaon errors, both at meter and general level, helping you to know if the
communicaon with one or more meters has failed.
• Flexible conguraon using the Intesis MAPS conguraon tool.
Overview M-BUS to BACnet/IP Server Gateway
USER MANUAL Version 1.0.0 Page 5 of 22

4.3. Gateway General Funconality
This gateway acts as a server on its BACnet side and as a master on its M-Bus interface, thus allowing the
integraon of M-Bus devices into a BACnet system.
The gateway is connuously polling the devices (together or individually), storing in its memory the current
status of every signal you want to track, and serving this data to the installaon when requested. This connuous
polling can be acvated/deacvated through a BACnet signal. It is also possible to congure the gateway to make
a single polling of the meters (refresh of readings) at start up.
Primary or secondary addressing is allowed for M-Bus devices. When a signal status changes, the gateway sends
a write telegram to the installaon, waits for the response, and performs the corresponding acon.
This acon can be: force a polling of a specic M-Bus device or force a polling of all M-Bus devices. This can also
be forced from the BACnet side at any me by wring a 1 in the corresponding binary point specially enabled for
this purpose.
Other M-Bus informaon accessible from BACnet, using specic points of the gateway, is:
• Bus acvity: Indicates if meters are currently being polled or polling is on standby.
• M-Bus status of every meter: This is sent by the own meter with every poll and indicates the internal status,
which is manufacturer specic in every case.
A lack of response from a signal acvates a communicaon error, allowing you to know which signal from which
M-Bus device is not correctly working. There is also a general communicaon error available that will be acve
whenever the communicaon with one or more M-Bus meters has failed.
M-BUS to BACnet/IP Server Gateway Gateway General Funconality
Page 6 of 22 USER MANUAL Version 1.0.0

5. Hardware
5.1. Mounng
IMPORTANT
Before mounng, please ensure that the chosen installaon place preserves the gateway from direct
solar radiaon, water, high relave humidity, or dust.
NOTE
Mount the gateway on a wall or over a DIN rail. DIN rail mounng inside a grounded metallic cabinet
is recommended.
IMPORTANT
Ensure the gateway has sucient clearances for all connecons when mounted. See
Dimensions (page 13).
Wall mount
1. Press the rear panel clips unl you hear a click.
2. Use the clip holes to screw the gateway to the wall.
3. Make sure the gateway is rmly xed.
DIN rail Mount
Keep the top side clip in its original posion.
1. Insert the gateway in the upper edge of the DIN rail.
2. Fit the low side of the gateway in the DIN rail.
3. Push the boom clip back to its original posion, locking the gateway to the rail.
4. Make sure the gateway is rmly xed.
Hardware M-BUS to BACnet/IP Server Gateway
USER MANUAL Version 1.0.0 Page 7 of 22

5.2. Connecon
CAUTION
Disconnect all systems from the power source before manipulang and connecng them to the
gateway.
IMPORTANT
Keep communicaon cables away from power and ground wires.
5.2.1. Gateway Connectors
Figure 2. General view of all gateway connectors
1. Power supply: 24 VDC, Max.: 220 mA, 5.2 W
2. Port A: M-Bus port, for M-Bus bus connecon
3. Ethernet Port: For BACnet/IP connecon
Port A connectors M-Bus wires
A1 +
A2 -
NOTE
You can also use the Ethernet Port to connect the gateway to the PC for conguraon purposes.
NOTE
Mount the gateway in the desired installaon site before wiring.
M-BUS to BACnet/IP Server Gateway Connecon
Page 8 of 22 USER MANUAL Version 1.0.0

IMPORTANT
Use solid or stranded wires (twisted or with ferrule).
Wire cross-secon/gauge for all wire connectors:
• 1 core: 0.5 to 2.5 mm2 (24 to 11 AWG).
• 2 cores: 0.5 to 1.5mm2 (24 to 15 AWG).
• 3 cores: not permied.
NOTE
To know more about each port's specicaons, see Technical Specicaons (page 12).
Connecon M-BUS to BACnet/IP Server Gateway
USER MANUAL Version 1.0.0 Page 9 of 22

5.2.2. Common Connecons
5.2.2.1. Connecng the Gateway to the Power Supply
The power supply connector is a green pluggable terminal block (3 poles) labeled as 24Vdc.
IMPORTANT
• Use SELV-rated NEC class 2 or limited power source (LPS) power supply.
• Connect the gateway's ground terminal to the installaon grounding.
• A wrong connecon may cause earth loops that can damage the Intesis gateway and/or any other
system equipment.
Apply the voltage within the admied range and of enough power:
• 24 VDC, Max.: 220 mA, 5.2 W
IMPORTANT
• Respect the polarity labeled on the power connector for the posive and negave wires.
5.2.3. Connecon Procedure for M-Bus
The gateway connects directly to the M-Bus system without requiring any external RS-232 or EIA-485 to M-Bus
level converter.
Connect the M-Bus bus to connectors A1 (+) and A2 (-) of the gateway's Port A. Respect the polarity.
Remember that the gateway provides 36 VDC M-Bus voltage to the bus, acng also as an M-Bus level converter.
In case no response from the M-Bus device(s) to the frames sent by the gateway is received, check that they
are operave and reachable from the network connecon used by the gateway. You can use an EIA-485-to-USB
converter and an M-Bus master soware (such as MBSheet or similar) to double-check the M-Bus installaon.
M-BUS to BACnet/IP Server Gateway Connecon
Page 10 of 22 USER MANUAL Version 1.0.0

5.2.4. Connecon Procedure for BACnet/IP
NOTE
Remember to check the Common Connecons (page 10).
• Connect the BACnet/IP Ethernet cable to the gateway's Ethernet Port. The correct cable to use depends on
where the gateway is connected:
–Connecng directly to a BACnet/IP device: Use a crossover Ethernet UTP/FTP CAT5 or higher cable.
–Connecng to a hub or switch of the LAN of the building: Use a straight Ethernet UTP/FTP CAT5 or higher
cable.
IMPORTANT
When commissioning the gateway for the rst me, DHCP will be enabled for 30 seconds. Aer
that me, the default IP address 192.168.100.246 will be set.
NOTE
The default port is 502.
IMPORTANT
If communicang through the LAN of the building, contact the network administrator and make
sure trac on the used port is allowed through all LAN paths.
Connecon M-BUS to BACnet/IP Server Gateway
USER MANUAL Version 1.0.0 Page 11 of 22

5.3. Technical Specicaons
Case
Plasc, type PC (UL 94 V-0)
Net dimensions (dxwxh): 93x53x58 mm / 3.6x2.1x2.3"
Recommended space for installaon (dxwxh): 100x60x70 mm / 3.9x2.4x2.7"
Color: Light Grey. RAL 7035
Mounng Wall
DIN rail EN60715 TH35
Terminal wiring
For power supply
and low-voltage
signals
Per terminal: solid wires or stranded wires (twisted or with ferrule)
Wire cross-secon/gauge:
1 core: 0.5mm2 to 2.5mm2 (24 to 11 AWG)
2 cores: 0.5mm2 to 1.5mm2 (24 to 15 AWG)
3 cores: not permied
For distances longer than 3.05 meters (10 feet), use Class 2 cables.
Power
1 x Green pluggable terminal block (3 poles)
24 VDC, Max.: 220 mA, 5.2 W
Recommended: 24VDC, 220 mA
Ethernet 1 x Ethernet 10/100 Mbps RJ45
Port A
1 x M-BUS port: pluggable terminal block (2 poles)
MBUS power consumpon: 90 mA
Voltage rang: 36VDC
Operaonal
temperature
Celsius: 0 to +60°C
Fahrenheit: 32 to 140°F
Operaonal
humidity 5 to 95%, no condensaon
Protecon IP20 (IEC60529)
LED indicators 2 x Onboard LED indicators
Ethernet Link/Speed
M-BUS to BACnet/IP Server Gateway Technical Specicaons
Page 12 of 22 USER MANUAL Version 1.0.0

5.4. Dimensions
•Net dimensions (DxWxH)
Millimeters: 93 x 53 x 58 mm
Inches: 3.6 x 2.1 x 2.3"
•Clear space for installaon (DxWxH)
Millimeters: 100 x 60 x 70 mm
Inches: 3.9 x 2.4 x 2.7"
Dimensions M-BUS to BACnet/IP Server Gateway
USER MANUAL Version 1.0.0 Page 13 of 22

6. M-Bus System
6.1. General Descripon
The M-Bus ("Meter-Bus") is a European standard for remote reading of heat meters, and it is also usable for all
other types of consumpon meters, as well as for various sensors and actuators.
M-Bus standards are:
• EN 13757-2 (physical and link layer)
• EN 13757-3 (applicaon layer)
Many manufacturers of energy meters, pulse counters, water meters, electricity meters, etc., add an M-Bus
interface to their devices, enabling them to be interconnected and remotely monitored through a 2-wire bus
based on the M-Bus standards. There are many manufacturers of these measurement devices incorporang
the M-Bus interface, and also some other manufacturers of specic M-Bus communicaon devices such as bus
repeaters, EIA-232/EIA-485 to M-Bus level converters, etc.
6.2. M-Bus Interface
The gateway connects directly to the M-Bus system. No external level converter is required.
Connecon to the M-Bus is made via the EIA-485 connecon. Noce that the gateway also powers the bus, so no
extra hardware is required to connect to M-Bus compable meters or devices.
6.3. M-Bus Signals
The gateway supports several meter magnitudes and units typically used on the energy, electric, water, and other
meters. During the scan, the gateway imports each signal with the units and details provided by the meter. See
the details of the units on the Signals tab (page 21) in Intesis MAPS.
The type of signals available from every meter may dier, depending on the manufacturer and model. Please
refer to the device's technical documentaon to determine the signals available for a given meter to integrate
the desired ones.
Besides this, to simplify and speed up the idencaon of the signals oered by any device (and their type), a
scanning funcon has been embedded in the rmware of the gateway to poll the meter and show details about
the signals oered by the device and the corresponding signal code needed in the signals list of the gateway for
every one of the signals to integrate, using the Intesis MAPS conguraon tool.
M-BUS to BACnet/IP Server Gateway M-Bus System
Page 14 of 22 USER MANUAL Version 1.0.0

7. BACnet System
7.1. General Descripon
BACnet is a solid standard with many detailed concepts, but for this manual purposes, we will focus on the two
most fundamental concepts:
• BACnet client, which is the device that sends service requests to the server.
• BACnet server, which is the device that performs the requested service and reports the result back to the
client.
BACnet server devices are represented in the form of devices holding objects. Usually, every physical device
corresponds to a logical one. The objects can be of dierent types depending on the data and funconality they
represent: Analog input, Analog output, Digital input, etc.
NOTE
• Output objects are meant to be wrien from the BACnet network to the device.
• Input objects are meant to oer status informaon on the BACnet device.
• Value objects are bidireconal.
Every object has dierent properes. The most meaningful one is the Present_Value property, which indicates
the real value of the object. Also, the gateway uses this property to read and write values. Every object of the
same type in a device is idened with its associated object instance.
NOTE
Refer to the Protocol Implementaon Conformance Statement (PICS) document for more
informaon.
NOTE
This model supports BACnet descripons, this is congurable through the Intesis MAPS conguraon
tool.
BACnet System M-BUS to BACnet/IP Server Gateway
USER MANUAL Version 1.0.0 Page 15 of 22

7.2. BACnet Server
7.2.1. Descripon
NOTICE
When the Intesis gateway acts as a server device, it is classied under the device prole of a BACnet
Advanced Applicaon Controller (B-AAC). For further details, check out the product website for the
BACnet client PIC statements.
Using the Intesis MAPS conguraon tool, you can congure the object type associated with the signal on the
other protocol.
To facilitate the translaon towards BACnet, the following object type opons are available:
Object Type ID
Analog-Input 0
Analog-Output 1
Analog-Value 2
Binary-Input 3
Binary-Output 4
Binary-Value 5
Calendar 6
Device 8
Mulstate-Input 13
Mulstate-Output 14
Mulstate-Value 19
Nocaon-Class 15
Schedule 17
Trend-Log 20
Trend-Log-Mulple 27
Every signal of the Intesis gateway can have several objects. These objects and their properes can be congured
with the Intesis MAPS conguraon tool.
Depending on the eld device protocol, you can dene the signals using one of the following opons:
•Conguring them manually for each or mulple signals at the me.
•Imporng a le with the signals of the eld devices.
• Scanning the network of the devices if this is supported.
NOTICE
The conguraon tool provides default templates that make this signals assignment process easier.
Also, you only have to click the Check table buon on the boom right corner of the window to
know if everything is correct or if there's some mistake. The project is also automacally checked
before you transfer it to the gateway.
All objects denion, BIBBs, and details about the implementaon can be found on the BACnet server PICS on
the product website.
M-BUS to BACnet/IP Server Gateway BACnet Server
Page 16 of 22 USER MANUAL Version 1.0.0

7.2.2. BACnet/IP
The UDP communicaon port is the main setup parameter for BACnet/IP, besides basic IP sengs (IP, netmask,
default gateway). The Intesis gateway uses the 47808 (0xBAC0) port by default, which you can change through
the conguraon tool.
When using BACnet/IP, the gateway can also act as a foreign device to communicate with devices in another
network domain. Alternavely, you can set it as a BBMD (Bacnet/IP Broadcast Management Device). This
funconality facilitates the communicaon of devices placed in other networks with the devices in the gateway
network.
BACnet Server M-BUS to BACnet/IP Server Gateway
USER MANUAL Version 1.0.0 Page 17 of 22