The OPC tab for the OPC Client driver tag properties folder consists of attributes used to identify and establish a connection to the control device to be associated with this driver. The OPC tab for an OPC Client driver is also used to identify the remote server node that the driver should use to transmit data.

(Click title to expand text)
The Server Prog ID field enables you to specify the program identifier for the OPC server to which you wish to connect. It may be:
• A string of the form Manufacturer.OPC.ServerType; or
• The corresponding VTS GUID (Globally Unique Identifier) (e.g. {F8582D24-88FB-11D0-B850-00C0F0104305}). For information on GUIDs, see VTS File Types: GDI.WIF
Examples of a Server Prog ID are: Trihedral.VTSOPC.DA or Matrikon.OPC.Modbus.
Note: The OPC Server vendor generally supplies the Server Prog ID; please refer to your OPC Server manufacturer's documentation for the correct details.
Use this field to specify the name of the workstation that is acting as the OPC server. The Remote Server Node field can be left blank in the event that the local workstation is the OPC server.
Analog Deadband (% of full scale)
The Analog Deadband spin box enables you to indicate a percentage by which analog values must change before a change in value is reported. If the percentage is 0, the updates will be event driven, occurring on each value change.