¼¯³ÉÍø¹Øintesisbox°ÑModbus ´ÓÉ豸ת³ÉKNX¿ØÖÆϵͳ£¬¼¯³Éµ½Modbus RTU´ÓÕ¾É豸£¨ÀäË®»ú×飬¥Óµç±í£¬Å¯ÆøµØ°å£¬Èȱã¬PLC£©µ½KNX¿ØÖÆϵͳת»»

IntesisBox acts as a Modbus RTU master device in its Modbus interface, reading/writing points of the Modbus slave device(s), and offering this point"s values through its KNX interface. IntesisBox acts in the KNX side as one more device of the KNX system. IntesisBox"s KNX EIB interface connects directly to the EIB bus and is opto-isolated from the rest of the internal electronics
The Modbus interface of IntesisBox reads continuously by polling the Modbus slave devices/registers configured. If a non response of the Modbus slave is detected, the corresponding virtual signal inside IntesisBox will be activated indicating communication error with the device. All the updated readings of the Modbus registers are maintained in IntesisBox memory for immediate interaction with KNX when needed.
Each Modbus register of the slave device is associated to a KNX group address. All the Modbus registers of the different slaves are accessible through KNX group addresses.
When a change in any Modbus register/slave occurs, a write telegram is sent to the KNX bus, to the associated KNX group address. This is configurable individually per point.
IntesisBox KNX series are configured using LinkBoxEIB, a software tool for windowsTM which is supplied along with the purchase of IntesisBox with no additional cost. With the standard installation of LinkBoxEIB, a Demo project for integration of Modbus slave devices is also installed, using this demo project makes the engineering needed for this integration easy and quick.

IntesisboxÓÐÈý¸ö°æ±¾---KNX MOdbus RTUÖ÷É豸Óв»Í¬µÄÄÜÁ¦¶Ôÿ¸öÐͺÅ

 Version with capacity of 100 points and up to 254 slave devices. Ref. IBOX-KNX-MBRTU-100.
 Version with capacity of 500 points and up to 254 slave devices. Ref. IBOX-KNX-MBRTU-A.
 Version with capacity of 3000 points and up to 254 slave devices. Ref. IBOX-KNX-MBRTU-B.