A PWM (Pulse Width Modulation) signal is a digital square wave that simulates analog voltage levels by rapidly switching a microcontroller pin between fully ON (HIGH) and fully OFF (LOW) at a specific ratio called the duty cycle. In a real circuit, a PWM signal changes the average power delivered to a load—like dimming an LED or controlling a DC motor's speed—without wasting energy as resistive heat, which is the unavoidable byproduct of using a linear potentiometer or resistor to drop voltage. By snapping the voltage fully on and fully off, the switching element (like a MOSFET) operates only in its highly efficient saturation or cutoff regions.
The Core Mechanics: Duty Cycle, Frequency, and Average Voltage
To understand how a digital pin fakes an analog voltage, you need to separate two distinct timing parameters: duty cycle and frequency.
The duty cycle is the percentage of one complete period where the signal is HIGH. A 50% duty cycle on a 5V logic pin yields an average voltage of 2.5V. A 20% duty cycle yields 1.0V. The frequency dictates how fast these ON/OFF cycles repeat, measured in Hertz (Hz). The frequency must be high enough that the load (or human eye) integrates the pulses into a smooth average, rather than seeing distinct flashes or jerks.
Worked Numeric Example: Driving a 12V DC Motor with an ESP32
Suppose you are using an ESP32-WROOM-32 (3.3V logic) to drive a 12V, 5A DC motor through a logic-level N-channel MOSFET like the IRLZ44N. You want the motor to run at roughly 20% of its maximum speed.
Chosen Frequency: 1000 Hz (Period = 1 millisecond)
ON Time: 0.2 ms | OFF Time: 0.8 ms
Because the ESP32's LEDC (LED Control) peripheral handles PWM via hardware timers, we configure it for an 8-bit resolution. This divides the 100% duty cycle into 256 discrete steps (0 to 255). To achieve our 20% target, we calculate the duty value:
Duty Value = (Target Percentage / 100) * Max Resolution
Duty Value = 0.20 * 255 = 51
Writing a duty value of 51 to the ESP32's PWM channel commands the hardware to hold the GPIO pin HIGH for exactly 51 out of every 255 time slices, delivering the precise 20% average power required to spin the motor at low speed without the MOSFET dissipating excess heat.
Microcontroller PWM Capabilities: ESP32 vs. ATmega328P vs. RP2040
Not all microcontrollers generate PWM signals equally. Older 8-bit architectures rely on shared hardware timers, meaning changing the frequency on one pin might accidentally alter the frequency on another. Modern 32-bit MCUs offer dedicated, highly flexible PWM peripherals. Below is a spec-sheet comparison of three popular hobbyist and prototyping boards.
| Microcontroller (Board) | Hardware PWM Pins | Max Resolution | Default Frequency | Max Frequency | Timer Architecture |
|---|---|---|---|---|---|
| ATmega328P (Arduino Uno) | 6 (Pins 3,5,6,9,10,11) | 8-bit (255) | 490 Hz / 980 Hz | ~62.5 kHz (8-bit mode) | 3 shared timers (Timer0,1,2) |
| ESP32-WROOM-32 (DevKit v1) | 16 (LEDC channels) | Up to 20-bit | 5000 Hz | 40 MHz (at 1-bit res) | 4 independent hardware timers |
| RP2040 (Raspberry Pi Pico) | 16 (All GPIOs via slices) | 16-bit | 125 MHz / 255 (varies) | 125 MHz (at low res) | 8 slices, 2 channels per slice |
| STM32F103C8T6 (Blue Pill) | 15 (via Advanced Timers) | 16-bit | 1000 Hz | 72 MHz (at low res) | 4 independent timers (TIM1-4) |
Key Takeaway for Builders: If you are using an Arduino Uno (ATmega328P), be aware that pins 5 and 6 share Timer0, which is also used for the millis() and delay() functions. Altering the PWM frequency on these pins via direct register manipulation will break your timing functions. The ESP32 and RP2040 avoid this by using dedicated, decoupled hardware peripherals for PWM generation, as noted in the Arduino analogWrite() documentation regarding timer conflicts.
Where You Meet PWM Signals in Practice
You will encounter PWM signals across almost every embedded system domain, but the required frequency and resolution change drastically depending on the physical load.
1. RC Servo Motor Positioning (50Hz, Low Frequency)
Standard hobby servos like the SG90 or MG996R do not use duty cycle as a percentage of power; they use it as a strict timing measurement. They expect a 50Hz signal (one pulse every 20ms). The width of the HIGH pulse dictates the shaft angle: a 1.0ms pulse commands 0°, a 1.5ms pulse commands 90° (center), and a 2.0ms pulse commands 180°. Sending a standard 1000Hz motor-control PWM to a servo will result in erratic twitching or no movement at all.
2. LED Dimming and Display Backlights (>1kHz, High Frequency)
When dimming high-power LEDs, the PWM frequency must be high enough to prevent visible flicker, especially when viewed through digital camera sensors (which suffer from rolling shutter banding). While the human eye integrates flicker above 100Hz, camera sensors require frequencies above 1000Hz to 5000Hz to render a clean, dimmed image without horizontal banding artifacts.
3. Switch-Mode Power Supplies and Buck Converters (>100kHz, Ultra-High Frequency)
In DC-DC buck converters, a PWM signal drives the gate of a high-speed MOSFET to chop input voltage and pass it through an inductor-capacitor filter. Here, frequencies range from 100kHz to over 2MHz. The high frequency allows the use of physically smaller inductors and capacitors, though it increases switching losses in the MOSFET. Microcontrollers rarely generate these directly; dedicated PWM controller ICs handle the ultra-high-speed switching and feedback loops.
Common PWM Confusions and Troubleshooting
Even experienced makers trip over a few fundamental misunderstandings when working with PWM signals on the bench.
Confusion 1: PWM vs. True Analog (DAC)
The Mistake: Assuming a 50% duty cycle PWM signal will safely power an analog audio amplifier or an op-amp reference input.
The Reality: A PWM signal is still a digital square wave swinging fully between 0V and VCC. If you feed a 5V PWM signal into an audio amp, you will hear a harsh, high-pitched square-wave buzz, not a smooth half-volume tone. To get true analog DC, you must pass the PWM signal through a low-pass RC filter (resistor-capacitor network) to smooth the square edges into a flat DC line, or use a microcontroller with a built-in DAC (Digital-to-Analog Converter).
Confusion 2: 5V PWM into 3.3V Logic Pins
The Mistake: Connecting the PWM output of a 5V Arduino Uno directly to a GPIO pin on a 3.3V ESP32 or Raspberry Pi Pico to act as a sync or control signal.
The Reality: The 5V HIGH state will exceed the absolute maximum ratings of the 3.3V microcontroller's input protection diodes, potentially bricking the chip. You must use a logic level shifter, or at minimum, a simple resistor voltage divider (e.g., 2kΩ and 3.3kΩ) to step the 5V PWM down to a safe 3.3V square wave.
Confusion 3: Frequency vs. Duty Cycle
The Mistake: Trying to make a motor spin 'faster' by increasing the PWM frequency in the code.
The Reality: Frequency dictates how many ON/OFF cycles happen per second. Duty cycle dictates how much power is delivered. Increasing the frequency from 1000Hz to 5000Hz will not make a DC motor spin faster; it will just make the motor whine at a higher pitch. To increase speed, you must increase the duty cycle percentage. For a deeper look at how these parameters interact with physical loads, All About Circuits provides an excellent breakdown of PWM integration in motor control circuits.
Mastering the PWM signal means moving beyond the basic analogWrite() function. By understanding your microcontroller's specific timer architecture, selecting the correct frequency for your physical load, and calculating exact duty cycle steps, you can efficiently control high-power devices using nothing but low-voltage digital logic.
