| Products & Services | Industries | 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 V7.3 (R2009a):
| New Features and Changes | Version Compatibility Considerations | Fixed Bugs and Known Problems | Related Documentation at Web Site |
|---|---|---|---|
| Yes Details below | Yes—Details labeled as Compatibility Considerations, below. See also Summary. | Bug
Reports | No |
New features and changes introduced in this version are:
Support for Saving the Complete Simulation State at a Specific Time
Enhanced Control of Inlining State Functions in Generated Code
New Diagnostic to Detect Unintended Backtracking Behavior in Flow Graphs
Use of Basic Linear Algebra Subprograms (BLAS) Libraries for Speed
Enhanced Support for Replacing C Math Functions with Target-Specific Implementations
Clicking Up-Arrow Button in the Stateflow Editor Closes Top-Level Chart
Enhanced Real-Time Workshop Generated Code for Charts with Simulink Functions
Support for Machine-Parented Events Being Removed in a Future Version
You can save the complete simulation state at a specific time and then load that state for further simulation. This enhancement provides these benefits:
Enables running isolated segments of a simulation without starting from time t = 0, which saves time
Enables testing of the same chart configuration with different settings
Enables testing of hard-to-reach chart configurations by loading a specific simulation state
For more information, see Saving and Restoring Simulations Using SimState in the Stateflow and Stateflow Coder User's Guide.
In R2009a, you can use enumerated data in Embedded MATLAB functions, truth table functions that use Embedded MATLAB action language, and Truth Table blocks. See Using Enumerated Data in Stateflow Charts in the Stateflow and Stateflow Coder User's Guide.
You can now use true and false as Boolean keywords in Stateflow action language. For more information, see Symbols in Action Language in the Stateflow and Stateflow Coder User's Guide.
In R2009a, a new Function Inline Option parameter is available in the State properties dialog box. This parameter enables better control of inlining state functions in generated code, which provides these benefits:
Prevents small changes to a model from causing major changes to the structure of generated code
Enables easier manual inspection of generated code, because of a one-to-one mapping between the code and the model
For more information, see Controlling Inlining of State Functions in Generated Code in the Stateflow and Stateflow Coder User's Guide.
A new diagnostic detects unintended backtracking behavior in flow graphs during simulation. A warning message appears, with suggestions on how to fix the flow graph to prevent unintended backtracking. For more information, see Best Practices for Creating Flow Graphs in the Stateflow and Stateflow Coder User's Guide.
Embedded MATLAB functions in Stateflow charts can now use BLAS libraries to speed up low-level matrix operations during simulation. For more information, see Simulation Target Pane: General in the Simulink documentation.
You can now replace the pow function with a target-specific implementation. For more information about Target Function Libraries, see:
Example: Mapping Math Functions to Target-Specific Implementations
Replacement of C Math Library Functions with Target-Specific Implementations
In R2009a, the graphical behavior of smart transitions has been enhanced as follows:
Smart transitions maintain straight lines between states and junctions whenever possible. Previously, smart transitions would preserve curved lines.
When you drag a smart transition radially around a junction, the end on the junction follows the tip to maintain a straight line by default. Previously, the end on the junction would maintain its original location and not follow the tip of the transition.
For more information, see What Smart Transitions Do in the Stateflow and Stateflow Coder User's Guide.
When a top-level chart appears in the Stateflow Editor, clicking the up-arrow button in the toolbar causes the chart to close and the Simulink model that contains the chart to appear. This behavior is consistent with clicking the up-arrow button in the toolbar of a Simulink subsystem window.
Previously, clicking the up-arrow button for a top-level chart would cause the Simulink model to appear, but the chart would not close. For more information, see Navigating Subcharts in the Stateflow and Stateflow Coder User's Guide.
In R2009a, type resolution for Stateflow data has been enhanced to support any MATLAB expression that evaluates to a type.
In R2009a, the generated code for managing Stateflow events uses a deterministic numbering method. This enhancement minimizes unnecessary differences in the generated code for Stateflow charts between R2009a and any future release.
In R2009a, Real-Time Workshop® generated code for charts with Simulink functions no longer uses unneeded global variables for the function inputs and outputs. The interface can be represented by local temporary variables or completely eliminated by optimizations, such as expression folding. This enhancement provides reduced RAM consumption and faster execution time.
In a future version of Stateflow software, use of en, du, ex, entry, during, or exit for naming data or events will be disallowed. In R2009a, a warning message appears when you run a model that contains any of these keywords as the names of data or events.
To avoid warning messages, rename any data or event that uses en, du, ex, entry, during, or exit as an identifier.
In a future version of Stateflow software, support for machine-parented events will be removed. In R2009a, a warning message appears when you simulate models that contain events at the machine level.
To prevent undesired behavior for simulation and code generation, do not use machine-parented events. For simulation, broadcasting an event to all charts in your model causes the following to occur:
Charts wake up without regard to data dependencies.
Charts that are disabled might wake up.
Charts that use function-call or edge-triggered events wake up.
Charts unrelated to the event wake up.
Infinite recursive cycles can occur because the chart that broadcasts the event wakes up.
For code generation, machine-parented events prevent code reuse for the entire model.
![]() | Version 7.4 (R2009b) Stateflow and Stateflow Coder Software | Version 7.2 (R2008b) 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 |