Following Cadence Design Systems’ acquisition of the Design & Engineering (D&E) business, the D&E Community Forum on the Nexus Community Center has been migrated in the Cadence Physical System Simulation Community. For more details and if you have any questions, please refer to the FAQ.

Stats

  • State Not Answered
  • Replies 4
  • Subscribers 1
  • Views 3
  • Members are here 0
More Content

How to use local site solver with cosimulation?

MKvist
simple_simulink_adams_sub
I'm trying to run a cosimulation with an A/Car model with Simulink as the master. My A/Car model use some subroutines that is included in our site solver, but the cosimulation use the standard solver. I have tried to use the "User Defined Library Name" when I export my plant, but I still get the same error.
 
From the msg-file:
---- START: ERROR ----
Error in dispatcher subroutine sfoSUB: Invalid PAR(1): 0800           
---- END: ERROR ----
 
Does anyone have any clue of how I solve this issue?
 
In the bat-file ctrlsctrl....bat, that is created when I push the run-button in Simulink, there is a row "set MDI_SOLVER_USER_LIB=C:\MSC~1.SOF\ADAMS_~1\2019.2\win64\acar_solver.dll". This points to the standard solver and I guess that it could be a clue of why it doesn't work as I want. Where do I set the value of this environment variable?
 
OS: Windows
ADAMS-ver: 2019.2
MatLab-ver: R2019b
 
 
Thanks in advance!
Markus Kvist
 
EDIT: (2022-04-14)
The co-simulation works if I update the standard acar.cfg and replace the standard solver with my site solver, but this is only a solution for my test run at the moment. So my problem is still a exists.
 
I have also tried to run the same model with compatible versions of MatLab and ADAMS, but the problem still remains.
ADAMS-ver: 2018.1
MatLab-ver: R2017b
 
How do I setup the co-simulation to run with my site settings?
Parents
  • 0
    Hi,
     
    The different release compatibility could be a reason. I have tried the similar thing with the MDI_Demo_Vehicle.asy and a simliar simulink model that is showed in the main question. This works fine!
     
    So the issue is still that the cosimulation scripts doesn't use my defined solver dll. The variable ADAMS_exec in MatLab is defined with my defined solver dll, so that looks correct so far.
     
    Is it enough to point out my local dll as "User Defined Library Name" when I create the control system in ADAMS?
Reply
  • 0
    Hi,
     
    The different release compatibility could be a reason. I have tried the similar thing with the MDI_Demo_Vehicle.asy and a simliar simulink model that is showed in the main question. This works fine!
     
    So the issue is still that the cosimulation scripts doesn't use my defined solver dll. The variable ADAMS_exec in MatLab is defined with my defined solver dll, so that looks correct so far.
     
    Is it enough to point out my local dll as "User Defined Library Name" when I create the control system in ADAMS?
Children
No Data
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.