The communications blocks are dynamically created according the pooling cycle defined on the Access Type for each Device Point.

Summary Information

Communication Driver Name: OPC HDA Client

Implementation DLL: T.ProtocolDriver.OPCHDA.dll

Protocol: OPC HDA proprietary

Interface: OPC HDA proprietary

OPC servers supported: Any OPC HAD server compatible

Protocol Options: None

Max number of nodes: User defined

PC Hardware requirements: None

PC Software requirements: OPC Core components


Note

You can find the OPC Core components on the OPC Foundation website.


Channel Configuration

There is no channel configuration for OPC Xml/DA Client channels.


Node Configuration

Station Configuration

HDA Server: Defines the OPC HDA Server. If HDA Server is running on a remote computer, you should include the computer name. Ex: \\SERVER\ Advosol.HDA.Net4.Test.5

Domain: [Optional] The Domain when connecting to a remote computer

User name: [Optional] The User name when connecting to a remote computer

Password: [Optional] The User password when connecting to a remote computer


Point Configuration

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

You can type the OPC HDA Server item's name into the textbox, or you can use the cell editor to browse the OPC HDA Server items


Troubleshoot

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

• Trace window
• Property Watch
• Module Information

The above tools indicate if the operations have succeeded or have failed. A status of 0 (zero) means communication is successful. Negative values indicate internal driver errors, and positive values indicate protocol error codes.

Consult your OPC HDA Server documentation for the specific protocol error codes.


  • No labels