Why state machines are used in embedded in Embedded C - Visual Breakdown

Concept Flow - Why state machines are used in embedded

Start

↓

Check Inputs

↓

Determine Current State

↓

Execute State Actions

↓

Check Conditions for Transition

↓

Change State

↓

Update State

↓

Repeat Loop

The system loops by checking inputs, executing actions based on the current state, and changing states when conditions are met.

Execution Sample

Embedded C

enum State {IDLE, RUNNING, ERROR};
enum State current = IDLE;

while(1) {
  switch(current) {
    case IDLE: /* wait */ break;
    case RUNNING: /* do work */ break;
    case ERROR: /* handle error */ break;
  }
}

This code shows a simple state machine cycling through states to control embedded behavior.

Execution Table

Step	Current State	Input/Event	Action Taken	Next State
1	IDLE	Start Button Pressed	Begin operation	RUNNING
2	RUNNING	Error Detected	Stop and signal error	ERROR
3	ERROR	Reset Button Pressed	Clear error	IDLE
4	IDLE	No input	Wait	IDLE
Exit	IDLE	No more events	System idle	IDLE

💡 System stays in IDLE with no new inputs, so loop continues waiting.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4
current	IDLE	RUNNING	ERROR	IDLE	IDLE

Key Moments - 2 Insights

Why do we use states instead of just if-else checks?

States organize behavior clearly and avoid complex nested if-else, as shown in the execution_table where each state has specific actions.

What happens if no input changes the state?

The system stays in the current state, like IDLE in step 4, waiting for events without changing behavior.

Visual Quiz - 3 Questions

Look at the execution_table, what is the current state after step 2?

A RUNNING

B ERROR

C IDLE

D RESET

💡 Hint

Check the 'Next State' column in row for step 2.

At which step does the system return to IDLE state?

A Step 3

B Step 1

C Step 2

D Step 4

💡 Hint

Look at the 'Next State' column for when it changes to IDLE.

If the error never occurs, what would the execution_table show?

A System cycles between IDLE and ERROR

B System moves to ERROR state anyway

C System stays in RUNNING state indefinitely

D System immediately resets

💡 Hint

Refer to the 'Input/Event' and 'Next State' columns for error transitions.

Concept Snapshot

State machines help embedded systems manage behavior clearly.
They use states to represent modes like IDLE or RUNNING.
Transitions happen on inputs or events.
This avoids complex if-else and makes code easier to follow.
Embedded loops check state, act, then update state.
This keeps system predictable and responsive.

Full Transcript

State machines are used in embedded systems to organize how the system behaves in different situations. The system stays in one state at a time, like IDLE or RUNNING. It checks inputs or events to decide if it should change to another state. This makes the code easier to understand and maintain compared to many if-else statements. The example code shows a loop that checks the current state and runs actions for that state. The execution table traces how the state changes step by step based on inputs like button presses or errors. If no input changes the state, the system stays in the same state, waiting. This approach helps embedded devices be reliable and clear in their behavior.