While using a demo model, I accidentally changed a data type from uint16 to uint8. The initial value was 499; this resulted in an erroneous simulation behavior. There is a missing compile/runtime range error when Stateflow data is initialized with values outside its range. The runtime data range checking is on, indicating a bug in the debug instrumentation of the simulation target. Therefore, the Stateflow Coder is also incorrect.
MATLAB: Does Stateflow 5.0 (R13) not throw an error when I simulate with out-of-range initial data
errormissingofoutoverflowr12.1pv1_swatrangestateflowuintunderrun
Related Question
- Do I receive an internal error when running the chart in Stateflow 5.1.1 (R13SP1)
- Do I receive an error when accessing the documentation from the Stateflow graphics editor in Stateflow 5.0 (R13)
- Does MATLAB crash when I try saving a model containing a Stateflow 5.1 (R13sp1) chart
- Does the generated code for the Data Type Conversion block perform temporary up-conversion to type double when I am using other data types in Real-Time Workshop Embedded Coder 5.0 (R2007b)
- Does Stateflow Coder always generate code that has complete code coverage
- Is the sample time parameter saved as a constant when I use SLSAVEAS to save a model from Simulink 6.2 (R14SP2) to Simulink 5.0 (R13)
- Does the model containing a Stateflow chart error out in Simulink 6.0 (R14) but builds the code fine for the chart in Simulink 5.0 (R13) and earlier
- When merging signals from different subsystems, why is incorrect code generated in the Real-Time Workshop
Best Answer