ModBus TCP to BACnet Server

• IBOX-BAC-MBTCP-100 (100 points and 5 devices)
• IBOX-BAC-MBTCP-A (500 points and 5 devices)
• IBOX-BAC-MBTCP-B (3000 points and 5 devices)

DESCRIPTION:

The aim of this integration is to make accessible Modbus TCP system signals and resources from a BACnet/IP 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 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 Modbus TCP system point of view, after the start-up process, IntesisBox reads continuously the points configured to be read in the Modbus TCP slave devices, and updates in its memory all the values received from the Modbus TCP 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 TCP slave device.