Entry, during, and exit actions in Simulink - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Entry Actions in Stateflow

In Simulink Stateflow, what is the primary purpose of an entry action in a state?

A To execute code once when the state is entered

B To execute code continuously while the state is active

C To execute code once when the state is exited

D To execute code only if a transition condition is true

💡 Hint

Think about what happens exactly at the moment you enter a state.

An entry action runs exactly once when the state becomes active. It is used to initialize or set variables at the start of the state.

❓ Predict Output

intermediate

Output of During Action Execution

Consider a Stateflow state with a during action that increments a variable count by 1 every time the state is active. If the state is active for 3 time steps starting with count = 0, what is the value of count after these steps?

Simulink

count = 0
for _ in range(3):
    count += 1
print(count)

A 3

B 1

C 0

D 4

💡 Hint

During actions run repeatedly while the state is active.

During actions execute at each time step the state is active, so count increments 3 times from 0 to 3.

❓ data_output

advanced

Exit Action Effect on Variable

A state has an exit action that sets a variable flag to True. If flag is initially False and the state is exited once, what is the value of flag after exit?

Simulink

flag = False
# exit action
flag = True
print(flag)

A Raises an error

B None

C False

D True

💡 Hint

Exit actions run once when leaving the state.

Exit actions execute once when the state is exited, so flag changes from False to True.

🔧 Debug

advanced

Identify the Error in Action Syntax

Which option contains a syntax error in defining an entry, during, or exit action in Stateflow?

A during: y = y + 1;

B exit x = 0;

C entry: z = z * 2;

D entry: x = 5;

💡 Hint

Check the correct keyword and colon usage for actions.

Exit actions require a colon after the keyword, like exit:. Option B misses the colon, causing a syntax error.

🚀 Application

expert

Sequence of Actions in State Transitions

In a Stateflow chart, a transition occurs from State A to State B. Which sequence correctly describes the order of actions executed during this transition?

A Entry actions of State B → Exit actions of State A → During actions of State B

B During actions of State A → Entry actions of State B → Exit actions of State A

C Exit actions of State A → Entry actions of State B → During actions of State B

D During actions of State A → Exit actions of State A → Entry actions of State B

💡 Hint

Think about what happens when leaving one state and entering another.

When transitioning, the exit actions of the current state run first, then the entry actions of the new state, followed by the during actions of the new state.

Practice

1. In Simulink Stateflow, what is the purpose of an entry action in a state?

easy

A. To execute code continuously while the state is active

B. To execute code once when the state is entered

C. To execute code once when the state is exited

D. To define transitions between states

Solution

1. Step 1: Understand what entry action means

   An entry action runs only once when the state becomes active, right at the moment of entry.

2. Step 2: Compare with other actions

   During actions run continuously while in the state, exit actions run once when leaving the state, and transitions define movement between states.

3. Final Answer:

   To execute code once when the state is entered -> Option B

4. Quick Check:

   Entry action = runs once on entering state [OK]

Hint: Entry actions run once at state start, not continuously [OK]

Common Mistakes:

• Confusing entry with during actions
• Thinking entry runs multiple times
• Mixing entry with exit actions

2. Which of the following is the correct syntax to define an exit action in a Simulink Stateflow state named Idle?

easy

A. exit() { disp('Exiting Idle'); }

B. on exit: disp('Exiting Idle');

C. exit: disp('Exiting Idle');

D. exit_action: disp('Exiting Idle');

Solution

1. Step 1: Recall exit action syntax in Stateflow

   Exit actions are defined with the keyword exit: followed by the action code.

2. Step 2: Check each option

   exit: disp('Exiting Idle'); uses correct exit: syntax. on exit: disp('Exiting Idle'); uses incorrect on exit:. exit() { disp('Exiting Idle'); } uses function style which is invalid. exit_action: disp('Exiting Idle'); uses exit_action: which is not recognized.

3. Final Answer:

   exit: disp('Exiting Idle'); -> Option C

4. Quick Check:

   Exit action syntax = exit: code [OK]

Hint: Exit actions start with 'exit:' keyword followed by code [OK]

Common Mistakes:

• Using 'on exit:' instead of 'exit:'
• Trying to define exit as a function
• Using incorrect keywords like 'exit_action:'

3. Consider the following Stateflow state Processing with these actions:

entry: count = 0;
during: count = count + 1;
exit: disp(count);

What will be displayed when the state Processing is exited after being active for 3 simulation steps?

medium

A. 3

B. 1

C. 0

D. 4

Solution

1. Step 1: Track variable changes during state

   On entry, count is set to 0. During each step, it increments by 1. After 3 steps, count = 3.

2. Step 2: Determine exit action output

   On exit, disp(count) prints the current count, which is 3.

3. Final Answer:

   3 -> Option A

4. Quick Check:

   Count increments 3 times, exit prints 3 [OK]

Hint: Count increments during each step, exit prints final count [OK]

Common Mistakes:

• Forgetting entry sets count to 0
• Assuming exit prints 0 or 1
• Counting one extra increment

4. You have this Stateflow state code:

entry: x = 5;
during: x = x + 2;
exit: disp(x);

But when you run the simulation, disp(x) shows 5 instead of increasing values. What is the likely error?

medium

A. The during action is not executing because the state is not active long enough

B. The entry action resets x every step

C. The exit action is placed incorrectly inside the during block

D. The variable x is not declared

Solution

1. Step 1: Analyze why during action might not run

   If the state is active only one step or immediately exited, the during action does not get a chance to increment x.

2. Step 2: Check other options for correctness

   Entry runs once on entry, not every step. Exit action placement is correct. Variable declaration is not required to see this behavior.

3. Final Answer:

   The during action is not executing because the state is not active long enough -> Option A

4. Quick Check:

   During runs only while state active [OK]

Hint: During runs only if state stays active multiple steps [OK]

Common Mistakes:

• Thinking entry runs every step
• Misplacing exit action inside during
• Assuming variable declaration causes issue

5. You want to count how many times a state Active is entered during a simulation. Which approach correctly uses entry, during, and exit actions to achieve this?

hard

A. Use entry: count = 0; to reset count every time state is entered

B. Use during: count = count + 1; to increment count continuously while active

C. Use exit: count = count + 1; to increment count when leaving the state

D. Use entry: count = count + 1; and initialize count outside the state; no during or exit needed

Solution

1. Step 1: Understand counting entries

   To count entries, increment count once each time the state is entered. This is done in the entry action.

2. Step 2: Evaluate other options

   During increments continuously, not suitable for counting entries. Exit increments on leaving, not entering. Resetting count on entry loses previous counts.

3. Final Answer:

   Use entry: count = count + 1; and initialize count outside the state; no during or exit needed -> Option D

4. Quick Check:

   Entry action increments count once per entry [OK]

Hint: Increment count in entry action, initialize count outside [OK]

Common Mistakes:

• Incrementing count in during action
• Resetting count on every entry
• Incrementing count on exit instead of entry