The built-in simulator exposes a single setting: the scan cycle time. (The simulation is also called the emulator internally, hence the emulation key.)
| Setting ID | automationview.emulation.cycleTimeMs |
| Type | number |
| Default | 100 |
| Range | 10 - 10000 |
| Scope | resource |
The scan cycle time in milliseconds. It controls how fast the simulator advances when running - a lower value runs faster. The setting is applied live, so changing it while a simulation runs takes effect on the next cycle.
If your program has many steps and transitions, a very fast cycle time may make the visual editor feel sluggish. Increase the value if you experience performance issues.
{
"automationview.emulation.cycleTimeMs": 500
}
| Setting | Type | Default | Range | Description |
|---|---|---|---|---|
automationview.emulation.cycleTimeMs |
number | 100 |
10 - 10000 | Scan cycle time in milliseconds; lower runs faster |
Cycle time is the only user-facing simulation setting. Other engine parameters (maximum cycles, stop-on-error, and so on) are fixed internal defaults and are not configurable.