States and transitions in Simulink - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a state in the context of Simulink Stateflow?

A state represents a condition or situation during the life of a system where it waits for events or performs actions. It is like a mode the system can be in.

beginner

What does a transition do between states in Stateflow?

A transition defines the rule or event that causes the system to move from one state to another.

intermediate

How do you trigger a transition in Stateflow?

Transitions are triggered by events, conditions, or both. When the condition is true or the event occurs, the transition happens.

intermediate

What is the difference between exclusive and parallel states?

Exclusive states mean the system can be in only one state at a time. Parallel states allow the system to be in multiple states simultaneously.

beginner

Why are states and transitions useful in modeling real-world systems?

They help represent how a system behaves over time, showing different modes and how it changes from one mode to another based on events or conditions.

In Stateflow, what causes a transition between states?

A An event or condition

B A random timer

C User input only

D No cause, transitions are automatic

Transitions happen when a specified event occurs or a condition becomes true.

What type of state allows the system to be in multiple states at once?

A Parallel state

B Exclusive state

C Initial state

D Final state

Parallel states let the system be in several states simultaneously.

Which of these best describes a state in Stateflow?

A A mathematical formula

B A graphical icon only

C A data storage unit

D A condition or mode the system is in

A state represents a mode or condition of the system.

What happens if a transition condition is never met?

A The system moves randomly

B The system stays in the current state

C The system crashes

D The system skips the state

Without the transition condition met, the system remains in the current state.

Which element in Stateflow defines when to move from one state to another?

A Event

B State

C Transition

D Action

Transitions specify the rules for moving between states.

Explain what states and transitions are in Stateflow and how they work together to model system behavior.

Think about how a traffic light changes colors based on timers or sensors.

Describe the difference between exclusive and parallel states and give an example of when each might be used.

Consider modes that cannot happen at the same time versus tasks that run together.

Practice

1. In Simulink Stateflow, what does a state represent?

easy

A. A mathematical operation

B. A graphical icon only

C. A data storage variable

D. A mode or condition of the system

Solution

1. Step 1: Understand the role of states in Stateflow

   States represent different modes or conditions that a system can be in during execution.

2. Step 2: Differentiate states from other elements

   States are not variables or operations; they define behavior and system modes.

3. Final Answer:

   A mode or condition of the system -> Option D

4. Quick Check:

   State = system mode [OK]

Hint: States = system modes or conditions [OK]

Common Mistakes:

• Confusing states with variables
• Thinking states are just icons
• Mixing states with mathematical operations

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

easy

A. state1 => state2 (condition)

B. state1 -> state2 {condition}

C. state1 --> state2 [condition]

D. state1 -- state2 [condition]

Solution

1. Step 1: Recall Stateflow transition syntax

   Transitions use the arrow --> followed by a condition in square brackets.

2. Step 2: Match syntax options

   state1 --> state2 [condition] uses --> and square brackets correctly, others use incorrect symbols or brackets.

3. Final Answer:

   state1 --> state2 [condition] -> Option C

4. Quick Check:

   Transition syntax = --> [condition] [OK]

Hint: Transitions use --> with [condition] brackets [OK]

Common Mistakes:

• Using wrong arrow symbols
• Using curly or round brackets instead of square
• Omitting the condition brackets

3. Given this Stateflow snippet:

state A
  entry: x = 0;
  during: x = x + 1;
end

transition from A to B [x >= 3]

What is the value of x when the system transitions from state A to B?

medium

A. 3

B. 4

C. 2

D. 0

Solution

1. Step 1: Analyze state A behavior

   On entry, x is set to 0. During state A, x increments by 1 each cycle.

2. Step 2: Determine when transition triggers

   Transition triggers when x >= 3. So after 3 increments, x equals 3 and transition occurs.

3. Final Answer:

   3 -> Option A

4. Quick Check:

   Transition at x >= 3 means x = 3 [OK]

Hint: Transition triggers when condition first becomes true [OK]

Common Mistakes:

• Counting increments before entry action
• Assuming transition triggers at x > 3 instead of >= 3
• Forgetting initial value of x

4. Identify the error in this transition definition:

state A
end
state B
end

A --> B (x > 5)

medium

A. Missing condition brackets [] around (x > 5)

B. Incorrect arrow symbol used

C. States must have entry actions

D. Transition must be inside state definitions

Solution

1. Step 1: Check transition condition syntax

   Transition conditions must be enclosed in square brackets [], not parentheses ().

2. Step 2: Verify other syntax elements

   The arrow --> is correct, states can be empty, and transitions are defined outside states.

3. Final Answer:

   Missing condition brackets [] around (x > 5) -> Option A

4. Quick Check:

   Conditions use [] not () [OK]

Hint: Use [] for conditions, not () [OK]

Common Mistakes:

• Using parentheses instead of square brackets
• Thinking arrow is wrong
• Believing states must have actions

5. You want to model a traffic light system with states Red, Green, and Yellow. The system should transition from Green to Yellow only if a timer reaches 60 seconds. Which transition condition correctly models this?

hard

A. Green --> Yellow [timer > 60]

B. Green --> Yellow [timer == 60]

C. Green --> Yellow [timer < 60]

D. Green --> Yellow [timer != 60]

Solution

1. Step 1: Understand the timing condition

   The transition should happen exactly when the timer reaches 60 seconds, so the condition must check equality.

2. Step 2: Evaluate options

   Green --> Yellow [timer == 60] uses timer == 60, which triggers transition at 60 seconds. Others check greater, less, or not equal, which do not match the requirement.

3. Final Answer:

   Green --> Yellow [timer == 60] -> Option B

4. Quick Check:

   Exact timer match triggers transition [OK]

Hint: Use == for exact timer match in transitions [OK]

Common Mistakes:

• Using > or < instead of ==
• Using != which triggers at wrong times
• Forgetting square brackets around condition