Inifite simulation stop time / Scope problems

2019 5 22
1 个回答
更新时间：2019 5 23
3 次查看（30 天）

0 个投票

Dear Sir / Madam,
I am using a Stateflow in Matlab simulink to determine whether a controller subsystem is enabled or disabled. Therefore, I have the simulation model stop time set to 'infinite' which also requires a variable step time.
The problem here that when I plot a value from the subsystem (cylinder displacement) into a simulink scope, the x-axis shows inrealistic time values of around 300 * 10^5 seconds.
What I actually would want to accomplish is an inifite stop time, but with realistic (RealTime) time values.
Is this possible?
Thanks in advance

请先登录，再回答此问题。

回答（1 个）

Toshinobu Shintai
Toshinobu Shintai 2019-5-23

0 个投票

Dear Mathieu Risseeuw.
I still don't understand fully what is the problem for you, but
is the "simulation pacing" solve your problem?
https://www.mathworks.com/help/simulink/ug/simulation-pacing.html?lang=en
If the scope of the model actually shows inrealistic value, please report as a bug.
(For example, real time step is 4.01s, but scope time step is 50700s.)
Thank you.

5 个评论
显示 3更早的评论 隐藏 3更早的评论

Mathieu Risseeuw
Mathieu Risseeuw 2019-5-23
编辑：Mathieu Risseeuw 2019-5-23
Dear Toshinobu Shintai,
Thanks for the reply. The pacing does not solve the problem (because I have the 2017b release which doesnt include the pacing option (yet)). I think it has to do with this fact:
When I run the simulation (inf.) only the stateflow runs idle. Only when I press a certain button, a subsystem (trigger block) is triggered and a control loop starts. When the required value is obtained, the subsystem is untriggered and the controllloop stops.
Then when I stop the simulation, and I open the triggerblock and plot the scope of the controller, the profile looks good, but the time is like 10*10^5 seconds. However, when I run this same controller in a different Simulink model (without trigger block and stateflow) the time is like 0.1 seconds.
It might have something to do with the infinite stoptime and triggered subsystem.
Thanks in advance.
Mathieu Risseeuw
Mathieu Risseeuw
Mathieu Risseeuw 2019-5-23
Additional:
I fixed it, with the pace block in the aerospace blockset. Thank you so much.
Mathieu Risseeuw
Toshinobu Shintai
Toshinobu Shintai 2019-5-23
Now I see your problem.
Because the Simulink time step is absolute,
you cannot change local block time from the base of Simulink.
If you use "To Workspace" block, you can log data exactly when the enabled(triggered) subsystem worked.
But it doesn't contain the local time step.
Please refer to the attached file.
Thank you.
Toshinobu Shintai
Toshinobu Shintai 2019-5-23
Sorry for delaying my answer.
I'm glad that you solve the problem.
Mathieu Risseeuw
Mathieu Risseeuw 2019-5-23
Thank you so much for your time. Have a nice day

请先登录，再进行评论。

类别

在 帮助中心 和 File Exchange 中查找有关 Simulink Functions 的更多信息

产品

标签

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by