CPU overloads are generally a result of unexpected events or trying to do too much with too little. The default configuration of the xPC Target real-time kernel will stop model execution when a CPU overload is detected. This guarantees hard real-time performance. Nevertheless, it is possible to continue model execution in the presence of CPU overloads. Also, blocks are available that can sense and control the CPU overload counter. This allows for implementing exception handling when CPU overloads occur. These capabilities are described and test models are included to demonstrate.
In attempting to determine CPU Overload on a Speedgoat i7 performance target machine my search lead me here. I am observing a strange occurance and hope you might shed some insight. Is it normal to have the target machine disconnect from the host Ethernet (xpcexplr connection goes from green to red) after running either Test1 or Test2 models? I'm having to resort to xpcexplr primary due to hardware vendor suggesting disabling of the graphics subsystem on the target (in addition to USB support). We are on the 2013b version of Simulink/RT.