User manual

Dymola 2013 FD01 Release notes 39
can be set to “me”, “cs” and “all” for inclusion of “model exchange”, “co-simulation” and
“all” respectively.
In addition, the new string argument
fmiVersion
controls the FMI verision (“1” or “2”) of the FMU. For FMI 2.0, see below.
The default values for the new arguments to translateModelFMU are chosen in a backward
compatible manner; old calls to it will behave the same except that fmiType defaults to “all”
instead of “me”.
Finally, for result storing (argument
storeResult = true), the result file is named
according to the instance name chosen during FMU initialization, <instance name>.mat,
instead of the generic “dsres.mat”.
Note that Dymola does no longer generate any static import library in the binaries folder
when exporting an FMU, see also section “No import library required in imported FMU”
above.
FMU Export on Linux
The FMU export on Linux requires the Linux utility “zip”. If not already installed, please
install using your packaging manager (e.g. apt-get) or see e.g. http://info-zip.org.html
.
Updated FMU export from Simulink
The package to generate FMUs from Simulink models (Dymola/Mfiles/rtwsfcnfmi.zip) has
been updated. The main changes are
• MATLAB support for releases R2007 to R2011b
• Support for 64-bit MATLAB installations
• Support for Visual Studio 2010 compiler
See the README file contained in the package for details and updated installation
instructions.
FMU import
No import library required in imported FMU
The previous restriction that imported FMUs needed to have a static import library in the
binaries folder (in addition to the DLL) is now removed. Also, no such libraries are
generated by Dymola when exporting an FMU.
Repeated import of FMU by scripting improved
A new argument
promptReplacement has been added to the importFMU function:
importFMU(fileName, includeAllVariables, integrate,
promptReplacement)