-
Notifications
You must be signed in to change notification settings - Fork 41
generated .fmu file is not runnable in Matlab/Simulink #222
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
Comments
We experienced the same. The FMU ran once, then MATLAB would crash on the second run. Have a look at this setting: https://se.mathworks.com/help/simulink/gui/fmuimportblocks.html;jsessionid=8d5c9ea364961b4142a101596f3b I MATLAB use the command: This fixed the problem for us. |
Which version? |
Matlab R2023b |
pythonfmu version,The latest version of pythonfmu has fixed this issue. |
Set a communication step size (not -1). If that does not work, try adding some log statements to check the internals of the model. |
We found a work around this problem.
And check if the FMU is running in Matlab/SIMULINK |
@RajKumar1242 What you outline sounds like a general PATH issue. PythonFMU needs to be able to load Python. These .dlls should be added to PATH (or similar temporal shell solution). No need to add them inside the FMU. |
The python3.dll and python313.dll and DLLs are added to the PATH and we still have this issue. So, we tried adding direct dlls to the binaries folder. Should also try adding vcruntime140.dll and vcruntime140_1.dll to the PATH? |
vcruntime140 should be located in system32 folder, which should be pre-populated on PATH. Now, by having these .dlls with the FMU they do get loaded before any other (not already loaded dlls), so it may solve an ordering issue in case you have conflicting dlls on PATH. |
Hi, I generated a .fmu file according to the tutorial then imported to the Matlab/simulink, but matlab will crash after running it.
The text was updated successfully, but these errors were encountered: