hexagon logo
Register Sign in
  • State Not Answered
  • Replies 3 replies
  • Subscribers 11 subscribers
  • Views 100 views
  • Users 0 members are here
Options
Related

Repeated ADAMS<=>Imported Simulink Control simulations crashes ADAMS

PMotaghe
I have an ADAMS <=>Simulink Controls Import (as an ESL DLL) working, but it only runs the FIRST time. Running a 2nd time causes ADAMS to crash.  Beside the Simulink Contorl Import ESL GSE, my ADAMS model also has a user-defined GFORCE subroutine (DLL) that works fine (even repeatedly, when the Simulink Controls Import ESL GSE is not present)
Parents
  • 0
    Hi Alexis - I've attached a copy of .msg files from the first run, then the 2nd run (which bombs). I'm increasingly suspecting there's a different level of "resetting" going on with models involving DLL-integrated Simulink models, and that's somehow messing with the initialization of the Python interpreter I have programmed into my user-written GFORCE C routine (Python function is called to compute and provide force feedback). I have observed IFLAG being set to 5 when this Simulink-integrated simulation is stopped, unlike the model WITHOUT the integrated Simulink version.
Reply
  • 0
    Hi Alexis - I've attached a copy of .msg files from the first run, then the 2nd run (which bombs). I'm increasingly suspecting there's a different level of "resetting" going on with models involving DLL-integrated Simulink models, and that's somehow messing with the initialization of the Python interpreter I have programmed into my user-written GFORCE C routine (Python function is called to compute and provide force feedback). I have observed IFLAG being set to 5 when this Simulink-integrated simulation is stopped, unlike the model WITHOUT the integrated Simulink version.
Children
No Data
© 2025 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement