NES1994
Aerospace
- Jun 5, 2024
- 5
Dear all,
I've encountered an issue when running my co-simulation between ADAMS and MATLAB Simulink.
The simulation runs without any issues for 100s. After 100s ADAMS stops updating my state variables.
Consequently, my closed loop controller saturates at the control variable limit. The simulation in Matlab runs until the nominally defined simulation duration of ~240s.
Please find below a plot of the position, velocity and acceleration of my mechanism illustrating the nominal behaviour until t = 100 and the behaviour after t = 100s.
Does anybody have a clue what the reason for this behaviour is and why ADAMS stops communicating at 100s?
Thanks for your support,
Sebastian
I've encountered an issue when running my co-simulation between ADAMS and MATLAB Simulink.
The simulation runs without any issues for 100s. After 100s ADAMS stops updating my state variables.
Consequently, my closed loop controller saturates at the control variable limit. The simulation in Matlab runs until the nominally defined simulation duration of ~240s.
Please find below a plot of the position, velocity and acceleration of my mechanism illustrating the nominal behaviour until t = 100 and the behaviour after t = 100s.
Does anybody have a clue what the reason for this behaviour is and why ADAMS stops communicating at 100s?
Thanks for your support,
Sebastian