You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 17, 2023. It is now read-only.
Reported by arunkumar.palanisamy on 31 Oct 2016 11:24 UTC
I was doing FMU cross checking tests with fmus (FMI2.0) generated from OpenModelica, When performing tests I am getting errors related to some fmi2 functions in continuous-time mode. According to the fmi2specification Page 85.
In Continuous-Time Mode only fmi2SetReal is allowed, but some examples involves setting fmi2setInteger and fmi2setBoolean in time continuous mode also, Currently when generating fmus from OpenModelica we generate fmus allowing only fmi2SetReal in Time-continuous mode. So when checking with FMU compliance checker the model fails.
Should all the fmi2set(Integer,string,Boolean) be allowed in time-continuous mode like fmi2setReal?
Comment by cbertsch on 26 Jan 2017 16:12 UTC
fmi2set(Inter,string,Boolean) in continuous time is forbidden. Thus this is not an issue of "all specification documents", but an error of the simple simulator that is part of the compliance checker, see #26.
Reported by arunkumar.palanisamy on 31 Oct 2016 11:24 UTC
I was doing FMU cross checking tests with fmus (FMI2.0) generated from OpenModelica, When performing tests I am getting errors related to some fmi2 functions in continuous-time mode. According to the fmi2specification Page 85.
In Continuous-Time Mode only fmi2SetReal is allowed, but some examples involves setting fmi2setInteger and fmi2setBoolean in time continuous mode also, Currently when generating fmus from OpenModelica we generate fmus allowing only fmi2SetReal in Time-continuous mode. So when checking with FMU compliance checker the model fails.
Should all the fmi2set(Integer,string,Boolean) be allowed in time-continuous mode like fmi2setReal?
Migrated-From: https://trac.fmi-standard.org/ticket/390
The text was updated successfully, but these errors were encountered: