Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Stair] f_event is not computed by fmi3GetInt32() #554

Closed
PTaeuberDS opened this issue Aug 12, 2024 · 0 comments · Fixed by #606
Closed

[Stair] f_event is not computed by fmi3GetInt32() #554

PTaeuberDS opened this issue Aug 12, 2024 · 0 comments · Fixed by #606
Labels
bug Something isn't working

Comments

@PTaeuberDS
Copy link
Collaborator

According to the FMI 3.0 standard, in Event Mode fmi3Get{VariableType} computes f_event (s. 2.3.5. State: Event Mode).
When fmi3UpdateDiscreteStates() is called and f_event is already computed (i.e., fmi3Get{VariableType} was called before), fmi3UpdateDiscreteStates() only computes the time of the next time event and Clock ticks.

In Stair.fmu:
When fmi3GetInt32() is called in Event Mode, only the old value is returned without triggering the computation of f_event. The computation is performed in fmi3UpdateDiscreteStates(). If the importer does not call fmi3GetInt32() again, it does not receive the updated data in this Event Mode.

@t-sommer t-sommer added the bug Something isn't working label Aug 13, 2024
t-sommer added a commit to t-sommer/Reference-FMUs that referenced this issue Oct 9, 2024
t-sommer added a commit to t-sommer/Reference-FMUs that referenced this issue Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants