Skip to content

Import & Export

A model may leverage external data files or resources that are needed to fully parameterize or simulate it.

  • Imported data files are stored in a folder named Resources within a Library or Workspace package.
  • If a library includes a Resources folder, it is shown in the library browser.
  • For read-only libraries, resource files can be downloaded for local editing.

The Workspace package resource files can be uploaded and manipulated.


Upload resource file to a workspace🔗

This action is performed in the Workspace browser.

  1. Click the , button next to the Resources folder to upload a file to the Workspace resources folder.

  2. A file selector dialog will be opened. The selected file will be uploaded to the Resources folder.


Upload resource folder to a workspace🔗

This action is performed in the Workspace browser.

  1. Click the , button next to the Resources folder to upload a folder to the Workspace resources folder.

  2. A folder selector dialog will be opened. The selected folder with contents will be uploaded to the Resources folder.


Upload resource to a workspace by drag and drop🔗

This action is performed in the Workspace browser.

  1. Uploading files and folders can be done by dragging and dropping the resource in the Resources folder.

Import a resource file into a model🔗

Imported resource files can be imported into modelling components that support this kind of usage. Next to input fields that can use file references there is a filter button (). Clicking this button will show all matching data files in the library browser. By dragging the file into the appropriate field the correct reference to the data file is inserted.


Create a new folder🔗

This action is performed in the workspace browser.

  1. Click the , button next to the Resources folder to create a new folder to the Workspace resources folder.

Delete resource files🔗

  1. Click the icon next to a file.

Download resource files🔗

  1. Download a file from a Resources folder by clicking the download button next to that file.

Export FMU🔗

Any model can be exported as a FMU and distributed outside of Modelon Impact. The exported FMU-file can be imported in any FMI-compliant tool.

  1. Select the model in the library browser.

  2. Right click on a class and select the option Export FMU.

  3. Select Model Exchange or Co-simulation and press the EXPORT button.

Modelon Impact support FMI version 2.0. FMI 1.0 can be exported using the API.

Export of FMU is governed by Global FMU export settings.

Note

FMUs generated with Modelon Impact's on-premise installation should not be exported into Simulink at this point of time . Attempting to do so may result in a crash due to incompatible BLAS libraries.

A workaround is to import the FMU with the FMU block from FMI toolbox instead of the native FMU block in Simulink.

Import FMU🔗

FMU (Functional Mock-up Unit) Import allows the user to import models to be used in Modelon Impact.

FMUs

Modelon Impact supports import of Co-Simulation (CS) FMUs.

  1. Import of FMU requires an FMU is stored in a drive accessible on you workstation.
  2. Go to the top of the Workspace panel located to the left of the canvas.
  3. Click on the upward pointing arrow for FMU Import. Hovering the mouse on the arrow will display its function.
  4. Click on the FMU or zip-file and a window called IMPORT FMU is opened: - FMU can be renamed. - FMU can be stored in workspace of choice.
  5. Press IMPORT and the FMU is found as a branch of the selected workspace.
  6. The model is ready to be opened, duplicated or extended to be worked upon in the canvas.

Location of input and putputs of an FMI are indicated by arrow heads. If number of inputs and outputs exceed three (3), the icon will be presented in rectangular shape. Else it will be square shaped.


Export a model🔗

Download a model from your browser using the Export class functionality. The model is exported as a Modelica .mo file which can be opened in another Modelica tool or in a text editor.

Instructions to export a Modelica model:

  1. Select a model (class) in the library browser.

  2. Right click and select the option Export class.

Note

It may not be possible to simulate the exported model as dependencies are not included.

Import a model🔗

  1. A model or a package stored as a single .mo file can be imported directly.

Export a workspace🔗

Workspaces can be exported (downloaded). The ZIP file optionally contains all Modelica packages including resources and if desired also results and FMUs. This ZIP file can be re-imported (uploaded) at another point.

  1. Click on the "Export workspace" button (Download icon) on top of library browser.
  2. Optional (export configuration mode): Select or deselect models and data that should be included.
  3. Click on the "EXPORT" button.

If you are in the configuration mode of the workspace export, the "ADVANCED" button also appears. Here you have the possibility to configure your workspace for the App Mode of Impact. In Impact's App Mode, you can only work with the selected model.

Follow these additional steps between steps 2 and 3:

  • Click "ADVANCED" and in the appearing Advanced Settings toggle "Export for App Mode"
  • Select a model ("Model name") from your workspace - this will be the available model in the App Mode

Note

The workspace is exported to a *.zip file (not *.mo) and by default it includes the latest result files and compiled models (FMU). Exporting a workspace to a .zip file involves downloading the workspace.

Import a workspace🔗

  1. Open Modelon Impact
  2. Click on icon.
  3. Select a workspace to import. The imported workspace should be zipped.
  4. The import icon can be found at the top of the Workspace panel. Alternatively, by clicking on the Modelon logo takes the user back one step at a time until coming back to the start page.

Importing a package stored in a folder-based structure🔗

  1. Compress the folder into a .zip file.

  2. Import the zip-file.

    See the picture below for an example of the structure a folder-based Modelica package (MyPackage) should have for import; MyPackage.zip will be imported using the Import button in this case.

Note

The zip archive must have the same name as the package. The package name can be found within package.mo file.