The M-Bus to BACnet Gateway has been specially designed to allow bidirectional control and monitoring of all parameters and functionalities of M-Bus Meters from a BMS, SCADA, PLC or any other device working as a BACnet client.
The aim of this integration is to make accessible M-Bus system signals and resources from a BACnet/IP or BACnet MSTP based control system or device as if it was a part of the own BACnet system and vice-versa. For this, the gateway acts as a BACnet/IP or BACnet MSTP Server device in its BACnet interface, allowing other BACnet/IP devices to perform subscription (COV) requests, and also read and write its internal points. From the M-Bus system 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 polls, either continuously or only when ordered from 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 BACnet side. When a change in any point configured as an output in IntesisBox is detected (this is written from the BACnet side), the corresponding action in the M-Bus will be performed, these actions can be: force a polling of a concrete M-Bus device or force a polling of all M-Bus devices.
The polling of a concrete 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.
Also, 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.