IntesisBox IBMBSMEB0100000, IBMBSMEB0200000, IBMBSMEB0600000, IBMBSMEB1200000 User Manual

IntesisBox

®

Modbus Server

M-Bus

User Manual

r1.1 eng

Issue date: 10/2017

IntesisBox® Modbus Server – M-Bus User Manual r1.1 EN

URL

email

tel

http://www.intesisbox.com
[e-mail]
[phone]

© Intesis Software S.L.U. - All rights reserved

IntesisBox is a registered trademark of Intesis Software SLU

2/20

© Intesis Software S.L.U. 2017 All Rights Reserved.

Information in this document is subject to change without notice. The software described in this document is furnished
under a license agreement or nondisclosure agreement. The software may be used only in accordance with the terms
of those agreements. No part of this publication may be reproduced, stored in a retrieval system or transmitted in
any form or any means electronic or mechanical, including photocopying and recording for any purpose other than
the purchaser’s personal use without the written permission of Intesis Software S.L.U.

Intesis Software S.L.U.
Milà i Fontanals, 1 bis
08700 Igualada
Spain

TRADEMARKS
All trademarks and trade names used in this document are acknowledged to be the copyright of their respective
holders.

IntesisBox® Modbus Server – M-Bus User Manual r1.1 EN

URL

email

tel

http://www.intesisbox.com
[e-mail]
[phone]

© Intesis Software S.L.U. - All rights reserved

IntesisBox is a registered trademark of Intesis Software SLU

3/20

Gateway for the integration of M-Bus meters into Modbus RTU
and/or Modbus TCP monitoring and control systems.

Order code:

IBMBSMEB0100000, 10 devices version
IBMBSMEB0200000, 20 devices version
IBMBSMEB0600000, 60 devices version
IBMBSMEB1200000, 120 devices version

IntesisBox® Modbus Server – M-Bus User Manual r1.1 EN

URL

email

tel

http://www.intesisbox.com
[e-mail]
[phone]

© Intesis Software S.L.U. - All rights reserved

IntesisBox is a registered trademark of Intesis Software SLU

4/20

INDEX

1 Description ............................................................................................................................................... 5

Introduction ....................................................................................................................................... 5

Functionality ..................................................................................................................................... 6

Gateway’s capacity .......................................................................................................................... 7

2 M-Bus System .......................................................................................................................................... 8

Description ........................................................................................................................................ 8

M-Bus interface ................................................................................................................................ 8

M-Bus signals ................................................................................................................................... 8

3 Modbus interface of IntesisBox .............................................................................................................. 10

Description ...................................................................................................................................... 10

Functions supported ....................................................................................................................... 10

Modbus RTU .................................................................................................................................. 10

Modbus TCP ................................................................................................................................... 10

Address Map .................................................................................................................................. 10

Points definition .............................................................................................................................. 11

4 Connections ........................................................................................................................................... 12

Powering the device ....................................................................................................................... 13

Connection to M-Bus ...................................................................................................................... 13

Connection to Modbus ................................................................................................................... 13

4.3.1 Modbus TCP ........................................................................................................................... 13

4.3.2 Modbus RTU ........................................................................................................................... 13

Connection to the configuration tool ............................................................................................... 13

5 Set-up process and troubleshooting ...................................................................................................... 14

Pre-requisites ................................................................................................................................. 14

IntesisBox MAPS. Configuration & monitoring tool for IntesisBox Modbus series ........................ 14

5.2.1 Introduction ............................................................................................................................. 14

5.2.2 Connection .............................................................................................................................. 14

5.2.3 Configuration tab .................................................................................................................... 15

5.2.4 Signals .................................................................................................................................... 15

5.2.5 Sending the configuration to IntesisBox ................................................................................. 16

5.2.6 Diagnostic ............................................................................................................................... 16

Set-up procedure ............................................................................................................................ 18

6 Electrical & Mechanical Features ........................................................................................................... 19

7 Dimensions ............................................................................................................................................ 20

IntesisBox® Modbus Server – M-Bus User Manual r1.1 EN

URL

email

tel

http://www.intesisbox.com
[e-mail]
[phone]

© Intesis Software S.L.U. - All rights reserved

IntesisBox is a registered trademark of Intesis Software SLU

5/20

1 Description

Introduction

This document describes the integration of M-Bus devices into Modbus RTU and Modbus TCP systems using the
IntesisBox Modbus Slave – M-Bus gateway.

The aim of this integration is to make accessible M-Bus devices from a Modbus control system or device, as if it was
part of the own Modbus installation.

For this, IntesisBox acts as a Modbus TCP server or Modbus RTU slave device in its Modbus interface, allowing
read/write points from the Modbus client device(s). From the M-Bus point of view, IntesisBox acts as a M-Bus level
converter and master device (EN-1434-3). The readings of the M-Bus slave device(s) are performed by IntesisBox
by automatic continuous polling or underdemand (to avoid batteries on meters run out).

Configuration is carried out using the configuration software IntesisBox® MAPS.

This document assumes that the user is familiar with M-Bus and Modbus technologies and their technical terms.

Integration of M-Bus devices into Modbus TCP

or Modbus RTU control and monitoring systems

M-BUS EIA485

Modbus TCP

Ethernet TCP

Modbus RTU EIA485

Modbus RTU EIA232

IntesisBox® Modbus Server – M-Bus User Manual r1.1 EN

URL

email

tel

http://www.intesisbox.com
[e-mail]
[phone]

© Intesis Software S.L.U. - All rights reserved

IntesisBox is a registered trademark of Intesis Software SLU

6/20

Functionality

IntesisBox polls, either continuously or only when ordered from the Modbus side, the M-Bus devices to obtain updated
readings for the points configured in it (the points corresponding to measures and states of the meters in the
integration points list explained later in this document). With every read, the new values received are updated in the
Intesisbox's memory and become available in the Modbus side. When a change in any point configured as output in
IntesisBox is detected (this is written from the Modbus side), the corresponding action in the M-Bus device will be
performed. These actions can be: force a polling of a specific M-Bus device or force a polling of all M-Bus devices.

The polling of a specific M-Bus device, or of all M-Bus devices, can be forced in any moment from the Mobus side
by writing a 1 in the corresponding binary point specially enabled for this purpose in the IntesisBox.

The automatic continuous polling of all M-Bus devices can be activated/deactivated writing from Modbus in a specific
binary point specially enabled for this purpose in the IntesisBox.

Other M-Bus information accessible from Modbus, using specific points of the IntesisBox, is:

• Bus activity (indicates if meters are currently being polled or if polling is in stand-by).

• M-Bus status of every meter (this M-Bus status is sent by the own meter with every poll and indicates the

internal status, manufacturer specific in every case).

These are the main features of the M-Bus interface of IntesisBox:

• Embedded level converter. Direct connection to M-Bus devices with no extra hardware required.

• Scan option to automatically detect M-Bus devices and its available registers.

• Import/Export of M-Bus device templates.

• EIA485 two wires (plug-in terminal bloc with screws) connection.

• Baud rate configurable from 300 to 9600 bps (allowed baud rates in M-Bus. The devices are normally

configured at 2400 bps at the factory).

• Primary or secondary addressing allowed.

• Useful timeouts and specific parameters to make the interface widely compatible with many meter's

peculiarities found usually between different manufacturers.

• Polling of the meters can be continuously, either configured in the own IntesisBox or you can
activate/deactivate continuous polling of the meters from BACnet side using a special datapoint.

• You can force a polling of the meters (refresh of readings) in any moment from BACnet side using special
datapoints: one datapoint to force a polling of all the meters, and one specific datapoint per meter to force
the polling of the individual meter.

• IntesisBox can also be configured to make a single polling of the meters (refresh of readings) at the start
up.

• For each meter, a datapoint is available in BACnet indicating communication error with the meter, also a
general communication error datapoint is available (that will be active whenever the communication with
one or more meters has failed).

• Fully flexible configuration of the registers to poll in the meter, to adapt to any meter.

Every meter, depending on manufacturer and model, offers different type of signals from the mentioned before. To
know what signals offers the meter and of what type, to be able to integrate those wanted, refer to the device technical
documentation. Anyway, and to ease and speed up the identification of the signals offered by any device (and of
what type), the scan option is highly recommended or the import of templates too.