Hierarchical state machines in Simulink - Mini Project: Build & Apply

Hierarchical State Machines in Simulink

📖 Scenario: You are designing a simple traffic light controller using hierarchical state machines in Simulink. The traffic light has two main states: Normal Operation and Flashing Mode. In Normal Operation, the light cycles through Green, Yellow, and Red. In Flashing Mode, the light flashes Yellow continuously.

🎯 Goal: Build a hierarchical state machine in Simulink that models the traffic light controller with the described states and transitions.

📋 What You'll Learn

Create a top-level state machine with two states: NormalOperation and FlashingMode.

Inside NormalOperation, create substates: Green, Yellow, and Red.

Add transitions between Green to Yellow, Yellow to Red, and Red back to Green.

Add a transition from NormalOperation to FlashingMode triggered by a variable flashSwitch.

Add a transition from FlashingMode back to NormalOperation when flashSwitch is false.

In FlashingMode, create a substate FlashingYellow that flashes the yellow light.

💡 Why This Matters

🌍 Real World

Traffic light controllers use hierarchical state machines to manage complex light sequences and modes efficiently.

💼 Career

Understanding hierarchical state machines is essential for embedded systems engineers and control system designers working with Simulink and Stateflow.

1

Create the top-level states

Create a Stateflow chart in Simulink with two top-level states named NormalOperation and FlashingMode.

Simulink

# Create two top-level states named NormalOperation and FlashingMode
# Your code here

Hint

Use the Stateflow editor to add two states at the top level and name them exactly NormalOperation and FlashingMode.

2

Add substates inside NormalOperation

Inside the NormalOperation state, create three substates named Green, Yellow, and Red.

Simulink

% Inside NormalOperation, add substates Green, Yellow, and Red
# Your code here

Hint

Double-click the NormalOperation state and add three states inside it named Green, Yellow, and Red.

3

Add transitions between substates and top-level transitions

Add transitions from Green to Yellow, from Yellow to Red, and from Red back to Green. Also, add a transition from NormalOperation to FlashingMode triggered by the variable flashSwitch, and a transition back from FlashingMode to NormalOperation when flashSwitch is false.

Simulink

# Add transitions between Green->Yellow, Yellow->Red, Red->Green
# Add transition NormalOperation->FlashingMode when flashSwitch == true
# Add transition FlashingMode->NormalOperation when flashSwitch == false
# Your code here

Hint

Use the transition tool in Stateflow to connect the substates in a cycle. Then add transitions between the top-level states with the specified conditions.

4

Add flashing yellow substate inside FlashingMode and output the state

Inside the FlashingMode state, create a substate named FlashingYellow that represents the flashing yellow light. Then, add code to output the current state name using disp() or equivalent to show the active state.

Simulink

# Inside FlashingMode, add substate FlashingYellow
# Add code to display the current active state
# Your code here

Hint

Inside the FlashingMode state, add a substate named FlashingYellow. Use a Stateflow action like disp(activeState) to show which state is active.

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