Remote Row Edit: Main tab

Name

Select (...) and select the name of the remote record from the Remote Select dialog box.

Description

Enter a description of the record. The Description can be up to 47 characters in length. This field is for information purposes only and can be used to describe the record, its association with other points, or any other textual information. The Name and Description configured for a record appear in the summary tables in easy eXtended Operator Station (ezXOS).

Protocol Record Edit

Select to open the Row Edit dialog box for the protocol associated with the remote.

Group

Select (...) and select the name of the group this record belongs to from the Group Select dialog box.

Dataset

Select (...) and select the name of the dataset you want to associate with this record from the Dataset Select dialog box.

A dataset contains privileges assigned for each system and mode. Once a record is assigned to a data set value, the dataset can only be changed to a value for which the system has a privilege record. A record’s dataset can not be changed in such a way that the system can no longer access the record.

Station

Select (...) and select the name of the station you want to associate with this record from the Station Select dialog box.

For further information, refer to the RealTime Controller documentation.

Point Class

The point class category contains multiple configuration enumerations used for categorical configuration of points.

For further information, refer to Configure msginfo sets.

Message

Select (...) and select the message associated with the record from the Message Select dialog box.

The default message for a remote is Remote Terminal Unit (RTU).

Mapping Flag

Enter the 32-bit integer value to map this point to a non-AVEVA Enterprise SCADA system.

For further information, refer to Map points with other systems.

Priority Display

Specify the graphic you want to be associated with the priority display button on an ezXOS Control dialog boxes.

RTU Test Mode

Select to place the RTU into Test Mode.

For further information, refer to Remote Terminal Unit (RTU) Test Mode.

Note: The RTU Test Mode application is not related to Test Mode Set functionality. For further information on Test Mode Set functionality, refer to Test Mode Set table.

Protocol

Select (...), and select the name of the protocol used for communication between this remote and the host. The select dialog box lists all of the available protocols assigned for your project.

Note: The same protocol must be defined at both ends of the communication process (the host and the remote) to complete the communication cycle.

Address

Enter the numerical address of the remote. The address is an integer (e.g., 1, 2, 3, etc.) assigned to the remote through its field unit configuration.

Note: A setup referred to as multi-dropping allows a number of remotes to share the same connection. Remotes with the same protocol must have unique addresses to be multi-dropped. Remotes with different protocols can also be multi-dropped.

Enable Communications Failure

Select to enable Omnicomm to attempt communication over a different connection when it fails to communicate with a remote (failover). Omnicomm will use the cheapest available connection for this remote as determined by the Cost Factor.

Minimum Integrity Poll Delay (sec)

Enter the minimum time between Integrity Update Polls for this remote. If this field is set to zero, a value of 10 seconds will be used.

Note: This field is only used for automated integrity update polls when there is a Sub-Remote Status Indicator point associated with the remote. It does not limit on-demand integrity update poll requests. Not all protocol drivers support integrity update poll requests.

Historical

Select to open the collect Table Edit dialog box that can be used to configure Historical data collection.

Translator

If available, enter the name of your custom AVEVA Enterprise SCADA Software Protocol Analyzer (SWANA) translator. SWANA will use this translator to decode communication messages with this remote.

If Omnicomm can't identify the remote with which it's communicating, SWANA will use the translator configuration configured for the active connection to decode the messages.

If no custom protocol translator is configured, SWANA will use a default translator based on the protocol configuration for the record.

Note: For a host poll configuration, Omnicomm can always identify the remote. For other connection types, it may or may not be able to identify the remote.