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

Infinite Analysis Runtime

nmruble
Hello,
I was wondering if there was a way to force an infinite analysis duration within Adams Car. My intent is to perform a simple analysis, such as straight-line maintain on flat, 2d road, but tell the solver to run until told to stop, so that I can manipulate control variables such as the steering input directly within the .adm file, save the file, and observe the impact the change has on the simulation.
Thank you for any advice you might have!
 
Edit: After looking into this further I have come to the understanding that all input variables reference a GSE which calls to the solver .dll, which is compiled in binary and unreadable, meaning even if I were able to force infinite runtime, there is no way for me to change the input parameters (steer, throttle, brake, etc.) during runtime. Can anyone confirm this?
 
Parents
  • 0
    @Alexis Del Rio​ ,
    The goal is to build a platform to iteratively replace select variables with ones taken out of Unreal Engine as the only way to get the variables into Unreal right now is through and FMI plugin, however, mapping the variables and getting UE to cosimulate with Adams nicely has been quite a problem as most of the variables I need to map to UE from Adams are stored in the .dll which is obviously unreadable. Without taking the time to read all of the C code of the plugin and understanding how (if it is even possible at all) I could utilize it to do things such read the commands within the .dll that prompt Adams to boot and for the .adm file to be evaluated, I have no way to actually prompt co-simulation from UE.
    Actually, the ideal solution would be for me to export the entire Adams model as C code, and build it directly in Unreal. I know this can be done with a model in Matlab, although I'm nearly certain this is not possible in Adams, with no blame to MSC, as the all of the solver C code is compiled in the solver library and unviewable/editable.
Reply
  • 0
    @Alexis Del Rio​ ,
    The goal is to build a platform to iteratively replace select variables with ones taken out of Unreal Engine as the only way to get the variables into Unreal right now is through and FMI plugin, however, mapping the variables and getting UE to cosimulate with Adams nicely has been quite a problem as most of the variables I need to map to UE from Adams are stored in the .dll which is obviously unreadable. Without taking the time to read all of the C code of the plugin and understanding how (if it is even possible at all) I could utilize it to do things such read the commands within the .dll that prompt Adams to boot and for the .adm file to be evaluated, I have no way to actually prompt co-simulation from UE.
    Actually, the ideal solution would be for me to export the entire Adams model as C code, and build it directly in Unreal. I know this can be done with a model in Matlab, although I'm nearly certain this is not possible in Adams, with no blame to MSC, as the all of the solver C code is compiled in the solver library and unviewable/editable.
Children
No Data
© 2025 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement