The OPC interface enables data exchange between ibaPDA and one or several OPC servers via OPC variables. Supported standards are DA 1.0 and DA 2.0.
Note |
|
|---|---|
|
The OPC UA interface is a licensed interface and is described further below in the Ethernet-based interfaces chapter. |
|
In order to make the measured signals available to other users in the network, ibaPDA serves also as an OPC server. Generally, all active signals are available via OPC.
Moreover, there are OPC server modules available containing signals, which can be written by other OPC clients. A maximum of up to 1024 modules are supported per interface.
The OPC interface of ibaPDA supports redundant OPC servers.
Note |
|
|---|---|
|
It is recommended to install .NET Framework 4.5 for a reliable function of the OPC connections. |
|
Basic settings for the OPC interface
Click on the OPC interface in the I/O Manager tree to select several options.

Start acquisition even if an OPC server is not accessible
Enable this option in order to prevent blocking of acquisition when OPC client modules are configured for measurement but not available at start of acquisition. After starting the acquisition, ibaPDA will continuously try to reach the OPC server. As soon as there is access to the OPC server, ibaPDA will establish the connection during the measurement.
Enable OPC connection timeout of … s
Enable this option and enter a time value if you want to specify the time allowed to elapse for enforcing a connection to the OPC server. After this time elapsed, ibaPDA will not attempt to connect to the OPC server until next start of acquisition.
Set OPC output items to zero when the acquisition is stopped
If you enable this option, then the values of OPC output items will be set to zero when the acquisition is stopped. If this option is disabled, the OPC output items keep the last actual value they have had at the moment of acquisition stop.
Ignore unavailable OPC items
If you enable this option, OPC items, which are not available at start of acquisition will be ignored and the acquisition still starts. If this option is disabled, the acquisition will not start unless all OPC items are available.
General properties
You can define any number of OPC modules in the OPC interface in the tree of the I/O Manager. Each client module can communicate with a different OPC server.
The data transmission from an OPC server to the ibaPDAsystem requires some preconditions:
-
Both computers, the one running the ibaPDA server and the one running the OPC server, should be logged on to the same domain or work group.
-
On both computers, the same user account with the same user name and password should be configured. Administrator rights are required for both machines.
-
Furthermore some of the DCOM settings must be checked and configured to guarantee for an adequate OPC communication. These settings are only relevant for the ibaPDA server PC, not for the ibaPDA client PC.
For the selection of the OPC signals to be measured, an OPC browser is available in the OPC module dialog.
Available modules
-
Module type OPC client, see OPC Client module
-
Module type OPC server, see OPC Server module
-
Module type redundant OPC client, see Redundant OPC client module
For more information about superordinate OPC settings, see OPC server.
Other documentation |
|
|---|---|
|
For additional information about security settings and DCOM configuration, please refer to the OPC connection configurations guide. This document is available on the "iba Software & Manuals" data medium and in the download area of the iba website. |
|