Skip to content
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

nested FMU: Access violation #168

Closed
fajansen opened this issue May 13, 2020 · 6 comments
Closed

nested FMU: Access violation #168

fajansen opened this issue May 13, 2020 · 6 comments
Labels
bug Something isn't working

Comments

@fajansen
Copy link

I have a model that imports an FMU and want to export it as FMU. The export (with FMIKit2.8 alpha2) works fine, but when I try to simulate the FMU it crashes with an access violation.

Example will be sent by mail.

@fajansen
Copy link
Author

Any news on this?

@t-sommer t-sommer added the bug Something isn't working label Jul 2, 2020
@t-sommer
Copy link
Contributor

t-sommer commented Jul 2, 2020

The problem seems to be that the path for the binary of the nested FMU is still pointing to an absolute path. This error is reported via ssSetErrorStatus() but it's not forwarded to the parent FMU.

@t-sommer
Copy link
Contributor

t-sommer commented Jul 2, 2020

As a workaround you can keep the unzip directory of the nested FMU (or create it on the target machine), so the S-function can use the hard-coded path.

t-sommer added a commit that referenced this issue Jul 2, 2020
@t-sommer
Copy link
Contributor

t-sommer commented Jul 2, 2020

@fajansen, can you give 9f1ba6c a spin?

@StefanMa-hub
Copy link

tested the build with new sfun_fmurun.cpp file, fmu is not crashing any more

@sibitvm
Copy link

sibitvm commented Mar 29, 2022

Hello, I am facing a similar access violation issue when tried to import and simulate the nested FMU in Simulink. Please find the attachment of my sample trial.
Ex_Nested_fmu.zip

@t-sommer t-sommer reopened this Mar 29, 2022
t-sommer added a commit that referenced this issue Mar 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants