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

In this example, we use an app that is prepared in the App Designer and deploy it with Simulink® Compiler™.

Develop an app that uses callbacks for simulation inputs and outputs to view the simulation of a Simulink® model of the Lorenz system. You can then deploy the app with Simulink Compiler™.

Use the simulink.compiler.genapp function to generate a MATLAB® app for a model, that is deployable. Typically when a Simulink® model is functionally complete, it is often used to run multiple simulations different input and parameter values. To try simulations for your model with different input and parameter values, you can generate a MATLAB App. You can also deploy this generated app for use outside of MATLAB.

In this example, you use an app with LiveIO functionality, that is prepared in the App Designer. You can then deploy it with Simulink® Compiler™.

Export 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.

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.

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.

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.

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.

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