Opened 9 years ago
Last modified 5 years ago
#3494 assigned defect
Start values not taken from modelDescription.xml
Reported by: | Marcus Walther | Owned by: | Willi Braun |
---|---|---|---|
Priority: | high | Milestone: | Future |
Component: | FMI 1.0 | Version: | |
Keywords: | Cc: | Adrian Pop, Willi Braun |
Description
The start values that are written in the modelDescription.xml are not passed to the FMU before initialization.
How to reproduce:
- take the bouncing-ball model from testsuite/openmodelica/fmi/ModelExchange/1.0 and export it to FMU 1.0 (either with C or C++ Runtime)
- the initial height of the ball is "1.0"
- change the start-value in the modelDescription.xml to "2.0" and repack the FMU
- if you now simulate it again, the height still starts at "1.0"
If I understand the FMI Standard correctly, than the start-values should be taken from the modelDescription.xml and passed to the FMU before the initial system is solved. I know that we are using the FMI-Library to import these stuff and it seems that the library is not passing the start-values if we just call "fmi1_import_instantiate_model" and "fmi1_import_initialize".
Change History (3)
comment:1 by , 9 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:2 by , 9 years ago
comment:3 by , 5 years ago
Component: | FMI → FMI 1.0 |
---|
Note:
See TracTickets
for help on using tickets.
Willi, if you update the
dumpVariable
function to handle the case when variable has novariability/causality
then you don't need to change anything else. And it will fix things for both FMI 1 & 2.