NETxKNX OPC Server 3.5

The OPC Server 3.5 is the logical further development of the established verion 3.0. New functions and features are implemented and the protocol management for the gateways is designed new.

With the UnifiedDriver variant it is now possible, various IP Router or IP Gateways using parallel in a KNX plant. The big advantage for the customer is, he can extent existing structures with various IP gateways without any problems. It is not necessary to adapt the existing structures and make changes on it.

The simplified applicability and the configuration of the system can easily be used from every project integrator.

The system allows the control and - in connection with an applicable OPC client - the visualisation of EIB/KNX plants. It builds a connection between the world of EIB/KNX and other systems. .

Also the security for OPC Server structures is extended, Main / Backup solutions or cluster definitions with more OPC servers are possible on a very easy way.

In combination with the NETxLAB OPC Bridge datas from OPC Server in other networks (LON, BacNet, ...) can be receive or send to control the foreign network.

The OPC Server is available in following versions:

• NETxKNX OPC Server 3.5 UnifiedDriver
• NETxKNX OPC Server 3.5 Direct(KNX)

Customers in over 30 countries had decided to use our NETxKNX OPC Server.

The experience and the know how out of the large projects was used during developing the large amount of new systems. So the system has been realised in a very reliable, open and user friendly way.

The OPEN OPC Server includes a form of the NETxKNX MultiProject kernel which is used in large projects.

Example of an OPC Network structure:

The main features:

•     Up to 1000 gateways can be administrated
•     All officially used EIS data types are supported
•     Up to 100.000 data points
•     Enormous data transfer - up to 1.000 telegrams per second (EIB/KNX)
•     MultiProject center - up to 32 ETS projects in a plant
•     Workspace Management - many workspaces can be managed
•     Event Processor
•     Link Manager
•     EIB/KNX Telegram Overflow Manager
•     Real Database Refresh - the update of the OPC Server data baseis carried out automatically
•     Gateway Manager - supplemented gateway administration
•     Extended NETxKNX MP Open OPC Studio
•     Additional address space - the real address of the data point consists of the logical EIB/KNX address and the IP address
•     Data recording in the ring storage - up to ten million sent or received telegrams are stored in a separate LOG-data
•     Process drawing of the whole system is also stored and will be loaded automatically when starting
•     On line check of the consistence of all linked gateways
•     Real-time view of the telegram traffic with clear text description and further information
•     Reliability - for continuous operation designed and developed
•     Performance optimization
•     OPC Foundation Compliance Tool tested

•     UnifiedDriver – the OPC Server can use all IP Gateway Types parallel (also various types in one workspace)
•     Device Monitor – the physically addresses (devices) are listed as individual Datapoints and can used directly in the OPC clients
•     Physically addresses – the Datapoints for physically addresses can have now alias names
•     New Datatyps – UI4 and UI8 allow data transfer of various values to the OPC Clients
•     N-Mesh Routing – routing of data and telegrams between OPC Servers
•     Redundant – allow coupling of two OPC Servers and build up a redundant System
•     Extended NETIP Tunnelling Engine – the new version of the NETIP driver monitors and avoids possible telegram lost
•     OPC Studio – new configuration tool for the system, router and N-Mesh parameter are available
•     OPC Tree shown more information e.g. the status of a Datapoints ort he actual value
•     Software protection – the system detect automatically an USB Dongle or valid softlock license (no different program versions for hardlock and softlock)
•     New licensing – up to 1000 IP Gateway versions can be direct addressed
•     Demo mode - Not registered software can be tested continuously 30 days (no breaks after 30 minutes)

Generell features:

•     Workspace Management- several workspaces can be easily managed.
•     Event Engine - cyclic (Cyclic Event), time related (Timer Event) and/or event related (Response Event) actions can be defined in the OPC Server.
      Cyclic events can be used for querying the actual values of certain Group Addresses in defined time intervals - (e.G. electricity power meters).
      Response Events make possible router functionality.  So certain KNX telegrams can be automatically forwarded to different  gateways or their values can even be routed to different addresses.
•     Link Manager - the management of linked group addresses can be immediately realized within of the OPC Server, and therefore the CPU loads of the connected OPC Clients are considerably reduced.
      The OPC  Server sets all values of the linked group addresses automatically and also informes  all connected OPC Clients about that.
•     Real Database Refresh - the updates of the OPC Server database are carried out automatically within the cyclic KNX read telegrams. This guarantees that the data base has always the actual values.
•     KNX Telegram Overflow Manager - the OPC Server watches about a good telegram flow, so that the KNX is not be overloaded. So the telegrams are sent in defined time intervals to KNX to guarantee the   
      maximum data transfer of the KNX. If several gateways are connected to the system , the max. data transfer is multiplied with the count of the gateways: with 10 gateways the system can achieve about 100 
      telegrams per second, with 32 - 320 telegrams per second.
•     No data point limit - so  100.000 and more data points can be managed.
•     Up to 32 ETS Projects in a single workspace - as the KNX group addresses in the NETxKNX OPC System are extended by the IP Adresse of the gateway, the same ETS structures (logical address ranges) 
      can be used after each gateway. The logical address range of an KNX plant is extended and address collisions  can not occur anymore.
•     Extended OPC Studio:
      telegram monitoring with plain text description and extended filter functionality
      data point monitoring
      Direct Import of ETS(c) projects
      Gateway Monitor
      direct Excel- Export/Import of all definition tabels
•     Displays unreachable devices - physical KNX devices can be checked for unattainability. The server generates a list of unreachable KNX devices.This list can be queried by every OPC Client by data point.
•     OPC Foundation specification OPC Data Access Server 2.05b compliant
•     OPC Fundation Compliance Tool tested (test results available)