Creating and exporting FMU > FMU Export via scripting
FMU platform and architecture definition
To export an FMU, it is necessary to define one or more target.
FMU for Real Time
For FMU for Real Time, you only need to define one target. The list of possible targets is provided below.
| Real-time target (FMU architecture) | Simcenter Amesim platform | ||
|---|---|---|---|
| Name | Description, FMU package | Windows | Linux |
| AVL_intime | AVL Testbed.CONNECT (source code) | Available | Available |
| SIMWB32 | Concurrent SimWB x32 (source code) | Available | Available |
| SIMWB64 | Concurrent SimWB x64 (binary) | Available | Available |
| SIMWB64_SC | Concurrent SimWB x64 (source code) | / | Available |
| SCALEXIO_QNX | dSPACE SCALEXIO qnx (source code) | Available | Available |
| SCALEXIO_LNX | dSPACE SCALEXIO x32 (source code) | Available | Available |
| LABCAR32 | ETAS LABCAR x32 (source code) | Available | Available |
| LABCAR64 | ETAS LABCAR x64 (binary) | Available | Available |
| LABCAR64_SC | ETAS LABCAR x64 (source code) | / | Available |
| xMOD | FEV xMOD (source code) | Available | Available |
| LINUX_X64_RT | Linux-based target x64 (binary) | Available | Available |
| LINUX_X64_RT_SC | Linux-based target x64 (source code) | Available | Available |
| LINUX_X32_RT_SC | Linux-based target x32 (source code) | Available | Available |
| NI_LNX_RT_X64 | NI Linux Real-Time x64 (binary) | Available | Available |
| SIMATICLiveTwin | SIMATIC LiveTwin (binary) | Available | Available |
| SIMATICLiveTwin_SC | SIMATIC LiveTwin (source code) | / | Available |
| SIMCENTER_TESTLAB_RT | Simcenter Testlab RT (binary) | Available | Available |
| SIMCENTER_TESTLAB_RT_SC | Simcenter Testlab RT (source code) | / | Available |
Example:
The command below:
$AME/python.bat $AME/interfaces/fmi/fmi_export.pyc cs 2.0 -a SIMWB64 -e
will generate a binary FMU for the Concurrent SimWB x64 real-time target.
Standard FMU
In the case of a standard FMU (i.e., an FMU for standard, non-real-time platforms), at least one compiler must be defined, knowing that only one compiler can be used for each FMU architecture.
Defining multiple compilers will produce a multi-architecture FMU. The list of compilers is shown hereafter. The list of available compilers depends on the compilers that are installed on the end-user’s machine. Remember that some compilers are distributed with Simcenter Amesim and do not require any specific installation.
| FMU architecture | Simcenter Amesim platform | |||
|---|---|---|---|---|
| Name | FMU architecture | Compiler | Windows | Linux |
| win64-gcc | win64 | Mingw64 | Available | / |
| win64-intel | win64 | Intel oneAPI compiler | Available | / |
| win64-vc140 | win64 | MSVC ≥ MSVC2015 | Available | / |
| linux64-gcc | linux64 | gcc (cross-compiler) | Available | / |
| linux64-gcc | linux64 | gcc | / | Available |
| linux64-intel | linux64 | Intel oneAPI compiler | / | Available |
Example:
The command below :
$AME/python.bat $AME/interfaces/fmi/fmi_export.pyc model cs 2.0 -a win64-vc140 -a linux64-gcc -e
will generate an FMU that includes binaries for the following architectures: win64 and linux64.
Limitations and requirements
FMU for real-time
The model must have been configured and preliminarily-tested using the fixed-step solver. Note also that only real-time capable libraries can be used (see Appendix B of the Real-Time Simulation manual for the complete list). The allowed FMU type is co-simulation. The FMI standard version and FMU customization must be chosen in accordance with the import capabilities of the chosen target. For a binary FMU generated for a Linux 64-bit target under Linux, please check the compatibility of the C library and the GCC compiler with the chosen target. In case of incompatibility, please generate a source-code FMU instead.
Source: https://docs.sw.siemens.com/en-US/doc/254352342/PL20250521841123434.amesim_collection.Functional_Mockup_Interface/xid2290031 · retrieved 2026-07-17