Connection Row Edit: Main tab
- Last UpdatedApr 24, 2025
- 3 minute read
The Main tab in the connection Row Edit dialog box is used to configure the basic properties of a connection record. The fields in this tab define the connections and determine what type of Omnicomm process and connection protocols are used.
Refer to the table below for field descriptions and instructions on how to configure the editable fields in the Main tab in the connection Row Edit dialog box.

Items on the Main Tab in the Connection Row Edit Dialog Box
|
Items |
Description |
|---|---|
|
Name |
Select (...) and select the name of the connection record from the Connection 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). |
|
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. |
|
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 connection record is conmsg. |
|
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. |
|
Omnicomm Process |
Select (...) and select the Omnicomm process associated with this connection from the Omnicomm Select dialog box. |
|
Protocol |
Select (...) and select the name of the protocol driver used with this connection. The choices are dependent on which protocols have been installed. |
|
Circuit |
Select (...) and select the name of the circuit to which this connection belongs from the Circuit Select dialog box. If no circuit is selected, Omnicomm assumes the connection is independent of all other circuits, for example, point-to-point IP connection. |
|
Issue Integrity Update Automatically |
Select to request an integrity update whenever a connection is established. |
|
Enable Connection FEP |
Select to enable connection FEP. This applies only if a front-end processing driver has been developed for the project. |
|
Protocol Specific Configuration |
Enter any additional parameters that may be required for the protocol driver selected in the Connection Protocol field. |
|
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. If Omnicomm can't identify the remote with which it's communicating, SWANA will use this custom translator to decode the messages. If Omnicomm can identify the remote, SWANA uses the protocol translator configuration configured in the remote record. 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. See also: The description of this field in Remote Row Edit: Main tab. |