AmesimKnowledge

Functional Mock-up Interface > Importing and using an FMU > Command line tool reference

Command line tool reference

Executable name: fmi_import_compiler. It takes one required argument, the path to the FMU to import:

fmi_import_compiler [options] <model.fmu>
Option Meaning
-v Display application version
-d Enable debug messages
-info Show version, type, and platform information about the FMU
-compliancy <strict|relaxed> Compliancy level with FMI for Model Exchange or Co-simulation specs
-outdir <outdir> Output directory
-ccomp <ccomp> C submodel compiler; special keywords release, debug, nocomp, or none
-ccopt <ccopt> Options passed to the C compiler
-name <name> Name of the submodel to be created
-preferred <cs|me> Preferred interface type for mixed-type FMUs (both Model Exchange and Co-simulation)
-help Display the option list

Defaults when options are omitted

  • Import submodel created in the current directory if -outdir is missing.
  • Compliancy level is strict if -compliancy is missing — import stops as soon as an error is detected in the FMU model description.
  • Import submodel compiled in release mode if -ccomp is missing.
  • Default platform compiler used if -ccopt is missing (Visual Studio on Windows, gcc on Linux). Other compilers can be selected via -ccopt (list available options via AMEcc_RELEASE -help). Example: to use the Mingw64/gcc bundled with Simcenter Amesim on Windows 64-bit, pass -win64_gcc -gcc.
  • Generated submodel name defaults to the FMU model identifier prefixed with MEIMP (Model Exchange) or CSIMP (Co-simulation), if -name is missing.

Source: https://docs.sw.siemens.com/en-US/doc/254352342/PL20251107523649413.amesim_collection.Functional_Mockup_Interface/Command_line_tool_reference · retrieved Tue Jul 07 2026 00:00:00 GMT+0000 (Coordinated Universal Time)