PWM frequency and duty cycle relationship in Raspberry Pi - Deep Dive

Overview - PWM frequency and duty cycle relationship

What is it?

PWM stands for Pulse Width Modulation. It is a way to control power by turning a signal on and off very fast. The frequency is how fast the signal repeats each second, and the duty cycle is how long the signal stays on during each cycle. Together, they control how much power a device receives.

Why it matters

PWM lets us control things like motor speed, LED brightness, or sound volume without changing voltage. Without understanding frequency and duty cycle, devices might behave unpredictably or inefficiently. For example, a motor might jerk or an LED might flicker if PWM is not set right.

Where it fits

Before learning PWM frequency and duty cycle, you should know basic electronics concepts like voltage and current, and how digital signals work. After this, you can learn how to program PWM on Raspberry Pi using libraries and how to apply it in real projects like robotics or lighting control.

Mental Model

Core Idea

PWM controls power by switching a signal on and off rapidly, where frequency sets how fast it repeats and duty cycle sets how long it stays on each time.

Think of it like...

Imagine a faucet that you turn on and off very quickly. Frequency is how many times you open and close the faucet each second, and duty cycle is how long the faucet stays open each time. More open time means more water flows.

┌───────────────┐
│ PWM Signal    │
├───────────────┤
│ Frequency:    │───┐  (cycles per second)
│ Duty Cycle:   │   │  (on-time percentage)
└───────────────┘   │
                    ▼
 ┌─────┐     ┌─────┐     ┌─────┐
 │ ON  │ OFF │ ON  │ OFF │ ON  │ ...
 └─────┘     └─────┘     └─────┘
  ↑           ↑           ↑
  |           |           |
 On-time    Off-time    On-time
 (Duty)    (Rest of     (Duty)
           cycle)

Build-Up - 7 Steps

1

Foundation

What is PWM and its basics

Concept: Introduce PWM as a method to control power by switching signals on and off.

PWM means turning a signal on and off very fast. The signal repeats many times per second. The two main parts are frequency (how fast it repeats) and duty cycle (how long it stays on each time). For example, if the signal is on half the time and off half the time, the duty cycle is 50%.

Result

You understand PWM as a fast on/off signal with two key parts: frequency and duty cycle.

Understanding PWM basics is essential because it is the foundation for controlling devices without changing voltage.

2

Foundation

Understanding frequency in PWM

Concept: Frequency is how many times the PWM signal repeats in one second.

Frequency is measured in Hertz (Hz). For example, 100 Hz means the signal repeats 100 times every second. Higher frequency means the signal switches faster. If frequency is too low, devices may notice the switching and behave oddly.

Result

You can explain frequency as the speed of PWM cycles per second.

Knowing frequency helps you choose how fast to switch signals so devices respond smoothly.

3

Intermediate

Understanding duty cycle in PWM

Concept: Duty cycle is the percentage of time the signal stays ON during one cycle.

If one cycle lasts 10 milliseconds, and the signal is ON for 3 milliseconds, the duty cycle is 30%. Duty cycle controls how much power the device gets. 0% means always off, 100% means always on.

Result

You can calculate and explain duty cycle as the ON time percentage in each cycle.

Duty cycle directly controls power output, so adjusting it changes device behavior like brightness or speed.

4

Intermediate

How frequency and duty cycle interact

🤔Before reading on: Do you think changing frequency affects duty cycle or power delivered? Commit to your answer.

Concept: Frequency and duty cycle are separate but together define the PWM signal shape and power delivery.

Changing frequency changes how fast the signal repeats but does not change the duty cycle percentage. Changing duty cycle changes how long the signal stays ON in each cycle, affecting power. Both must be chosen carefully for smooth device operation.

Result

You understand that frequency controls speed of switching, duty cycle controls power level, and they work together.

Knowing their separate roles prevents confusion and helps you tune PWM signals for specific devices.

5

Intermediate

Effects of frequency on device behavior

🤔Before reading on: Does increasing PWM frequency always improve device performance? Commit to your answer.

Concept: Frequency affects how devices perceive PWM signals and can cause flicker or noise if set wrong.

Low frequency PWM can cause visible flicker in LEDs or jerky motor movement. High frequency PWM can reduce flicker but may cause more heat or require more processing power. Different devices have ideal frequency ranges.

Result

You learn how frequency choice impacts real device behavior and performance.

Understanding frequency effects helps avoid common problems like flicker or noise in PWM-controlled devices.

6

Advanced

Trade-offs in frequency and duty cycle settings

🤔Before reading on: Is it better to always use the highest frequency possible for PWM? Commit to your answer.

Concept: Choosing frequency and duty cycle involves balancing device needs, power efficiency, and hardware limits.

Higher frequency reduces flicker but increases power loss and CPU load. Lower frequency saves power but may cause flicker. Duty cycle must be precise to control power accurately. Raspberry Pi PWM hardware and software have limits on frequency and resolution.

Result

You understand the practical trade-offs and constraints when setting PWM parameters.

Knowing these trade-offs helps you design efficient and reliable PWM control in real projects.

7

Expert

PWM resolution and its impact on control

🤔Before reading on: Does increasing PWM frequency always improve control precision? Commit to your answer.

Concept: PWM resolution is how finely you can adjust duty cycle, which depends on frequency and timer bits.

Higher frequency reduces the time per cycle, limiting how many duty cycle steps fit in one cycle. This lowers resolution and makes fine control harder. Lower frequency allows more precise duty cycle steps but may cause flicker. Raspberry Pi PWM uses hardware timers with fixed bit depth, so frequency and resolution trade off.

Result

You grasp how frequency affects PWM resolution and control precision.

Understanding resolution trade-offs prevents common mistakes in PWM tuning and improves device control quality.

Under the Hood

PWM works by using a timer that counts up to a set value repeatedly. The timer resets each cycle, creating a frequency. A compare value sets when the output switches from ON to OFF within each cycle, defining the duty cycle. The Raspberry Pi hardware PWM uses dedicated timers and registers to generate these signals precisely without CPU overhead.

Why designed this way?

PWM was designed to efficiently control power using digital signals instead of analog voltage changes. Using timers and compare registers allows precise, repeatable signals with minimal CPU use. This design balances hardware complexity and flexibility, enabling many devices to use PWM for control.

┌───────────────┐
│ Timer Counter │
│ 0 → Max Count │
└──────┬────────┘
       │
       ▼
┌───────────────┐      ┌───────────────┐
│ Compare Value │─────▶│ Output Signal │
│ (Duty Cycle)  │      │ ON when timer < compare
└───────────────┘      │ OFF otherwise
                       └───────────────┘

Myth Busters - 4 Common Misconceptions

Quick: Does changing PWM frequency change the power delivered if duty cycle stays the same? Commit yes or no.

Common Belief: Changing frequency changes the power delivered to the device.

Reality: Power delivered depends on duty cycle, not frequency. Frequency only changes how fast the signal repeats.

Why it matters: Confusing frequency with power can lead to wrong PWM settings, causing devices to behave unexpectedly.

Quick: Is a 100% duty cycle PWM signal the same as a constant ON signal? Commit yes or no.

Common Belief: 100% duty cycle PWM is different from a constant ON signal.

Reality: 100% duty cycle means the signal is always ON, identical to a constant ON signal.

Why it matters: Misunderstanding this can cause unnecessary complexity or confusion in circuit design.

Quick: Does increasing PWM frequency always improve LED brightness control? Commit yes or no.

Common Belief: Higher PWM frequency always improves LED brightness control.

Reality: Higher frequency reduces flicker but can reduce resolution, making fine brightness control harder.

Why it matters: Ignoring resolution trade-offs can cause poor brightness steps or wasted processing power.

Quick: Can Raspberry Pi software PWM achieve the same precision as hardware PWM? Commit yes or no.

Common Belief: Software PWM on Raspberry Pi is as precise and efficient as hardware PWM.

Reality: Software PWM is less precise and uses more CPU, causing jitter and timing issues compared to hardware PWM.

Why it matters: Using software PWM for critical timing can cause unstable device behavior.

Expert Zone

1

PWM frequency and duty cycle are independent parameters but must be balanced to optimize resolution and device response.

2

Hardware PWM on Raspberry Pi uses fixed timer bit widths, so increasing frequency reduces duty cycle resolution.

3

Some devices have minimum frequency requirements to avoid audible noise or flicker, which constrains PWM settings.

When NOT to use

PWM is not suitable for controlling devices that require true analog voltage or current levels. In such cases, use DACs (Digital to Analog Converters) or linear regulators instead.

Production Patterns

In real projects, engineers use hardware PWM channels for stable signals and software PWM only for non-critical tasks. They tune frequency and duty cycle based on device datasheets and test for flicker, noise, and heat. Duty cycle is often adjusted dynamically for smooth control, while frequency remains fixed.

Connections

Digital Signal Processing

PWM is a form of digital signal modulation used to represent analog values.

Understanding PWM helps grasp how digital signals can encode analog information, a key idea in signal processing.

Human Visual Perception

PWM frequency affects how humans perceive flicker in lights.

Knowing human flicker fusion threshold guides PWM frequency choices for lighting to avoid visible flicker.

Music Tempo and Rhythm

PWM frequency is like tempo, and duty cycle is like note length in music.

This connection shows how timing and duration combine to create patterns, helping understand PWM timing intuitively.

Common Pitfalls

#1 Setting PWM frequency too low causing visible flicker.

Wrong approach:

pwm.start(50) # frequency default low, duty cycle 50%

Correct approach:

pwm.ChangeFrequency(1000) # set frequency to 1kHz to avoid flicker
pwm.ChangeDutyCycle(50)

Root cause:

Not knowing that low frequency causes flicker leads to poor user experience.

#2 Confusing duty cycle percentage with time in milliseconds.

Wrong approach:

pwm.ChangeDutyCycle(5) # thinking 5 means 5 ms ON time

Correct approach:

pwm.ChangeDutyCycle(50) # 50 means 50% ON time of cycle

Root cause:

Misunderstanding duty cycle units causes incorrect power control.

#3 Using software PWM for high-frequency control causing jitter.

Wrong approach:

Using RPi.GPIO PWM at 20kHz for motor control.

Correct approach:

Using hardware PWM via pigpio or dedicated PWM hardware for stable high-frequency signals.

Root cause:

Ignoring hardware limitations of software PWM leads to unstable signals.

Key Takeaways

PWM controls power by switching signals on and off rapidly with two key parameters: frequency and duty cycle.

Frequency sets how fast the signal repeats, while duty cycle sets how long the signal stays ON each cycle.

Changing duty cycle changes power delivered; changing frequency affects device response and flicker but not power.

Higher frequency reduces flicker but can reduce control resolution and increase CPU load.

Choosing PWM settings requires balancing device needs, hardware limits, and desired control precision.

Practice

1. What does the duty cycle in PWM control on a Raspberry Pi?

easy

A. The percentage of time the signal is ON during one cycle

B. The speed at which the signal pulses repeat

C. The voltage level of the signal

D. The total duration of the PWM signal

Solution

1. Step 1: Understand duty cycle meaning

   The duty cycle is the fraction of one cycle when the signal is ON (high).

2. Step 2: Differentiate from frequency

   Frequency controls how fast cycles repeat, not how long signal stays ON.

3. Final Answer:

   The percentage of time the signal is ON during one cycle -> Option A

4. Quick Check:

   Duty cycle = ON time percentage [OK]

Hint: Duty cycle = ON time percentage in each pulse [OK]

Common Mistakes:

• Confusing duty cycle with frequency
• Thinking duty cycle controls voltage
• Assuming duty cycle affects total signal duration

2. Which of the following is the correct Python syntax to set a PWM frequency to 1000 Hz on a Raspberry Pi GPIO pin using RPi.GPIO?

easy

A. pwm = GPIO.PWM(pin, 1000)

B. pwm = GPIO.setPWM(pin, 1000)

C. pwm = GPIO.PWM(pin).frequency(1000)

D. pwm = GPIO.frequency(pin, 1000)

Solution

1. Step 1: Recall RPi.GPIO PWM syntax

   The correct way to create a PWM instance is GPIO.PWM(pin, frequency).

2. Step 2: Check options for correct method and parameters

   pwm = GPIO.PWM(pin, 1000) matches the correct syntax; others use invalid methods or chaining.

3. Final Answer:

   pwm = GPIO.PWM(pin, 1000) -> Option A

4. Quick Check:

   GPIO.PWM(pin, freq) creates PWM [OK]

Hint: Use GPIO.PWM(pin, frequency) to set PWM frequency [OK]

Common Mistakes:

• Using non-existent methods like setPWM or frequency()
• Trying to set frequency after creating PWM without parameters
• Confusing method chaining syntax

3. Consider this Python code snippet controlling an LED brightness with PWM on Raspberry Pi:

import RPi.GPIO as GPIO
GPIO.setmode(GPIO.BCM)
pin = 18
GPIO.setup(pin, GPIO.OUT)
pwm = GPIO.PWM(pin, 500)
pwm.start(0)
pwm.ChangeDutyCycle(75)

What is the effect of setting the duty cycle to 75%?

medium

A. LED will be off

B. LED will be at full brightness

C. LED will blink 75 times per second

D. LED will be at 75% brightness

Solution

1. Step 1: Understand duty cycle effect on LED brightness

   Duty cycle of 75% means LED is ON 75% of the time, so brightness is about 75%.

2. Step 2: Confirm frequency and duty cycle usage

   Frequency 500 Hz controls pulse speed; duty cycle controls brightness level.

3. Final Answer:

   LED will be at 75% brightness -> Option D

4. Quick Check:

   Duty cycle 75% = 75% brightness [OK]

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

Common Mistakes:

• Confusing frequency with blinking count
• Thinking duty cycle 75 means LED off
• Assuming full brightness only at 100% duty cycle

4. This code tries to change PWM frequency on Raspberry Pi but does not work as expected:

pwm = GPIO.PWM(18, 1000)
pwm.start(50)
pwm.changeFrequency(2000)

What is the error and how to fix it?

medium

A. ChangeFrequency is not a valid method; use pwm.ChangeFrequency(2000)

B. ChangeFrequency method name is incorrect; use pwm.ChangeFrequency(2000)

C. Frequency cannot be changed after PWM.start(); recreate PWM object

D. Method name is case sensitive; use pwm.ChangeFrequency(2000)

Solution

1. Step 1: Identify method name case sensitivity

   RPi.GPIO does not provide a method to change frequency after PWM object creation.

2. Step 2: Correct approach to change frequency

   To change frequency, stop PWM and create a new PWM instance with the new frequency.

3. Final Answer:

   Frequency cannot be changed after PWM.start(); recreate PWM object -> Option C

4. Quick Check:

   RPi.GPIO PWM frequency fixed at creation [OK]

Hint: To change frequency, recreate PWM object [OK]

Common Mistakes:

• Using wrong method name spelling
• Ignoring case sensitivity in Python
• Trying to change frequency by creating new PWM instance

5. You want to control a motor speed using PWM on Raspberry Pi. The motor requires a minimum frequency of 1000 Hz for smooth operation. If you set frequency to 1000 Hz and duty cycle to 20%, what happens if you increase frequency to 2000 Hz but keep duty cycle at 20%?

hard

A. Motor speed doubles because frequency doubled

B. Motor speed stays roughly the same because duty cycle is unchanged

C. Motor stops because frequency is too high

D. Motor speed halves because frequency doubled

Solution

1. Step 1: Understand frequency vs duty cycle effect on motor speed

   Motor speed depends mainly on duty cycle (power ON time), not frequency.

2. Step 2: Analyze frequency change with constant duty cycle

   Increasing frequency while keeping duty cycle constant keeps average power same, so speed stays similar.

3. Final Answer:

   Motor speed stays roughly the same because duty cycle is unchanged -> Option B

4. Quick Check:

   Speed ~ duty cycle, frequency affects smoothness [OK]

Hint: Motor speed depends on duty cycle, not frequency [OK]

Common Mistakes:

• Assuming frequency change affects speed directly
• Thinking doubling frequency doubles speed
• Ignoring duty cycle's role in power delivery