Error while running motionview exported model in Adams
Description: [Porting Motionsolve subroutines to Adams]
Product/Topic Name : Motionview
Hi,
I have a vehicle model built in motionview that I would like to solve with Adams solver. I had exported out the acf, adm files and was able to submit the job to adams.
However, there are some outputs which require subroutines which are specific for Motionsolve. I get the following error
"Encountered error "The user library "msautoutils" could not be located"
I copied the msautoutils.dll to the same directory as the simulation input files after which this error disappeared. But i got a new error
"ERROR: Unable to establish AccessFunction connection, please set NUSOL_DLL_DIR"
I added a new environment variable named NUSOL_DLL_DIR along with the equivalent path
After this the simulation starts but exits without any further message.
Also, in the adm file, i see that msautoutils subroutine is being called instead of equivalent relevant adams subroutine. I would like to understand why motionsolve subroutine is being called while exporting the model to Adams.
I would like to know how to port the Altair subroutines to Adams correctly. Could you guide me with the process?
Regards
Karthikeyan
Find more posts tagged with
Hi @Karthikeyan,
Excellent! I'm glad you were able to reach a resolution for your issue.
Thanks,
Adam Reid
Hi @Karthikeyan,
As stated earlier, the issue may lie with the fact that you are trying to use the ADAMS solver for MotionSolve only entities, like the tires and driver model. As a test, I would suggest that you create a simple model that does not use the msautoutils subroutine, such as a spring-mass-damper model, and try your MotionView-ADAMS coupled simulation to see if it completes. Assuming it does, you will possibly not be able to couple this type of analysis with these automotive entities.
Thanks,
Adam Reid
Hi @Karthikeyan,
As stated earlier, the issue may lie with the fact that you are trying to use the ADAMS solver for MotionSolve only entities, like the tires and driver model. As a test, I would suggest that you create a simple model that does not use the msautoutils subroutine, such as a spring-mass-damper model, and try your MotionView-ADAMS coupled simulation to see if it completes. Assuming it does, you will possibly not be able to couple this type of analysis with these automotive entities.
Thanks,
Adam Reid
Hi @Karthikeyan,
Are you trying to use the Adams solver option within an older version of MotionView (below) or are you exporting the model and trying to run it within an Adams/View session?
The msautoutils, or MotionSolve Automotive Utilities subroutine, will be used for entities like tires and the driver model. If you are trying to use this model within Adams/View, then you will likely need to replace those entities with Adams-specific automotive entities, or just simply solve the model using MotionSolve.
Hope this helps!
Adam Reid