IR remotes still run living rooms, classrooms, and conference rooms worldwide.
This page explains how IR signaling works, how to capture/replay responsibly,
and how to harden devices against misuse.
Quick-start checklist
Permission & scope: Only test on your own equipment or with explicit written authorization.
Receiver basics: Confirm target uses IR (not RF/Bluetooth). Check for line-of-sight.
Carrier & protocol: Many remotes use ~38 kHz carrier; determine likely protocol (NEC, RC5/RC6, Sony SIRC, Samsung, Panasonic, etc.).
Gear ready: One device with IR receive (learning) and transmit (emulation) capability.
Test plan: Start with non-disruptive commands (e.g., volume down on a spare TV), document results, then expand coverage.
IR protocol primer
IR remotes modulate infrared light (typically around 940 nm) at a carrier frequency (commonly 38 kHz)
and send bursts of “on/off” pulses encoding addresses and commands. Different vendors use different
frame layouts and timings.
Common families: NEC (LG, Vizio, many TVs), Sony SIRC, Philips RC5/RC6, Samsung, Panasonic,
JVC, Sharp, Mitsubishi, Daikin/AC vendors, and projector/AV remotes with “discrete” power inputs.
IR messages are sequences of timed “marks” and “spaces” at a carrier frequency.
Many consumer devices accept both “toggle” commands (Power) and discrete commands (Power On, Power Off),
which are useful for reliable automation. Air conditioners often use long frames encoding entire state
(mode, temp, fan), not just single buttons.
Common research workflows
1) Learn → Replay (universal remote basics)
Use your tool’s IR learn function to capture a button press from the original remote.
Save it with a readable label (e.g., tv_samsung_power).
Replay to confirm the device responds; test from various angles and distances.
2) Protocol identification & library matching
Attempt auto-decode; many tools can identify NEC, RC5/6, SIRC, etc.
If decoding fails, record raw timings; search vendor code sets or community databases.
Create a reusable “codebook” for your environment (TVs, projectors, AV switchers).
3) Discrete power & input selection for automation
Prefer discrete ON/OFF/INPUT commands for reliable state machines (no “toggle confusion”).
Chain sequences with delays (Power On → wait 3s → HDMI1 → Volume 12).
Use line-of-sight considerations and stick an IR LED near the receiver in rack installs.
4) AC & HVAC remotes (state-full frames)
Capture multiple frames (Cool 72°, Auto fan; Heat 68°) to learn full-state encodings.
Replay known-good presets rather than trying to craft raw bits from scratch.
Document brand-specific quirks (checksum bytes, temperature steps, swing modes).