Transition conditions and actions in Simulink

Introduction

Transition conditions and actions help control how a system moves from one state to another. They make sure the system behaves correctly based on rules you set.

When you want to model a traffic light changing colors based on timers.

When you need to switch a machine between different modes like idle, running, and stopped.

When you want to trigger an alarm only if a sensor value crosses a limit.

When you want to perform an action right after changing from one state to another.

When you want to control a robot's behavior depending on sensor inputs.

Syntax

Simulink

Transition: [condition] {action}

- condition: a logical expression that decides when to move to the next state
- action: code or commands that run when the transition happens

The condition must be true for the transition to occur.

Actions run only once when the transition happens.

Examples

This means: when speed is greater than 10, move to the next state and run startMotor().

Simulink

Transition: [speed > 10] {startMotor()}

This means: when the button is pressed, transition and reset the counter.

Simulink

Transition: [buttonPressed] {resetCounter()}

This means: if temperature is below zero, switch state and turn on the heater.

Simulink

Transition: [temperature < 0] {turnOnHeater()}

Sample Program

This example shows two states: Idle and Running. The system moves from Idle to Running when startButton is true and runs initialize(). It moves back to Idle when stopButton is true and runs shutdown().

Simulink

/* Simulink Stateflow example pseudocode */

state Idle {
  during: display("Idle mode")
  transition to Running [startButton == true] {initialize()}
}

state Running {
  during: display("Running mode")
  transition to Idle [stopButton == true] {shutdown()}
}

function initialize() {
  display("Starting system")
}

function shutdown() {
  display("Stopping system")
}

/* Simulate pressing startButton and stopButton */
startButton = true
stopButton = false
// Transition from Idle to Running triggers initialize()

startButton = false
stopButton = true
// Transition from Running to Idle triggers shutdown()

Important Notes

Make sure conditions are clear and do not conflict to avoid unexpected transitions.

Actions should be short and only do what is needed during the transition.

Test transitions carefully to see if the system moves as expected.

Summary

Transition conditions decide when to move between states.

Actions run once when the transition happens.

Use them to control system behavior clearly and safely.

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