Transition conditions and actions in Simulink - Mini Project: Build & Apply

Transition Conditions and Actions in Simulink Stateflow

📖 Scenario: You are designing a simple traffic light controller using Simulink Stateflow. The traffic light changes states based on timer conditions. You will create states and transitions with conditions and actions to control the light colors.

🎯 Goal: Build a Stateflow chart with three states: Red, Green, and Yellow. Define transition conditions based on a timer variable t and add actions to change the light color accordingly.

📋 What You'll Learn

Create a Stateflow chart with states named Red, Green, and Yellow.

Define a timer variable t initialized to 0.

Add transition conditions using t to move between states.

Add entry actions to each state to set the light color.

Print the current state and light color at each step.

💡 Why This Matters

🌍 Real World

Traffic light controllers use transition conditions and actions to change lights safely and timely based on timers and sensors.

💼 Career

Understanding transition conditions and actions is essential for designing state machines in embedded systems, automation, and control engineering.

1

Create the timer variable t

Create a variable called t and set it to 0 to represent the timer.

Simulink

# Create a variable called t and set it to 0
# Your code here

Hint

The timer variable t will help control transitions between states.

2

Define the initial state and entry actions

Create a variable called state and set it to 'Red'. Also create a variable called light_color and set it to 'Red' as the entry action for the Red state.

Simulink

t = 0
# Set the initial state to 'Red' and light_color to 'Red'
# Your code here

Hint

The initial state is Red and the light color should match it.

3

Add transition conditions and update actions

Write an if-elif-else block to update state and light_color based on t: if state is 'Red' and t >= 5, change state to 'Green' and light_color to 'Green'. If state is 'Green' and t >= 10, change state to 'Yellow' and light_color to 'Yellow'. If state is 'Yellow' and t >= 12, change state to 'Red', reset t to 0, and set light_color to 'Red'. Otherwise, increment t by 1.

Simulink

t = 0
state = 'Red'
light_color = 'Red'

# Add transition conditions and update state, light_color, and t
# Your code here

Hint

Use if-elif-else to check the timer and update states and colors accordingly.

4

Print the current state and light color

Write a print statement to display the current state and light_color in the format: State: <state>, Light Color: <light_color>.

Simulink

t = 0
state = 'Red'
light_color = 'Red'

if state == 'Red' and t >= 5:
    state = 'Green'
    light_color = 'Green'
elif state == 'Green' and t >= 10:
    state = 'Yellow'
    light_color = 'Yellow'
elif state == 'Yellow' and t >= 12:
    state = 'Red'
    light_color = 'Red'
    t = 0
else:
    t += 1

# Print the current state and light_color
# Your code here

Hint

Use an f-string to format the print output showing the state and light color.

Practice

1. In Simulink Stateflow, what does a transition condition specify?

easy

A. The initial value of a variable

B. The color of the state in the diagram

C. How long the system stays in a state

D. When the system should move from one state to another

Solution

1. Step 1: Understand transition conditions

   Transition conditions define the criteria that trigger moving from one state to another in Stateflow.

2. Step 2: Differentiate from other elements

   Colors and variable initial values do not control state changes; only conditions do.

3. Final Answer:

   When the system should move from one state to another -> Option D

4. Quick Check:

   Transition condition = state change trigger [OK]

Hint: Transition conditions control state changes timing [OK]

Common Mistakes:

• Confusing transition conditions with state colors
• Thinking actions control timing instead of conditions
• Assuming initial values trigger transitions

2. Which of the following is the correct syntax for a transition condition in Simulink Stateflow?

easy

A. [x > 5]

B. (x > 5)

C. {x > 5}

D. 5>

Solution

1. Step 1: Recall Stateflow transition syntax

   Transition conditions are enclosed in square brackets, e.g., [condition].

2. Step 2: Compare options

   Only [x > 5] uses square brackets correctly; others use parentheses, braces, or angle brackets which are invalid.

3. Final Answer:

   [x > 5] -> Option A

4. Quick Check:

   Transition condition syntax = square brackets [OK]

Hint: Use square brackets for transition conditions [OK]

Common Mistakes:

• Using parentheses instead of square brackets
• Confusing braces or angle brackets with correct syntax
• Omitting brackets entirely

3. Consider this Stateflow transition: [speed > 10] / count = count + 1; What happens when speed is 12 and count is 3?

medium

A. Transition does not occur and count stays 3

B. Transition occurs and count becomes 4

C. Transition occurs but count stays 3

D. Syntax error due to missing semicolon

Solution

1. Step 1: Check transition condition

   Condition is speed > 10. Given speed = 12, condition is true, so transition occurs.

2. Step 2: Apply transition action

   Action increments count by 1: count = 3 + 1 = 4.

3. Final Answer:

   Transition occurs and count becomes 4 -> Option B

4. Quick Check:

   Condition true + action increments count = 4 [OK]

Hint: Check condition first, then apply action on transition [OK]

Common Mistakes:

• Ignoring the action and leaving count unchanged
• Assuming transition does not occur when condition is true
• Thinking semicolon causes syntax error in Stateflow

4. You wrote this transition in Stateflow: [temp > 50] count = count + 1; but the action does not execute. What is the error?

medium

A. Missing slash '/' before the action

B. Condition syntax is wrong

C. Count variable is not initialized

D. Semicolon should be outside brackets

Solution

1. Step 1: Review transition syntax

   Transition actions must follow a slash '/' after the condition, e.g., [condition] / action.

2. Step 2: Identify missing slash

   The given transition lacks '/', so action is not recognized or executed.

3. Final Answer:

   Missing slash '/' before the action -> Option A

4. Quick Check:

   Action requires '/' separator [OK]

Hint: Always put '/' before actions in transitions [OK]

Common Mistakes:

• Forgetting the slash '/' before actions
• Assuming condition syntax error without checking slash
• Thinking variable initialization affects action execution here

5. You want a transition that only happens when pressure > 100 and increments alarmCount only once per transition. Which transition syntax is correct?

hard

A. [pressure > 100] alarmCount = alarmCount + 1;

B. / [pressure > 100] alarmCount = alarmCount + 1;

C. [pressure > 100] / alarmCount = alarmCount + 1;

D. [pressure > 100] / alarmCount += 1

Solution

1. Step 1: Confirm correct transition condition and action format

   Condition must be in square brackets, followed by a slash '/', then the action ending with a semicolon.

2. Step 2: Evaluate each option

   [pressure > 100] / alarmCount = alarmCount + 1; matches correct syntax: [condition] / action;. [pressure > 100] alarmCount = alarmCount + 1; misses '/', C has '/' before condition, D uses '+=' which is not standard in Stateflow.

3. Final Answer:

   [pressure > 100] / alarmCount = alarmCount + 1; -> Option C

4. Quick Check:

   Condition in [] + '/' + action with ';' = correct [OK]

Hint: Use [condition] / action; format for transitions [OK]

Common Mistakes:

• Omitting slash '/' before action
• Placing slash before condition
• Using '+=' instead of '=' for assignment