Why PWM is needed for analog-like control in Raspberry Pi - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start PWM on pin 18 with a frequency of 1000 Hz.

Raspberry Pi

import RPi.GPIO as GPIO
GPIO.setmode(GPIO.BCM)
GPIO.setup(18, GPIO.OUT)
pwm = GPIO.PWM(18, [1])
pwm.start(0)

Drag options to blanks, or click blank then click option'

A50

B500

C1000

D2000

Attempts:

3 left

💡 Hint

Common Mistakes

Using too low or too high frequency causing flickering or no effect.

The frequency for PWM is set to 1000 Hz to control the output signal speed.

2fill in blank

medium

Complete the code to set the duty cycle to 75%, which controls the analog-like output level.

Raspberry Pi

pwm.ChangeDutyCycle([1])

Drag options to blanks, or click blank then click option'

A25

B75

C50

D100

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing duty cycle with frequency or using values outside 0-100.

The duty cycle of 75% means the signal is ON 75% of the time, simulating an analog output.

3fill in blank

hard

Fix the error in the code to properly stop PWM and clean up GPIO.

Raspberry Pi

pwm.[1]()
GPIO.cleanup()

Drag options to blanks, or click blank then click option'

Astop

Bclose

Cend

Dterminate

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-existent methods like close() or end() causing runtime errors.

The correct method to stop PWM is stop(). This stops the PWM signal before cleaning up GPIO.

4fill in blank

hard

Fill both blanks to create a dictionary comprehension that maps each brightness level to its duty cycle if the level is greater than 50.

Raspberry Pi

brightness_levels = [30, 60, 90]
duty_cycles = {level: [1] for level in brightness_levels if level [2] 50}

Drag options to blanks, or click blank then click option'

Alevel

B>

C<

Dlevel * 2

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong comparison operators or incorrect value expressions.

The dictionary comprehension uses the level as the duty cycle and filters levels greater than 50.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that maps the uppercase level name to its duty cycle if the duty cycle is less than 80.

Raspberry Pi

levels = {'low': 30, 'medium': 60, 'high': 90}
filtered = { [1]: [2] for [3] in levels.items() if [2] < 80 }

Drag options to blanks, or click blank then click option'

Alevel.upper()

Bduty

Clevel, duty

Dlevels

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong variable names or forgetting to unpack items.

The comprehension maps uppercase level names to duty cycles, filtering duty cycles less than 80.

Practice

1. Why do we use PWM (Pulse Width Modulation) on a Raspberry Pi to control devices like LEDs instead of just turning them fully on or off?

easy

A. Because PWM is the only way to turn devices on.

B. Because PWM makes the Raspberry Pi run faster.

C. Because PWM simulates different power levels by switching on and off quickly, making devices appear dimmer or brighter.

D. Because PWM uses less electricity than turning devices fully on.

Solution

1. Step 1: Understand what PWM does

   PWM switches power on and off very fast to create the effect of different power levels.

2. Step 2: Compare PWM to simple on/off

   Simple on/off only gives full power or no power, so devices can't appear dim or partially powered.

3. Final Answer:

   Because PWM simulates different power levels by switching on and off quickly, making devices appear dimmer or brighter. -> Option C

4. Quick Check:

   PWM simulates analog power = Because PWM simulates different power levels by switching on and off quickly, making devices appear dimmer or brighter. [OK]

Hint: PWM controls brightness by fast on/off switching [OK]

Common Mistakes:

• Thinking PWM makes the Pi run faster
• Believing PWM is only for turning devices fully on
• Assuming PWM always saves electricity

2. Which of the following is the correct way to start PWM on a Raspberry Pi GPIO pin using the RPi.GPIO library?

easy

A. pwm = GPIO.PWM(pin, frequency); pwm.start(duty_cycle)

B. pwm = GPIO.startPWM(pin, duty_cycle); pwm.setFrequency(frequency)

C. pwm = GPIO.PWMStart(pin, frequency, duty_cycle)

D. pwm = GPIO.beginPWM(pin); pwm.setDutyCycle(frequency)

Solution

1. Step 1: Recall RPi.GPIO PWM syntax

   The correct syntax is to create a PWM object with GPIO.PWM(pin, frequency) and then start it with pwm.start(duty_cycle).

2. Step 2: Check each option's method names

   Only pwm = GPIO.PWM(pin, frequency); pwm.start(duty_cycle) uses the correct method names and order as per RPi.GPIO documentation.

3. Final Answer:

   pwm = GPIO.PWM(pin, frequency); pwm.start(duty_cycle) -> Option A

4. Quick Check:

   RPi.GPIO PWM start = pwm = GPIO.PWM(pin, frequency); pwm.start(duty_cycle) [OK]

Hint: Remember: PWM(pin, freq) then start(duty) [OK]

Common Mistakes:

• Using incorrect method names like startPWM or beginPWM
• Mixing frequency and duty cycle in wrong order
• Trying to set frequency after starting PWM

3. What will be the visible effect on an LED connected to a Raspberry Pi GPIO pin if PWM is set with a frequency of 100 Hz and a duty cycle of 25%?

medium

A. The LED will be dim, about one quarter brightness.

B. The LED will be fully bright.

C. The LED will blink slowly once every second.

D. The LED will be fully off.

Solution

1. Step 1: Understand duty cycle meaning

   A 25% duty cycle means the LED is on 25% of the time and off 75% of the time in each cycle.

2. Step 2: Relate duty cycle to brightness

   Because the LED is on only a quarter of the time, it appears dimmer, roughly 25% brightness.

3. Final Answer:

   The LED will be dim, about one quarter brightness. -> Option A

4. Quick Check:

   25% duty cycle = dim LED = The LED will be dim, about one quarter brightness. [OK]

Hint: Duty cycle % roughly equals LED brightness % [OK]

Common Mistakes:

• Thinking LED will be fully off at 25% duty cycle
• Assuming LED blinks slowly instead of fast
• Confusing frequency with brightness

4. You wrote this code to control an LED brightness with PWM on Raspberry Pi but the LED stays fully on:

import RPi.GPIO as GPIO
GPIO.setmode(GPIO.BCM)
pin = 18
GPIO.setup(pin, GPIO.OUT)
pwm = GPIO.PWM(pin, 100)
pwm.start(100)

What is the likely mistake?

medium

A. The pin number 18 is invalid for PWM.

B. The frequency 100 is too low for PWM to work.

C. You forgot to call GPIO.cleanup() before starting PWM.

D. The duty cycle is set to 100%, so the LED is always fully on.

Solution

1. Step 1: Check the duty cycle value

   The code uses pwm.start(100), which means 100% duty cycle (always on).

2. Step 2: Understand effect of 100% duty cycle

   At 100% duty cycle, the LED receives full power constantly, so it stays fully on.

3. Final Answer:

   The duty cycle is set to 100%, so the LED is always fully on. -> Option D

4. Quick Check:

   100% duty cycle = LED fully on = The duty cycle is set to 100%, so the LED is always fully on. [OK]

Hint: 100% duty cycle means always on [OK]

Common Mistakes:

• Thinking frequency 100 is too low to work
• Believing GPIO.cleanup() is needed before PWM start
• Assuming pin 18 can't do PWM

5. You want to control a motor speed smoothly using PWM on Raspberry Pi. The motor needs a voltage between 0V (off) and 5V (full speed). Which PWM setup will best simulate this analog voltage control?

hard

A. Use a low frequency (e.g., 1 Hz) PWM with fixed 50% duty cycle.

B. Use a high frequency (e.g., 1 kHz) PWM with varying duty cycle from 0% to 100%.

C. Use a high frequency PWM with fixed 100% duty cycle.

D. Use a low frequency PWM with duty cycle always 0%.

Solution

1. Step 1: Understand motor voltage control with PWM

   Varying the duty cycle changes the average voltage the motor receives, controlling speed smoothly.

2. Step 2: Choose frequency and duty cycle range

   High frequency PWM (like 1 kHz) avoids motor jerks and noise; duty cycle must vary from 0% (off) to 100% (full speed).

3. Final Answer:

   Use a high frequency (e.g., 1 kHz) PWM with varying duty cycle from 0% to 100%. -> Option B

4. Quick Check:

   High freq + variable duty = smooth motor speed [OK]

Hint: High freq PWM + variable duty = smooth analog control [OK]

Common Mistakes:

• Using low frequency causes jerky motor movement
• Fixing duty cycle prevents speed control
• Using 0% or 100% duty cycle only gives off or full speed