OPC UA Client OPC UA Client

OPC Router is a graphical OPC Client for OPC UA and OPC DA

The first version of the OPC standard was published in 1994 and since then has been widely developed and distributed. OPC provides a general standard for access to automation components.

The OPC Router can act as an OPC UA/DA client and can read and write data from OPC servers and couple this data with various systems (see image). The OPC servers are supplied either by the manufacturer of the automation component itself or by third-party manufacturers. With the new OPC UA (Unified Architecture) standard, it is now also possible for the first time for automation devices to implement the standard themselves on their own, non-Windows based platforms and thus serve as OPC UA servers themselves (e.g. WAGO PFC-200 or S7-1500). Common OPC server software products are the Kepware OPC Server (various drivers), Siemens OPC Server, Matrikon, Softing (also known as INAT OPC Server), etc..

Take a look at our tutorial video about the easy transfer of OPC data into CSV format.

Run a free test now

Example of a connection as OPC UA Client:

Example of a connection as OPC UA Client:

That’s how easy it is.

Connecting Systems

What's Transfer, Trigger and Browsing?


The transfer object of the OPC UA Client plug-in allows access to the data points of the OPC Server.

Data Points

The OPC standard defines the structure and organization of data points. Each data point has a unique name. As an OPC client, the OPC server provides the current value, the associated time and the quality of the value (device connected, no connection, etc.).
The desired data points are selected via browsing. These are available in the transfer object of the graphical configuration and can be connected to other fields during the transfer.


The OPC UA Client Plug-in includes several triggers.

DataChange Trigger

The datachange trigger is configured for an OPC data point and triggers the transfer when the data point changes.

Limit Trigger

The limit value Trigger monitors a data point for compliance with limits. It can be checked for exceeding or falling short. A hysteresis can also be set.

Bit trigger

Handshakes are often implemented for data transfers. The bit trigger is the simplest variant here. The OPC router checks whether a bit requests a transfer. Once transferred, the bit is optionally reset or another bit is set as response. The success of the transfer can be transferred to another data point.

Message Trigger

The message trigger is the further development of the bit trigger in the form of telegram data exchange. Here not a bit is checked, but a counter is checked for a value change. In response, the number that triggered the transfer is written back after the transfer.
The reliability and traceability of this exchange is significantly higher.


The OPC UA Client Plug-in can browse the data points of the OPC server.

Data Point Hierarchy

The OPC Standrad defines the possible ways to read data points. The standard is the hierarchical structure in form of a data point tree. The OPC Router reads all data points as a tree and displays them to the user. In this form, even large datapoints are easily accessible. Each data point is identified via the unique path and is taken over including type information.

OPC UA Client Plug-in Application Examples

Provide the PLC with data and decisions

PLCs have the task of controlling complex machine sequences and processes in automation. More and more, however, decisions have to be made in the process based on data from other systems. For example, products are produced individually according to customer requirements. The customer-specific parameters are stored in databases. The PLC can trigger a transfer of these special production parameters via the coupling with OPC Router. OPC Router reads the corresponding selection criteria from the PLC via OPC UA (e.g. order number), loads the data from the database and writes them via OPC UA to the PLC. The standard “OPC” allows the OPC Router to do this with any controller type and other OPC compatible devices.

Symbol Arrows
SQL Symbol
OPC UA Smybol
Symbol Arrows
Symbol Cloud

Edge Computing with OPC Router as OPC UA Client

Industry 4.0 thrives on networking. At the field level, the OPC protocol has long established itself as the leading protocol for data exchange. More and more devices can provide their data directly via OPC UA. In addition, OPC servers with many driver implementations, e.g. Kepware OPC Server with over 160 drivers, ensure that the majority of automation devices can be accessed via OPC UA. The OPC Router can be used with its OPC UA Client Plug-in as an edge computing unit by connecting the available OPC data sources in the local network, pre-processing and buffering data (via SQL database), and then transferring it to higher-level systems (e.g. SAP) or via MQTT to the cloud. This is, of course, bidirectional, so that data from the cloud can also be sent to the devices and controllers via this way.

Video tutorial: Easy transfer of OPC Data into CSV Format

This video tutorial shows how easy it is to read process values out of an OPC UA server and save them into a CSV file. The process values are read on data change and create a new record set into an existing csv file (or creates a new one, if one already exists). Just connect OPC UA data points, CSV document and create corresponding CSV file simply via drag & drop.

Here you will find further information
about OPC Router and Plug-ins.

Run a free test now