Main Content


Export Simulink model to functional mock-up unit (FMU)

Since R2020a



exportToFMU2CS(mdl) exports mdl to mdl.fmu. The model solver type must be fixed-step solver.

exportToFMU2CS(mdl,Name,Value) exports a model to a Functional Mock-Up Unit (FMU) using one or more Name, Value pair arguments.


collapse all

Export the model vdp to an FMU.

Open the model.


Set the solver type of the model to fixed-step.

set_param('vdp', 'SolverType', 'Fixed-step')

Export the model to vdp.fmu


Input Arguments

collapse all

Name of the model to be exported to an FMU, specified as a string.

Name-Value Arguments

Specify optional pairs of arguments as Name1=Value1,...,NameN=ValueN, where Name is the argument name and Value is the corresponding value. Name-value arguments must appear after other arguments, but the order of the pairs does not matter.

Before R2021a, use commas to separate each name and value, and enclose Name in quotes.

Example: 'CreateModelAfterGeneratingFMU','off'

Option to create model after export, specified as 'on' or 'off'. This argument creates a model, mdl_fmu.slx, that contains an FMU Co-Simulation block with the original model. Create this model to check the integrity of the exported FMU.

When set to 'off', no model is created.

Block icon or exported FMU image, character vector specified as one of these values:

  • 'off' – No block icon image.

  • 'snapshot' – Use image of model as block icon.

  • 'filepath' – Filepath of the image.

Option to generate 32-bit DLL, specified as 'on' or 'off'. Set the option to 'on' to support exporting Co-simulations of FMUs with 32-bit binaries. Only valid on win64 platform with MSVC toolchain installed.

Option to save source code to FMU, specified as 'on' or 'off'. Set to 'on' to package the source code in the source directory and documentation file, which recompiles the binary files in the documentation directory in the FMU. This option requires Simulink® Coder™.

Save location for FMU, specified as a string or character vector. By default, the location is the current working folder.

Example: exportToFMU2CS(model,'SavedDirectory','/tmp/flightcontrol/')

Option to create to create a wrapper-archived project or harness model with dependencies, specified as 'off' or 'project'. Set to 'project' to enable this option.

Name of archived project with harness model, specified as a string. This argument must be specified along with the 'ExportContent' argument. By default, archived project is named modelName_fmu

Destination folder and files to be packaged, specified as a cell array.

Example: exportToFMU2CS(model, 'Package', {'documentation/', {'/local/bouncingBall/index.html','/local/bouncingBall/siteFiles'},... 'resources',{'local/bouncingBall/resources/input.txt'}})

Version History

Introduced in R2020a