Resolving Data Properties from Simulink Signal Objects

About Explicit Signal Resolution

Stateflow local and output data in Stateflow charts can explicitly inherit properties from Simulink.Signal objects in the model workspace or base workspace. This process is called signal resolution and requires that the resolved signal have the same name as the chart output or local data.

For information about Simulink signal resolution, see Resolving Symbols and Hierarchical Symbol Resolution in the Simulink documentation.

Back to Top

Inherited Properties

When Stateflow local or output data resolve to Simulink signal objects, they inherit these properties:

• Size

• Complexity

• Type

• Minimum value

• Maximum value

• Initial value

• Storage class

  Storage class controls the appearance of Stateflow chart data in the generated code. See Custom Storage Classes in the Embedded Coder User's Guide.

Back to Top

Enabling Explicit Signal Resolution

To enable explicit signal resolution, follow these steps:

1. In the model workspace or base workspace, define a Simulink.Signal object with the properties you want your Stateflow data to inherit.

   For more information about creating Simulink signals, see Simulink.Signal in the Simulink Reference documentation.

2. Add output or local data to a Stateflow chart.

   The Data properties dialog box opens.

3. Enter a name for your data that matches the name of the Simulink.Signal object.

4. In the Data properties dialog box, select the Data must resolve to Simulink signal object check box.

   After you select this check box, the dialog box removes or grays out the properties that your data inherits from the signal. For a list of properties that your data can inherit during signal resolution, see Inherited Properties.

Back to Top

A Simple Example

The following model shows how a Stateflow chart resolves local and output data to Simulink.Signal objects.

In the base workspace, there are three Simulink.Signal objects with these properties:

The chart contains three data objects — two outputs and a local variable — that will resolve to a signal with the same name, as follows:

When you build the model, each data object inherits the properties of the identically named signal:

The generated code declares the data based on the storage class that the data inherits from the associated Simulink signal. For example, the header file below declares local to be an exported global variable:

/*
 * Exported States
 *
 * Note: Exported states are block states with an exported
 * global storage class designation.
 *
 */
extern real32_T local;                  /* '<Root>/Chart' */

Back to Top

Using Dot Notation to Identify Data in a Chart

Best Practices for Using Data in Stateflow Charts

Free Stateflow Interactive Kit

Learn how engineers use Stateflow to model state machines in their Simulink models.

Get free kit

Trials Available

Try the latest version of Stateflow.

Get trial software