Tips and Limitations

Triggered Model Block

Consider the case where a triggered Model block is configured to run in the SIL or PIL simulation mode. The software generates one execution time measurement each time the referenced model is triggered to run. If there are multiple triggers in a single time step, there are multiple measurements for the triggered Model block. Conversely, if there is no trigger in a given time step, the software generates no time measurements.

Back to Top

Outliers in Execution Profiles

The operating system may preempt a SIL application after the start of a measurement, making the execution profiling result for the time step unreliable. As a consequence of preemption, you may see outliers in your code execution profiles, with execution times that are longer than expected.

Additionally, for execution time measurements greater than 2³² ticks, the counter wraps. Counter wrapping occurs when the actual execution time is very long, which results in a measured execution time that is shorter than expected.

Back to Top

Execution Times with Separate Output and Update Functions

Before building your model, if you clear the check box Configuration Parameters > Code Generation > Interface > Single output/update function , the generated code has separate output and update functions.

Back to Top

Analyze Code Execution Data

Embedded IDEs and Embedded Targets

Related Products & Applications

• Simulink
• Control Design
• Signal Processing & Communications
• Model-Based Design
• Physical Modeling
• Verification & Validation

Get Simulink trial software

Learn more about Simulink through this collection of videos, articles, technical literature and the Getting Started with Simulink Guide.

Get this Simulink Kit