PWM sensors explained for embedded design and signal interfaces
What PWM sensors are
A PWM sensor reports a measurement through pulse-width modulation, usually by changing the duty cycle of a repetitive digital waveform. Instead of reading a voltage with an ADC or exchanging packets over I2C, SPI, SENT or another bus, the controller measures how long the signal remains high or low within each period. This approach is useful when a design needs a simple one-wire signal, better tolerance to voltage-drop-related errors, or direct timer-based measurement. The tradeoff is that accuracy depends on timing resolution, signal integrity, carrier frequency, duty-cycle range and edge detection. In embedded designs, PWM sensors are often considered for magnetic position, pressure, displacement and other modules where a microcontroller already has capture timers available.
For more interface background, see our sensors and modules section.
How a PWM sensor encodes a measurement
A PWM waveform has two main timing values: period and pulse width. The period is the time for one complete cycle. The pulse width is the time the signal stays in its active state, most often high. Duty cycle is calculated as pulse width divided by period and is normally expressed as a percentage. A 50% duty cycle means the signal is high for half of the cycle and low for the other half.
In a PWM-output sensor, the measured physical quantity changes the duty cycle, the pulse width, or sometimes both. Many practical sensor interfaces keep the carrier frequency approximately fixed and encode the reading mainly in duty cycle. A microcontroller can then use an input capture peripheral to measure one or more edges and calculate the result without using an analog-to-digital converter.
Manufacturer documentation shows several common mapping styles. Analog Devices has described pressure transducer conditioning where an analog ratiometric output is converted into a PWM duty cycle, with an example span from 10% to 90%. Texas Instruments describes the DRV5057 linear Hall-effect sensor as a PWM-output magnetic sensor whose duty cycle is proportional to magnetic flux density, with 50% duty cycle at zero magnetic field and a specified linear output range from 8% to 92% duty cycle. These examples highlight a key design point: the useful range is often not 0% to 100%. Designers need to follow the range and transfer function in the specific datasheet.
Why designers use PWM instead of analog voltage
PWM is not automatically better than analog signaling, but it solves several practical interface problems. A voltage-output sensor can be easy to filter and sample, yet its reading may be affected by reference accuracy, supply variation, ground offsets, cable resistance and ADC performance. A PWM sensor still needs clean logic levels, but the information is carried mainly in timing. If the receiver can reliably distinguish high and low levels, the measured duty cycle can be less sensitive to moderate amplitude variation than a raw analog voltage.
Analog Devices notes that PWM sensor transmission can provide good noise immunity and can be suitable for longer-distance transmission, especially compared with sending a small analog signal directly. The same source also describes a battery-oriented benefit: in the example circuit, a PWM transmitter connected to a high-impedance input can require much less information-transfer power than a current-loop approach. That does not mean every PWM design is lower power. The actual result depends on pull-up value, output driver type, frequency, cable capacitance and the rest of the signal-conditioning circuit.
PWM is also familiar to embedded developers. Many low-cost microcontrollers include timer capture blocks, compare units and interrupt logic. Microchip application material for AVR devices describes using an input capture unit to compute both pulse width and period. This type of peripheral support is one reason PWM sensors are practical in compact modules.
Where PWM sensors fit among other sensor interfaces
Choosing PWM is usually an interface decision, not a statement about sensor quality. The same physical sensing principle may be available with analog, PWM or digital bus outputs. Hall-effect position sensors, for example, may be sold with analog, PWM, SENT, PSI5 or SPI outputs depending on application requirements. TDK-Micronas selection material for automotive Hall sensors lists multiple output families, including analog, PWM, PSI5, SENT and SPI, showing that PWM sits between simple analog signaling and packet-based digital interfaces.
| Interface type | Typical strength | Typical limitation | Good fit |
|---|---|---|---|
| Analog voltage | Simple to inspect and filter | Depends on ADC, references and noise control | Short traces, low-cost boards, slow signals |
| PWM | Encodes value in timing and can use timer capture | Needs accurate edge measurement and known mapping | One-signal modules, position sensors, pressure transducers |
| I2C or SPI | Can carry calibrated data and status bits | More protocol complexity and bus constraints | Multi-sensor boards, configuration-heavy devices |
| SENT or PSI5 | Designed for robust automotive-style sensor communication | Requires compatible decoding and application knowledge | Automotive and safety-aware signal chains |
The table is not a ranking. A PWM sensor can be a strong choice when the controller has available timer channels and the application benefits from a compact digital-like output. A bus sensor is often better when the design needs device identification, diagnostics, factory calibration data, interrupt registers or multiple channels on the same line. An analog sensor may still be preferred when the signal must be continuously filtered, observed with basic instruments, or processed by analog circuitry before digitization.
Design checks before selecting a PWM sensor
The first check is the transfer function. Do not assume that 0% equals minimum and 100% equals maximum. Many sensors reserve headroom near the rails for diagnostics, saturation behavior or practical edge detection. TI’s DRV5057 example uses a specified linear duty-cycle range from 8% to 92%, not the full 0% to 100%. Other devices may use 10% to 90%, 5% to 95%, a fixed pulse width, or a vendor-specific code range.
The second check is carrier frequency. A higher PWM frequency can reduce latency and make filtering easier in some systems, but it also requires faster timing capture and may be more affected by edge jitter, propagation delay and cable capacitance. A lower frequency is easier to measure with modest microcontrollers, but it increases update time. If a control loop needs fresh data every millisecond, a very slow PWM output may be unsuitable.
The third check is timer resolution. If the PWM period is short and the microcontroller clock is slow, the number of timer counts per period may be too small for the required measurement resolution. For example, a timer that captures only a few hundred counts per period cannot deliver fine duty-cycle precision without averaging. This is a system-level limit, not only a sensor specification.
The fourth check is electrical compatibility. Open-drain or open-collector PWM outputs need a pull-up resistor, and their rise time depends on resistance and capacitance. Push-pull outputs switch faster but require voltage-level compatibility and careful fault analysis. Long wiring should be evaluated for ringing, common ground quality, electromagnetic interference and input threshold margins.
The fifth check is startup and fault behavior. A sensor may output a default duty cycle at zero input, enter high impedance during startup, clamp at a minimum or maximum code, or use out-of-range duty cycles for diagnostics. These states should be treated as part of the design, especially where motion, pressure or current readings affect machine behavior. See also: device architecture.
How to read PWM sensors accurately
The most robust method is usually hardware input capture. The microcontroller records timer values at rising and falling edges, then firmware calculates high time, low time, period and duty cycle. This reduces the uncertainty that would come from polling a GPIO in a software loop. Microchip’s AVR application note on timer capture is a representative example of this approach, and similar capture features exist across many microcontroller families.
Firmware should normally measure both pulse width and period, not just pulse width alone. Measuring both helps the system detect unexpected frequency changes, missing pulses or wiring faults. It also avoids assuming the sensor frequency is fixed when the actual output has tolerance over voltage, temperature or production variation.
Averaging can improve stability, but it adds latency. A position sensor in a fast control loop may need quick response, while a pressure or level sensor may tolerate averaging over several cycles. The right filter depends on the application: too little filtering exposes jitter, while too much filtering can hide real changes.
Extreme duty cycles need special attention. Texas Instruments published a 2025 application note explaining that edge-triggered timer capture cannot directly capture 0% or 100% duty cycle because those states do not provide the edges required by the capture logic. The note describes additional detection methods, such as timeout logic and signal-state checks, when the PWM frequency is fixed or known. The practical lesson is that if a sensor can legally output near 0% or 100%, the receiver must be designed to distinguish a valid endpoint from a stuck-low, stuck-high or disconnected condition.
Common mistakes with PWM sensor modules
- Reading PWM with an ADC without a proper filter. A raw PWM waveform is digital switching, not a steady analog voltage. An RC filter can convert duty cycle into an average voltage, but the filter must be designed for the PWM frequency, response time and ADC input characteristics.
- Ignoring the datasheet duty-cycle range. Many PWM sensors reserve part of the range. Treating 8% as an error or 92% as saturation may be wrong for one device and correct for another.
- Using interrupt-only edge timing at high frequency. Interrupt latency and other firmware tasks can introduce jitter. Hardware capture is usually safer for precise measurement.
- Forgetting pull-up effects on open-drain outputs. A weak pull-up on a capacitive cable can slow rising edges and distort measured duty cycle.
- Assuming frequency is always fixed. Some outputs vary frequency with tolerance, operating mode or device family. Measure period or confirm the specification.
- Not defining fault handling. A stuck line, broken wire, startup delay or out-of-range duty cycle should be handled explicitly in firmware.
When PWM sensors are a good choice
PWM sensors make sense when a design needs a simple signal path, has timer capture resources available, and can tolerate the update rate implied by the PWM frequency. They are especially practical when the measured quantity does not require very high bandwidth but does need stable transmission across a board or cable. Magnetic position, throttle or pedal-style sensing, pressure transducers, distance modules and custom sensor-conditioning circuits are common areas where PWM can be considered.
They are less attractive when the system needs many sensors on the same bus, extensive diagnostics, high-speed synchronized sampling, or very high precision without calibration. In those cases, a digital interface with framing and status data, or a carefully designed analog front end, may be more appropriate.
In practice, PWM should be evaluated as a timing interface. The sensor, wiring, receiver timer, firmware and fault model all influence the final measurement. When those parts are designed together, PWM sensors can provide a clean and economical bridge between analog sensing elements and digital controllers.
Frequently asked questions
Are PWM sensors digital or analog?
They are often described as digital-output sensors because the pin switches between logic levels. However, the measured value is encoded in timing, usually duty cycle, so the receiver still performs a measurement rather than simply reading a binary state.
Do PWM sensors need an ADC?
Not usually. A microcontroller can measure duty cycle with a timer capture input. An ADC is only needed if the PWM is intentionally filtered into an average voltage or if the design uses extra analog checks for fault detection.
Can one microcontroller read many PWM sensors?
Yes, if it has enough timer capture channels, interrupt capacity and processing time. For many channels, designers may need timer multiplexing, external capture hardware, a different sensor interface, or a microcontroller selected specifically for capture resources.
Is a higher PWM frequency always better?
No. Higher frequency can reduce the update interval, but it also demands better timer resolution, faster edges and tighter signal integrity. The best frequency is the one that supports the required response time while leaving enough counts per period for accurate duty-cycle measurement.
What should be checked first in a PWM sensor datasheet?
Start with duty-cycle transfer function, output frequency, valid duty-cycle range, electrical output type, supply range, startup behavior, fault codes, temperature limits and timing tolerance. These specifications determine whether the sensor can be read accurately in the target system.
