Add a model to a system definition to connect it to other parts of the system and run the model on a hardware target.Before you begin, you should understand the components of a model and how the Primary Control Loop (PCL) steps execute in models. VeriStand executes each model in its own loop. If a system definition contains multiple models that reference the same compiled model, VeriStand makes a temporary copy of the model so each loop has its own compiled model to execute. Adding more than one instance of the same compiled model can cause errors if the model accesses a shared resource, such as a dependant file. Contact your model provider for information about whether the model accesses such resources.
Scalar channels provide greater flexibility than vector channels. You can only map vector channels to another model that contains a vector channel of the same size. You cannot map a vector channel to controls or indicators on your Workspace or use it with calculated channels, alarms, procedures, and others.
|Set model timing||Set a model to run at a certain rate, or step size.|
|Set model parameters||Use the VeriStand Editor, Workspace, Model Parameter Manager, and Stimulus Profile Editor to set the values of model parameters.|
|Scope global parameters||Update the scope of a global parameter to the target-level or model-level for all global parameters in a model.|
|Set the default values for inports||Change the default value for an inport to prevent your models from using invalid values.|
|Configure the execution order of multiple models||Define the order that the Primary Control Loop (PCL) executes models relative to each other.|