Versions Compared

Version Old Version 3 New Version Current
Changes made by

Sylvain Ménard

Amira Aouina

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note

Platform requirement: FMUs are exclusively supported on 'OPAL-RT Linux RTLinux (x64 based)' platform.

FMUConfGenerator Tool description

...

The FMUConfGenerator tool should be executed in the format shown below:
FMUConfGenerator.exe -f <Path_to_FMU_folder>\fmu_file_name.fmu
The tool is invoked from a command line using the following arguments:

Parameter name

Required

Description

-f

Yes

Specifies a path to the FMU file

-m

No

Specifies the run mode which may be:- rt: real-time on a specific target - simulation: non-real time but running on its own core(s)- test: OS managed execution of the process
Default: simulation

-t

No

Specifies the time step in seconds

Anchor
generated_files
generated_files
Generated files overview

The FMUConfGenerator tool produces a set of configuration-files which are required by RT-LAB Orchestra Framework and URTMain tools that operate on the FMU archive file and helps in its integration.
All files are generated within a directory with the same name as the model. The model name is extracted directly from the modelDescription.xml contained within the FMU file. This directory is contained inside the folder under which the provided *.FMU file resides. If directory does not exist it is automatically created by the tool. So, the path of the directory created by the tool will be as follow:
<path_to_fmu_file>\<fmu_file_name><modelName>


The following 4 files are generated :

File name

Description

<fmu_file_name>

<modelName>.xml


Contains all the inputs and outputs of the FMU.

The inputs are grouped under the PUBLISH set whereas the outputs are grouped under the SUBSCRIBE set.

These two sets, PUBLISH and SUBSCRIBE, together are defined within a DOMAIN which is named as same as the FMU archive file.

driver_

<fmu_file_name>

<modelName>.opal


Specifies the run mode which may be:

- rt: real-time on a specific target

- simulation: non-real time but running on its own core(s)

- test: OS managed execution of the process
Default: simulation

connections_

<fmu_file_name>

<modelName>.opal

Internal configuration file for communication between Orchestra Framework and Simulink model

urtmain_

<fmu_file_name>

<modelName>.json

  • Configuration file of URTMain, which run the FMU

Anchor
using_generated_files
using_generated_files
Using generated files in RT-LAB

...