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

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?

Answer 1

[Biao]

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.

[Vivek]

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