OPC Client Driver Tags
By adding OPC client driver tags to your application, you are able to communicate with OPC servers on your network, whether those are other VTS applications, control equipment or other programs. The OPC interface allows for two-way communication, thus you can go on to add both input and output tag types that exchange information with the OPC server through the OPC client drivers you configure.
Note: If you have used the OPC client driver in versions of VTS prior to 8.1, you may expect to see a field for the Automation ProgID. With the introduction of Trihedral's own OPC Automation DLL, which is used by default, you no longer need to provide this information.
If updating an older application that did include Automation ProgID information, the existing id will still be used, but will not be visible in the tag's configuration dialog.
The characteristics of the OPC Client driver are described in the table below.
OPC Client Driver Characteristics
Tag Browser Name: OPC Client Driver
Database Table Name: OPCClientDriver
Type: Driver
Tag Group Memberships: Drivers, Numeric
Log Enabled Variables: see Communication Driver Log-Enabled Variables
Native Drawing Methods: OPC Client Driver Tag Drawing Methods
OPC Client Driver Tag Type Properties: ID
Tab