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

Data Archive Administration

The SYSTEM digital state set

  • Last UpdatedOct 03, 2024
  • 5 minute read

The SYSTEM digital state set contains over 300 states that can apply to any point. Descriptions of commonly encountered states are shown in the following table.

All points, no matter what their data type, can store values from the SYSTEM digital state set. For example, an Int32 type point could have the following values: 2, 3, 4, Shutdown, 8, 9, and so on. This enables you to store errors and informational values alongside regular values.

Note: For points with a data type of Digital state, use a user-defined digital state set, and not a SYSTEM digital state value.

You should not change the default SYSTEM digital state values, unless you need to translate their names into another language.

You should not use state number 0 (zero) in the SYSTEM digital state set.

If necessary, you can add states to the SYSTEM digital state set, but state numbers 193-320 are reserved for use by Data Archive and should not be modified. The last state in the SYSTEM digital state set is number 16383. It is reserved for internal Data Archive use.

The meaning of a particular SYSTEM digital state always depends on the interface or source application that wrote the event. For example, the Arc Off-line state is returned when there is an archive gap, but in rare situations Arc Off-line can be sent for other reasons.

Additionally, your site might have programmed use of a particular SYSTEM digital state in a non-standard way. For example, to indicate a graceful shutdown by an interface the default SYSTEM digital state is Intf Shut. But it is possible to configure UniInt interfaces to write any of the SYSTEM digital states to points at shutdown.

Note: You can view all of the SYSTEM digital state names and numbers in PI SMT. Go to Points > Digital States and select the SYSTEM set.

State number

State name

Description

238

Scan Off

A point was removed from an interface while the interface was running. This can happen in the following situations.

  • The Scan attribute for a point is set to 0 (off).

  • The Point Source attribute is changed so that the point no longer belongs to the interface on which it is currently loaded.

240

Configure

The point configuration has been rejected as invalid by the data source. Check the interface message logs for additional information.

244

Filtered

Might be returned when filtering data from the archive, for example, using a filter expression in PI Data Link.

246

I/O Timeout

Communication with a remote device has failed. I/O Timeout is written by the interface to each input point when:

  • The interface is shut down (to show that data collection was stopped).

  • The interface is unable to receive a response from the data source within the assigned time. This situation could be caused by a network communication loss from the device.

    Note: For each interface, you can configure the amount of time to wait before writing the I/O Timeout status.

248

No Data

The point contains no archived values in the specified time period. The time period might be specified in a query, or by the input parameters of a calculation (for example, in an analysis or performance equation).

249

Calc Failed

A calculation point failed due to a mathematical error (for example, dividing by zero). Or a source point used in the calculation did not contain valid data.

To troubleshoot this error, check the value of each input parameter to the calculation at the time of execution.

251

Under Range

For Float16 type points, indicates a value that is less than the bottom of range (Zero attribute) for the point.

For other point types, this state is usually the result of a substitution coming from the data source.

252

Over Range

For Float16 type points, indicates a value that is greater than the top of range (Zero+Span attributes) for the point.

For other point types, this state is usually the result of a substitution coming from the data source.

253

Pt Created

Assigned to a point when it is created. The value of the point is updated as soon as data arrives.

Optionally, you can delete this event or edit its value using the Archive Editor in PI SMT. The Pt Created state is also removed if you write any events that have a timestamp before the Pt Created event.

Note: If you expect data but the point shows Pt Created, the point is not getting data. To diagnose the issue, contact Customer Portal.

254

Shutdown

When the Data Archive server is restarted, Shutdown state is written to all points that meet the criteria defined in shutdown.dat. By default, this is all points with Point Source set to R that have their Shutdown attribute set to 1.

For more information about the Shutdown state, see Shutdown events and Set shutdown events for specific points.

The following Customer Portal articles also have useful information.

255

Bad Input

Written by the interface, if the data received was invalid. For example:

  • The data does not match the point type (such as writing a float value to an integer point).

  • The quality flag of the data received from the data source was invalid.

    For more information on the specific cause, see the interface message log close to the event's timestamp.

302

Arc Off-line

Marks a time where interpolation of the value is unsafe. The most common cause is a time period for which there is no archive file (an archive gap).

You can set the MarkArchiveGaps tuning parameter to 0 (zero) to stop Data Archive from returning the Arc-Offline status. For more information about the effects of adjusting the MarkArchiveGaps tuning parameter, see the Customer Portal article What are the effects of changing the MarkArchiveGaps tuning parameter?.

311

Intf Shut

Indicates a graceful shutdown by an interface.

For example, when the interface shuts down gracefully you can use the UniInt parameter /STOPSTAT or the OPC parameter /OPCSTOPSTAT to configure an interface to write Intf Shut to all points loaded by that interface.

315

Coercion Failed

After the data type of a point is changed, data from the previous type is coerced to the current type at retrieval time. If an event cannot be coerced to the edited point type, Coercion Failed is returned. See Allowable point type coercions for more details.

316

snapfix

The snapfix procedure has been used on the Data Archive server to fix a corrupted snapshot table. After a new value arrives, the value of snapfix is replaced and not archived.

317

Invalid Float

A point of floating-point data type received an invalid value (for example, a string value).

318

Future Data Unsupported

The notion of the current value of a future PI point depends on the usage and requirements of the client application. Therefore, for the end-of-stream value for a future PI point, Data Archive returns Future Data Unsupported.

For more information, see Learn about future data in Data Archive.

Related Links
TitleResults for “How to create a CRG?”Also Available in