IntesisBox
®
BACnet/IP Server - Modbus RTU Master
User’s Manual r14 eng
© Intesis Software S.L. - All rights reserved
This information is subject to change without notice
IntesisBox
®
is a registered trademark of Intesis Software SL
URL
Email
tel
http://www.intesis.com
[email protected]
+34 938047134
6 / 27
1.2 Functionality
The integration operation is as follow:
From the Modbus system point of view, after the start up process, IntesisBox reads
continuously the points configured to be read in the Modbus slave devices, and updates in
its memory all the values received from the Modbus system.
From the BACnet system point of view, after the start up process, the gateway listen for any
subscription (COV) request, serves any polling request, or performs any writing request of
its internal points received from BACnet system. The values received from BACnet are
immediately written in the associated register of the corresponding Modbus slave device.
Every one of the Modbus registers in the slave devices is associated to a
BACnet
object
,
with this, all the Modbus system (all the slave devices) is seen as
a single
BACnet
device
with many objects
from the BACnet system point of view, each object corresponding to a
Modbus slave/register address.
When a new value is read from Modbus for a given register, the new value is updated in the
gateway's memory and, if this signal is associated to a BACnet active subscription then the
new value will be sent to the subscripted BACnet device(s).
In the continuous polling of the Modbus devices, if a non response of the Modbus device is
detected, the corresponding virtual signal inside IntesisBox will be activated indicating
communication error with the Modbus device. These virtual signals indicating
communication status in real time with the Modbus devices are also accessible from BACnet,
like the rest of the points of IntesisBox.
