Importing an FMU - MapleSim Help

Online Help

All Products    Maple    MapleSim


Home : Support : Online Help : MapleSim : Using MapleSim : Building a Model : Working with Subsystems : tasks/building/subsystems/importFMU

Importing an FMU

You can import a model or component created in other FMI-compatible software into your model.

To import an FMU:

1. 

Click Import an FMU ( ) in the main toolbar. Alternatively, from the File menu, select Import FMU... .

2. 

Click Browse... .

3. 

Browse to the location of your .fmu file, select it, and then click Open.
In the FMU Import dialog, the fields in the General and Advanced tabs are populated with information about the FMU. You can access this information after you import the FMU (see the following note for details).

4. 

Enter a name for the component in the Component Name field.

5. 

Required For Co-Simulation FMUs: Enter a value in the FMU Synchronization Time field.  
See the notes section for more information on this option.

6. 

Select Attach to MapleSim Model if you want to attach the FMU to your model.
See the notes section for more information on this option.

7. 

Click OK.
The FMU is imported into your model. Components are converted to shared subsystems and can be found in the Components palette under the Local Components ( ) tab. To use a component, drag it onto the Model Workspace and connect it to other components. When you select an FMU component in the Model Workspace, the Properties tab ( ) shows the properties of the component, including the FMU file type and the location of the FMU file on your computer (if you did not attach the FMU file to your MapleSim model).

Notes:

• 

MapleSim currently supports importing FMI 2.0 Model Exchange and Co-Simulation models for both variable and fixed-step integrators.

• 

FMU Synchronization Time: This value must be specified for Co-Simulation FMUs and it represents the time interval at which the FMU will be synchronized with the rest of the system.  If the FMU specifies stepSize in the DefaultExperiment element of the modelDescription.xml file then this value is interpreted as a minimum communication step size for the Co-Simulation FMU.  Therefore, the synchronization interval can not be smaller than that value.  For fixed-step integration, the synchronization interval can not be smaller than the step size.  Additionally, if the FMU has the attribute canHandleVariableCommunicationStepSize set to false, then the synchronization interval must be a multiple of the fixed-step integrator step size (and communication step size if specified).  For variable-step integrators, the largest step taken will be limited to the smallest synchronization step size of all of the CoSimulation FMUs. This limitation may be more severe if the FMUs have widely differing synchronization step sizes.  The synchronization interval parameter can be changed after import, as it is accessible in the parameter inspector view.

• 

Attach to MapleSim Model: Attaching the FMU makes it more convenient to share your model with other users because the .fmu file will be embedded in the model. However, if you need to make changes to the FMU, you will need to delete the old FMU shared subsystem from your MapleSim model and then import the updated .fmu file.
If you do not attach the FMU to the MapleSim model, MapleSim references the location of the .fmu file on your computer. Updates to the .fmu file will be included in your MapleSim model the next time you open the MapleSim model. However, if you move the .fmu file to another location on your computer, your MapleSim model will not work the next time you open it. Also, you may not be able to share your model with other users.

• 

The information shown in the FMU Import dialog can be viewed in MapleSim after you import the FMU. To view this information, in the Attachments tab ( ) select the FMU from the FMUs palette, and then select the Properties tab ( ). You can do this even if you did not attach the FMU to your model. (An unattached FMU will have link icon ( ) next to its entry in the FMUs palette.)

See Also

Grouping Components into Subsystems

Managing Subsystems and Custom Components

Trademark Attributions