OPC UA Client Connector

Clients compatible with OPC UA specification.

Overview

PC UA Client implements communication with local and remote OPC Servers. The communication blocks are dynamically created according to the pooling cycle defined on the Access Type for each Device Point.

OPC UA Certificate Configuration

UA security relies on X.509 Certificates. Every UA server and client application must have its own certificate containing the application’s ApplicationUri.

By default, UA servers can be configured to run with certificate validation disabled. In this mode, any valid certificate is accepted, regardless of whether it matches the application. To enable this behavior, select the Disable Security checkbox.

For OPC UA Clients, there are two ways to generate client certificates:

• Default Method – Generates a certificate using default values.

• Custom Method – Allows full configuration of certificate parameters.

Default Method

This certificate creation method uses pre-defined parameters for the certificate. These parameters are described below.

• Application Name:  TRunModule
• Organization Name: Tatsoft
• Domain Name: Domain name for the certificate validation
• Issuer Key File: Private Key from the certificate, it is, a secret number that only the certificate holder knows (Not obligatory)
• Issuer Password: It is the Private key numbers from the Issuer Key File. (Not obligatory)
• KeySize: Rsa1024
• Hash Algorithm: Sha1
• LifeTime: 12 Months
• Server Certificate: Add the Server Certificate

In Devices → Nodes, the user can access this feature by clicking the Default button. The certificate will automatically be saved in the /ProgramData/?ProductName?. Click the Test button to check the connection.

The Client certificate should be imported / trusted on the OPC Server side.

Custom Method

In Devices → Nodes, the user can access this feature by clicking the Custom button. The ClientCertificateHelper application should open. Fill the input fields and save the certificate file.

The Server certificate should be imported / trusted on the OPC Server side.

To Save

After clicking OK, save the two folders in the software platform installation folder where you can find the Certificate and the Issuer Key. They are in "C:\Users\Public\Documents\FrameworX\MachineSettings\Certificates\own\":

• "certs": In this folder will be the certificate.
• "private": In this folder will be the "Private Key", it is, a secret number that only the certificate holder knows.

Channel Configuration

Protocol Options

There is no channel configuration required for OPC UA Client channels.

Node Configuration 

Station Configuration

The station parameters are:

• Service URL: Defines the location of the OPC E.g.: opc.tcp://127.0.0.1:49300
• Domain: String containing the domain for security credential.
• UserName: String containing the user name for security credential.
• Password: String containing the user password for security credential.
• Windows Authentication: Flag indicating if Windows Authentication security should be used.
• Disable Security: Flag indicating if security is disabled. (Security Policy set to None in OPC Server).
• Refresh Rate: The OPC UA Server checks for changes in the tag value at a defined interval in milliseconds. Once the change is detected, the OPC UA Client is notified and updates the corresponding value. We have this configuration because if you want faster updates, you can change it as long as the OPC UA Server supports a higher update rate. This is a refresh rate between the OPC Server and the device on the field. Default is 500ms.
• All Items Same Group: Flag indicating if the driver should add all items to the same OPC group, and only one connection is created with the OPC Server.
• Enable Read Pooling: By default, OPC uses read by exception. When this setting is enabled, Read Polling is used, and the polling interval is defined in AccessTypes.
• Read From Device: Force all reads made from device.
• Use Timestamp From Computer: Use timestamp from computer instead of device.

You can use the Discovery button to search for the OPC Servers located in a specific IP address and port. If the port number is left empty, the utility will look for Servers on pre-defined ports (4840, 49320, 62841, 4845, 49380).

Importer Tool

You can import existing variables directly into your Project by clicking the Import Button.

With this tool, you can choose which Branch from the OPC Server namespace will be accessed and filter the variables that will be imported. The Tags and Points will be created automatically.

Point Configuration

Address

Choose the OPC Server item that will communicate with the Project Tag. You can type the OPC Server item name into the textbox, or you can browse the OPC Server items in the Cell Editor.

For OPC Array DataTypes, you should add the Array Element of index 0 to the TagName field and set the Array field under the Modifiers column to match the array size.

For automatic address mapping when using arrays in your project and addresses in OPC Server that follows the syntax: ItemName[0 ... n], you can add the Main Array element without index in the TagName column.

TagProvider

This Communication Protocol supports the TagProvider feature, which is a tool that allows you to access your Communication Device Data Model without creating any Project Tags.

For more information, please refer to the Tag Provider document. 

How to Configure

To configure the OPC UA protocol as a TagProvider, go to Edit → Tags → Providers, and create a new provider for the CanaryLabs protocol.

Configure the items under the PrimaryStation column the same way that was described in the Node Configuration.

Troubleshoot

The status of the driver execution can be observed through the diagnostic tools, which are:

• Trace window
• Property Watch
• Module Information

Status value of 0 (zero) means communication success. Negative values indicate an internal driver error and positive values means protocol errors code.

Driver Revision History

In this section...