Description

Both OPC UA client and OPC UA server modules can be configured on the OPC UA interface.

In order to use OPC UA client modules, you need an ibaPDA-Interface-OPC-UA-Client license.

To use OPC UA server modules, you need an ibaPDA-OPC-UA-Server+ license.

With an OPC UA client module, ibaPDA connects to an OPC UA server to receive data. ibaPDA is not cyclically polling for new data. Instead, ibaPDA will be notified by the OPC UA server whenever at least one of the values to be measured has changed. ibaPDA can only read and not write the variables provided by the OPC UA server.

An OPC UA server module can be used to write the variables provided by an OPC UA server.

With an OPC UA client interface license, up to 16 connections can be configured per license. A total of a maximum of 256 connections can be implemented by the additional purchase of up to 15 further one-step-up OPC UA client licenses.

You can import or generate the certificates required for the communication between OPC UA client (ibaPDA) and an OPC UA server in ibaPDA.

The signals to be measured can be conveniently selected using their symbolic names with support from the OPC UA Symbol Browser. This allows access to all measurable symbols, which are defined in the OPC UA server.

The acquisition of current values is supported.
Interface configuration

The interface itself has the following features and configuration options:

Set all values to zero when the connection to an OPC UA server is broken.

If this option is enabled, all the measured values of an OPC UA server affected are set to zero as soon as the connection is lost. If this option is disabled, ibaPDA keeps the last valid measured value in the memory at the time the connection was lost in the memory.

Start acquisition even if an OPC UA server is not accessible.

If this option is enabled, the acquisition will start even if an OPC UA server is not accessible. In case of an error, a warning is indicated in the validation dialog. If the system has been started without a connection to a configured OPC UA server, then ibaPDA tries to connect to this server at regular intervals. As long as the OPC UA server is not connected, the measured values stay at zero.

Allow inaccessible symbols.

Enable this option to start the acquisition even if no symbols are accessible. The inaccessible symbols are issued as warnings in the validation dialog box. This can only occur if a symbol, whose address is requested by ibaPDA from the OPC UA server, is no longer available on the server. The OPC UA server then issues an error.

If you enable this option, ibaPDA ignores this error message and starts the acquisition anyway.

Measurement will not start when inaccessible symbols are present if you do not enable this option.

Connection table

The table shows the error counters as well as the response times (actual value, average, min and max) of each connection during the data measurement. To reset the calculated times and error counters to zero, simply click on the <Reset counters> button.

Button <Open log file>

If connections to OPC UA servers have been established, all connection-specific actions are logged in a text file. Using this button, you can open and see this file. In the file system on the hard disk, you will find the log files in the program path of the ibaPDA server (…\Programs\iba\ibaPDA\Server\Log\). The file name of the current log file is OpcUAClientLog.txt, the name of the archived log files is OpcUAClientLog_yyyy_mm_dd_hh_mm_ss.txt.
Available modules

  • OPC UA Client (ibaPDA-Interface-OPC UA-Client license required)

  • OPC UA Server (ibaPDA-OPC UA-Server+ license required)
Product name

ibaPDA-Interface-OPC-UA-Client (Art. no. 31.001111)

ibaPDA-OPC-UA-Server+ (Art. no. 30.670051)