Troubleshooting the LabVIEW Model Interface Toolkit

Guidance on troubleshooting the LabVIEW Model Interface Toolkit, including compatibility, performance, and model execution considerations.

Modeling Environment Compatibility with the LabVIEW Model Interface Toolkit

The LabVIEW Model Interface Toolkit runs models from several environments, including MathWorks Simulink. You must compile the models to work with the VeriStand Model Framework.
Note For more information on the model types that the LabVIEW Model Interface Toolkit supports, see Support for Model Types and Modeling Environments.

MathWork Compatibility with the LabVIEW Model Interface Toolkit

For more information on the versions of the LabVIEW, Windows, model compiler, and MathWorks you can use with the LabVIEW Model Interface Toolkit, see the VeriStand Model Generation Support and MathWorks Simulink Compatibility knowledge base article at ni.com.

Hardware Target Compatibility with Operating Systems

The Model Interface API supports targets that run the following operating systems:

  • NI Linux Real-Time
  • Microsoft Windows

Model Run Rates

The rate at which a model runs depends on how often the Take Model Time Step VI executes to step your model. To ensure this VI runs at a specific rate, execute the Take Model Time Step VI in a Timed Loop.

System Performance

If you suspect that models are causing your application to run slower than you desire, consider the following solutions:

  • Only set parameter values in the control loop if you must update the values during every time step. Instead, initialize the parameter values prior to running the control loop or set them in lower priority, background code.
  • Probe only signals whose values you require. Probing many signals can negatively impact performance.
  • Avoid changing the list of signals to probe frequently with the Set Signals to Probe VI.

Upgrading Applications and Models Created for the LabVIEW Simulation Interface Toolkit to Use the LabVIEW Model Interface Toolkit API

For more information on upgrading applications and models, see the Migrating Simulation Interface Toolkit (SIT) Applications to the Model Interface Toolkit knowledge base article at ni.com.