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
Co-Simulation: The value may change at communication points and in Event Mode, if supported.
So it's not clear whether discrete values can change at communication points if Event Mode is used.
On a similar note, does the importer have to enter Event Mode if a non-float value (e.g. a crank speed sensor providing its value as an UInt64) changes?
The text was updated successfully, but these errors were encountered:
Since we now require CS FMU's to declare if they will use event mode. I don't see it as practical to no enforce event mode for changing discrete values of a CS FMU if it uses event mode, as they are forced to do it for other events.
Integers are discrete values and therefore a change requires event handling. as events are discrete changes.
So if the FMU uses event mode it has to enter event mode each time an integer changes its value.
Currently the Spec reads:
So it's not clear whether discrete values can change at communication points if Event Mode is used.
On a similar note, does the importer have to enter Event Mode if a non-float value (e.g. a crank speed sensor providing its value as an
UInt64
) changes?The text was updated successfully, but these errors were encountered: