meEventUpdate and discrete inputs

[modelica-trac-importer]

Reported by mauss on 4 Oct 2009 13:42 UTC
The mathe. description says: "The non-real (input) variables change
their values only at events." Who generates these events? The FMU
could use event indicators to detect changes of discrete input
variables. Alternatively, the environment could by responsible
for calling meEventUpdate after having changed a discrete input
using meSetBoolean/Integer/String. What is the policy here?

---

Migrated-From: https://trac.fmi-standard.org/ticket/5

[modelica-trac-importer]

Modified by andreas on 25 Nov 2009 20:06 UTC

[modelica-trac-importer]

Comment by Torsten Blochwitz on 4 Dec 2009 08:34 UTC
For me we do not a further clearification. Inputs are read by the FMU. That means they are set by the environment. For that reason the environment is responsible for calling meEventUpdate after setting a discrete input.

[modelica-trac-importer]

Comment by Martin Otter on 6 Dec 2009 17:40 UTC
Defined this more precisely in section 2.1:

An event is always triggered from the environment in which the FMU is called (so it is not triggered inside the FMU). Typically, this is performed in the following way by evaluating the three conditions above in an appropriate way: [...]

[modelica-trac-importer]

Modified by dietmarw on 7 Sep 2012 10:18 UTC