| Products & Services | Solutions | Academia | Support | User Community | Company |
| Download Product Updates | | | Get Pricing | | | Trial Software |
| Documentation → Stateflow |
| Contents | Index |
| Learn more about Stateflow |
This table summarizes what's new in V 6.2 (R14SP2):
| New Features and Changes | Version Compatibility Considerations | Fixed Bugs and Known Problems | Related Documentation at Web Site |
|---|---|---|---|
| Yes Details below | No | Bug
Reports at Web site | No |
New features introduced in this version are described here:
Stateflow charts now support a mode where you can explicitly specify the testing/execution order of transitions sourced by states and junctions. This is called the Explicit mode. The Implicit mode retains the old functionality, where the transition execution order is determined based on a set of rules (parent depth, triggered/conditional properties, and geometry around the source). In addition, the transition numbers, according to their execution order, are now displayed on the Stateflow Editor at all times, both in Implicit and Explicit modes.
Note that the old models created in earlier releases load in Implicit mode, thus yielding identical simulation results. Any new charts created are in Implicit mode by default. To change to Explicit mode, use the Chart Properties dialog box.
Charts in library models do not require full specification of data type and size. During simulation, library charts can inherit data properties from the main model in which you link them.
This enhancement also affects code generation in library charts. When building simulation and code generation targets, only the library charts that you link in the main model participate in code generation.
In previous releases, library charts required complete specification of data properties. You had to enter these properties for both the library chart and the main model before simulation.
Data in Stateflow charts and Embedded MATLAB functions may now be explicitly typed using the same aliased types that a Simulink model uses. Also, inherited and parameterized data types in Stateflow charts and Embedded MATLAB functions support propagation of aliased types. However, code generated for Stateflow charts and Embedded MATLAB functions does not yet preserve aliased data types.
You can now specify fixed-point override for Stateflow library charts.
![]() | Version 6.3 (R14SP3) Stateflow and Stateflow Coder Software | Version 6.1 (R14SP1) Stateflow and Stateflow Coder Software | ![]() |

Learn more about Simulink through this collection of videos, articles, technical literature and the Getting Started with Simulink Guide.
| © 1984-2009- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |