Debug Integer Overflow Design Error Detection using Model Slicer
This example shows how to use Model Slicer to debug integer overflow design errors in a Simulink model.
This example uses the following products to demonstrate debugging the Design Error Detection violations:
Simulink Design Verifier
Simulink Check (Model Slicer)
1. Open model
2. Open Simulink Design Verifier by clicking on Apps > Design Verifier.
3. In the Design Verifier tab, click Detect Design Errors. Simulink Design Verifier analyses the model and displays the results in Results Summary window.
The model highlights the subsystem where the failed objectives are located.
Controller subsystem and select either of the blocks that are highlighted in red.
5. In the Results window, click Debug to debug the violation using Model Slicer. Alternatively, in the Design Verifier tab, click Review Results > Debug using Slicer to debug the violation using Model Slicer.
On Clicking either of the entry points for debugging, the following setup is done on the model:
The selected block with a failed objective is added as a starting point for Model Slicer.
The model is highlighted with the slice responsible for the failing objective.
The design model is simulated and paused at the time of violation.
6. Debug and analyze the model by inspecting the port labels.
Tip: Click on the output signal line of the Sum block to enable the port value label for the block.
You can observe that the sum of the input variables should result in a non-zero number.
7. Investigate the input and output data types of the sum block.
The output of the Sum block has a value larger than the maximum value that the output data type can store. This condition therefore results in an integer overflow.
To confirm that the integer overflow error was resolved, on the Design Verifier tab, click Detect Design Errors. After the analysis completes, the software reports that all the objectives are valid.
You can use the workflow demostrated in this example to debug the other Design Error Detection violations using Model Slicer. Following are the design errors supported:
Division by zero
Non-Finate and NaN (Not a Number) floating-point values
Specified minimum and maximum value violations
Datastore access violations
Specified block input range violations