Time settings tab

General Settings

• Scan (/SCAN=<seconds>)

  Specifies how frequently the interface scans active points.

• Cache time (/CACHETIME=<days>)

  Specifies how long completed events are retained in memory. Default is one day. Specify the maximum duration expected between event frames that need to be merged, plus any margin of safety.

  The value can be specified as whole day or fraction of a day. For example, to release completed batches when their end time is less than 7 days and 12 hours from current time, specify the following cache time setting:

  CACHETIME=7.5 days

• Abandoned batch timeout (/ABTO=<days>)

  Specifies how long event frames can remain open before being considered abandoned. When this period (plus cache time) elapses, the interface writes an end time to the event to close it. Specify the maximum duration expected for events, plus any margin of safety.

  For example, if you set abandoned batch timeout to 50.5 days and cache time is seven days, events open for 57.5 days are automatically closed. The following figure illustrates timeout logic.

  

• Maximum query time frame (/MAXQTF=<days>)

  To help manage workload and memory usage, defines the maximum time frame for queries. For example, if you specify 30 days and the interface queries for one year’s worth of data, the interface issues 12 one-month queries rather than one (large) one-year query.

• Maximum stop time (/MAXSTOPTIME=<seconds>)

  Specifies the maximum time allowed for the interface to properly shutdown. If the shutdown process takes longer than the specified time, the interface is forced to terminate immediately. The default value is 120 seconds.

• Query Buffer Delay

  Specifies the amount of time (in minutes) subtracted from the current time when calculating the Next Query End Time. This configuration allows the system to catch recently closed batches that were missing from the latest database call.

  The default value is two minutes, but you can configure the amount of time to a maximum of 10 minutes. To disable the configuration, set the /DELAYBUFFER to zero (0) in the INI file.

  This configuration is used in both real-time and history recovery mode but only applies to interface configurations where the end time for data recovery (/ret) is not defined.

• Use local time stamps to process incoming events (/TS)

  Applies the time on the local machine to the event frame start and end, overriding the time stamp read from the active point in the PI Server. By default, time stamps are recorded using local time.

• Extended Procedure Search Time (/AFSYNCSTARTOFFSETHOURS)

  (Specified in hours) During recovery, this setting enables the recovery algorithm to look a specified number of hours into the past for potential event frames to merge with. This setting adds additional time to the Recovery Start Time (RST) to ensure that event frames are located and merged with recovered event frames. It is largely useful when you have merged batches during a recovery period.

For users who have migrated from PIBaGen, this setting is similar to PIBatch Search Time.

PI Connection Settings

• PI connection timeout (/PICONNTO=<seconds>)

  Override the default PI SDK Connection TimeOut property.

• PI data access timeout (/PIDATO=<seconds>)

  Override the default PI SDK Data Access TimeOut property.

• Retry (/RETRY=<seconds>)

  Specifies how long to wait before retrying a failed SDK attempt to write data to PI Server. The default is 60 seconds.

• Retry timeout (/RETRYTO=<seconds>)

  Specifies timeout for failed SDK attempts to write data to PI Server. To avoid data loss, set to 0 (default, no timeout).

Settings

• Event analysis delay time

  Specifies how long the interface waits before analyzing incoming event triggers and creating event frames. Intended for situations where the arrival of source data required to create events is often delayed. This setting is applied to all PI EFGen configurations for an interface instance.

  The following figure shows how this window of time is applied to incoming data.

  

• Parent delay time

  Change the time in seconds that a child stop event should wait for a parent event to arrive.

• Max events in event pipe

  Sets the maximum number of events an event pipe can hold. It is used by PI EFGen to calculate memory allocation for processing events. The interface creates an event pipe for snapshot updates to active points. (Default is 10,000.)

  If you have a large PI EFGen configuration or the PIPC.log file has messages indicating that the number of events is approaching the maximum, increase this value.

• Extended Procedure Search time

  Sets an extended search time in hours.