Stateflow

Checking the Chart for Errors

The parser evaluates the graphical and nongraphical objects in each Stateflow machine against the supported Stateflow notation and the action language syntax. Errors are displayed in informational pop-up windows. See Parsing Stateflow Diagrams for more information.

Some aspects of the notation are verified at run-time. Others are verified during application run-time. Using the Debugger, you can detect the following run-time errors during simulation:

• State Inconsistency -- Most commonly caused by the omission of a default transition to a substate in superstates with XOR decomposition. See Debugging State Inconsistencies.
• Transition Conflict -- Occurs when there are two equally valid transition paths from the same source. See Debugging Data Range Violations.
• Data Range Violation -- Occurs when minimum and maximum values specified for a data in its properties dialog are exceeded or when fixed-point data overflows its base word size. See Debugging Data Range Violations.
• Cyclical Behavior -- Occurs when a step or sequence of steps repeats itself indefinitely. See Debugging Cyclic Behavior.

You can modify the notation to resolve run-time errors. See Debugging and Testing, for more information on debugging run-time errors.

Specifying Chart Properties

Creating Chart Libraries