VeriStand enables configuration and execution of FMI 2.0 and FMI 3.0 CoSimulation models on Windows and NI Real-Time Linux 64-bit systems. This support requires FMUs to have the proper executable binaries available.

Model Configuration

You can use the same general model import and configuration steps in System Explorer to import FMUs into VeriStand.

The following table displays how a variable appears based on its causality when a FMU is imported into VeriStand.

FMU Variable Causality VeriStand Node Type
input inport
output outport
parameter parameter that can be imported as a channel or accessed through Model Parameter Manager
calculatedParameter not visible
independent not visible
local signal
structural parameter not visible

The rate of the model is defined by the stepSize attribute in the DefaultExperiment. Decimation must be configured based on the rate at which the VeriStand Engine is running.

Model Execution

The following table displays the model execution target architectures that FMI supports on the NI platform.

NI Target Architecture Folder in .zip
FMI 2.0 FMI 3.0
PXI Linux linux64 x86_64-linux
Linux64 cRIO linux64 x86_64-linux
Windows win64 x86_64-windows

Configuring Log Level

To configure the log level of the FMU, create a file named fmu_log_level_override in the following directory:

Windows: C:\Program Files\National Instruments\VeriStand <Version>

Linux RT: /usr/local/natinst/lib

The file should contain a single digit specifying the desired log level index, ranging from 0 to 7. The default log level Fatal will be used if the fmu_log_level_override file is not available.

The log file will be created in the same directory as the FMU, named <modelName>.fmu.log. In case of Linux RT, the default path for the FMU and the log file is /c/ni-rt/NIVeriStand/Models/<modelName>.fmu.log.

The log levels are given below:

Log Level Description
0 Nothing
1 Fatal
2 Error
3 Warning
4 Info
5 Verbose
6 Debug
7 All
Note Configuring log level greater than 1 can degrade the performance of the system.