Skip to content
This repository has been archived by the owner on Oct 17, 2023. It is now read-only.

FMUChecker-2.0.3 issues in Continuous Time Mode #20

Open
modelica-trac-importer opened this issue Feb 8, 2018 · 2 comments
Open

FMUChecker-2.0.3 issues in Continuous Time Mode #20

modelica-trac-importer opened this issue Feb 8, 2018 · 2 comments

Comments

@modelica-trac-importer
Copy link

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

@modelica-trac-importer
Copy link
Author

modelica-trac-importer commented Feb 8, 2018

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.

@modelica-trac-importer
Copy link
Author

Modified by cbertsch on 4 Jun 2017 19:39 UTC

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant