Learn about PI EFGen modes of operation
- Last UpdatedJan 14, 2025
- 2 minute read
- PI System
- PI Event Frames Generator 5.1.7
- Interfaces
PI EFGen can be run in the following modes:
-
Realtime (default)
-
Recovery
-
Statistics
-
Delete
To set the mode, go to the Operational settings tab in the PI Event Frames Interface Manager.
The interface can be started or stopped using the PI Event Frames Interface Manager Service Configuration tab or by using the Windows Services applet.
-
Realtime mode
In Realtime mode, the interface monitors active points in the PI server for changes in value that indicate the beginning or end of an event. When it detects such a change, PI EFGen creates or updates event frames in the PI AF database. During startup, the interface performs recovery for each PI EFGen configuration, based on the setting for recovery time or the global interface cache time (whichever is greater), then begins scanning active points in real time.
-
Recovery mode
Recovery mode corrects history or recovers missing data for existing PI AF elements, element attributes, event frames and PI points, based on the history of active points. You can specify the start and end time for the period to be recovered. If you omit end time, the interface performs recovery and then switches to Realtime mode.
-
Statistics mode
In Statistics mode, the interface verifies existing event frames against active point data in the PI Server for a specified time period, and reports results. If you omit the time period, results are reported from the recovery start time until the current time.
-
Delete mode
In Delete mode, the interface deletes event frames from the PI EFGen server for a specified period. If you intend to restore history using Recovery mode, ensure a correct recovery by first deleting events for the period that you intend to recover. See Learn about recovery examples for additional details.
Note: If you are in PI BAGen mode and delete a unit in a procedure, the entire event frame is deleted. Depending on what Unit Procedures already exist in other Procedures from the same Units, recovery may require a separate scan of each unit. Units are often set with different /RST and /RET times, which may also necessitate a separate scan of each.