Code organization with functions in Arduino - Step-by-Step Execution

Concept Flow - Code organization with functions

Start

↓

Define function

↓

Setup function runs once

↓

Loop function runs repeatedly

↓

Call function inside loop

↓

Function executes code block

↓

Return to loop

↓

Loop function runs repeatedly

The program starts by defining functions, then runs setup once, then repeatedly runs loop, calling functions inside loop to organize code.

Execution Sample

Arduino

void blinkLED() {
  digitalWrite(LED_BUILTIN, HIGH);
  delay(500);
  digitalWrite(LED_BUILTIN, LOW);
  delay(500);
}

void setup() {
  pinMode(LED_BUILTIN, OUTPUT);
}

void loop() {
  blinkLED();
}

This code defines a function to blink the LED, sets the LED pin mode once, then repeatedly calls the blink function to blink the LED.

Execution Table

Step	Function Called	Action	Pin State	Delay(ms)
1	setup	Set LED pin as OUTPUT	LED pin mode=OUTPUT	0
2	loop	Call blinkLED()	LED LOW	0
3	blinkLED	digitalWrite HIGH	LED ON	0
4	blinkLED	delay(500)	LED ON	500
5	blinkLED	digitalWrite LOW	LED OFF	500
6	blinkLED	delay(500)	LED OFF	1000
7	loop	Call blinkLED() again	LED OFF	1000
8	blinkLED	digitalWrite HIGH	LED ON	1000
9	blinkLED	delay(500)	LED ON	1500
10	blinkLED	digitalWrite LOW	LED OFF	1500
11	blinkLED	delay(500)	LED OFF	2000
...	loop continues	...	...	...

💡 Loop runs forever, repeatedly calling blinkLED to blink LED on and off.

Variable Tracker

Variable	Start	After setup	After blinkLED 1	After blinkLED 2	...final
LED_BUILTIN state	LOW	Configured OUTPUT	HIGH then LOW	HIGH then LOW	Repeating HIGH/LOW

Key Moments - 3 Insights

Why do we define blinkLED() before using it in loop()?

Arduino requires functions to be defined before they are called, so the compiler knows what blinkLED() means when loop() calls it (see execution_table step 2).

Does setup() run multiple times?

No, setup() runs only once at the start to initialize things like pin modes (see execution_table step 1). Loop() runs repeatedly.

What happens if we put the blink code directly inside loop() instead of a function?

The code would work the same, but using a function like blinkLED() keeps code organized and easier to read or reuse (see execution_table steps 2-6).

Visual Quiz - 3 Questions

Look at the execution_table, what is the LED pin state right after step 3?

A LED is ON (HIGH)

B LED is OFF (LOW)

C LED pin mode is set

D LED is blinking

💡 Hint

Check step 3 in execution_table where digitalWrite HIGH is called.

At which step does the program first wait for 500 milliseconds?

A Step 2

B Step 4

C Step 5

D Step 6

💡 Hint

Look for delay(500) in execution_table rows.

If we remove the blinkLED() function and put its code directly in loop(), what changes in the execution_table?

A Delay will be removed

B Pin State will never change

C Function Called column will show 'loop' only

D Setup will run multiple times

💡 Hint

Without blinkLED(), loop() contains all code, so only loop() is called.

Concept Snapshot

Functions organize code into reusable blocks.
Define functions before calling them.
setup() runs once; loop() runs repeatedly.
Call functions inside loop() to keep code clean.
Use digitalWrite and delay inside functions for actions.

Full Transcript

This example shows how Arduino code uses functions to organize tasks. First, a function blinkLED() is defined to turn the LED on and off with delays. The setup() function runs once to set the LED pin as output. Then the loop() function runs forever, calling blinkLED() each time to blink the LED. The execution table traces each step: setup configures the pin, loop calls blinkLED, which changes the LED state and waits. Variables track the LED pin state changing from LOW to HIGH and back. Key moments clarify why functions must be defined before use, that setup runs once, and how functions help keep code organized. The quiz checks understanding of LED states, timing, and function calls. This method helps beginners see how code flows and how functions improve readability and reuse.

Practice

1. What is the main purpose of using functions in Arduino programming?

easy

A. To increase the size of the program

B. To organize code into reusable parts

C. To make the program run faster

D. To avoid using variables

Solution

1. Step 1: Understand what functions do

   Functions group code into small blocks that can be used many times.

2. Step 2: Identify the main benefit

   This grouping helps keep code clean and easy to manage.

3. Final Answer:

   To organize code into reusable parts -> Option B

4. Quick Check:

   Functions = reusable code blocks [OK]

Hint: Functions group code for reuse and clarity [OK]

Common Mistakes:

• Thinking functions make code run faster
• Believing functions increase program size
• Confusing functions with variables

2. Which of the following is the correct way to declare a function named blinkLED that takes no parameters and returns nothing in Arduino?

easy

A. void blinkLED() { /* code */ }

B. int blinkLED() { /* code */ }

C. blinkLED void() { /* code */ }

D. function blinkLED() { /* code */ }

Solution

1. Step 1: Recall Arduino function syntax

   Functions start with return type, then name, then parentheses for parameters.

2. Step 2: Match syntax for no return and no parameters

   Use void for no return and empty parentheses for no parameters.

3. Final Answer:

   void blinkLED() { /* code */ } -> Option A

4. Quick Check:

   void + name() = correct function declaration [OK]

Hint: Use 'void' for no return and () for no parameters [OK]

Common Mistakes:

• Using 'function' keyword (not Arduino style)
• Putting return type after function name
• Omitting parentheses

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

void setup() {
  Serial.begin(9600);
  printSum(3, 4);
}

void loop() {}

void printSum(int a, int b) {
  Serial.println(a + b);
}

medium

A. Error: missing return

B. 34

C. 7

D. Nothing

Solution

1. Step 1: Understand function call and parameters

   The function printSum is called with 3 and 4 as inputs.

2. Step 2: Calculate the sum inside the function

   The function adds 3 + 4 = 7 and prints it to Serial Monitor.

3. Final Answer:

   7 -> Option C

4. Quick Check:

   3 + 4 = 7 printed [OK]

Hint: Add parameters inside function and print result [OK]

Common Mistakes:

• Thinking '34' is printed as string concatenation
• Expecting a return value instead of print
• Assuming no output because loop is empty

4. Identify the error in this Arduino code snippet:

void setup() {
  blinkLED();
}

void blinkLED {
  digitalWrite(13, HIGH);
  delay(500);
  digitalWrite(13, LOW);
  delay(500);
}

medium

A. delay function requires a return value

B. Missing semicolon after function call

C. digitalWrite cannot be used inside functions

D. Missing parentheses after function name in declaration

Solution

1. Step 1: Check function declaration syntax

   The function blinkLED is declared without parentheses, which is invalid.

2. Step 2: Confirm correct syntax

   Function declarations must have parentheses even if no parameters: void blinkLED() { ... }.

3. Final Answer:

   Missing parentheses after function name in declaration -> Option D

4. Quick Check:

   Function declaration needs () [OK]

Hint: Always include () after function name in declaration [OK]

Common Mistakes:

• Forgetting parentheses in function declaration
• Adding semicolon after function call (not needed)
• Misunderstanding digitalWrite usage

5. You want to create a function setLED that turns an LED on or off based on a parameter. Which of these function definitions correctly uses a parameter to control the LED state on pin 13?

hard

A. void setLED(int state) { digitalWrite(13, state); }

B. void setLED() { digitalWrite(13, HIGH); }

C. int setLED(int state) { return digitalWrite(13, state); }

D. void setLED(boolean state) { digitalWrite(13, !state); }

Solution

1. Step 1: Understand parameter type for LED state

   LED state is usually HIGH or LOW, which are integers in Arduino.

2. Step 2: Check function that uses parameter correctly

   void setLED(int state) { digitalWrite(13, state); } takes an int parameter and passes it directly to digitalWrite on pin 13.

3. Step 3: Evaluate other options

   B ignores parameter, C wrongly returns digitalWrite result, D inverts boolean state which may confuse usage.

4. Final Answer:

   void setLED(int state) { digitalWrite(13, state); } -> Option A

5. Quick Check:

   Parameter controls LED state directly [OK]

Hint: Use int parameter for HIGH/LOW and pass to digitalWrite [OK]

Common Mistakes:

• Returning digitalWrite result (void function expected)
• Ignoring parameter and hardcoding LED state
• Inverting boolean state unintentionally