Create Standalone FMU

Generate standalone Functional Mockup Unit from Simulink models using FMU Builder for Simulink^®

Use the FMU Builder for Simulink support package to create a Functional Mockup Unit (FMU) from Simulink models or C/C++ code.

Debug FMU that contains its source code using an external debugger. See, Debug FMU with Source Code Using External Debugger.

Functions

`exportToFMU`	Export Simulink model to functional mock-up unit (FMU) (Since R2023b)
`Simulink.SFunctionBuilder.generateFMU`	Generate FMU compatible with FMI 3.0 standards from C/C++ code using S-Function Builder block (Since R2023b)
`Simulink.fmuexport.GetExportableVariableList`	Get the list of exportable inputs, outputs, parameters, and internal variables for a model that is to be exported as an FMU (Since R2020a)

Topics

Export Simulink Models to Functional Mock-up Units
Generate cosimulation FMU compatible with FMI 2.0 and FMI 3.0 standards.
Configure Model to Export as FMU with Internal Variables
Export Simulink model to FMU with internal variables.
Generate FMU from C/C++ Code Using S-Function Builder
Integrate C/C++ code into Simulink S-Function Builder and generate an FMU.

Featured Examples

Export Simulink Model to Standalone FMU

Export Simulink® component to standalone Co-Simulation FMU 2.0 with Simulink Compiler™. For a detailed explanation of the model, see:

Open Script

Export Simulink Model with Protected Model and FMU Import Block to Standalone FMU

Export a Simulink® model with external references to Standalone FMU. In this example, the model f14_flight_control demonstrates exporting protected model and FMU Import block to a Standalone FMU.

Open Live Script

Export Standalone FMU with External C++ Code

Import external C++ code into Simulink® model using S-Function Builder and export it to a standalone FMU. S-Function Builder block lets user import C/C++ code into Simulink Semantic by building an S-function wrapper for external code. This example demonstrates this process in a phased approach by implementing a C++ multiply class, integrating C++ code with S-Function Builder, and exporting the model as a standalone FMU.

Open Live Script

Export Simulink Model to Standalone FMU with User Specified Files and Archived Project with Harness Model

Export Simulink® component to standalone Co-Simulation FMU 2.0 with user specified documentation and harness model using Simulink Compiler™. This example demonstrate following features of Standalone FMU Export: User file packing.

Open Script

Export Simulink Model to Standalone FMU with Source Code

Export Simulink® component to standalone Co-Simulation FMU 2.0 with source code using Simulink Compiler™ and Simulink Coder™. The source code is packed inside the sources folder of the Standalone FMU. A documentation file, index.html is also generated. It lists the steps to regenerate the binaries on another platform. This documentation file is located inside documentation folder of the Standalone FMU. The source code can be used for cross platform workflow.

Open Script

Eliminate Single Step Delay in Co-Simulation FMU Using Event Mode

A functional mockup unit (FMU) exhibits a single step delay of output in Simulink® when it is used in co-simulation mode. This is due to the delay in communication between the local FMU solver and Simulink solver. This example shows how to export a Simulink model to a standalone co-simulation FMU that is compatible with FMI 3.0 standard and leverage the event mode of the FMU in Simulink to eliminate the single step delay caused during co-simulation. This method works for FMUs that were created from a Simulink model and contain only direct feedthrough blocks.

Open Script

Export Simulink Model to FMU with Variable Step Solver

The following example demonstrates how to generate a Functional Mockup Unit (FMU) from a Simulink® model that uses variable step solver. Export a Simulink model to a FMU that supports Co-Simulation in FMI version 2.0 or 3.0. Simulating an FMU with variable step solver requires MATLAB® or MATLAB Runtime to be installed on the deployment machine.

Open Live Script