Import assistant reference

The first step of the assistant

The first step of the assistant is entitled "Welcome … Choose an FMU to import". It features four elements that have to be provided by the user:

• The first field, entitled FMU, receives the absolute path to the FMU to be imported. The … button on the left opens a file selection browser that helps selecting the FMU file. After closing this browser, the field is filled with the absolute path to the selected file.

• The second field, entitled Submodel storage directory, receives the absolute path to the directory in which the import submodel and the corresponding library node is to be generated. This could be a directory containing an existing library node, in that case the import submodel is automatically added to this existing library. The … button on the left opens a file selection browser that helps selecting a directory.

• The third field, entitled Submodel name, is enabled by a check box on the left. If this check box is not enabled the name of the import submodel is automatically generated by prepending either MEIMP (for Model Exchange FMU) or CSIMP (for Co-simulation FMU) to the name of the FMU1.

• The last element, entitled Add submodel to category path list is a checkbox which specifies – if enabled – that the path to the newly created (or updated) library node has to be automatically added to the category path list of Simcenter Amesim. If the corresponding path is already part of the category path list, the checkbox can be left disabled.

The second step of the assistant

The second step of the assistant is entitled "Import settings … Set import options". It allows you to choose the compiler used for building the generated import submodel. With Windows platforms, three options are usually available:

• GNU GCC (64-bit)

• Intel oneAPI 64-bit

• Microsoft Visual C++ 2017 to 2022 (64-bit)

The first option corresponds to the Mingw64/gcc compiler provided with the Simcenter Amesim distribution. The second option can be selected if the Intel oneAPI compiler is installed. The last option can be used if a version of Microsoft Visual Studio is installed and available in the Simcenter Amesim environment.

For Linux platforms the available options are:

• GNU GCC compiler 64-bit

• Intel oneAPI compiler 64-bit

Warning

In all cases the compiler chosen must be consistent with the one selected in Simcenter Amesim for compiling the models that make use of the import submodel.

According to the choice made at this step, the corresponding -ccopt option is passed to the command line tool (see the Platform selection section hereafter).

The last field entitled Additional compilation settings is aimed at specifying some infrequent options to the command line tool (see next section).

The third step of the assistant

The last step of the assistant, entitled "Results … Native Simcenter Amesim submodel generation results" does not require any interaction from the user. It only reports the messages produced by the command line tool:

• The type (Model Exchange or Co-simulation), version (1.0, 2.0 or 3.0) and supported platforms of the FMU being imported

• The warning or error messages reported by the Import Tool while checking the compliance of the FMU with respect to the specification

• The compilation messages reported by the C compiler (which is actually called through the AMEcc_RELEASE or AMEcc_DEBUG script of the Simcenter Amesim distribution)

1

For FMI 1.0 this is the name of the FMU file, whereas for FMI 2.0 and 3.0 this is the model identifier of the Co-simulation element declared in the description file of the FMU.