Wrong results after the latest back end changes

[Lennart Ochel]

There are wrong results for the following two fmu tests after the latest back end changes (#3452):

openmodelica/cppruntime/fmu/modelExchange/1.0/CoupledClutches_FMU1_CPP.mos
openmodelica/cppruntime/fmu/modelExchange/2.0/CoupledClutches_FMU2_CPP.mos

[Marcus Walther]

The BouncingBall-model has the same issue if it is translated to a model exchange FMU with the c++ runtime. I started to debug it and I noticed that the height "h" of the ball is wrong at the beginning. The modelDescription says the start value should be 1:

<ScalarVariable name="h" valueReference="0" description="height of ball" ...>

<Real start="1.0"/>

</ScalarVariable>

But the setReal-Function is not called for the value with reference 0, it is only called for the values with the references 5 and 6. The function setContinuousStates is called later and with calculated values (that are wrong as well), so the height of the ball is 0 at the beginning.
@lochel: Do you know why this value is not set according to the modelDescription at the beginning? Have I overlooked something?

[Marcus Walther]

I have added a debug flag that puts all start values hard coded into the c++ code. With this modification, the c++ runtime Bouncing-Ball-FMU can be correctly imported and simulated with the c-Runtime. However, this will not fix the issue with the CoupledClutches. Who is responsible for the FMU-import and can be added to this ticket? We really need a working FMU export / import.

Besides that I've noticed that the FMU c++ import is broken. We have used the code generated by the c-runtime for the import, but it seems that the c-runtime code is not longer compatible to the c++-runtime code, especially for models with events. I think that's not an issue, because we do not really need a c++ based fmu-import in OMC. Thus I will change the c++ based FMU-tests to use the c-runtime as import-environment.

[Martin Sjölund]

Milestone pushed to 1.9.5

[Martin Sjölund]

Milestone renamed

[Martin Sjölund]

Ticket retargeted after milestone closed

[Martin Sjölund]

Milestone moved to 1.12.0 due to 1.11.0 already being released.

[Francesco Casella]

The milestone of this ticket has been reassigned to "Future".

If you think the issue is still valid and relevant for you, please select milestone 1.13.0 for back-end, code generation and run-time issues, or 2.0.0 for front-end issues.

If you are aware that the problem is no longer present, please select the milestone corresponding to the version of OMC you used to check that, and set the status to "worksforme".

In both cases, a short informative comment would be welcome.