LED class and methods in Raspberry Pi - Step-by-Step Execution

Concept Flow - LED class and methods

Create LED object

↓

Call turn_on() method

↓

LED state set to ON

↓

Call turn_off() method

↓

LED state set to OFF

↓

Call toggle() method

↓

LED state switched ON/OFF

↓

End

This flow shows creating an LED object and using its methods to turn it on, off, or toggle its state.

Execution Sample

Raspberry Pi

class LED:
    def __init__(self):
        self.state = False
    def turn_on(self):
        self.state = True
    def turn_off(self):
        self.state = False
    def toggle(self):
        self.state = not self.state

This code defines an LED class with methods to turn it on, off, and toggle its state.

Execution Table

Step	Action	Method Called	LED State Before	LED State After
1	Create LED object	N/A	N/A	False (OFF)
2	Turn LED on	turn_on()	False (OFF)	True (ON)
3	Turn LED off	turn_off()	True (ON)	False (OFF)
4	Toggle LED	toggle()	False (OFF)	True (ON)
5	Toggle LED again	toggle()	True (ON)	False (OFF)

💡 All method calls completed, LED state updated accordingly.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5
led.state	N/A	False	True	False	True	False

Key Moments - 3 Insights

Why does the LED state change from False to True after calling turn_on()?

Because the turn_on() method sets the led.state variable to True, as shown in execution_table step 2.

What happens when toggle() is called if the LED is currently ON?

The toggle() method switches the state from True to False by using 'not self.state', as seen in execution_table step 5.

Why is the initial LED state False when the object is created?

The __init__ method sets self.state to False, meaning the LED starts OFF, shown in execution_table step 1.

Visual Quiz - 3 Questions

Look at the execution_table, what is led.state after step 3?

A False (OFF)

B True (ON)

C None

D Error

💡 Hint

Check the 'LED State After' column for step 3 in the execution_table.

At which step does the LED state first become True (ON)?

A Step 3

B Step 1

C Step 2

D Step 4

💡 Hint

Look at the 'LED State After' column to find when the state changes to True.

If we call toggle() twice starting from OFF, what will be the final state?

A True (ON)

B False (OFF)

C Error

D Undefined

💡 Hint

Refer to steps 4 and 5 in the execution_table where toggle() is called twice.

Concept Snapshot

LED class basics:
- __init__ sets initial state (False = OFF)
- turn_on() sets state to True (ON)
- turn_off() sets state to False (OFF)
- toggle() switches state True<->False
Use methods to control LED state simply.

Full Transcript

We start by creating an LED object, which sets its state to OFF (False). Calling turn_on() changes the state to ON (True). Calling turn_off() sets it back to OFF. The toggle() method flips the state from ON to OFF or OFF to ON. Each method updates the led.state variable accordingly. This simple class helps control an LED's on/off state with clear methods.

Practice

1.

What does the on() method of an LED class typically do in Raspberry Pi programming?

easy

A. Turns the LED light on

B. Turns the LED light off

C. Makes the LED blink continuously

D. Cleans up the GPIO pins

Solution

1. Step 1: Understand the purpose of on() method

   The on() method is designed to switch the LED light to the ON state.

2. Step 2: Compare with other methods

   Other methods like off() turn the LED off, and blink() makes it blink. Cleanup is done separately.

3. Final Answer:

   Turns the LED light on -> Option A

4. Quick Check:

   on() means LED ON [OK]

Hint: Remember: on() means light ON, off() means light OFF [OK]

Common Mistakes:

• Confusing on() with off()
• Thinking on() cleans GPIO pins
• Assuming on() makes LED blink

2.

Which of the following is the correct way to create an LED object on GPIO pin 17 using the gpiozero library?

from gpiozero import LED

led = ?

easy

A. LED(17)

B. LED.pin(17)

C. LED[17]

D. LED{17}

Solution

1. Step 1: Recall LED object creation syntax

   In gpiozero, you create an LED by calling LED(pin_number), e.g., LED(17).

2. Step 2: Check other options for syntax errors

   Options A, B, and D use invalid Python syntax for object creation.

3. Final Answer:

   LED(17) -> Option A

4. Quick Check:

   LED(pin) = LED(17) [OK]

Hint: Use parentheses with pin number: LED(17) [OK]

Common Mistakes:

• Using square brackets instead of parentheses
• Trying to call a method like LED.pin()
• Using curly braces which are invalid here

3.

What will be the output of this code snippet controlling an LED?

from gpiozero import LED
from time import sleep

led = LED(22)
led.on()
sleep(1)
led.off()
print('LED state:', led.is_lit)

medium

A. SyntaxError

B. LED state: True

C. LED state: None

D. LED state: False

Solution

1. Step 1: Trace the LED state changes

   The LED is turned on, then after 1 second turned off before printing.

2. Step 2: Check the printed LED state

   After led.off(), led.is_lit is False, so output is 'LED state: False'.

3. Final Answer:

   LED state: False -> Option D

4. Quick Check:

   LED off means is_lit = False [OK]

Hint: Check final LED state after all commands run [OK]

Common Mistakes:

• Assuming LED stays on after off()
• Confusing is_lit property value
• Expecting syntax error due to sleep

4.

Identify the error in this code that tries to blink an LED on pin 5:

from gpiozero import LED
from time import sleep

led = LED(5)
led.blink(on_time=0.5, off_time=0.5)
sleep(2)
led.off()

medium

A. Missing led.on() before blink

B. Should call led.close() to clean GPIO

C. No error; code works correctly

D. blink() method requires a times argument

Solution

1. Step 1: Review the code for GPIO cleanup

   The code blinks the LED and turns it off but does not release GPIO resources.

2. Step 2: Identify missing cleanup step

   Proper practice is to call led.close() to free GPIO pins after use.

3. Final Answer:

   Should call led.close() to clean GPIO -> Option B

4. Quick Check:

   Always close GPIO pins after use [OK]

Hint: Always close() LEDs to free GPIO pins [OK]

Common Mistakes:

• Thinking blink() needs on() first
• Assuming blink() requires times argument
• Ignoring GPIO cleanup after program

5.

You want to create a program that blinks two LEDs on pins 17 and 27 alternately every 0.5 seconds for 5 seconds total. Which code snippet correctly implements this using the LED class?

from gpiozero import LED
from time import sleep

led1 = LED(17)
led2 = LED(27)

start = 0
while start < 5:
    led1.on()
    led2.off()
    sleep(0.5)
    led1.off()
    led2.on()
    sleep(0.5)
    start += 1

led1.off()
led2.off()
led1.close()
led2.close()

hard

A. Should use blink() method instead of manual on/off

B. The loop runs too long; should use start < 10

C. This code blinks LEDs alternately for 5 seconds correctly

D. Missing sleep between led1.off() and led2.on()

Solution

1. Step 1: Analyze the loop timing and LED control

   The loop runs 5 times, each iteration takes 1 second (two 0.5s sleeps), total 5 seconds blinking alternately.

2. Step 2: Check LED on/off sequence and cleanup

   LED1 and LED2 turn on/off alternately with proper sleep delays, and GPIO pins are closed at the end.

3. Final Answer:

   This code blinks LEDs alternately for 5 seconds correctly -> Option C

4. Quick Check:

   Loop count x sleep = total blink time [OK]

Hint: Count loop x sleep to verify total blink time [OK]

Common Mistakes:

• Miscounting total blink duration
• Forgetting to close GPIO pins
• Assuming blink() method is mandatory