Main Content


Operating point information for state, box, or function


A Stateflow.op.OperatingPointContainer object contains a snapshot of a state, box, or function in a Stateflow® chart during simulation. The operating point includes information about:

  • Active substates

  • State and function local data

  • Persistent variables in MATLAB® functions and truth tables


When you save the final operating point for a Simulink® model, as described in Save Operating Points, you create a Stateflow.op.BlockOperatingPoint object for each Stateflow chart in the model. This object contains a Stateflow.op.OperatingPointContainer object for each state, box, or function in the chart.

Access a Stateflow.op.OperatingPointContainer object by using the property that matches the name of the state, box, or function in the parent Stateflow.op.BlockOperatingPoint or Stateflow.op.OperatingPointContainer. For example, suppose that op is the Stateflow.op.BlockOperatingPoint object for a chart. To access the Stateflow.op.OperatingPointContainer object for a top-level state called state, enter:


Similarly, to access the Stateflow.op.OperatingPointContainer object for a substate called substate in the top-level state state, enter:



The Stateflow.op.OperatingPointContainer object contains a property for each substate, box, function, local data, and persistent variables in the state, box, or function. The name of the property matches the name of the state, function, box, or data. For example:

  • If a state has a substate named substate, the Stateflow.op.OperatingPointContainer object for the state has a property named substate that is specified as a Stateflow.op.OperatingPointContainer object.

  • If a MATLAB function has a persistent variable named persistentVar, the Stateflow.op.OperatingPointContainer object for the function has a property named persistentVar that is specified as a Stateflow.op.OperatingPointData object.

Object Functions

setActiveSet state as active
isActiveDetermine if state is active
getPrevActiveChildGet previously active substate
setPrevActiveChildSet previously active substate
openDisplay object in editing environment


collapse all

  1. Open the sf_aircraft model.


    For more information about this model, see Detect Faults in Aircraft Elevator Control System.

  2. Set the model to save the final operating point. Open the Configuration Parameters dialog box and, in the Data Import/Export pane:

    1. Select Final states and enter a name for the operating point. For this example, use xSteadyState.

    2. Select Save final operating point.

    3. Click OK.

  3. Set the stop time for this simulation segment. In the Simulation tab, set Stop Time to 3.

  4. Run the simulation.

  5. Access the Stateflow.op.BlockOperatingPoint object that contains the operating point information for the Mode Logic chart.

    blockpath = "sf_aircraft/Mode Logic";
    op = get(xSteadyState,blockpath)
    op = 
      Block:    "Mode Logic"    (handle)    (active)
      Path:     sf_aircraft/Mode Logic
        + Actuators          "State (OR)"                    (active)
        + LI_act             "Function"
        + LO_act             "Function"
        + L_switch           "Function"
        + RI_act             "Function"
        + RO_act             "Function"
        + R_switch           "Function"
          LI_mode            "State output data"		sf_aircraft_ModeType [1,1]
          LO_mode            "State output data"		sf_aircraft_ModeType [1,1]
          RI_mode            "State output data"		sf_aircraft_ModeType [1,1]
          RO_mode            "State output data"		sf_aircraft_ModeType [1,1]
  6. Access the Stateflow.op.OperatingPointContainer object that contains the operating point information for the Actuators state.

    ans = 
      State:    "Actuators"    (handle)    (active)
      Path:     sf_aircraft/Mode Logic/Actuators
        + LI            "State (AND)"         (active)
        + LO            "State (AND)"         (active)
        + RI            "State (AND)"         (active)
        + RO            "State (AND)"         (active)
  7. Highlight the states that are active in the chart at t = 3.


    Stateflow chart showing active states.

  8. Change the substate activity in the state LO to reflect a failure of the left-outer actuator.


    Stateflow chart showing active states.

  9. Verify that the substate Isolated in the state LO is active in the modified operating point.

    ans =

  10. Remove the highlighting of active states in the Stateflow Editor.


Version History

Introduced in R2009b

expand all