Hierarchical state machines in Simulink - Step-by-Step Execution

Concept Flow - Hierarchical state machines

Start

↓

Top State

↓

Substate A

↓

Nested Substate A1

↓

Nested Substate A2

↓

Substate B

↓

Nested Substate B1

↓

Nested Substate B2

↓

Transitions

↓

End

The machine starts at a top state, which contains substates. Each substate can have nested substates. Transitions can occur between these states, moving the machine through its hierarchy.

Execution Sample

Simulink

state TopState {
  state SubstateA {
    state NestedA1 {}
    state NestedA2 {}
  }
  state SubstateB {
    state NestedB1 {}
    state NestedB2 {}
  }
}

Defines a hierarchical state machine with a top state containing two substates, each of which has nested substates.

Execution Table

Step	Current State	Event	Transition Taken	Next State
1	TopState	start	Enter SubstateA	SubstateA
2	SubstateA	start	Enter NestedA1	NestedA1
3	NestedA1	eventX	Transition to NestedA2	NestedA2
4	NestedA2	eventY	Transition to SubstateB	SubstateB
5	SubstateB	eventZ	No transition	SubstateB
6	SubstateB	stop	Exit to TopState End	End

💡 Reached End state, machine stops.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	Final
Current State	None	SubstateA	NestedA1	NestedA2	SubstateB	SubstateB	End

Key Moments - 3 Insights

Why does the machine enter NestedA1 after entering SubstateA?

Because SubstateA is a composite state with nested states, the machine automatically enters its initial nested state NestedA1 as shown in execution_table step 2.

What happens when eventY occurs in NestedA2?

The machine transitions from NestedA2 to SubstateB, moving up one level in the hierarchy, as shown in execution_table step 4.

Why is there no transition on eventZ in SubstateB?

Because no transition is defined for eventZ in SubstateB, the machine stays in SubstateB, as shown in execution_table step 5.

Visual Quiz - 3 Questions

Look at the execution table, what is the current state after step 3?

A NestedA2

B NestedA1

C SubstateB

D SubstateA

💡 Hint

Check the 'Next State' column at step 3 in the execution_table.

At which step does the machine transition from a nested substate to a sibling substate?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Look for a transition moving from NestedA2 to SubstateB in the execution_table.

If eventZ had a transition to End state, what would be the next state after step 5?

A SubstateB

B End

C NestedA1

D NestedA2

💡 Hint

Refer to the 'Next State' column and imagine eventZ triggers a transition to End.

Concept Snapshot

Hierarchical State Machines:
- States can contain nested substates.
- Entering a composite state enters its initial nested state.
- Transitions can move within or across hierarchy levels.
- Events trigger transitions changing current active state.
- Useful for modeling complex behaviors with layers.

Full Transcript

Hierarchical state machines organize states inside other states, creating layers. When the machine starts, it enters the top state and then its initial nested state automatically. Events cause transitions that can move the machine between nested states or up and down the hierarchy. If no transition matches an event, the machine stays in the current state. This structure helps model complex systems by breaking behavior into manageable parts.

Practice

1. What is the main purpose of using hierarchical state machines in Simulink Stateflow?

easy

A. To organize states inside bigger states for simpler system modeling

B. To speed up simulation by skipping states

C. To create random state transitions automatically

D. To remove all states and use only transitions

Solution

1. Step 1: Understand hierarchical state machines concept

   Hierarchical state machines group smaller states inside bigger parent states to manage complexity.

2. Step 2: Identify the main benefit in Simulink Stateflow

   This grouping helps model complex systems in smaller, manageable parts.

3. Final Answer:

   To organize states inside bigger states for simpler system modeling -> Option A

4. Quick Check:

   Hierarchical states simplify models = A [OK]

Hint: Think: bigger states hold smaller states inside [OK]

Common Mistakes:

• Confusing hierarchical states with speeding simulation
• Thinking transitions create states automatically
• Believing hierarchical states remove all states

2. Which of the following is the correct way to define a child state inside a parent state in Simulink Stateflow?

easy

A. Draw the child state box next to the parent state box without overlap

B. Use a transition arrow from parent to child state only

C. Place the child state box completely inside the parent state box

D. Name the child state with the same name as the parent state

Solution

1. Step 1: Recall how hierarchical states are shown visually

   Child states are drawn inside the parent state box to show containment.

2. Step 2: Identify correct visual representation

   Only placing the child state fully inside the parent state box correctly defines hierarchy.

3. Final Answer:

   Place the child state box completely inside the parent state box -> Option C

4. Quick Check:

   Child inside parent box = B [OK]

Hint: Child states go inside parent state box visually [OK]

Common Mistakes:

• Placing child states outside parent states
• Using transitions to define hierarchy instead of containment
• Naming child and parent states identically

3. Consider this Stateflow snippet: A parent state P has two child states S1 and S2. If the machine starts in P and the default child state is S1, what is the active state after initialization?

medium

A. S2 only

B. S1 only

C. P only

D. P and S1

Solution

1. Step 1: Understand hierarchical state activation

   When a parent state is active, its default child state is also active.

2. Step 2: Apply to given states

   Starting in parent P activates P and its default child S1.

3. Final Answer:

   P and S1 -> Option D

4. Quick Check:

   Parent and default child active = A [OK]

Hint: Parent and default child states are active together [OK]

Common Mistakes:

• Thinking only parent or only child is active
• Confusing default child with other child
• Ignoring hierarchical activation rules

4. You have a hierarchical state machine where a child state C is not activating when the parent state P is active. What is the most likely cause?

medium

A. The child state C is not placed inside the parent state P

B. The parent state P has no exit transitions

C. The child state C has no transitions

D. The parent state P is not connected to any other state

Solution

1. Step 1: Check child state placement in hierarchy

   For a child state to activate with its parent, it must be inside the parent's boundary.

2. Step 2: Identify cause of non-activation

   If C is outside P, it won't activate when P is active.

3. Final Answer:

   The child state C is not placed inside the parent state P -> Option A

4. Quick Check:

   Child outside parent means no activation = C [OK]

Hint: Check if child state is inside parent state box [OK]

Common Mistakes:

• Assuming transitions affect child activation directly
• Ignoring visual containment rules
• Confusing exit transitions with activation

5. You want to model a traffic light system with hierarchical states: a parent state Operational and child states Green, Yellow, and Red. How can hierarchical states help improve this model?

hard

A. By using hierarchical states to skip the yellow light automatically

B. By grouping the light colors inside Operational, you can manage transitions and timers centrally

C. By creating separate machines for each light color without hierarchy

D. By removing the parent state and using only child states for simplicity

Solution

1. Step 1: Understand hierarchical grouping benefits

   Grouping child states inside a parent allows shared logic like timers or transitions at the parent level.

2. Step 2: Apply to traffic light example

   Parent Operational can handle common behavior, while child states represent light colors.

3. Final Answer:

   By grouping the light colors inside Operational, you can manage transitions and timers centrally -> Option B

4. Quick Check:

   Hierarchy centralizes shared logic = D [OK]

Hint: Use parent state for shared logic, children for specific states [OK]

Common Mistakes:

• Removing parent state loses shared control
• Using separate machines complicates coordination
• Assuming hierarchy skips states automatically