Button press detection in Raspberry Pi - Step-by-Step Execution

Concept Flow - Button press detection

Start program

↓

Setup GPIO pin as input

↓

Wait for button press event

↓

Detect button state change

↓

If pressed, execute action

↓

Loop back to wait for next press

↓

Program ends on exit

The program sets up a GPIO pin to read button presses, waits for the button to be pressed, then runs code when pressed, repeating until stopped.

Execution Sample

Raspberry Pi

import RPi.GPIO as GPIO
import time

GPIO.setmode(GPIO.BCM)
GPIO.setup(18, GPIO.IN, pull_up_down=GPIO.PUD_UP)

while True:
    if GPIO.input(18) == GPIO.LOW:
        print("Button pressed!")
        time.sleep(0.3)

This code waits for a button connected to pin 18 to be pressed and prints a message each time.

Execution Table

Step	GPIO Pin 18 State	Condition (GPIO.input(18) == LOW)	Action	Output
1	HIGH (not pressed)	False	Wait
2	HIGH (not pressed)	False	Wait
3	LOW (pressed)	True	Print message	Button pressed!
4	LOW (pressed)	True	Print message	Button pressed!
5	HIGH (released)	False	Wait
6	LOW (pressed)	True	Print message	Button pressed!
7	HIGH (released)	False	Wait
...	...	...	...	...
Exit	Program stopped by user	N/A	Exit loop

💡 Program runs until user stops it manually (e.g., Ctrl+C).

Variable Tracker

Variable	Start	After Step 3	After Step 5	After Step 6	Final
GPIO Pin 18 State	HIGH	LOW	HIGH	LOW	Depends on button
Condition (GPIO.input(18) == LOW)	False	True	False	True	Depends on button

Key Moments - 3 Insights

Why does the program print multiple times when the button is held down?

Because the loop keeps checking the button state and prints each time it sees LOW (pressed), as shown in execution_table rows 3 and 4.

Why do we use pull_up_down=GPIO.PUD_UP in setup?

It sets the pin to HIGH by default so the button press pulls it LOW, making detection reliable, as seen in the initial HIGH state in the execution_table.

What stops the program from running forever?

The program runs in an infinite loop until the user manually stops it, as noted in the exit_note and final execution_table row.

Visual Quiz - 3 Questions

Look at the execution_table, what is the GPIO Pin 18 state at step 5?

A LOW (pressed)

B Floating (undefined)

C HIGH (released)

D Not connected

💡 Hint

Check the 'GPIO Pin 18 State' column at step 5 in the execution_table.

At which step does the condition GPIO.input(18) == LOW become true for the first time?

A Step 1

B Step 3

C Step 2

D Step 5

💡 Hint

Look at the 'Condition' column in the execution_table to find when it first becomes True.

If the button is never pressed, what will the output be?

A No output, program waits

B Button pressed! printed repeatedly

C Error message

D Program crashes

💡 Hint

Refer to the execution_table rows where GPIO Pin 18 state is HIGH and condition is False.

Concept Snapshot

Button press detection on Raspberry Pi:
- Setup GPIO pin as input with pull-up resistor
- Loop: read pin state
- If LOW (button pressed), run action
- Use time.sleep to debounce
- Program runs until stopped manually

Full Transcript

This program sets up a Raspberry Pi GPIO pin 18 as an input with a pull-up resistor. It then enters an infinite loop checking the pin state. When the button connected to pin 18 is pressed, the pin reads LOW, triggering the program to print 'Button pressed!'. The program waits briefly to avoid multiple prints from one press. It continues checking until the user stops it. The execution table shows the pin state and actions step by step, helping beginners see how the program reacts to button presses.

Practice

1. What does setting a Raspberry Pi GPIO pin as input with a pull-up resistor do when detecting a button press?

easy

A. It keeps the pin at HIGH until the button connects it to LOW when pressed.

B. It keeps the pin at LOW until the button connects it to HIGH when pressed.

C. It disables the pin to save power when the button is not pressed.

D. It makes the pin output a signal when the button is pressed.

Solution

1. Step 1: Understand pull-up resistor behavior

   A pull-up resistor keeps the input pin at a HIGH voltage level by default.

2. Step 2: Detect button press effect on pin

   When the button is pressed, it connects the pin to ground, making the input LOW.

3. Final Answer:

   It keeps the pin at HIGH until the button connects it to LOW when pressed. -> Option A

4. Quick Check:

   Pull-up resistor means default HIGH, press pulls LOW [OK]

Hint: Pull-up means default HIGH, press pulls pin LOW [OK]

Common Mistakes:

• Thinking pull-up sets pin LOW by default
• Confusing input with output pin modes
• Assuming button press sets pin HIGH

2. Which of the following is the correct Python code snippet to set GPIO pin 17 as input with a pull-up resistor on Raspberry Pi?

easy

A. GPIO.setup(17, GPIO.IN, pull_up_down=GPIO.PUD_UP)

B. GPIO.setup(17, GPIO.OUT, pull_up_down=GPIO.PUD_UP)

C. GPIO.setup(17, GPIO.IN)

D. GPIO.setup(17, GPIO.OUT)

Solution

1. Step 1: Identify pin mode for button input

   Button pins must be set as input to read their state.

2. Step 2: Add pull-up resistor parameter

   Use pull_up_down=GPIO.PUD_UP to enable internal pull-up resistor.

3. Final Answer:

   GPIO.setup(17, GPIO.IN, pull_up_down=GPIO.PUD_UP) -> Option A

4. Quick Check:

   Input pin with pull-up resistor = GPIO.IN + PUD_UP [OK]

Hint: Input pin with pull-up uses GPIO.IN and PUD_UP [OK]

Common Mistakes:

• Using GPIO.OUT instead of GPIO.IN
• Omitting pull_up_down parameter
• Setting pull-up resistor on output pin

3. What will be the output of this Python code snippet when the button connected to GPIO 18 is pressed?

import RPi.GPIO as GPIO
import time

GPIO.setmode(GPIO.BCM)
GPIO.setup(18, GPIO.IN, pull_up_down=GPIO.PUD_UP)

if GPIO.input(18) == GPIO.LOW:
    print("Button Pressed")
else:
    print("Button Not Pressed")

medium

A. No output

B. Button Not Pressed

C. SyntaxError

D. Button Pressed

Solution

1. Step 1: Understand pin setup and input reading

   Pin 18 is set as input with pull-up resistor, so default is HIGH.

2. Step 2: Check condition when button is pressed

   Pressing button pulls pin LOW, so condition GPIO.input(18) == GPIO.LOW is True.

3. Final Answer:

   Button Pressed -> Option D

4. Quick Check:

   Pressed button pulls pin LOW, prints "Button Pressed" [OK]

Hint: Pressed button reads LOW on pull-up input pin [OK]

Common Mistakes:

• Assuming pressed button reads HIGH
• Confusing pull-up with pull-down resistor
• Expecting syntax or runtime errors

4. Identify the error in this Raspberry Pi button press detection code:

import RPi.GPIO as GPIO
import time

GPIO.setmode(GPIO.BCM)
GPIO.setup(23, GPIO.IN, pull_up_down=GPIO.PUD_UP)

while True:
    if GPIO.input(23) == GPIO.HIGH:
        print("Button Pressed")
    time.sleep(0.1)

medium

A. time.sleep(0.1) should be before the if statement.

B. The pull_up_down parameter is missing in GPIO.setup.

C. The code should check for GPIO.LOW to detect button press.

D. GPIO.setmode(GPIO.BCM) is incorrect and should be GPIO.BOARD.

Solution

1. Step 1: Review button wiring and logic

   With pull-up resistor, button press pulls pin LOW, not HIGH.

2. Step 2: Check condition in if statement

   Code incorrectly checks for GPIO.HIGH to detect press; should check GPIO.LOW.

3. Final Answer:

   The code should check for GPIO.LOW to detect button press. -> Option C

4. Quick Check:

   Pull-up input reads LOW when pressed, so check GPIO.LOW [OK]

Hint: Pressed button reads LOW on pull-up input pin [OK]

Common Mistakes:

• Checking for HIGH instead of LOW on button press
• Forgetting pull_up_down parameter
• Misplacing sleep causing missed presses

5. You want to detect a button press on GPIO 21 and print "Pressed" only once per press, avoiding multiple prints while the button is held down. Which code snippet correctly implements this behavior?

import RPi.GPIO as GPIO
import time

GPIO.setmode(GPIO.BCM)
GPIO.setup(21, GPIO.IN, pull_up_down=GPIO.PUD_UP)

pressed = False
while True:
    if GPIO.input(21) == GPIO.LOW and not pressed:
        print("Pressed")
        pressed = True
    elif GPIO.input(21) == GPIO.HIGH:
        pressed = False
    time.sleep(0.05)

hard

A. This code never prints anything because pressed is always True.

B. This code prints "Pressed" once per press and avoids repeats while held.

C. This code prints "Pressed" continuously while button is held down.

D. This code causes a syntax error due to missing colon.

Solution

1. Step 1: Understand the pressed flag usage

   The variable 'pressed' tracks if the button press was already detected to avoid repeats.

2. Step 2: Analyze the if-elif logic

   When button is LOW and not pressed, it prints once and sets pressed True; when released (HIGH), resets pressed to False.

3. Final Answer:

   This code prints "Pressed" once per press and avoids repeats while held. -> Option B

4. Quick Check:

   pressed flag prevents multiple prints during hold [OK]

Hint: Use a flag variable to print once per press [OK]

Common Mistakes:

• Printing inside loop without flag causes repeated prints
• Not resetting flag on button release
• Syntax errors from missing colons or indentation