Simulink overload conditions

Hi,

I have been reading through the simulink documentation on how the simulink engine executes a model. However, I am still unclear regarding what happens in the case of overload (i.e., CPU is too busy for completing execution by the next simulation round). Could someone explain simulink's behavior in this case or point me to the appropriate documentation?

Thank you! -- Octav

Answer 1

[Kaustubha Govind]

Simulink/MATLAB would simply wait for a CPU cycle, just like any other software on a non-real-time OS. In other words, the model execution is single-threaded, so the next time-step is not reached until the current step is complete.

[Octav Chipara]

I assume that there would be no problem in having a blocking system call (e.g., receiving a udp packet) as part the execution. I am surprised that a block such as the UDP receive would not block until a message is received rather than return if no message is available. Is there a way to modify accomplish such a behavior with the existing components?