An infrared (IR) receiver is a solid-state optoelectronic component that detects modulated IR light (typically 38 kHz) from a remote control and demodulates it into a clean, digital logic-level signal for a microcontroller. In a real circuit, it changes a chaotic, analog barrage of photons into a crisp 3.3V or 5V digital square wave, entirely offloading the high-frequency demodulation math from your microcontroller and saving you from writing complex analog sampling routines.
How an IR Receiver Actually Works (The Demodulation Trick)
If you point a TV remote at a raw IR photodiode, the diode outputs a messy, millivolt-level analog waveform buried in ambient light noise. An integrated IR receiver module (like the ubiquitous Vishay TSOP38238 or the generic VS1838B) solves this by packing a complete optical receiver chain into a single 3-pin epoxy package.
Inside that black dome, the signal path follows a strict sequence:
- Photodiode & Pre-Amplifier: Converts incoming 940nm IR photons into a microvolt-level electrical current and applies initial gain.
- Automatic Gain Control (AGC): Dynamically adjusts the amplifier's sensitivity. If ambient light is high, it drops the gain to prevent false triggers; if the signal is weak, it boosts it.
- Bandpass Filter: A tuned analog filter that aggressively rejects everything except the target carrier frequency (usually 38 kHz).
- Envelope Detector & Demodulator: Strips away the 38 kHz carrier wave, leaving only the baseband data pulses (the actual button press code).
- Output Transistor: An open-drain or push-pull NPN/PNP stage that pulls the output pin LOW when a signal is detected, and HIGH when idle.
Where You Meet This in Practice
You will encounter demodulating IR receivers in several distinct corners of electronics design and repair:
- Consumer AV & HVAC: Every television, soundbar, and mini-split air conditioner uses a 3-pin IR receiver on the front panel to decode NEC, RC5, or Samsung protocols.
- Robotics & Obstacle Avoidance: The cheap "IR obstacle avoidance" modules found in smart car kits use an IR receiver paired with a 38 kHz astable multivibrator. They bounce modulated light off objects; if the receiver catches the reflection, the comparator triggers.
- DIY Smart Home Hubs: Projects using ESP32 or Raspberry Pi boards to clone remote controls (like the Broadlink RM4 or custom Adafruit IR breakouts) rely on these receivers to capture raw timing data before transmitting it over MQTT.
Worked Numeric Example: Sizing the Support Circuit
Beginners often wire an IR receiver directly to 5V and GND, then wonder why their ESP32 registers phantom button presses. Integrated IR receivers are highly sensitive to power supply ripple, which can trick the internal AGC. Let's calculate the proper support components for a Vishay TSOP38238 running at 5V.
The Power Supply Filter (RC Network):
The datasheet recommends an RC filter on the Vcc pin to isolate the receiver from microcontroller switching noise. We need a time constant that smooths ripple without causing a voltage drop during high-current signal bursts.
- Resistor (R1): 100 Ω to 1 kΩ. Let's use 100 Ω to minimize voltage sag.
- Capacitor (C1): 4.7 µF electrolytic or ceramic.
- Current Draw: The TSOP38238 draws a typical supply current of 0.7 mA (max 1.5 mA). At 0.7 mA, the voltage drop across a 100 Ω resistor is only 0.07V (V = I × R = 0.0007 × 100), leaving 4.93V at the chip's Vcc pin—well within the 2.5V to 5.5V operating range.
Numbered Wiring Steps for an ESP32 DevKit V1
- Connect the receiver's GND pin (Pin 1 on most VS1838B, Pin 2 on Vishay TSOP) to the ESP32 GND.
- Route 5V from the ESP32 Vin pin through a 100 Ω resistor to the receiver's Vcc pin. Place the 4.7 µF capacitor between the receiver's Vcc pin and GND.
- Connect the receiver's OUT pin to ESP32 GPIO 15.
- Add a 10 kΩ external pull-up resistor between the OUT pin and 3.3V. While the receiver has an internal pull-up (typically 30kΩ–50kΩ), an external 10kΩ ensures crisp rising edges on wires longer than 10 cm, preventing the ESP32's high-impedance input from floating.
Real-World Scenario Walkthrough: The Workshop Interference Bug
The Setup: I was building an ESP32-based IR-controlled relay box to switch my workbench power tools. I used a generic VS1838B receiver module, mounted it on the ceiling 3 meters away from the workbench, and powered it from a cheap 5V USB buck converter. On my kitchen table, the remote worked flawlessly.
The Numbers: Carrier frequency: 38 kHz. Distance: 3 meters. Remote transmit power: standard 940nm LED at 100mA pulses. Receiver supply voltage: 4.9V measured at the module.
The Outcome: Once installed on the ceiling, the system was completely dead. The ESP32 serial monitor showed zero IR pulses, even when I pointed the remote directly at the sensor from 1 meter away.
What Went Wrong: The ceiling mount placed the receiver directly next to a bank of cheap, unbranded LED shop lights. These lights use low-frequency PWM dimming drivers that emit massive broadband optical noise, including harmonics that bleed into the 38 kHz spectrum. Because the ambient optical noise was so high, the receiver's Automatic Gain Control (AGC) aggressively suppressed its internal amplifier gain to prevent false triggering. With the gain crushed, the 3-meter remote signal fell below the detection threshold. The receiver was essentially blinding itself to survive the LED noise.
The Fix: I swapped the generic VS1838B for a genuine Vishay TSOP3438, which features an advanced AGC algorithm specifically designed to distinguish between continuous optical noise (like CFL/LED ballasts) and pulsed data signals. I also placed a piece of dark red optical filter acrylic over the epoxy dome to physically block visible light spectrum noise. The system has worked perfectly since.
What People Commonly Confuse It With
The most frequent mistake in hobbyist parts ordering is confusing a demodulating IR receiver module with a raw IR photodiode. They look similar (both are often black or clear epoxy domes), but they behave entirely differently in a circuit.
| Feature | Demodulating IR Receiver (e.g., TSOP38238) | Raw IR Photodiode (e.g., BPV10NF) |
|---|---|---|
| Pins | 3 (Vcc, GND, OUT) | 2 (Anode, Cathode) |
| Output Type | Digital square wave (Active LOW) | Analog current (requires transimpedance amplifier) |
| MCU Processing | Read digital pulse widths (easy) | High-speed ADC sampling & software demodulation (hard) |
| Sunlight Rejection | Excellent (internal optical filter + AGC) | Poor (saturates easily in daylight) |
| Primary Use | Remote control decoding, data links | Beam-break sensors, proximity detection, flame sensing |
FAQ: Infrared Receiver Troubleshooting
Q: Why is my IR receiver output pin floating or giving random noise when no remote is pressed?
A: Your output line is likely missing a pull-up resistor. While many modules include a weak internal pull-up, long wires act as antennas for EMI. Solder a 10 kΩ resistor between the OUT pin and your logic voltage (3.3V or 5V) to force the line HIGH when the internal transistor is off.
Q: Can I run a 5V-rated TSOP module directly on a 3.3V ESP32 or Raspberry Pi Pico?
A: Check the specific datasheet. Most modern Vishay and Everlight receivers operate from 2.5V to 5.5V. If you power it with 3.3V, the output HIGH level will be 3.3V, which is perfectly safe and natively compatible with 3.3V microcontroller GPIOs without needing a logic level shifter.
Q: My remote works up close, but fails at 5 meters. The receiver LED flashes, but the MCU misses the code.
A: This is usually a voltage sag issue, not an optical one. When the receiver detects a long burst of IR, its internal current draw spikes. If your power supply trace is too thin or lacks the 4.7 µF decoupling capacitor, the Vcc pin dips below the brownout threshold for a microsecond, corrupting the output pulse width. Add the RC filter mentioned in the numeric example above.
