需要帮助吗? 常见问题解答!

Our ASCII server gateway series use pre-defined ASCII commands to communicate between the ASCII Master device (such as a SCADA or a BMS system) and the KNX, LON or BAC devices.

Therefore, if your system is also using pre-defined ASCII commands and can’t understand our commands or if your system can’t be programmed to understand them, we will not be able to fit in your integration.

On the other hand, if your ASCII device can be programmed in order to communicate with our gateway, there should be no problem in using one of our gateways to fit your integration./p>

Please, find below some examples of the commands supported by our gateway:

• Read a value in the gateway: >Daaaa?\r
• Write a value in the gateway: >Daaaa=vv\r   

Where aaaa stands for the register address inside our gateway; vv stands for the desired value to place in the specific register; \r stands for carry return.

LinkBoxASCII, the software tool to configure Intesis ASCII series gateways, can be downloaded from the following link:
www.intesis.com/docs/software/setupv_linkboxascii

IBOX-BAC-KNX is a Bacnet server, whose objects are connected to KNX group addresses. This way, accessing this bacnet server from other BACnet devices you'll be able to communicate with the devices / group addresses in your KNX installation. IBOX-BAC-KNX is configured using LinkboxBacnet.


On the contrary, IBOX-KNX-BAC is not a BACnet server: it is Bacnet client, meant to access other BACnet servers. You need to know a priori which BACnet objects on which devices in the BACnet network you want to access, and declare them in Intesis configuration. Once configured, the information of the BACnet objects is exchanged with KNX. IBOX-KNX-BACNET is configured with LinkboxEIB.

LinkBoxBACnet, the software tool to configure Intesis BACnet IP Server series gateways, can be downloaded from the following link:

www.intesis.com/docs/software/setupv_linkboxbac

IBOX-BAC-KNX is a BACnet server, whose objects are connected to KNX group addresses. This way, accessing this BACnet server from other BACnet devices you'll be able to communicate with the devices / group addresses in your KNX installation. IBOX-BAC-KNX is configured using LinkboxBACnet.

On the contrary, IBOX-KNX-BAC is not a BACnet server: it is BACnet client, meant to access other BACnet servers. You need to know a priori which BACnet objects on which devices in the BACnet network you want to access, and declare them in Intesis configuration. Once configured, the information of the BACnet objects is exchanged with KNX. IBOX-KNX-BACnet is configured with LinkboxEIB.

We have the product IBOX-LON-KNX, which should be configured with LinkboxLON, and implements a LON node to be commissioned with LonMaker or other typical LON commissioning tools on its LON side. Using IBOX-LON-KNX the KNX network will be seen within the LON installation as just one more LON device, with the NV where you've decided to map all KNX communication objects at configuration time.

On the other hand, we also have the product IBOX-KNX-LON (note the difference in the order of the references KNX-LON). In that case, it is configured using LinkboxEIB. IBOX-KNX-LON is not a LON node in itself. Rather, it operates by periodically polling (or sending writes) to Network Variables present in other LON devices in the network. This yields in a high traffic in the LON network (resulting of the continuous polling messages). In that case though, there is no need of commissioning the devices with LonMaker (our product can also operate if the network has been commissioned a priori – but this commissioning is not required). LinkboxEIB does allow for importing an XIF of an existing external LON device, so that you're able to get a list of points of it in LinkboxEIB - and be able to associate them with KNX group addresses, to interact with the device from the KNX network.

LinkBoxEIB, the software tool to configure Intesis KNX series gateways, can be downloaded from the following link:

www.intesis.com/docs/software/setupv_linkboxeib

We have the product IBOX-LON-KNX, which should be configured with LinkboxLON, and implements a LON node to be commissioned with LonMaker or other typical LON commissioning tools on its LON side. Using IBOX-LON-KNX the KNX network will be seen within the LON installation as just one more LON device, with the NV where you've decided to map all KNX communication objects at configuration time. On the other hand, we also have the product IBOX-KNX-LON (note the difference in the order of the references KNX-LON). In that case, it is configured using LinkboxEIB. IBOX-KNX-LON is not a LON node in itself. Rather, it operates by periodically polling (or sending writes) to Network Variables present in other LON devices in the network. This yields in a high traffic in the LON network (resulting of the continuous polling messages). In that case though, there is no need of commissioning the devices with LonMaker (our product can also operate if the network has been commissioned a priori – but this commissioning is not required). LinkboxEIB does allow for importing an XIF of an existing external LON device, so that you're able to get a list of points of it in LinkboxEIB - and be able to associate them with KNX group addresses, to interact with the device from the KNX network.

LinkBoxLON, the software tool to configure IntesisBox LON series gateways, can be downloaded from the following link:

www.intesis.com/docs/software/setupv_linkboxlon

LinkBoxMB, the software tool to configure IntesisBox Modbus Slave series gateways, can be downloaded from the following link:

www.intesis.com/docs/software/setupv_linkboxmb