Check the fit for your KNX and SCADA project

• KNXnet/IP UDP tunnelling, or KNX IP Secure TCP tunnelling.
• IP Secure credentials can be entered manually or selected from a .knxkeys file.
• Import supported ETS5/ETS6 .knxproj files or create points manually.
• Multiple KNX/IP connections can be configured. Each tag belongs to a connection in its project.
• KNX Data Secure and KNXnet/IP Routing are not supported. KNX IP Secure protects the tunnel; it does not add support for KNX Data Secure.

Each published tag links a KNX point to an OPC UA variable. The client receives the value, quality and timestamp. Commands are available for command tags whose write access and confirmation method have been configured by the engineer.

Renaming a tag or changing its folder or group address within the same project preserves its NodeId. Changing the OPC type of a published tag requires a replacement tag with a new NodeId and an updated SCADA binding.

After a KNX connection is lost, the last value is no longer reported as current good data. Commands are not automatically replayed after reconnection.

Supported scalar DPTs include families 1, 9, 14 and 20, plus 5.001, 5.010, 6.001, 6.010, 7.001, 8.001, 12.001, 13.001, 16.000 and 16.001. Specify the exact DPT for each point in ETS or in ZVENO.

SCADA connects as an OPC UA client. The server uses SecurityPolicy None and SecurityMode None, without message signing or encryption. Use a protected network segment and a VPN for remote access.

Provide the server endpoint and the NodeIds of published tags to the SCADA engineer. Applying configuration restarts KNX connections and the OPC UA server; agree a maintenance window and client reconnection beforehand.

The gateway runs on the project network. A customer-owned Linux computer can be assessed as an alternative to hardware delivery.

The gateway configuration interface is currently in Russian. An English- or Arabic-speaking manager coordinates project discussions with our engineer.