FMI Support Limitations
- Updated2025-12-15
- 1 minute(s) read
Early Access FMI support has several limitations.
- Data with more than two dimensions is not supported.
- All FMI numeric data types are supported but cast to doubles internally.
- Arrays of numeric types in FMI 3.0 are supported but cast to doubles internally.
- Clock, String, Binary, and Char variables are not supported.
- A DefaultExperiment
section with a non-zero stepSize is mandatory. Models without the
DefaultExperiment section will fail to run. Note An example of a working stepSize is <DefaultExperiment stepSize="0.01"/>.
- Changing stepSize in VeriStand is not supported. The only way to change stepSize is by modifying the modelDescription.xml file inside the FMU.
- Only Co-Simulation interface type is supported.
- Early Return and Event Mode capabilities in FMI 3.0 are not supported.
- Terminal Grouping and Icons in FMI 3.0 are not supported.
Configuring Stack Size for FMU Models on Linux Real-Time Targets
When running an FMU model in VeriStand on Linux Real-Time (NILRT) targets, a segmentation fault may occur if the default stack size (256 KB) is exceeded, typically due to a stack overflow.
Workaround:
For VeriStand 2023 and later, you can prevent this issue by increasing the stack size. To do this, edit the lvrt.conf file located at /etc/natinst/share and add or modify the following line:
PosixThreadStackSizeLimit = 2048
This sets the stack size to 2048 KB, helping to avoid overflow during FMU execution.