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

AVEVA Enterprise SCADA

Status Row Edit: Input tab

  • Last UpdatedApr 24, 2025
  • 3 minute read

The Input tab in the status Row Edit dialog box is used to configure status inputs.

Refer to the table below for field descriptions and instructions on how to configure the editable fields.

Items on the Input Tab in the status Row Edit Dialog Box

Items

Description

Has Input

Select the checkbox to allow the setting of the multistate point’s current value field.

Use Device Based Questionable DQ

Select to alert downstream krunch processes that, when said processes krunch the current value of the point, freshness should be based on the data quality from the field.

Number of Input Bits

Enter the status point type.

For two-bit devices, input-bit 1 (Input #1) is the low-order bit, and input-bit 2 (Input #2) is the high-order bit.

Possible inputs are:

  • 0. Enter this for digital output devices that do not return "command success" messages. With this setting, neither Input #1 nor Input #2 need to be configured.

  • 1. Enter this for two-state devices. With this setting Input #1 must be configured.

  • 2. Enter this for four-state devices. With this setting both Input #1 and Input #2 must be configured.

Bit in RTU Status

Select the checkbox if this status record is monitoring a remote-specific condition.

If this is selected, no other fields on the Input tab need to be configured.

In some protocols like TANO, the Remote Status Word (RSW) is an 8-bit status word that is returned to the host. Each bit in this word represents a remote-specific condition, such as: AC powerfail, bulk powerfail in one or more expansion baskets, unit powered up, command disabled, uninitialized.

Coordinates

Enter the coordinates where the data is mapped within the remote. This mapping depends on the protocol used.

Some protocols use registers to allocate data in remote memory, others use a definition of the point or file number for access. Representative data mappings and point configuration are described for various protocols in RealTime. Refer to your specific remote or protocol documentation for a definition of the data mappings and to determine the remote’s input/output data location in memory.

Poll Group

A text string that may consist of multiple comma-separated values to define the frequency poll groups to which the point belongs.

For further information, refer to volume 2 of the RealTime Administrator documentation.

Bit Number

Enter the bit number that points to the device’s status bit number within that word.

A single word of RealTime data can encode messages from a number of status/multistate devices.

Normally Open

Select the checkbox if your remote does not return a value of 1 to indicate OPEN.

The system expects 1 to indicate the device is in an open state. When Normally Open is selected, the bits from the remote are inverted (for example, 0 is changed to 1; 1 is changed to 0). If Normally Open is cleared, the bits that are returned from the remote remain unprocessed.

Accumulate Runtime

Select the checkbox to record the time (in hours) that the status input has been in the state specified in the Accumulated State field. It indicates the time during the current and preceding hour, day, shift, and month.

Runtime values may be used in a report to determine device maintenance requirements. For instance, pump maintenance is performed when a pump runtime value exceeds the maximum runtime recommended for the month. This could be checked using a Microsoft SQL statement, such as the following:

select name from status where run.month.previous > 1.5

Accumulated State

Select (...) and select the state you want to monitor from the Accumulated Runtime State dialog box.

Refer to Select an accumulated runtime state for more information.

SOE Point

Select the checkbox to designate the point as a sequence-of-events (SOE) type. When a point is designated as a SOE type, all events and alarms, regardless of what type they are normally, will be SOE type.

SOE points are typically used by the electrical industry, which can receive a very high volume of alarms in a short period. The analysis of events at key points at the millisecond level becomes important. Customers will typically create a separate easy eXtended Operator Station (ezXOS) event screen to isolate these events for analysis.

This feature requires Command Failure Timeout and COS Failure Timeout to be greater than 0.