Digital input (GPIO.input) in Raspberry Pi - Step-by-Step Execution

Concept Flow - Digital input (GPIO.input)

Setup GPIO pin as input

↓

Read pin state with GPIO.input

↓

Check if pin is HIGH or LOW

↓

Use pin state in program

↓

Repeat or Exit

This flow shows how to set a pin as input, read its digital state, and use that value in your program.

Execution Sample

Raspberry Pi

import RPi.GPIO as GPIO
GPIO.setmode(GPIO.BCM)
GPIO.setup(17, GPIO.IN)
state = GPIO.input(17)
print(state)

This code sets GPIO pin 17 as input, reads its digital state (0 or 1), and prints it.

Execution Table

Step	Action	Pin 17 Mode	GPIO.input(17) Result	Output
1	Set GPIO mode to BCM	Not set yet	N/A	No output
2	Setup pin 17 as input	Input	N/A	No output
3	Read pin 17 state	Input	0 (LOW) or 1 (HIGH)	No output yet
4	Print state	Input	0 or 1	Prints 0 or 1 to console

💡 Program ends after printing the pin state.

Variable Tracker

Variable	Start	After GPIO.setup	After GPIO.input	Final
state	Undefined	Undefined	0 or 1	0 or 1

Key Moments - 3 Insights

Why do we need to set the pin mode before reading it?

GPIO pins must be set as input or output first; otherwise, GPIO.input won't know how to read the pin. See execution_table step 2 where pin mode changes to input.

What does GPIO.input(17) return?

It returns 0 if the pin voltage is LOW (off) or 1 if HIGH (on). This is shown in execution_table step 3.

Can GPIO.input return values other than 0 or 1?

No, GPIO.input only returns digital states: 0 (LOW) or 1 (HIGH), never other numbers.

Visual Quiz - 3 Questions

Look at the execution_table, what is the pin mode after step 2?

A Output

B Not set

C Input

D Analog

💡 Hint

Check the 'Pin 17 Mode' column in execution_table row for step 2.

At which step does GPIO.input(17) return the pin state?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at the 'GPIO.input(17) Result' column in execution_table.

If the pin is connected to 3.3V, what will GPIO.input(17) return?

A 1

B 0

C -1

D It depends on the pin mode

💡 Hint

GPIO.input returns 1 for HIGH voltage, see key_moments about return values.

Concept Snapshot

GPIO.input reads the digital state of a pin.
1. Set pin mode to input with GPIO.setup(pin, GPIO.IN).
2. Call GPIO.input(pin) to get 0 (LOW) or 1 (HIGH).
3. Use the returned value in your program.
Always set mode before reading.
Returns only 0 or 1.

Full Transcript

This lesson shows how to read a digital input from a Raspberry Pi GPIO pin. First, you set the pin mode to input using GPIO.setup. Then, you read the pin state with GPIO.input, which returns 0 if the pin is LOW or 1 if it is HIGH. Finally, you can use this value in your program, for example, printing it. The execution table traces these steps, showing the pin mode changes and the input reading. Key points include the need to set the pin mode before reading and that GPIO.input only returns 0 or 1. The visual quiz tests understanding of these steps and values.

Practice

1. What does GPIO.input(pin) do in Raspberry Pi programming?

easy

A. Resets the pin to default state

B. Sets the pin mode to output

C. Writes a value to the pin

D. Reads the current digital state (True/False) of the specified pin

Solution

1. Step 1: Understand GPIO.input function

   GPIO.input(pin) reads the current digital signal on the given pin, returning True if the pin is HIGH and False if LOW.

2. Step 2: Differentiate from other GPIO functions

   Functions like GPIO.setup set pin modes, and GPIO.output writes values. Only GPIO.input reads the pin state.

3. Final Answer:

   Reads the current digital state (True/False) of the specified pin -> Option D

4. Quick Check:

   GPIO.input reads pin state = A [OK]

Hint: Remember: input reads pin state, output writes to pin [OK]

Common Mistakes:

• Confusing GPIO.input with GPIO.output
• Thinking GPIO.input sets pin mode
• Assuming GPIO.input writes values

2. Which of the following is the correct way to set up GPIO pin 17 as an input pin?

easy

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

B. GPIO.input(17, GPIO.IN)

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

D. GPIO.input(17)

Solution

1. Step 1: Identify the correct function to set pin mode

   Use GPIO.setup(pin, mode) to set pin mode. Here, mode should be GPIO.IN for input.

2. Step 2: Check each option

   GPIO.setup(17, GPIO.OUT) sets pin as output, wrong mode. GPIO.input(17, GPIO.IN) uses GPIO.input incorrectly with two arguments. GPIO.input(17) calls GPIO.input without setup. Only GPIO.setup(17, GPIO.IN) correctly sets pin 17 as input.

3. Final Answer:

   GPIO.setup(17, GPIO.IN) -> Option C

4. Quick Check:

   Setup input pin = B [OK]

Hint: Use GPIO.setup(pin, GPIO.IN) to prepare input pins [OK]

Common Mistakes:

• Using GPIO.input to set pin mode
• Setting pin as output instead of input
• Calling GPIO.input before setup

3. What will be the output of this code snippet if the button connected to pin 22 is pressed (assuming pressed means HIGH)?

import RPi.GPIO as GPIO
GPIO.setmode(GPIO.BCM)
GPIO.setup(22, GPIO.IN)
state = GPIO.input(22)
print(state)

medium

A. True

B. 22

C. False

D. Error

Solution

1. Step 1: Understand pin setup and input reading

   Pin 22 is set as input. When the button is pressed, the pin reads HIGH, so GPIO.input(22) returns True.

2. Step 2: Check the print output

   The variable state holds True, so print(state) outputs True.

3. Final Answer:

   True -> Option A

4. Quick Check:

   Pressed button = True output [OK]

Hint: Pressed button means pin HIGH, so GPIO.input returns True [OK]

Common Mistakes:

• Assuming pressed means False
• Confusing pin number with state
• Expecting numeric output instead of boolean

4. Identify the error in this code snippet:

import RPi.GPIO as GPIO
GPIO.setmode(GPIO.BCM)
GPIO.input(18)
GPIO.setup(18, GPIO.IN)

medium

A. GPIO.input called before GPIO.setup

B. GPIO.setup uses wrong pin number

C. GPIO.setmode is missing

D. No error, code is correct

Solution

1. Step 1: Check order of GPIO calls

   GPIO pins must be set up before reading input. Here, GPIO.input(18) is called before GPIO.setup(18, GPIO.IN), which is incorrect.

2. Step 2: Verify other parts

   Pin number 18 is consistent, and GPIO.setmode(GPIO.BCM) is present. So no error there.

3. Final Answer:

   GPIO.input called before GPIO.setup -> Option A

4. Quick Check:

   GPIO.input called before GPIO.setup = D [OK]

Hint: Always setup pins before reading input [OK]

Common Mistakes:

• Calling GPIO.input before GPIO.setup
• Ignoring pin mode setup
• Assuming code runs without setup

5. You want to detect if a motion sensor connected to pin 27 is active (HIGH) and print "Motion detected" only once when it changes from LOW to HIGH. Which code snippet correctly implements this behavior?

hard

A. GPIO.setup(27, GPIO.OUT)
while True:
if GPIO.input(27):
print("Motion detected")

B. GPIO.setup(27, GPIO.IN)
prev_state = False
while True:
current_state = GPIO.input(27)
if current_state and not prev_state:
print("Motion detected")
prev_state = current_state

C. GPIO.setup(27, GPIO.IN)
while True:
if GPIO.input(27):
print("Motion detected")

D. GPIO.setup(27, GPIO.IN)
prev_state = True
while True:
current_state = GPIO.input(27)
if current_state and not prev_state:
print("Motion detected")
prev_state = current_state

Solution

1. Step 1: Setup pin as input and track previous state

   Pin 27 must be set as input. To detect change from LOW to HIGH, store previous state starting as False (LOW).

2. Step 2: Detect rising edge and print once

   Inside the loop, read current state. If current is True and previous is False, print message once. Then update previous state.

3. Step 3: Analyze options

   GPIO.setup(27, GPIO.IN) prev_state = False while True: current_state = GPIO.input(27) if current_state and not prev_state: print("Motion detected") prev_state = current_state correctly implements this logic. GPIO.setup(27, GPIO.OUT) while True: if GPIO.input(27): print("Motion detected") sets pin as output, wrong. GPIO.setup(27, GPIO.IN) while True: if GPIO.input(27): print("Motion detected") prints repeatedly while HIGH, not once. GPIO.setup(27, GPIO.IN) prev_state = True while True: current_state = GPIO.input(27) if current_state and not prev_state: print("Motion detected") prev_state = current_state starts prev_state as True, so first detection missed.

4. Final Answer:

   GPIO.setup(27, GPIO.IN), prev_state = False (rising edge detection) -> Option B

5. Quick Check:

   Detect rising edge with prev_state = False first [OK]

Hint: Track previous state to detect change from LOW to HIGH [OK]

Common Mistakes:

• Setting pin as output instead of input
• Printing repeatedly instead of once
• Initializing previous state incorrectly