Dear,
I have a FMU with a parameter that I want to change before the simulation. I use the set_method to change this parameter.
If I initialize the FMU, the parameter is changed to his previous quantity. How can I fixe this problem and why is he overruling my setting? The new quantity of the parameter is a valid value and it gives no problem If I adapt my model by myself. So I don't know why he is overruling my setting before the initialization.
With kind regards,
Rutger
FMU initialization overrules setting parameter
Mon, 2012-05-21 11:58
#1
FMU initialization overrules setting parameter
Sun, 2012-05-27 22:10
#2
Hi Rutger,
Which tool did
Hi Rutger,
Which tool did you use to generate the FMU? Only parameters/variables/input with a start attribute set in the XML-file contained in the FMU can be set prior to initialization without being overridden. It may be that we don't check this properly in PyFMI.
If you unzip the FMU and find the corresponding parameter declaration in modelDescription.xml, is there a start-attribute set in for this variable? Also, you may check the parameter declaration in the Modelica code - what does i look like.
Best
/Johan
Tue, 2012-05-29 09:29
#3
Hi,
I use Dymola to
Hi,
I use Dymola to generate the FMU. But the problem is solved. I set after my parameter an annotation(Evaluate=False) and then it works.
But did you change something about the FMU initialization? Because I can't initialize my FMU anymore from Sunday evening about 21:15. And I didn't change anything at my FMU. So this is really strange. I made already another FMU but still I can't initialize my FMU anymore.
With kind regards,
Rutger
Tue, 2012-05-29 10:52
#4
Hi,
I get the following log
Hi,
I get the following log report from the FMU.
[['Model', 3, '', 'fmiInitialize: dsblock_ failed, QiErr = 1']]
What does this report mean?
With kind regards,
Rutger
Tue, 2012-05-29 12:47
#5
Hi,
The problem was due to
Hi,
The problem was due to the license of Dymola that was expired and It's fixed
With kind regards,
Rutger