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

AVEVA Enterprise SCADA

Main tab PI Template Row Edit

  • Last UpdatedApr 24, 2025
  • 3 minute read

The Main tab in the PI Template Row Edit dialog box is used to set up the basic properties of the record such as AVEVA Enterprise SCADA-specific information, tag definitions, data types and display properties.

Item

Description

OASyS PI Interface instance

Interfaces are software modules for collecting data from a computing device with measures, such as AVEVA Enterprise SCADA. There can be more than one interface running at one time. This field indicates the interface instance number (interface ID number) in case multiple PI-OASyS interfaces are running concurrently.

Collection type

This field indicates the collect methods that the PI-OASyS interface uses to retrieve data from the AVEVA Enterprise SCADA data source.

Command timeout period (sec)

This field is not supported.

Scan class (defines collect period)

This field determines how often to poll for new values.

Extended descriptor

PI-OASyS Interface Configuration.

Note: In the PI Template table Extended Descriptor field is shown as exdes.

Engineering Units

The engineering unit string describes the units of the measurement. Any string of any length may be used, however the PI API only retrieves the first 12 characters. Examples are: Degrees Centigrade or gallons per minute.

Instrument tag

This field is not supported.

Source tag (output trigger)

This field is not supported.

Data type (extended def.)

Data type

Digital set

A collection of digital states is called a digital set. For example, a digital state can consist of two states: Open and Closed. This field is only active when the Data type field is set to digital.

Span

Specifies the difference between the top and bottom range. Span is required for all numeric data types.

Zero

A zero is required for all numeric data types to indicate the lowest value possible. It does not have to be the same as the instrument zero, but is usually the logical choice. Certain interfaces require that the zero and Span match the instrument system range. The zero is the bottom of the range used for scaling float 15 values for the PI archive.

Typical Value

The typical value is used only to document an example of a reasonable value for the point. For a numeric tag, it must be greater than or equal to the Zero, and less than or equal to the Zero plus the Span.

Number of digits to display

This field controls the format of numeric values on screens and in reports. Zero or a positive number indicates the number of digits to display to the right of the decimal point. A negative number indicates the number of significant digits to display. In this case, the absolute value of this field is the number of significant digits.

1

R field w v_fldget

Read the field value from a RealTime database (RTDB) point without data quality checking (using v_fldget function).

6

R_DQ

Read only the data quality from a RTDB point.

11

R field

Read the field value from a RTDB point without data quality checking (directly access to field value in database, fast than collection type 1). We suggest users to use the collection type 1 instead of collection type 11 unless they have a performance problem.

12

R field w DQ

Read the field value from a RTDB point with data quality checking (using set layer function, fast).

13

R field w PS

Use PubSub to read the field value from a RTDB point without data quality checking.

14

R field w DQ w PS

Use PubSub to read the field value from a RTDB point with data quality checking.

15

R w PS

Generic PubSub subscription. Use PubSub to read any publication from a data source other then RTDB.

16

R field w packed PS

Use PubSub to read the field value from the packed<table>RT virtual field of a RTDB point.

For more information, refer to Configure a packed<table>Rt virtual field.

17

R DQ w packed PS

Use PubSub to read the data quality from the packed<table>RT virtual field of a RTDB point.

For more information, refer to Configure a packed<table>Rt virtual field.