This document has only the specific information about the device connection settings and its address syntax.

Refer to the User Guide for more information on the Device Module.



Summary

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

Communication Driver Information
Driver nameOPCHDAUA
Assembly NameT.ProtocolDriver.OPCHDAUA
Assembly Version1.0
Available for LinuxFalse
Devices supported 

Any OPC HDA server compatible with OPC UA specifications

ManufacturerOPC Foundation
ProtocolProprietary over TCP/IP
PC RequirementsOPC Core components


NOTE

You can find the OPC Core components in the OPC Foundation web site.


OPC UA Certificate Configuration

  • The UA security bases on X509 Certificates.
  • Each UA server and client application requires a certificate with the application's ApplicationUri. UA servers can be typically configured for the certificate validation to be disabled. In this mode, any proper certificate is accepted. It does not need to match the application.
  • Self-signed certificates can be created with the uaPLUS UaClientConfigHelper utility.
  • OPC UA maintains certificates in the Windows Certificates Store. The certificates are by default in the stores LocalMachine\UA Applications and LocalMachine\Trusted UA Applications.
  • The stores are defined in the application UA configuration and can be changed if necessary.
  • The UaClientConfigHelper utility creates and imports certificates into the stores defined in the configuration.

To create certificates so that Manager and Device Module work with OPC UA:

  1. In Windows Explorer, open the installation folder
  2. Run UaClientConfigHelperNet4.exe utility (right-click it and choose Run as Administrator);
  3. Inside UA Client Configutaration Helper, click Browse and select the TManager.exe file inside the product installation folder.
  4. Click Create UA Configuration;
  5. Click Edit UA Configuration;
  6. Click Certificates;
  7. Click Create and then OK;
  8. Click Save and Close;
  9. Click Done to close;


NOTE

Repeat the same steps to TRunModule.exe application.


  • Server and Client on the same machine: the certificates are in the right place when created or imported with the UaClientConfigHelper utility.
  • Server and Client on different machine: the following steps are required:
  1. On the client machine, create a certificate for the client application with the UaClientConfigHelper utility. The created certificate is automatically exported into a .DER file in the directory of the utility.
  2. Copy the client certificate .DER file to the server machine and import it according the UA server documentation.
  3. Copy the server .DER certificate file to the client machine and import it with the UaClientConfigHelper utility.


NOTE

The Windows Certificates manager can be used to check and maintain the certificates beyond the capabilities of the UaClientConfigHelper utility.

Channels Configuration

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



Nodes Configuration

Station Configuration

  • Service URL: Defines the location of the OPC HDA Server. Example: ua:opc.tcp://127.0.0.1:62841/Advosol/uaPLUS.
  • Domain: String containing domain as security credentials.
  • UserName: String containing user name as security credentials.
  • Password: String containing user password as security credentials.
  • WindowsAuthentication: Flag indicating whether it should use Windows Authentication security.
  • DisableSecurity: Flag indicating whether security is disabled.

Points Configuration

Choose the OPC HDA Server item that will communicate with the tag.

You can type the OPC HDA Server item name into the textbox, or you can browse the OPC HDA Server items with the cell editor.



Troubleshoot

Please, consult your OPC HDA Server documentation for the protocol specific error codes.



Driver Revision History

OPCHDAUA Revision History
Version Notes
1.0Initial release on new documentation standards.

In this section...

  • No labels