Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA Enterprise SCADA

Open Platform Communications (OPC) Row Edit: Main tab

Open Platform Communications (OPC) Row Edit: Main tab

  • Last UpdatedApr 24, 2025
  • 2 minute read

The Main tab on the opc Row Edit dialog box is used to configure the Open Platform Communications (OPC) client frequency time and enter the OPC server’s name and host name.

Refer to the table below for descriptions and instructions on how to configure the tab.

Items on the Main Tab in the opc Row Edit Dialog Box

Item

Description

Name

This field displays the name of the opc record.

Group

This field indicates the group to which this record belongs.

Dataset

This field indicates the dataset to which the record is assigned. Datasets are used to associate the record with privileges assigned to each system mode. Once a record is assigned to a dataset value, the dataset can only be changed to a value for which the system has a privilege record.

Host

Enter the host name of the computer where the OPC server is running. If the OPC Client is on the same host as the OPC server, the host value should not be assigned.

Server

Enter the OPC server name. This should be the name that is registered in COM+ on the host computer.

Heartbeat

Enter the minimum frequency time (in seconds) for the OPC Client to send the heartbeat message to the AVEVA Enterprise SCADA host. The heartbeat message is only required if there is no other data to be sent. If the AVEVA Enterprise SCADA host does not receive any valid message in 2.5 times the Heartbeat value, the system disconnects the connection and generates the alarm.

Notes: The heartbeat message is used to determine the health state of the OPC Client application and its connection to the OPC server. If no alarm in relation to the health state occurs, there is no need to change the heartbeat to a value lower than what is already configured. However, if you do change the setting, you may need to manually initialize the OPC remote by either placing the remote offscan and then onscan, or sending an fnput remote.<opc remote> initialize command.

If Heartbeat is set to 0, the OPC Client does not send a heartbeat message.

Auto Update Group

Select to automatically perform an init when the group definition changes.

Note: Each enabled group is defined on an OPC Server, but only groups that are set up as active will send data back to the AVEVA Enterprise SCADA host.