Skip to content
This repository has been archived by the owner on Oct 17, 2023. It is now read-only.

FMUComplianceChecker-2.0.3 illegal calling sequence #26

Open
modelica-trac-importer opened this issue Feb 8, 2018 · 1 comment
Open

Comments

@modelica-trac-importer
Copy link

modelica-trac-importer commented Feb 8, 2018

Reported by awad.mukbil on 26 Jan 2017 15:29 UTC
During my work on creating reference FMUs, I tried to test the Compliance Checker with a reference FMU that deals with integer variables to test integer capabilities. I provided the Compliance Checker with integer inputs and the FMU triggered the following errors:

[FMU][logError][FMU status:Error] fmi2SetInteger: Illegal call sequence.
[FATAL][FMUCHK] Simulation loop terminated at time ... since FMU returned status: Error

because the it calls fmi2SetInteger in Continuous-Time Mode, which is not allowed according to the standard p. 85.

[FMU][logError][FMU status:Error] fmi2Terminate: Illegal call sequence.
[ERROR][FMUCHK] fmiTerminate returned status: Error

Last error returned fmi2Error, by which the state changed to error and it is not allowed to call fmi2Terminate.

This is related to the ticket #20. The experiment data are attached.
experiment.zip


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

@beutlich
Copy link
Contributor

beutlich commented Mar 15, 2021

This bug (of major priority) still can be observed in FMI/FMU Compliance Checker 2.0.4 and also for FMI 1.0.

beutlich added a commit to beutlich/LastLib that referenced this issue Mar 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants