Simulink r2014a gets stuck at 25% CPU, but same model in r2010b runs perfectly fine

2 次查看（过去 30 天）
Vivek
Vivek 2015-2-23
评论： Vivek 2015-7-1
Hi Everyone,
With R2014a, my simulink model which contains libraries and simscape components gets stuck when I hit play and says "running" bu the clock doesn't run. I look at taskmanager and MATLAB process shows around 25% CPU usage. After a few minutes, it starts to simulate and completes successfully. But how can I find out why Matlab gets stuck? Because the same model in r2010b runs perfectly fine. Is it just more error checking in r2014a that's making this happen?

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

回答（1 个）

Biao
Biao 2015-5-5
I get the same Problem with 2014a and simscape. the Simulink model says running, but the progress clock does not run. it may take more than 10 minutes then I get this error: "Initial conditions solve failed to converge. ...Nonlinear solver to advance time one step failed to converge, residual norm too large."
it may be caused by some initializing values.
but matlab/simulink doesn't provide useful information about which block caused the problem.
  1 个评论
Vivek
Vivek 2015-7-1
Hi Biao, One thing to look at is to initialize simscape variables on components explicitly. You can do this on the "variables" tab on a component dialog box when y ou double click it. You can specify the priority and value of the initialization. This helped a lot in minimizing the running delay that you experienced

请先登录，再进行评论。

类别

在 Help Center 和 File Exchange 中查找有关 Troubleshooting 的更多信息

标签

产品

Community Treasure Hunt

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

Start Hunting!

Translated by