Control & Simulation Loop

Owning Palette: Simulation VIs and Functions

Requires: Control Design and Simulation Module

Executes the simulation diagram until the Control & Simulation Loop reaches the simulation final time or until the Halt Simulation function stops the execution programmatically. You must place all Simulation functions within a Control & Simulation Loop or in a simulation subsystem. You also can place simulation subsystems within a Control & Simulation Loop or another simulation subsystem, or you can place simulation subsystems on a block diagram outside a Control & Simulation Loop or run the simulation subsystems as stand-alone VIs.

Note  If a VI contains a Control & Simulation Loop, you only can use save for previous functionality to save the VI for LabVIEW 2009 or later.

Input Node

The Control & Simulation Loop has an Input Node, which you use to configure simulation parameters programmatically. You also can configure these parameters interactively using the Configure Simulation Parameters dialog box. Access this dialog box by double-clicking the Input Node or by right-clicking the border and selecting Configure Simulation Parameters from the shortcut menu.

Note  Parameters that you programmatically configure using the Input Node override any settings that you make in the Configure Simulation Parameters dialog box.

The Control & Simulation Loop has an Error input on the Input Node and an Error output on the Output Node. These error terminals send error information through the simulation diagram. If the Error input detects an error, the simulation diagram returns the error information in the Error output and does not execute the simulation.

(C Generator) If you place a checkmark in the Synchronize Loop to Timing Source checkbox of the Configure Simulation Parameters dialog box, you cannot use the Control & Simulation Loop.

Output Node

The Control & Simulation Loop has an Output Node that contains an Error output terminal. If an error occurs while the Control & Simulation Loop is executing, the simulation stops running and returns the error information in the Error output.

You can add terminals to the Output Node that return signal histories collected when the simulation runs. To create and configure these output terminals, double-click the Output Node to display the Access Model Hierarchy Configuration dialog box.