Frequently Asked Questions (FAQ) (Model Interface Toolkit)

LabVIEW 2017 Model Interface Toolkit Help

Edition Date: May 2017

Part Number: 374160C-01

»View Product Info
Download Help (Windows Only)

Hardware and Software Support

Q: Which modeling environments produce models that are compatible with the Model Interface Toolkit?
A: The Model Interface Toolkit can run models from several environments, including The MathWorks, Inc. Simulink® software, after the models are compiled to work with the NI VeriStand Model Framework. Refer to the following help topic for more details about the types of models the Model Interface Toolkit supports: Support for Model Types and Modeling Environments


Q: What versions of The MathWorks, Inc. software are compatible with my version of the Model Interface Toolkit?
A: Refer to the following KnowledgeBase document at ni.com for a list of the versions of the LabVIEW, Windows, model compiler, and The MathWorks, Inc. software you can use with the Model Interface Toolkit: NI VeriStand Version Compatibility.


Q: What types of hardware targets can run applications that call the Model Interface API?
A: The Model Interface API supports targets that run the following operating systems: NI Linux Real-Time, Phar Lap ETS, VxWorks, and Windows. Refer to the KnowledgeBase at ni.com for a list of NI RT targets and the real-time operating system that each runs.

Timing and Performance

Q: What determines the rate at which a model runs?
A: 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.


Q: How can I improve the performance of my system as it relates to models?
A: If you suspect that models are causing your application to run slower than you desire, consider the following solutions that might improve performance:
  • Only set parameter values in the control loop if you must update them 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.

Migrating from the Simulation Interface Toolkit

Q: How do I upgrade an application and models created for the LabVIEW Simulation Interface Toolkit to use the Model Interface Toolkit API?
A: Refer to the following KnowledgeBase document for this information: Migrating Simulation Interface Toolkit Applications to Use the Model Interface Toolkit


WAS THIS ARTICLE HELPFUL?

Not Helpful