Reviewing and Modifying the Configuration File
- Last UpdatedApr 20, 2020
- 1 minute read
Mostly, FAIM uses only a subset of the information available in an AIM batch configuration file, but in some cases, it overrides the settings in the configuration file. The modifiable settings are listed below:
Instance Component
|
MAXPTS |
Maximum number of RTPs: Set this value to the maximum number of Real Time Points expected with FAIM. This value determines the size of the database files maintained by FAIM; therefore, it directly effects the storage requirements for ICs and the time taken to save and restore the state. In AIM, this value can be set significantly larger than the number of configured RTPs; therefore, reduce it to a value slightly larger than the number of actual RTPs. |
|
ARCHSIZE |
Archive size: This value is ignored by FAIM. All RTP database files are created at a fixed size as configured in the Engine Configuration dialog box for the FAIMEngine. See FAIM Engine Configuration below. |
|
RTTIME |
Database retention time: This value is ignored by FAIM. All RTP database files have a retention time of 3600 seconds (1 hour). FAIM expires and rolls over an RTP database file every 3600 seconds of elapsed simulation time. An RTP database file in FAIM never rolls over on size if it becomes full before it contains 3600 seconds of data. It grows to create additional space. |
|
IATIME |
Foxboro Evo Time vs. UTC: This value is ignored by FAIM and forced to IATIME=NO. Whole data stored by FAIM is time stamped to the simulation clock, and the timestamps returned by FAIM to external applications are specified as UTC. |