IntesisBox IBBACMEB0100000, IBBACMEB0200000, IBBACMEB0600000, IBBACMEB1200000 User Manual

IntesisBox

®

BACnet Server

M-Bus Meters

User Manual

r1.0 eng

Issue date: 09/2017

IntesisBox® BACnet Server – M-Bus User Manual r1.0 eng

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/41

© 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® BACnet Server – M-Bus User Manual r1.0 eng

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/41

Gateway for the integration of M-Bus devices into BACnet MSTP
or BACnet IP enabled monitoring and control systems.

Order code:

IBBACMEB0100000, 10 M-Bus devices
IBBACMEB0200000, 20 M-Bus devices
IBBACMEB0600000, 60 M-Bus devices
IBBACMEB1200000, 120 M-Bus devices

IntesisBox® BACnet Server – M-Bus User Manual r1.0 eng

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/41

INDEX

1 Description ............................................................................................................................................... 6

Introduction ....................................................................................................................................... 6

Functionality ..................................................................................................................................... 7

1.2.1 Signals ...................................................................................... ¡Error! Marcador no definido.

Gateway’s capacity .......................................................................................................................... 8

2 Protocol Implementation Conformance Statement .................................................................................. 9

BACnet Standardized Device Profile (Annex L): .............................................................................. 9

Segmentation Capability: ................................................................................................................. 9

Data Link Layer Options: .................................................................................................................. 9

Device Address Binding: ................................................................................................................ 10

Networking Options: ....................................................................................................................... 10

Character Sets Supported .............................................................................................................. 10

Gateway ......................................................................................................................................... 10

3 BACnet Interoperability Building Blocks Supported (BIBBs) ................................................................. 11

Data Sharing BIBBs ....................................................................................................................... 11

Alarm and Event Management BIBBs ............................................................................................ 11

Scheduling BIBBs ........................................................................................................................... 12

Trending BIBBs .............................................................................................................................. 12

Network Management BIBBs ......................................................................................................... 12

Device Management BIBBs ........................................................................................................... 13

4 Service Types ........................................................................................................................................ 14

5 Objects ................................................................................................................................................... 15

Supported Object Types ................................................................................................................. 15

Objects and properties ................................................................................................................... 16

5.2.1 IBOX-BAC-MBM (Device Object Type) .................................................................................. 16

5.2.2 Analog Input Object Type ....................................................................................................... 18

5.2.3 Analog Output Object Type .................................................................................................... 19

5.2.4 Analog Value Object Type ...................................................................................................... 20

5.2.5 Binary Input Object Type ........................................................................................................ 21

5.2.6 Binary Output Object Type ..................................................................................................... 22

5.2.7 Binary Value Object Type ....................................................................................................... 23

5.2.8 Multistate Input Object Type ................................................................................................... 24

5.2.9 Multistate Output Object Type ................................................................................................ 25

5.2.10 Multistate Value Object Type .................................................................................................. 26

5.2.11 Calendar Object Type ............................................................................................................. 27

5.2.12 Schedule Object Type ............................................................................................................ 28

5.2.13 Notification Class Object Type ............................................................................................... 29

5.2.14 Trend Log Object Type ........................................................................................................... 30

5.2.15 Trend Log Multiple Object Type ............................................................................................. 31

6 Connections ........................................................................................................................................... 32

Powering the device ....................................................................................................................... 33

Connection to BACnet .................................................................................................................... 33

6.2.1 BACnet IP ............................................................................................................................... 33

6.2.2 BACnet MSTP ........................................................................................................................ 33

Connection to M-Bus ...................................................................................................................... 34

Connection to the configuration tool ............................................................................................... 34

7 Set-up process and troubleshooting ...................................................................................................... 35

Pre-requisites ................................................................................................................................. 35

IntesisBox MAPS. Configuration & monitoring tool for IntesisBox BACnet series ......................... 35

7.2.1 Introduction ............................................................................................................................. 35

7.2.2 Connection .............................................................................................................................. 35

7.2.3 Configuration tab .................................................................................................................... 36

7.2.4 Signals .................................................................................................................................... 36

7.2.5 Sending the configuration to IntesisBox ................................................................................. 37

7.2.6 Diagnostic ............................................................................................................................... 37

Set-up procedure ............................................................................................................................ 39

8 Electrical & Mechanical Features ........................................................................................................... 40

IntesisBox® BACnet Server – M-Bus User Manual r1.0 eng

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/41

9 Dimensions ............................................................................................................................................ 41

IntesisBox® BACnet Server – M-Bus User Manual r1.0 eng

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/41

1 Description

Introduction

This document describes the integration of M-Bus meters with BACnet ASHRAE 135 – 2001 Annex J - BACnet
protocol compatible devices or systems using the gateway IntesisBox BACnet/IP Server - M-Bus.

The aim of this integration is to make accessible M-Bus devices signals and resources from a BACnet based control
system or device, as if it was a part of the own BACnet system and vice-versa.

The gateway acts as a BACnet/IP Server or BACnet MSTP device in its BACnet interface, allowing other BACnet
devices to perform subscription (COV) requests and reads/writes to its internal points. From the M-Bus point of view,
IntesisBox acts as a M-Bus master device (EN-1434-3), the readings of the M-Bus slave device(s) is performed by
IntesisBox by automatic continuous polling.

IntesisBox incorporates and embeded M-Bus level converter, so no extra hardware is required.
Configuration is carried out using the configuration software IntesisBox® MAPS.

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

Integration of MBUS devices

to BACnet IP or MSTP control and monitoring systems

BACnet/IP

BACnet MSTP

Ethernet TCP

MBUS

IntesisBox® BACnet Server – M-Bus User Manual r1.0 eng

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

7/41

Functionality

IntesisBox polls, either continuously or only when ordered from the BACnet 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 BACnet side. When a change in any point configured as output in
IntesisBox is detected (this is written from the BACnet 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 BACnet 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 BACnet in a specific
binary point specially enabled for this purpose in the IntesisBox.

Other M-Bus information accessible from BACnet, 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.

IntesisBox® BACnet Server – M-Bus User Manual r1.0 eng

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

8/41

Gateway’s capacity

IntesisBox capacity is listed below:

Element

10

version

20

version

60

version

120

version

Notes

Type of BACnet
devices

IP / MSTP

Communication with BACnet IP and MSTP.

Number of BACnet
Objecs

250

500

1500

3000

Maximum number of points that can be
defined in the virtual BACnet device inside the
gateway.

Number of BACnet
Subscriptions (COV)
requests

500

1000

3000

6000

Maximum number of BACnet subscriptions
(COV) requests accepted by the gateway.

Type of M-Bus
devices

M-Bus EIA485 Slave devices

Those supporting M-Bus EN-1434-3 standar.
Communication over RS485

Number of M-Bus
slave devices

10

20

60

120

Number of M-Bus slave devices supported
by the gateway.

Number of M-Bus
signals

250

500

1500

3000

Number of M-Bus signals (readings in the
meters) that can be read from IntesisBox.

IntesisBox® BACnet Server – M-Bus User Manual r1.0 eng

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

9/41

2 Protocol Implementation Conformance Statement

BACnet Protocol Implementation Conformance Statement (PICS)

Date: 2017-09-18
Vendor Name: Intesis Software SLU
Product Name: IBOX-BAC-MEB
Product Model Number: IBOX-BAC-MEB
Application Software Version: 1.0
Firmware Revision: 1.0.0.0
BACnet Protocol Revision: 12

Product Description:

M-Bus – BACnet MS/TP & BACnet IP Gateway

Abstraction of M-Bus slave device registers as BACnet Objects.

BACnet Standardized Device Profile (Annex L):

BACnet Operator Workstation (B-OWS)
BACnet Building Controller (B-BC)
BACnet Advanced Application Controller (B-AAC)
BACnet Application Specific Controller (B-ASC)
BACnet Smart Sensor (B-SS)
BACnet Smart Actuator (B-SA)

Additional BACnet Interoperability Building Blocks Supported (Annex K):
Reference of BIBBs List

Segmentation Capability:

Segmented request supported No Yes Window Size · 16 ·
Segmented responses supported No Yes Window Size · 16 ·

Data Link Layer Options:

BACnet IP, (Annex J)
BACnet IP, (Annex J), Foreign Device
ISO 8802-3, Ethernet (Clause 7)
ANSI/ATA 878.1, 2.5 Mb. ARCNET (Clause 8)
ANSI/ATA 878.1, RS-485 ARCNET (Clause 8), baud rate(s) ____
MS/TP master (Clause 9), baud rate(s): 9600, 19200, 38400, 57600, 76800, 115200
MS/TP slave (Clause 9), baud rate(s):
Point-To-Point, EIA 232 (Clause 10), baud rate(s):
Point-To-Point, modem, (Clause 10), baud rate(s):
LonTalk, (Clause 11), medium: _____
Other:

IntesisBox® BACnet Server – M-Bus User Manual r1.0 eng

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

10/41

Device Address Binding:

Is static device binding supported? (This is currently necessary for two-way communication with
MS/TP slaves and certain other devices.) Yes No

Networking Options:

Router, Clause 6 - List all routing configurations, e.g., ARCNET-Ethernet, Ethernet-MS/TP, etc.
Annex H, BACnet Tunneling Router over IP
BACnet/IP Broadcast Management Device (BBMD)

Does the BBMD support registrations by Foreign Devices? Yes No

Character Sets Supported

Indicating support for multiple character sets does not imply that they can all be supported simultaneously.

ISO 10646 (UTF-8) IBM



/Microsoft DBCS ISO 8859-1

ISO 10646 (UCS-2) ISO 10646 (UCS-4) JIS X 0208

Gateway

If this product is a communication gateway, describe the types of non-BACnet equipment/network(s) that the gateway
supports:

M-Bus slave devices.

IntesisBox® BACnet Server – M-Bus User Manual r1.0 eng

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

11/41

3 BACnet Interoperability Building Blocks Supported (BIBBs)

Data Sharing BIBBs

BIBB Type

Active

BACnet Service

Initiate

Execute

DS-RP-A

Data Sharing-ReadProperty–A

ReadProperty

DS-RP-B

Data Sharing-ReadProperty–B

ReadProperty

DS-RPM-A

Data Sharing-ReadPropertyMultiple–A

ReadPropertyMultiple

DS-RPM-B

Data Sharing-ReadPropertyMultiple–B

ReadPropertyMultiple

DS-RPC-A

Data Sharing-ReadPropertyConditiona–A

ReadPropertyConditional

DS-RPC-B

Data Sharing-ReadPropertyConditional–B

ReadPropertyConditional

DS-WP-A

Data Sharing-WriteProperty–A

WriteProperty

DS-WP-B

Data Sharing-WriteProperty–B

WriteProperty

DS-WPM-A

Data Sharing-WritePropertyMultiple–A

WritePropertyMultiple

DS-WPM-B

Data Sharing-WritePropertyMultiple–B

WritePropertyMultiple

DS-COV-A

Data Sharing-COV–A
SubscribeCOV

ConfirmedCOVNotification

UnconfirmedCOVNotification

DS-COV-B

Data Sharing-COV–B
SubscribeCOV

ConfirmedCOVNotification

UnconfirmedCOVNotification

DS-COVP-A

Data Sharing-COVP–A
SubscribeCOVProperty

ConfirmedCOVNotification

UnconfirmedCOVNotification

DS-COVP-B

Data Sharing-COVP–B
SubscribeCOVProperty

ConfirmedCOVNotification

UnconfirmedCOVNotification

DS-COVU-A

Data Sharing-COV-Unsubscribed–A

UnconfirmedCOVNotification

DS-COVU-B

Data Sharing-COV- Unsubscribed -B

UnconfirmedCOVNotification

Alarm and Event Management BIBBs

BIBB Type

Active

BACnet Service

Initiate

Execute

AE-N-A

Alarm and Event-Notification–A
ConfirmedEventNotification

UnconfirmedEventNotification

AE-N-I-B

Alarm and Event-Notification Internal–B
ConfirmedEventNotification

UnconfirmedEventNotification

AE-N-E-B

Alarm and Event-Notification External–B
ConfirmedEventNotification

UnconfirmedEventNotification

AE-ACK-A

Alarm and Event-ACK–A

AcknowledgeAlarm

AE-ACK-B

Alarm and Event-ACK–B

AcknowledgeAlarm

AE-ASUM-A

Alarm and Event-Alarm Summary–A

GetAlarmSummary

AE-ASUM-B

Alarm and Event-Alarm Summary–B

GetAlarmSummary

AE-ESUM-A

Alarm and Event-Enrollment Summary-A

GetEnrollmentSummary

AE-ESUM-B

Alarm and Event-Enrollment Summary-B

GetEnrollmentSummary

AE-INFO-A

Alarm and Event-Information–A

GetEventInformation

AE-INFO-B

Alarm and Event-Information–B

GetEventInformation

AE-LS-A

Alarm and Event-LifeSafety–A

LifeSafetyOperation

AE-LS-B

Alarm and Event-LifeSafety–B

LifeSafetyOperation

IntesisBox® BACnet Server – M-Bus User Manual r1.0 eng

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

12/41

Scheduling BIBBs

Trending BIBBs

Network Management BIBBs

BIBB Type

Active

BACnet Service

Initiate

Execute

SCHED-A

Scheduling–A
(must support DS-RP-A and DS-WP-A)

SCHED-I-B

Scheduling-Internal–B

(shall support DS-RP-B and DS-WP-B)
(shall also support ether DM-TS-B or DS-UTC-B)

SCHED-E-B

Scheduling-External–B
(shall support SCHED-I-B and DS-WP-A)

BIBB Type

Active

BACnet Service

Initiate

Execute

T-VMT-A

Trending - Viewing and Modifying Trends–A

ReadRange

T-VMT-I-B

Trending - Viewing and Modifying Trends Inernal–B

ReadRange

T-VMT-E-B

Trending - Viewing and Modifying Trends External–B

ReadRange

T-ATR-A

Trending - Automated Trend Retrieval–A
ConfirmedEventNotification

ReadRange

T-ATR-B

Trending - Automated Trend Retrieval–B
ConfirmedEventNotification

ReadRange

BIBB Type

Active

BACnet Service

Initiate

Execute

NM-CE-A

Network Management - Connection
Establishment–A

Establish-Connection-To­Network

Disconnect-Connection-To­Network

NM-CE-B

Network Management - Connection
Establishment– B

Establish-Connection-To­Network

Disconnect-Connection-To­Network

NM-RC-A

Network Management - Router Configuration–A

Who-Is-Router-To-Network

I-Am-Router-To-Network

I-Could-Be-Router-To­Network

Initialize-Routing-Table

Initialize-Routing-Table-Ack

NM-RC-B

Network Management - Router Configuration–B
Who-Is-Router-To-Network

I-Am-Router-To-Network

Initialize-Routing-Table

Initialize-Routing-Table-Ack

IntesisBox® BACnet Server – M-Bus User Manual r1.0 eng

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

13/41

Device Management BIBBs

BIBB Type

Active

BACnet Service

Initiate

Execute

DM-DDB-A

Device Management - Dynamic Device Binding–A
Who-Is

I-Am

DM-DDB-B

Device Management - Dynamic Device Binding–B
Who-Is

I-Am

DM-DOB-A

Device Management - Dynamic Object Binding–A
Who-Has

I-Have

DM-DOB-B

Device Management - Dynamic Object Binding–B
Who-Has

I-Have

DM-DCC-A

Device Management - DeviceCommunicationControl–A

DeviceCommunicationControl

DM-DCC-B

Device Management - DeviceCommunicationControl–B

DeviceCommunicationControl

DM-PT-A

Device Management - PrivateTransfer–A
ConfirmedPrivateTransfer

UnconfirmedPrivateTransfer

DM-PT-B

Device Management - PrivateTransfer–B
ConfirmedPrivateTransfer

UnconfirmedPrivateTransfer

DM-TM-A

Device Management - Text Message–A
ConfirmedTextMessage

UnconfirmedTextMessage

DM-TM-B

Device Management - Text Message–B
ConfirmedTextMessage

UnconfirmedTextMessage

DM-TS-A

Device Management - TimeSynchronization–A

TimeSynchronization

DM-TS-B

Device Management - TimeSynchronization–B

TimeSynchronization

DM-UTC-A

Device Management - UTCTimeSynchronization–A

UTCTimeSynchronization

DM-UTC-B

Device Management - UTCTimeSynchronization–B

UTCTimeSynchronization

DM-RD-A

Device Management - ReinitializeDevice–A

ReinitializeDevice

DM-RD-B

Device Management - ReinitializeDevice–B

ReinitializeDevice

DM-BR-A

Device Management - Backup and Restore–A
AtomicReadFile

AtomicWriteFile

CreateObject

ReinitializeDevice

DM-BR-B

Device Management - Backup and Restore–B
AtomicReadFile

AtomicWriteFile

ReinitializeDevice

DM-R-A

Device Management - Restart–A

UnconfimedCOVNotification

DM-R-B

Device Management - Restart–B

UnconfimedCOVNotification

DM-LM-A

Device Management - List Manipulation–A
AddListElement

RemoveListElement

DM-LM-B

Device Management - List Manipulation–B
AddListElement

RemoveListElement

DM-OCD-A

Device Management - Object Creation and Deletion–A
CreateObject

DeleteObject

DM-OCD-B

Device Management - Object Creation and Deletion–B
CreateObject

DeleteObject

DM-VT-A

Device Management - Virtual Terminal–A
VT-Open

VT-Close

VT-Data

DM-VT-B

Device Management - Virtual Terminal–B
VT-Open

VT-Close

VT-Data