FMI Type Selection

With FMI 2.0, an FMU may simultaneously offer both Model Exchange and Co-simulation interfaces (an optional choice made by the exporting tool — not all FMUs or exporters support mixed-type FMUs).

When importing a mixed-type FMU into Simcenter Amesim, the preferred interface must be specified via the -preferred option, taking cs (Co-simulation) or me (Model Exchange). In the FMU Import Assistant, this is exposed as a Preferred simulation type radio button on the assistant's second step (Import settings).

If the FMU declares only one interface type, -preferred is ignored and the FMU imports using its only declared type.

Generated import submodel

Once the Import Tool runs on an FMU, a new Simcenter Amesim library containing the generated import submodel is created in the output directory (-outdir, or current directory by default). This library defines a new FMI category. Within the library node directory, the tool creates/updates:

• Icons/fmi.svg and Icons/fmi.icosvg — icon files referenced by the AMEIcons file, which defines the new "FMI imported blocks" category.
• submodels.index — references the generated import submodel, e.g. an entry like &MEIMP<model_identifier> fmi (Model Exchange) or &CSIMP<model_identifier> fmi (Co-simulation), under a subdirectory such as ./submodels/fmuin001out001.

The generated submodel behaves as an ordinary Amesim submodel once created (see "Getting started").