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

AVEVA™ Simulation for Foxboro Control

Suggested Settings for Various Applications

  • Last UpdatedApr 20, 2020
  • 2 minute read

SimSync Engine Application

Simulation time step (sec)

Number of time slices per second (resolution)

AW / WP with FoxView HMI *

1

1

AW / WP with InTouch / Evo Control HMI * @

1

10

SCP (for alarm time stamps) @

For finest alarm time stamp granularity, the value should be based on the fastest BPC of the various CPs - this may reduce simulation speed.

If the fastest BPC is 0.5, then resolution = 1 / 0.5 = 2

If the fastest BPC is 0.1, then resolution = 1 / 0.1 = 10

For best simulation speed, the value should be 1 – this will coarsen the alarm time stamps.

1

1 to 10

FAIM

1

1

Wonderware Historian @

For an Evo system historizing CCS (I/A) data from SCP, the value should be based on the fastest BPC (see SCP above).

For a non-Evo system (TriSim, OPC, etc.) historizing data, the value should be based on the highest frequency of data change.

If the fastest engine time step is 0.25 sec, then the resolution = 1/0.25 = 4

1

10

Note: * - For standard Foxboro Evo applications that make use of the FoxView HMI, the number of time slices per second should be set to 1. This precision matches that of the Foxboro Evo alarm server and optimizes simulation performance. For InTouch applications, the number of time slices should be 10 to match their update rates.

Note: @ - The larger the resolution, the slower the maximum simulation speed. If the simulation speed is limited to 100% and greater than real-time speed is desired, try lowering the largest resolution setting amongst all the SimSync Engines.

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