State machine design for Arduino - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a state machine in the context of Arduino programming?

A state machine is a way to organize code by defining different states and the rules to move between them. It helps control how the Arduino behaves step-by-step, like following a map of actions.

beginner

Why use a state machine instead of many if-else statements in Arduino code?

State machines make code easier to read and manage by clearly separating different behaviors. They reduce confusion and bugs compared to many if-else checks scattered around.

beginner

What are the main parts of a state machine design for Arduino?

The main parts are: states (different modes or steps), events or inputs (things that cause change), and transitions (rules to move from one state to another).

intermediate

How can you represent states in Arduino code?

You can use an enum (a list of named constants) to name each state, and a variable to keep track of the current state.

beginner

What is a simple example of a state machine controlling an LED with Arduino?

A simple example: states are OFF and ON. When a button is pressed, the state changes from OFF to ON or ON to OFF, turning the LED on or off accordingly.

What does a state machine help you do in Arduino programming?

A Make the Arduino run faster

B Organize code by different modes or steps

C Increase the memory of Arduino

D Connect to the internet

A state machine organizes code by defining states and transitions, making behavior clear and manageable.

Which Arduino code structure is best for naming states in a state machine?

A for loop

B if statement

C enum

D array

An enum lets you name states clearly, making the code easier to read and maintain.

In a state machine, what triggers moving from one state to another?

A Events or inputs

B Random numbers

C Comments in code

D Arduino reset

Events or inputs like button presses cause the state machine to change states.

What is a benefit of using a state machine over many if-else statements?

A Code is easier to read and less error-prone

B It uses less electricity

C It makes the Arduino smaller

D It automatically fixes bugs

State machines organize code clearly, reducing mistakes and improving readability.

Which of these is NOT a part of a state machine?

A Transitions

B States

C Events

D Loops

Loops are programming structures but not a core part of state machine design.

Explain how you would design a simple state machine for an Arduino project that controls a traffic light.

Think about the different light colors as states and how time controls switching.

Describe the advantages of using a state machine in Arduino programming compared to using many if-else statements.

Focus on how state machines help manage complexity.

Practice

1. What is the main purpose of using a state machine in an Arduino program?

easy

A. To organize the program into clear, manageable steps

B. To increase the speed of the Arduino processor

C. To reduce the power consumption automatically

D. To connect multiple Arduino boards together

Solution

1. Step 1: Understand the concept of state machines

   A state machine breaks a program into distinct states or steps to manage behavior clearly.

2. Step 2: Identify the main benefit in Arduino context

   This organization helps make the code easier to read, debug, and extend.

3. Final Answer:

   To organize the program into clear, manageable steps -> Option A

4. Quick Check:

   State machine purpose = organize steps [OK]

Hint: State machines organize code into clear steps [OK]

Common Mistakes:

• Thinking state machines speed up the processor
• Confusing power saving with state management
• Assuming state machines connect multiple boards

2. Which of the following is the correct way to declare states in an Arduino state machine using enum?

easy

A. enum State {START, RUNNING, STOPPED};

B. enum State = {START, RUNNING, STOPPED};

C. enum State {START; RUNNING; STOPPED};

D. enum State (START, RUNNING, STOPPED);

Solution

1. Step 1: Recall enum syntax in Arduino (C++)

   The correct syntax uses curly braces and commas to list states without assignment or semicolons.

2. Step 2: Check each option for syntax errors

   enum State {START, RUNNING, STOPPED}; uses correct syntax: enum State {START, RUNNING, STOPPED}; Options B, C, and D have incorrect assignment, semicolons, or parentheses.

3. Final Answer:

   enum State {START, RUNNING, STOPPED}; -> Option A

4. Quick Check:

   Correct enum syntax = enum State {START, RUNNING, STOPPED}; [OK]

Hint: Use curly braces and commas for enum states [OK]

Common Mistakes:

• Using '=' sign after enum name
• Separating states with semicolons instead of commas
• Using parentheses instead of braces

3. What will be the output on the Serial Monitor when running this Arduino code snippet?

enum State {IDLE, PROCESS, DONE};
State currentState = IDLE;

void setup() {
  Serial.begin(9600);
  switch(currentState) {
    case IDLE:
      Serial.println("Waiting");
      break;
    case PROCESS:
      Serial.println("Working");
      break;
    case DONE:
      Serial.println("Finished");
      break;
  }
}

medium

A. Finished

B. Working

C. Waiting

D. No output

Solution

1. Step 1: Identify the initial state value

   The variable currentState is set to IDLE before setup() runs.

2. Step 2: Follow the switch-case logic

   Switch checks currentState; since it is IDLE, it prints "Waiting" to Serial Monitor.

3. Final Answer:

   Waiting -> Option C

4. Quick Check:

   State IDLE prints "Waiting" [OK]

Hint: Check initial state value to predict output [OK]

Common Mistakes:

• Assuming PROCESS or DONE prints without state change
• Thinking setup() runs multiple times
• Ignoring break statements in switch

4. Identify the error in this Arduino state machine code snippet:

enum State {START, RUNNING, STOPPED};
State currentState = START;

void loop() {
  switch(currentState) {
    case START:
      Serial.println("Start");
      currentState = RUNNING
      break;
    case RUNNING:
      Serial.println("Running");
      break;
    case STOPPED:
      Serial.println("Stopped");
      break;
  }
}

medium

A. Incorrect enum declaration

B. Serial not initialized in setup()

C. Missing break in RUNNING case

D. Missing semicolon after currentState = RUNNING

Solution

1. Step 1: Check syntax line by line

   Look at the line: currentState = RUNNING without a semicolon at the end.

2. Step 2: Identify the error type

   Missing semicolon causes a compile error. Other parts are correct or not critical for this snippet.

3. Final Answer:

   Missing semicolon after currentState = RUNNING -> Option D

4. Quick Check:

   Missing semicolon = syntax error [OK]

Hint: Check each statement ends with a semicolon [OK]

Common Mistakes:

• Ignoring missing semicolon errors
• Assuming enum declaration is wrong
• Forgetting to initialize Serial in setup()

5. You want to design a state machine for an Arduino traffic light with states: RED, GREEN, YELLOW. Which approach correctly updates the state to cycle through RED -> GREEN -> YELLOW -> RED inside loop()?

hard

A. Use a while loop inside loop() to cycle states infinitely

B. Use a switch on currentState and set currentState to the next state in each case

C. Use if statements comparing currentState to integers 0,1,2 and increment currentState by 1

D. Use delay() to wait and then reset currentState to RED always

Solution

1. Step 1: Understand state machine cycling

   Using a switch-case on currentState allows clear, readable transitions between states.

2. Step 2: Evaluate each option's suitability

   Use a switch on currentState and set currentState to the next state in each case correctly updates currentState to the next state inside each case. Use if statements comparing currentState to integers 0,1,2 and increment currentState by 1 uses integers but lacks clarity and safe cycling. Use a while loop inside loop() to cycle states infinitely with while loop inside loop() blocks Arduino's main loop. Use delay() to wait and then reset currentState to RED always resets state always to RED, not cycling properly.

3. Final Answer:

   Use a switch on currentState and set currentState to the next state in each case -> Option B

4. Quick Check:

   Switch-case for cycling states = Use a switch on currentState and set currentState to the next state in each case [OK]

Hint: Use switch-case to update states clearly [OK]

Common Mistakes:

• Using while loops inside loop() causing freezes
• Resetting state without cycling
• Using integers without clear state names