Version 7.0 (R2007b) Stateflow® and Stateflow® Coder™ Software Release Notes

Version 7.0 (R2007b) Stateflow^® and Stateflow^® Coder™ Software

This table summarizes what's new in V7.0 (R2007b):

New features and changes introduced in this version are:

• Enhanced Continuous-Time Support with Zero-Crossing Detection

• New Super Step Feature for Modeling Asynchronous Semantics

• Support for Inheriting Data Properties from Simulink^® Signal Objects Via Explicit Resolution

• Common Dialog Box Interface for Specifying Data Types in Stateflow^® Charts and Simulink^® Models

• Support for Animating Stateflow^® Charts in Simulink^® External Mode

• Support for Target Function Library

• Support for Fixed-Point Parameters in Truth Table Blocks

• Loading 2007b Stateflow^® Charts in Earlier Versions of Simulink^® Software

• Bug Fixed for the History Junction

Enhanced Continuous-Time Support with Zero-Crossing Detection

Using enhanced support for modeling continuous-time systems, you can do the following:

• Detect zero crossings on state transitions, enabling accurate simulation of dynamic systems with modal behavior.

• Support the definition of continuous state variables and their derivatives for modeling hybrid systems as state charts with embedded dynamic equations

For more information, see Modeling Continuous-Time Systems in Stateflow^® Charts in the Stateflow^® and Stateflow^® Coder™ User's Guide documentation.

Compatibility Considerations

Previously, Stateflow charts implemented continuous time simulation without maintaining mode in minor time steps or detecting zero crossings. Accurate continuous-time simulation requires several constraints on the allowable constructs in Stateflow charts. Charts created in earlier versions may generate errors if they violate these constraints.

New Super Step Feature for Modeling Asynchronous Semantics

Using a new super step property, you can enable Stateflow charts to take multiple transitions in each simulation time step. For more information, see Executing a Chart with Super Step Semantics in the Stateflow and Stateflow Coder User's Guide.

Support for Inheriting Data Properties from Simulink^® Signal Objects Via Explicit Resolution

You can use a new data property, Data Must Resolve to Simulink signal object, to allow local and output data to explicitly inherit the following properties from Simulink.Signal objects of the same name that you define in the base workspace or model workspace:

• Size

• Type

• Complexity

• Minimum value

• Maximum value

• Initial value

• Storage class (in Real-Time Workshop^® generated code)

For more information, see Resolving Data Properties from Simulink^® Signal Objects in the Stateflow and Stateflow Coder User's Guide.

Compatibility Considerations

Stateflow software no longer performs implicit signal resolution, a feature supported for output data only. In prior releases, Stateflow software attempted to resolve outputs implicitly to inherit the size, type, complexity, and storage class of Simulink.Signal objects of the same name that existed in the base or model workspace. No other properties could be inherited from Simulink^® signals.

Now, local as well as output data can inherit additional properties from Simulink.Signal objects, but you must enable signal resolution explicitly. In models developed before Version 7.0 (R2007b) that rely on implicit signal resolution, Stateflow charts may not simulate or may generate code with unexpected storage classes. In these cases, Stateflow software automatically disables implicit signal resolution for chart outputs and generates a warning at model load time about possible incompatibilities. Before loading such a model, make sure you have loaded into the base or model workspace all Simulink.Signal objects that will be used for explicit resolution. After loading, resave your model in Version 7.0 (R2007b) of Stateflow software.

Common Dialog Box Interface for Specifying Data Types in Stateflow^® Charts and Simulink^® Models

You can use the same dialog box interface for specifying data types in Stateflow charts and Simulink models. For more information, see Setting Data Properties in the Data Dialog in the Stateflow and Stateflow Coder User's Guide.

Support for Animating Stateflow^® Charts in Simulink^® External Mode

When running Simulink models in external mode, you can now animate states, and view Stateflow test points in floating scopes and signal viewers. For more information, see Animating Stateflow^® Charts in the Stateflow and Stateflow Coder User's Guide.

These Real-Time Workshop targets support Stateflow chart animation in external mode:

Note   * xPC supported parameter download only from release R12 through R14sp3. As of release R2006a, xPC supports signal upload as well. ** xPC has documented support for xpcexplr to display the boolean value of test point Stateflow states. You can also retrieve the state value via the xPC command-line API. There is no documented support for animating a Stateflow chart that is running in Simulink external mode. *** dSPACE RTI supports parameter download only.

Support for Target Function Library

Stateflow Coder code generation software supports the Target Function Library published by Real-Time Workshop^® Embedded Coder™ software, allowing you to map a subset of built-in math functions and arithmetic operators to target-specific implementations. For more information, see Replacing Operators with Target Functions and Replacing C Math Library Functions with Target-Specific Implementations in the Stateflow and Stateflow Coder User's Guide.

Support for Fixed-Point Parameters in Truth Table Blocks

You can now define fixed-point parameters in Truth Table blocks.

Loading 2007b Stateflow^® Charts in Earlier Versions of Simulink^® Software

If you save a Stateflow chart in release 2007b, you will not be able to load the corresponding model in earlier versions of Simulink software. To work around this issue, save your model in the earlier version before loading it, as follows:

1. In the Simulink model window, select File > Save As.

2. In the Save as type field, select the version in which you want to load the model.

   For example, if you want to load the model in the R2007a version of Simulink software, select Simulink 6.6/R2007a Models (#.mdl).

Bug Fixed for the History Junction

In previous releases, there was a bug where a default transition action occurred more than once if you used a history junction in a state containing only a single substate. The history junction did not remember the state's last active configuration unless there was more than one substate. This bug has been fixed.

Version 7.1 (R2008a) Stateflow® and Stateflow® Coder™ Software

Version 6.6.1 (R2007a+) Stateflow® and Stateflow® Coder™ Software