KarlWernersson
KarlWernersson
Some probably more an issue of FMPY than Dymola but if the original Modelica model could be provided or the minimal example I can look at it.
Hi would it not be easier to state the max doStepSize in the xml? If you want to change this dynamicaly i dont see how solution 3 would be better...
The problem with introducing something like this is that it would enforce all importers to support it, as this is not optional for an FMU that uses this functionality. I...
But is this at all a backwards compatible change? An Importer cannot ignore these function calls this as the FMU would otherwise be faulty. Isn't it better to work on...
I am all for the initiative, however assuming memory layout based on the order variables appear in modelDescription.xml is not feasible, in addition there might be internal variables not exposed...
Also if you share memory with the FMU and the master isn't get/set redundant?, you would just need a update/compute function that could replace all the get/set functions
Since this is an enhancement I don't see this as an 2.0.1 issue, Proposal, move to 3.0
I do not see what should be clarified for 2.0.1
fix in hybrid co-sim
Well, if model structure/derivatives is used the states are exposed. So that functionality is already there Then one could use setFloat64 directly if one wants to avoid the function setContinousStates...