![]() ![]() On the KNX side, IntesisBox simulates a KNX device and acts as if it was a single device into the KNX system.The IntesisBox's KNX interface connects directly to the KNX bus and it is optoisolated from the rest of the internal electronics.Ĭonfiguration project is done through IntesisBox MAPS. The KNX bus integration makes connections between primary controls (heating, ventilation, energy production) and secondary control (zones, rooms) easy, and helps to bring the KNX variables to SCADA where the values may be further processed using trending, alarming, logging and the like.IntesisBox acts as a master in the BACnet side allowing to read/write points of other BACnet/IP device(s) connected to a BACnet network and offering these point's values through its KNX interface. ![]() The input linear transform („Kx + Q“) in Merbon IDE must be set accordingly. Note that the temperature in Register 2 shows 22 ☌ multiplied by 10 to achieve resolution of one decimal position. The ModComTool communication for the configuration shown above looks like this: Domat ModComTool) before configuring the devices in Merbon IDE. It is recommended to test the communication using a general Modbus client (e.g. In the variables table, for each Modbus register there is the KNX value type (EIS), variable address, KNX read / write rights, variable format, Modbus register number, and for binary values access over Modbus bit-oriented functions, and Modbus read / write rights.Īfter the configuration (or „project“) has been uploaded to the converter, establishing of communication is a matter of several seconds. The IntesisBox configuration using the LinkBoxMB software (supplied free of charge together with the converter) is fairly easy and consists of converter parameters settings (IP address and other network parameters, if Modbus TCP is used, RS232 or RS485, if serial interface is used), converter KNX address, and several other parameters, and of course of the Modbus table definition with addresses and variables properties at the KNX bus, which correspond to the Modbus registers. Modbus TCP offers higher data throughput in general, and therefore is more suitable for larger projects.Ī Modbus RTU topology is usually used at smaller sites, or at PLCs which do not provide Modbus TCP channels. When choosing between Modbus TCP and Modbus RTU, the required response time, PLC capabilities, and number of variables.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |