| Version 6.3 (R14SP3) Stateflow® and Stateflow® Coder™ Software Release Notes | |
This table summarizes what's new in V6.3 (R14SP3):
| 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 and changes introduced in this version are organized by these topics:
This release provides an interface that gives Stateflow® charts access to global variables in Simulink® models. A Simulink model implements global variables as data stores, created either as data store memory blocks or instances of Simulink.Signal objects. Now Stateflow charts can share global data with Simulink models by reading and writing data store memory symbolically using the Stateflow action language. See Sharing Global Data with Simulink® Models in the Stateflow and Stateflow® Coder™ User's Guide documentation.
The Stateflow data dialog has been enhanced to
Accommodate fixed point support
Support parameter expressions in data properties
Stateflow charts now accept Simulink parameters or parameters defined in the MATLAB® workspace for the following properties in the data dialog:
Initial Value
Minimum
Maximum
Entries for these parameters can be expressions that meet the following requirements:
Expressions must evaluate to scalar values.
For library charts, the expressions for these properties must evaluate to the same value for all instances of the library chart. Otherwise, a compile-time error appears.
See Defining Data in the Stateflow and Stateflow Coder User's Guide.
You can now use the Embedded MATLAB™ action language in Stateflow truth tables. Previously, you were restricted to the Stateflow action language. The Embedded MATLAB action language offers the following advantages:
Supports the use of control loops and conditional constructs in truth table actions
Provides direct access to all MATLAB functions
See Truth Table Functions in the Stateflow and Stateflow Coder User's Guide.
A truth table function block is now available as an element in the Simulink library. With this new block, you can call a truth table function directly from your Simulink model. Previously, there was a level of indirection. Your Simulink model had to include a Stateflow block that called a truth table function.
The Simulink truth table block supports the Embedded MATLAB language subset only. You must have a Stateflow software license to use the Truth Table block in Simulink models.
See Truth Table Functions in the Stateflow and Stateflow Coder User's Guide.
A new Stateflow function sfgco retrieves the object handles of the most recently selected objects in a Stateflow chart.
Stateflow Coder code generation software now implements a default case in generated switch statements to account for corrupted memory at runtime. In this situation, the default case performs a recovery operation by calling the child entry functions of the state whose variable is out of bounds. Reentering the state resets the variable to a valid value.
This recovery operation is not performed if a Stateflow chart contains any of the following elements:
Local events
Machine-parented events
Implicit events, such as state entry, state exit, and data change
If any of these conditions exist in a chart, state machine processing can become recursive, causing variables to temporarily assume values that are out of range. However, when processing finishes, the variables return to valid values.
You can specify the execution order of parallel states explicitly in Stateflow charts. Previously, the execution order of parallel states was governed solely by implicit rules, based on geometry. A disadvantage of implicit ordering is that it creates a dependency between design layout and execution priority. When you rearrange parallel states in your chart, you may inadvertently change order of execution and affect simulation results. Explicit ordering gives you more control over your designs. See Execution Order for Parallel States in the Stateflow and Stateflow Coder User's Guide.
You can now directly hyperlink the Simulink subsystem connected to a Stateflow output event by using the context menu option Explore for any state or transition broadcasting event. See Accessing Simulink® Subsystems from Stateflow® Events in the Stateflow and Stateflow Coder User's Guide.
A common modeling error is to create charts where a transition loops out of the logical parent of the source and destination objects. The logical parent is either a common parent of the source and destination objects, or if there is no common parent, the nearest common ancestor.
Consider the following example:
In this Stateflow chart, transition 1 loops outside of logical parent A, which is the common parent of transition source B and destination C.
This type of illegal looping causes the parent to deactivate and then reactivate. In the previous example, if transition 1 is taken, the exit action of A executes and then the entry action of A executes. Executing these actions unintentionally can cause side effects.
This situation is now detected as a parser warning that indicates how to fix the model. Here is the warning associated with the earlier example:
You can now use color highlighting to differentiate syntax elements in the Stateflow action language. Syntax highlighting is enabled by default. To specify highlighting preferences, select Highlighting Preferences from the Stateflow chart Edit menu, and then click the colors you want to change. See Differentiating Syntax Elements in the Stateflow® Action Language in the Stateflow and Stateflow Coder User's Guide.
This release introduces enhancements to Stateflow chart notes. The chart notes property dialog now has a ClickFcn section, which includes the following options:
Use display text as click callback check box
ClickFcn edit field
See Annotations Properties Dialog Box in the Simulink software documentation for a description of these new options.
This release adds the following chart viewing enhancements:
View Command History. This release enhances the chart viewing commands. You can now maintain a history of the chart viewing commands, i.e., pan and zoom, that you execute for each chart window. The history allows you to quickly return to a previous view in a window, using commands for traversing the history (see New View Menu Viewing Commands).
New View Menu Viewing Commands. This release adds the following viewing commands to the chart's View menu:
View > Back
Displays the previous view in the view history.
View > Forward
Displays the next view in the view history.
View > Go To Parent
Goes to the parent of the current subchart.
New Shortcut Menu Commands. The shortcut menu now has Forward and Go To Parent commands. The Back command has been moved to be with these new commands. These commands are the same as those described in New View Menu Viewing Commands.
View Command Shortcut Keys. This release adds the following viewing command shortcut keys for users running the UNIX® operating system or the Windows® operating system:
| Shortcut Key | Command |
|---|---|
| d or Ctrl+Left Arrow | Pan left |
| g or Ctrl+Right Arrow | Pan right |
| e or Ctrl+Up Arrow | Pan up |
| c or Ctrl+Down Arrow | Pan down |
| b | Go back in pan/zoom history |
| t | Go forward in pan/zoom history |
Note These shortcut keys, together with the existing zoom shortcuts (r or + for zoom in, v or - for zoom out), allow you to pan and zoom a model with one hand (your left hand). |
| Version 6.4 (R2006a) Stateflow® and Stateflow® Coder™ Software | Version 6.2 (R14SP2) Stateflow® and Stateflow® Coder™ Software | |
| © 1984-2008- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |