Skip to content
Discussion options

You must be logged in to vote

Thanks for closing the loop. For future readers, the resolution was two-part:

  1. Restore importer-owned state as well as FMU state. The wrapper must save and restore its simulation time, next-event time, and the corresponding nextEventTimeDefined flag alongside the serialized FMU bytes. It must also preserve the FMI 2.0 Model Exchange state-machine and event-iteration rules.
  2. Initialize the model-owned state consistently. In this case, an internal variable in the exported Simulink model was not initialized correctly. That produced inconsistent behavior after an otherwise successful fmi2SetFMUstate. Correcting the initialization made serialization and restoration reproducible.

Because this p…

Replies: 4 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by chrbertsch
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
4 participants