-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
32bits and 64bits FMUs for all examples #10
Comments
Actually, we need to generate binaries from different tools - because we have seen with Michael Tiller that there are issues with FMUs depending on tool. I recommend that we generate the FMUs using:
We can't generate them using Dymola because we lack a license that would allow us to do this kind of job. |
I thought the only problem was that FMUs generated by Dymola required a dymola license to execute, or that we buy a more expansive Dymola license that allow standalone FMUs. @lvanfretti it would be surprising that FMI being a standard, you'd have software dependent issues. |
@MaximeBaudette Yes, we can't generate FMUs with Dymola because we lack the license for Binary Code Export. However, what I noticed is that, when the FMU created by Dymola without license is used, FMI Toolbox looks for the license on our server. Since, for I don't know which reason, the connection to it is not good, the simulation and estimation process is interrupted. I should note here that this was happening with the quite old version of RaPId so I don't know if it's the same now. But, in any case, those kinds of FMUs (without the license) we should not include in the repo. Regarding the FMUs created with JModelica, I haven't experienced any problems. The only thing that might cause some issues is that JModelica is much stricter when it comes to the rules of Modelica language so I had to change some models a little bit. I should also note that we haven't tried running RaPId simulations with FMUs generated with MapleSim. |
All examples should be delivered with binaries for both 32 bits and 64 bits.
The text was updated successfully, but these errors were encountered: