Configuring the Execution Order of Models
- Updated2025-10-27
- 2 minute(s) read
Configuring the Execution Order of Models
Define the order that the Primary Control Loop (PCL) executes models.
-
Use the following table to determine the order that your models execute.
Note The PCL execution mode does not affect the execution order for multiple models.
Model execution Description Diagram In parallel (default) Models read data from the previous PCL iteration and execute in parallel.
If you map one model to another, the second, dependent, model always receives data the first model generated during the previous iteration of the Model Execution Loop. It does not receive data the first model generates during the current iteration.

In series Models execute relative to each other.
If you map one model to another, defining an execution order allows you to ensure that the second, dependent model receives data the first model generates during the same iteration.

- Launch your project in the VeriStand Editor.
- In the Project Files pane, left-click a system definition file (.nivssdf) and select Configure in System Explorer.
- Click in the configuration tree.
-
On the Execution Order Configuration page, drag the red
cells representing the Models from one group to another
to arrange them in the order that you want the models to execute.
Note Models in the same execution groups execute in parallel.
- Click Refresh to reorder the Models and Execution order lists based on the changes you have made.
- Save the system definition file.
Related Information
- Primary Control Loop Step Execution in Models
The Primary Control Loop (PCL) executes steps in models differently if it is in parallel mode or in low latency mode.