Building management software 
for medium-sized and enterprise building automation projects

The standard OPC solution for KNX: NETx KNX OPC Server

 

With the NETx KNX OPC Server you have access to KNX networks, KNX devices and their data points. As OPC Data Access 2.0 server, KNX data points (KNX group addresses) are mapped to OPC items which can be accessed by any OPC client. Moreover, it is possible to add additional control functionality, that is not available in the KNX system. For this, server tasks, timers, response events and scripts are available. Through its powerful and scalable server engine, the NETx KNX OPC Server is a reliable standard solution for every KNX project. By using the user friendly NETx KNX OPC Studio and the integrated ETS import, the configuration is quite simple. The standardized OPC interface allows to integrate KNX data points into visualizations or other management clients.

NETx KNX OPC Server

Functions

Performance
The Unified Driver version of NETx KNX OPC Server uses KNXnet/IP tunnelling to connect to the KNX network and its data points. When using several KNXnet/IP routers or interfaces,  the data throughput increases as the NETx KNX OPC Server communicates parallel with each KNXnet/IP device. Changes in data and other network telegrams are sent in specific time intervals to the KNXnet/IP devices. In this way, it is ensured that the maximum bandwidth of the KNX TP1 medium is not exceeded. Therefore, a high data flow is possible without overloading the network. More than 100,000 group addresses in one project are realizable with a single NETx KNX OPC Server.
Scalability
The KNX group addresses are extended by the IP addresses of the KNXnet/IP routers or interfaces. Therefore, the group address space behind each KNXnet/IP router or interface can be re-used. This feature gives you the opportunity to run several KNX installations with separated ETS projects on one single NETx KNX OPC Server.
Adding functions
By using server tasks, timers, response events and LUA scripts, missing functionalities can be implemented in the NETx KNX OPC Server. In addition to physical data points, Custom Items can be generated. Those can be used like standard data points, but they only exist in the server virtually. Furthermore, you can create user-defined data structures.
Monitoring

The extended NETx KNX OPC Studio allows the monitoring of network telegrams and data points. In addition, the connection state of all KNXnet/IP routers/interfaces and the status of the server (Online/Simulation, Main/Backup, Active/Standby) can be monitored and used as OPC items. These OPC items can be used like any other data point (e.g. within a visualization).

Management client connection
The NETx KNX OPC Server has a standardized OPC Data Access 2.0 interface. Via this interface, any OPC client can connect to the NETx KNX OPC Server. The number of OPC clients is not limited. Also, the proprietary VNET protocol is supported which provides an easy connection to the NETx Voyager without the need for Windows DCOM.
Main/backup
For highest redundancy, the NETx KNX OPC Server can also be integrated into a main/backup solution (see BMS Server)

Versions and license types

Unified Driver
Driver: NETxAutomation (KNXnet/IP tunnelling)
  • Connection to KNX networks via KNXnet/IP routers and/or KNXnet/IP interfaces
  • Supported protocols: KNXnet/IP tunnelling, ABB IG/S, b.a.b-tec (eibNode)
  • Active monitoring of availability of physical devices
KNXnet/IP router or interfaces: 1 Product-ID: S03.03.5.20.01
KNXnet/IP router or interfaces: 3 Product-ID: S03.03.5.20.03
KNXnet/IP router or interfaces: 5 Product-ID: S03.03.5.20.05
KNXnet/IP router or interfaces: 10 Product-ID: S03.03.5.20.10
KNXnet/IP router or interfaces: 20 Product-ID: S03.03.5.20.20
KNXnet/IP router or interfaces: 32 Product-ID: S03.03.5.20.32
KNXnet/IP router or interfaces: >32 Product-ID: S03.03.5.20.xx
 
Direct(KNX)
Falcon Driver - KNX Association
  • Connection to KNX network via USB, KNXnet/IP router or interface
  • Supported protocols: KNXnet/IP tunnelling, KNXnet/IP routing, USB
  • Falcon Driver is integrated
  • Only for one interface to KNX
  • Suitable for small KNX projects
KNX interface: 1 Product-ID: S03.03.5.10.01

 

 

download Software  |  Documentation  |  Product data sheet Request

 

 

 

 

System requirements:

PC: Intel or AMD - 1.8 GHz (multi-core recommended), 4GB RAM, Hard disk: 16 GB (32 GB recommended), Ethernet interface: 100 MBit/s
Operation system: Windows 7 - SP 1 (32 bit | 64 bit), Windows 8 (64 bit) | Windows 8.1 (64 bit), Windows 10, Windows Server 2008 R2 (32 bit | 64 bit), Windows Server 2012 | 2012 R2 (64 bit)