OPCClient object configuration General tab

Server node

ServerNode

The name of the node (computer) on which the OPC communications driver is running. If this attribute is blank, the OPC communications driver is assumed to be running on the local node.

Click the Browse button to find the network for the node.

Supervisory, User

Server name

ServerName

The name of the OPC communications driver. The naming syntax for the OPC communications driver varies according to the type.

Supervisory, User

Run server out-of-proc

ServerActivation

If enabled, the OPC communications driver will be run out-of-process. An in-process OPC communications driver runs as a .DLL within the engine process. An out-of-process OPC communications driver runs as a stand-alone executable. The method you choose depends on the methods supported by the OPC communications driver and performance considerations.

To connect to the OPC communications driver in-process, all of the following must be true:

• The OPC communications driver must be installed locally relative to where the OPCClient is installed.

• The OPC communications driver must support an in-process connection.

• The OPC communications driver is not currently running out-of-process.

• The value of the ServerNode attribute must be blank.

• This Run server out-of-proc check box must be unchecked.

Read-Only

Use scan group name as access path

DAGroupAsAccessPath

If enabled, the name of the scan group will be used for the OPC access path. Select this option for OPC communications drivers that require a topic to be specified for the access path. You must then make sure that any scan group you specify is named the same as a topic within the OPC communications driver.

Read-Only

Restart attempts

RestartMax

The maximum number of times that the OPCClient object should attempt to restart a failed OPC communications driver. Once RestartMax is reached, no more restart attempts are made until RestartReset is set.

Supervisory, User

Restart period

RestartPeriod

The time period, in milliseconds, between restart attempts. If RestartPeriod is set to 10000, the OPCClient object will attempt a restart every 10 seconds. If RestartMax is set to 3, that means that no additional restarts are attempted after 30 seconds.

Supervisory, User

Detect restart alarm

RestartAlarm.Alarmed

If enabled, an alarm will be triggered when the number of attempts to start the OPC communications driver has exceeded the allowed maximum within the restart period.

None

Priority

RestartAlarm.Priority

See Alarm attributes.

Supervisory, User

Connection heartbeat period

ConnectionHeartbeatPeriod

The time interval, in milliseconds, at which the OPCClient object will check the connection to the OPC communications driver.

Supervisory, User

Detect connection alarm

ConnectionAlarm.Alarmed

If enabled, an alarm will be triggered when the OPCClient object can no longer communicate with the OPC communications driver.

None

Priority

ConnectionAlarm.Priority

See Alarm attributes.

Supervisory, User

Restart reset security

RestartReset

Used to set security for restarting the OPC communications driver.

Supervisory, User