After code-generating my Simulink model to a deployed executable and running it on in a Linux environment, I receive the following messages printed out over stdout:
"Overrun detected: The sample time for the rate 0 is too short."
My model is a multi-rate model and each rate group is as follows:
- Discrete 1: 0.0005 (2 kHz)
- Discrete 2: 0.004 (250 Hz)
- Discrete 3: 0.032 (~31 Hz)
- Discrete 4: 0.128
- Discrete 5: 0.512
- Discrete 6: 3.072
My question is two-fold:
- Does "rate 0" (from the error message) refer to the base rate of the model?
- Why can't this output be more specific and tell me what part of the model is executing when the overrun occurs?
My question is not about how to fix task overruns (just the above), so please refrain from linking me to posts/articles that tell me to increase my sample time, etc.
Thanks, Tyler
Best Answer