We guide you to the right product choice based on √ Environment√ Economics

INTESIS IN701KNX, KNX to Modbus/BACnet protocol translator


Alternative:

  • KNX TP to Modbus® TCP & RTU Server.
  • Modbus TCP & RTU Client to KNX TP.
  • KNX TP to BACnet®/IP & MS/TP Server.
  • BACnet/IP & MS/TP Client to KNX TP.
  • KNX TP to ASCII IP & Serial Server.

Available in the following sizes:
100 points
250 points
600 points
1200 points
3000 points

Part Number N/A Category: Label:

IN701KNX is a protocol translator between KNX and Modbus or BACnet

Datasheet

Link to download the Intesis MAPS tool

KNX TP to Modbus TCP & RTU server:
This section describes the integration of KNX systems into Modbus RTU and/or Modbus TCP systems using the application KNX TP to Modbus TCP & RTU server from the Intesis gateway. This integration enables a Modbus installation to access groups, objects and associated devices in KNX systems as if they were part of the Modbus system, and vice versa. Gateways act as a Modbus TCP or RTU server device in its Modbus interface, enabling the reading/writing of points from Modbus client devices, and offer the values ​​of these points through its KNX interface, making it act as another KNX device in the system.

Modbus TCP & RTU client for KNX TP:
This section describes the integration of Modbus RTU devices into KNX installations using the application Modbus TCP & RTU client to KNX TP from the Intesis gateway. This integration enables a KNX installation to access signals and resources from Modbus devices as if they were part of the KNX system, and vice versa. Gateways act as a Modbus TCP or RTU client device in their Modbus interface, continuously reading/writing points from Modbus server devices through automatic continuous polling. Gateways offer the values ​​of these points through their KNX interface and act as an additional KNX device in the system.

KNX TP to BacNET server:
This section describes the integration of KNX devices into BACnet MS/TP or BACnet/IP installations using the KNX TP to BACnet server application from the Intesis gateway. This integration enables a BACnet installation to access signals and resources from KNX devices as if they were part of the BACnet system, and vice versa. Gateways act as a BACnet/IP server or BACnet MS/TP device in its BACnet interface, enabling other BACnet devices to make subscription requests (COV) and read/write to its internal points. From a KNX perspective, the gateway emulates a KNX device.

BACnet client for KNX:
This section describes the integration of BACnet MS/TP and BACnet/IP devices into KNX installations using the BACnet client to KNX application from the Intesis gateway. This integration enables a KNX installation to access signals and resources from BACnet devices as if they were part of the KNX system, and vice versa. From a BACnet perspective, the gateway acts as a BACnet client device, meaning it can subscribe (COV) or perform periodic polling and writes to configured BACnet objects. The values ​​of the BACnet points are available via its KNX interface, which makes it work as another KNX device in the system.

Gateway configuration is performed via the configuration tool.

Sizes

100 points, 250 points, 600 points, 1200 points, 3000 points

Updating ...
  • No products in the shopping cart.