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?
Thank you for your response. Yes, the intention is to get an idea as to how I could go about modifying variables while running synchronously with another simulator.
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.
I would download the last release of Adams A2022_2 and review the existing AdamsRT model there. You can export an FMU directly. this works well in Concurrent/dSPACE machines with the last release fo VI-Grade software. then have a look at how the vehicle model talks to the simulator componets and compare to yours.
Thank you for the advice. Actually, exporting as an FMU directly has not been any issue, (I am using 2022_1). With FMU, the called variables in the .adm file are stored in array which is defined as the outputs of a GSE. The GSE is contained within the .dll, Concurrent/dSPACE I assume had access to the source code contained in the Adams solver library to build a platform that calls all of the executables in this library that, for example, run Adams solver command file when simulation is started in the other simulation program. Unfortunately, I am beginning to believe that without developer level access, this problem would be an incredibly complicated, if not impossible one to solve.