If an FMU version 3.0 is imported with the resettable option enabled, and a reset is triggered by the corresponding signal, the instance time is not correctly reseted. This means that after the reset the currentCommunicationPoint argument of the fmi3DoStep function is not consistent with the startTime value defined when calling fmi3EnterInitializationMode. Notice that this issue only exists with FMI 3.0, this is working for version 2.0.
This issue can be fixed by adding:
instance->time = startTime;
in the FMI3EnterInitializationMode function.
If an FMU version 3.0 is imported with the resettable option enabled, and a reset is triggered by the corresponding signal, the instance time is not correctly reseted. This means that after the reset the currentCommunicationPoint argument of the fmi3DoStep function is not consistent with the startTime value defined when calling fmi3EnterInitializationMode. Notice that this issue only exists with FMI 3.0, this is working for version 2.0.
This issue can be fixed by adding:
instance->time = startTime;
in the FMI3EnterInitializationMode function.