|Download Help (Windows Only)|
A model is a mathematical representation of a real-world system. As you develop the plant and controller for your closed-loop control system, you might find value in creating software models that simulate one or both of these components. Models run on hardware targets and are typically used to respond to stimuli from other parts of the system by producing outputs in a way that simulates the modeled item. Models also can serve the functions of signal generation, signal analysis, and control.
Models can contain the following components that connect to other parts of the system or allow you to interact with the model:
Consider a system that contains a physical motor controller and a model that represents a DC motor. The model runs on a hardware target. Such a model might contain the following components:
The remainder of this topic describes tasks you typically perform to create and integrate a model into an NI VeriStand system.
You can build models using several different modeling environments. You typically must compile a model in the modeling environment before it can run on an RT target in your NI VeriStand system. The exact process for preparing a model to execute in NI VeriStand depends on the modeling environment you use to build it. Refer to the appropriate resource for your specific modeling environment for information about preparing the model for use in NI VeriStand:
If you build the model in some other modeling environment, refer to the modeling environment documentation for information on how to convert your model into a compiled model.
You add models to a system definition file to include them in an NI VeriStand system. When you add the model, you also configure its timing and choose how to import its inports, outports, parameters, and signals.
After you add a model, you map parts of the model to channels in other parts of the system to create connections between them. For example, you might map a hardware channel to a model inport so the model receives and operates on data from the hardware device.
Use UI Manager or workspace objects and other tools to control the execution of models, monitor their status and timing, configure their parameters, and read from their signals.