Describe Component Behavior Using Stateflow Charts - MATLAB & Simulink - 金宝app,下载188bet金宝搏,金宝搏官方网站

Describe Component Behavior UsingStateflowCharts

Astate chartdiagram demonstrates the state-dependent behavior of a component throughout its state lifecycle and the events that can trigger a transition between states.

添加Stateflow^®chart behavior to describe a component using state machines. You cannot synchronize and reuse Stateflow chart behaviors asReference Componentblocks because the component is part of the parent model.

You can simulate the Stateflow component implementations in System Composer™. Use theSimulation Data Inspectorto view and compare simulation results between model designs.

状态图是由一组有限的智慧h transitions between them to capture the modes of operation for the component. Charts allow you to design for different modes, internal states, and event-based logic of a system. You can also use charts as stubs to mock a complex component implementation during top-down integration testing. This functionality requires a Stateflow license. For more information, seeStateflow.

Add State Chart Behavior to Component

A System Composer component with stereotypes, interfaces, requirement links, and ports, is preserved when you add StateflowChart(Stateflow)behavior.

This example uses the architecture model for an unmanned aerial vehicle (UAV) to add state chart behavior to a component. In the MATLAB^®Command Window, enter the following command:
```
scExampleSmallUAV
```
Double-click theAirframecomponent. Select theLandingGearcomponent on the System Composer composition editor.
Select theBrakeport. Open theInterface Editorfrom the toolstripModeling>Interface Editor. Right-click the interfaceoperatorCmdsand selectAssign to Selected Port(s).
Right-click theLandingGearcomponent and selectCreate Stateflow Chart Behavior. Alternatively, navigate toModeling>Create Stateflow Chart Behavior.
Double-clickLandingGear, which has the Stateflow icon. Navigate toModeling>Design Data>Symbols Paneto view the Stateflow symbols. The input portBrakeappears as input data in the symbols pane.

Note

Some Stateflow objects remain local to Stateflow charts. Input and output event ports are not supported in System Composer. Only local events are supported.

Since Stateflow ports show up as input and output data objects, they must follow Stateflow naming conventions. Ports are automatically renamed to follow Stateflow naming conventions. For more information, seeGuidelines for Naming Stateflow Objects(Stateflow).
Select theBrakeinput and view the interface in the Property Inspector. The interface can be accessed like a Simulink^®bus signal. For information on how to use bus signals in Stateflow, seeIndex and Assign Values to Stateflow Structures(Stateflow).
You can populate the Stateflow canvas to represent the internal states of theLandingGear.

RemoveStateflowChart Behavior from Component

You can remove Stateflow chart behavior from a component to delete the contents inside the Stateflow chart while preserving interfaces on the component.

Right-click on theLandingGearcomponent and selectInline Behavior.
To confirm the operation to delete all the content inside the Stateflow chart, clickOK.
The Stateflow chart behavior on the component is removed. Interfaces on the component are preserved.