Alarm Time Stamps

When an alarm is generated in an I/A block running in an SCP App, the time stamp (or time the alarm occurs) is provided by the SimSync Engine running on the machine with the SCPEngine. Therefore, every SCPEngine needs a SimSync Engine running with it on the same machine.

The SimSync Engine adjusts time for simulation. It updates itself according the resolution setting. This means that the smaller the time slice (resolution) setting, the coarser the alarm time stamps. The larger the resolution, the finer the alarm time stamps (but simulation speed may suffer).

For example, for a BPC of 0.1, the table above recommends a setting of 10.

A setting of 10 means that an alarm occurring in the third 0.1 sec will get a different time stamp than an alarm occurring in the fourth 0.1 sec (or the seventh 0.1 sec) because the SimSync Engine updates every 100 ms (at 100% simulation speed).

A setting of 1 for the same BPC means that an alarm occurring in the third 0.1 sec will get the same time stamp as an alarm occurring in the fourth 0.1 sec (or the seventh 0.1 sec) because the SimSync Engine only updates every 1000 ms (at 100% simulation speed).

You should adjust the time slice (resolution) setting of the SimSync Engine on the SCP machine to balance alarm time stamp granularity against simulation speed.