FMUComplianceChecker icon indicating copy to clipboard operation
FMUComplianceChecker copied to clipboard

FMI Compliance Checker for validation of FMUs 1.0 and 2.0

Results 40 FMUComplianceChecker issues
Sort by recently updated
recently updated
newest added

**Reported by cbertsch on 8 Jan 2017 08:06 UTC** The FMI Compliance Checker 2.0.3 does currently not check for mandatory elements of the model structure in the modeldescription.xml p.58 of...

bug
P: major

**Reported by aviel on 22 Sep 2016 08:37 UTC** In FMI 2.0, the units referred to by the simple types or scalar variables shall be defined in the unit definitions...

bug
P: minor

**Reported by maplesoft on 16 Jun 2016 19:11 UTC** For FMI 1.0 Model Exchange, the FMUChecker (version 2.0.3b2) fails to exit when fmiGetReal() returns an error. When the FMUChecker log...

bug
P: major

**Reported by ottot on 5 Feb 2016 07:59 UTC** The compliance checker ignores the `nominalsOfContinuousStatesChanged` and `valuesOfContinuousStatesChanged` `eventInfo` flags except for the last call during event iteration. See the following...

bug
P: blocker

**Reported by andreas.junghanns on 12 Nov 2015 12:13 UTC** It is currently not clear to everyone what the Compliance Checker should be used for. ---- Migrated-From: https://trac.fmi-standard.org/ticket/355

P: major
discussion

**Reported by cbertsch on 9 Nov 2015 19:16 UTC** Currently for C-source code FMUs only the XML file can be checked. As more and more support import and export of...

enhancement
P: major

**Reported by andreas.pfeiffer on 30 Jan 2015 07:27 UTC** If an FMU contains both ME and CS models, then the FMU compliance checker simulates ME and CS, but there is...

bug
P: trivial

**Reported by anonymous on 14 Dec 2012 21:38 UTC** The official FMU Checker 2.0a1 (on Windows 7) crashes if the loaded FMU DLL gives an exception like an access violation...

enhancement
P: trivial

https://github.com/modelica-tools/FMUComplianceChecker/blob/dcc15abc94038a7afb8d4828d2bf3ea359de6c09/src/FMI2/fmi2_me_sim.c#L267 The states should not be set to their nominal values when the nominal values change. Since the checker currently uses a fixed step euler it doesn't have any use...

With FMUComplianceChecker v2.0.4 I can see an error message if `freeMemory` was called less often than `allocateMemory`, e.g., ``` [ERROR][FMUCHK] Memory leak: freeMemory was not called for 1 block(s) allocated...