Versions Compared

Key

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

...

FMU component

Absolute or relative (to the model directory) path to FMUs if they are required.
This path must be inside single quotes ('). Alternately, the Path button can be used.

Activate FMU logger

When this option is checked, the two following options are made visible from the Block Parameters: Solver, Library Tab:

  • Log level

  • Log filter

Offline mode

The FMU logger is not supported in offline mode.

RT-LAB mode

If checked, the messages regarding initialization and runtime will be printed in the MATLAB command window.
This log can help debug an FMU model. 

...

logging messages from FMU components are printed to the RT-LAB display console.

Log level

Log levels below the selected log level are silenced. When a FMU component produces logging, a fmiStatus is passed to the functions->logger callback as per the FMI for Co-Simulation v1.0 specification. The mapping between fmiStatus and log levels is detailed as follows:

  • fmiOk: info

  • fmiWarning: warn

  • fmiDiscard: warn

  • fmiError: error

  • fmiFatal: critical

Log filter

The log filter is a string containing coma separated values. The values can either be the modelName field from the modelDescriptor.xml of FMU components or the component instance’s short name. When the filter is empty, no filter is applied, otherwise the filter excludes everything that isn’t a match.

...

Note

Enabling the FMU logger comes with a performance penalty which may cause overruns. This option should be enabled for debugging purposes only.