Generated import submodel

Once the Import Tool has been invoked on a FMU, a new Simcenter Amesim library containing the generated import submodel is created in the output directory given by the -outdir option (or the current directory by default). This library defines a new FMI category. In the node directory of the new library (see ref. [6] for details about the structures of a library node directory), the following files are either created or updated if the directory and files previously existed:

Figure 9: Content of the node directory created by the Import Tool

The AMEIcons file defines the new FMI category:

• Icons/fmi.svg

• Icons/fmi.icosvg

• %FMI imported blocks

The submodels.index file references the generated import submodel:

• ./submodels

• fmuin001out001

• &MEIMP<model_identifier> fmi

The last line may also appear as

• &CSIMP<model_identifier> fmi

when a slave FMU for Co-simulation is being imported.

The Icons directory contains two files referenced by the AMEIcons file:

• fmi.svg defines the category icon

• fmi.icosvg defines the submodel icon

The submodels directory contains the generated import submodel. At least two files are generated in this directory for Model Exchange:

• MEIMP.spe is the standard SPE file which describes the submodel

• MEIMP.c is the source file of the submodel

For Co-simulation, the files are called CSIMP.spe and CSIMP.c.

The submodels directory contains also a platform subdirectory (win32 for Windows, lnx for Linux, following the Simcenter Amesim conventions). The compiled object of the import submodel is stored in this platform subdirectory.

In addition to these directories, a directory with the same name as the FMU is also created (it is shown as model in the figure above).It contains the unpacked FMU zip-file. It is the exact image of the FMU distribution structure described in [1] or [2], with at least one subdirectory called binaries in which is stored the platform-dependent binary file of the model (in the Model Exchange case) or of the simulator (in the Co-simulation case).

The new Simcenter Amesim library node has to be added to the Category Path List of Simcenter Amesim (see figure below).

Figure 10: the Simcenter Amesim Category Path List showing the new library node directory

In Sketch mode, the new FMI category titled "FMI imported blocks" then appears in the Library Tree (see figure below). The generated icon is available as any ordinary Simcenter Amesim submodel icon. It can be dropped in multiple instances onto the sketch area shown on the left.

Figure 11: the Simcenter Amesim main window showing the new FMI category in the Library Tree