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

AVEVA™ Simulation for Foxboro Control

FAIM Engine Configuration Parameters

  • Last UpdatedApr 20, 2020
  • 2 minute read

The operations of each FAIMEngine (as associated historian instance) are controlled by its configuration options . The FAIMEngine may have any name supported by DYNSIM.

To edit these options:

  1. Open the Simulation Configuration dialog box.

    Embedded Image (65% Scaling) (LIVE)

  2. Select the FAIMEngine instance and click the Edit button. The Engine Configuration dialog box appears.

  3. In Engine Configuration dialog box, set the following options:

    Option

    Description

    Default value

    Historian logical name

    The historian instance logical name associated with the FAIM Engine instance. This is REQUIRED.

    <not specified>

    Maximum hours of available history

    The maximum amount of historical RTP data available in the simulation

    8

    Maximum number of stored alarms

    The maximum number of historical alarms available in the simulation

    5000

    Default RTP data file size (in MB)

    The initial size of an RTP database file (at creation time)

    10

    Historian collectors to ignore

    A list of collector names (separated by commas) who’s RTPs should not be collected.

    Blank: It means data collection for all the RTPs in the instance is attempted

    Directory path for historian data files

    The directory where FAIM should store the ‘current’ historian database files.

    Blank: It means FAIM stores the data in the simulation specific directory

    Directory path for initial condition (IC) files

    The directory where FAIM should store the database files for an IC

    Blank: It means FAIM stores the IC data in the simulation specific directory

    Directory path for backtrack files

    The directory where FAIM should store backtrack files

    Blank: It means FAIM stores data in the simulation directory

  4. When specifying non-default locations for historian database files and IC files, ensure that the locations are unique for each simulation, to prevent different simulations from attempting to utilize the same database files.

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