This Website is using cookies to improve your user experience and our service. By using this website you agree the use of cookies.


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.



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.



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.


For highest redundancy, the NETx KNX OPC Server can also be integrated into a main/backup solution.

System requirements

PC: Intel or AMD - 1.8 GHz (multi-core recommended), 4GB RAM, Hard disk: 32 GB (64 GB recommended), Ethernet interface: 100 MBit/s
Betriebssystem: Up to Windows 8.1 or Windows Server 2012. On higher Windows and Windows Server versions, we can not guarantee stable functionality of the server. However, due to limited future support for these operating systems by Microsoft we will not be able to provide full support for our software running on these systems.