This page lists the current limitations of the JModelica.org platform. The development of the platform can be followed at the Trac site, where future releases and associated features are planned. The JModelica.org platform download page has links to compliance reports detailing the current MSL compliance.
The Modelica compliance of the front-end is limited; the following features are currently not supported:
The support for String variables and parameters is limited.
Partial support for external functions; records are not supported as arguments or return values.
The following built-in functions are not supported:
The following built-in functions are only supported in FMUs:
In the Optimica front-end the following constructs are not supported:
Annotations for transcription information.
The following limitations apply to FMUs compiled with JModelica.org:
Source code FMUs can not be generated, only binary FMUs.
Functions for setting and getting string variables do not work.
The dependenciesKind attribute in the XML file for FMU 2.0 is not generated.
Directional derivatives are known to have limitations in some cases.
Asynchronous simulation is not supported.
FMU states (set, get and serialize) are not supported.
The following limitations apply to optimization using CasADi-based collocation with JModelica.org:
Incomplete support for the
Boolean types: To the extent that they are supported, they are treated more or less like reals.
No support for
Attributes with any name can be set on any type of variable.
The property of whether an optimization problem has free or fixed time horizon cannot be changed after compilation.
The following limitations apply to JMUs compiled with JModelica.org (note that JMUs are deprecated in JModelica.org 1.15):
The ODE interface requires the Modelica model to be written on explicit ODE form in order to work.
Second order derivatives (Hessians) are not provided.
The interface for interacting with JMUs does not comply with FMI specification.
Discrete variables are not supported in JMUs.