IRDA Infrared Data

What Was IRDA?

IRDA (Infrared Data Association) was a serial data communication protocol that used infrared light to transfer files between devices. Unlike IR remotes which send simple one-way commands, IRDA provided bidirectional, error-checked data transfer at speeds far beyond what remote controls could achieve. Founded in 1993 by a consortium including HP, IBM, Sharp, and Fujitsu, IRDA became the first widely-adopted wireless data standard for portable devices.

From the mid-1990s to the mid-2000s, IRDA ports were standard equipment on laptops, PDAs (like the Palm Pilot), mobile phones, and printers. You could beam a business card from one Palm Pilot to another, print a document wirelessly, or sync your phone with your laptop — all using invisible infrared light at 850–870 nm wavelength.

How IRDA Worked

IRDA used a fundamentally different approach than consumer IR remotes. While remotes use wide-angle IR LEDs with simple pulse coding, IRDA used focused IR transceivers with structured packet protocols:

• Bidirectional: Both devices could send and receive data simultaneously (full-duplex at SIR speeds) or alternately (half-duplex at FIR speeds)
• Narrow beam: IRDA used a focused beam (±15° cone) for better range and less interference. The transmit power was controlled to achieve 0–1 meter range at data rates up to 4 Mbit/s
• Packet-based: Data was sent in structured packets with error checking (CRC-16), address fields, and control information. The IrLAP (Infrared Link Access Protocol) layer handled framing, error detection, and retransmission
• Point-to-point: Only two devices could communicate at once (unlike WiFi). The IrLAP protocol included a discovery phase to identify the single peer device
• Line of sight: Required direct alignment between devices. The focused beam meant devices had to be within ±15° of each other's IR windows

Protocol Stack

The IRDA protocol stack consisted of four layers, each serving a specific function:

• IrPHY (Physical Layer): Defined the IR optical interface. Transmitter: 850–870 nm IR LED, modulation depth >50%. Receiver: PIN photodiode with AGC. Data encoding: RZI (Return-to-Zero Inverted) for SIR; 4PPM for FIR. Pulse width: 1.6 μs (SIR at 115.2 kbit/s)
• IrLAP (Link Access Protocol): Similar to HDLC. Handles device discovery, connection establishment, data framing (flags, address, control, information, FCS), and error recovery. Supports point-to-point and point-to-multipoint (with one primary and up to 7 secondary devices)
• IrLMP (Link Management Protocol): Multiplexes multiple services over a single IrLAP connection. Each service is identified by a Layer Service Access Point (LSAP) selector. Enables simultaneous file transfer and remote control over one IR link
• IrTinyTP (Tiny Transport Protocol): Flow control for upper-layer protocols. Implements credit-based flow control (window size negotiation) to prevent buffer overflow. Handles segmentation and reassembly of large data units

Speed Tiers

IRDA defined several speed tiers, each with distinct physical layer characteristics:

• SIR (Serial IR, 9.6–115.2 kbit/s): Compatible with standard UART serial ports (16550 UART). Uses NRZ (Non-Return-to-Zero) encoding with RZI modulation. Bit period: 8.68 μs at 115.2 kbit/s. This was the most widely supported speed — all IRDA devices supported SIR
• MIR (Medium IR, 0.576–1.152 Mbit/s): Intermediate speed using 4PPM (Pulse Position Modulation). Each symbol encodes 2 bits in one of 4 time slots. Required dedicated IRDA controller hardware
• FIR (Fast IR, 4 Mbit/s): Uses 4PPM with 125 ns slot width. Required dedicated FIR controller chip (e.g., National Semiconductor IrDA transceiver). This was the high-performance tier for laptop-to-laptop file transfers
• VFIR (Very Fast IR, 16 Mbit/s): Sharp proprietary technology. Uses 2-PPM with 31.25 ns slots. Rare in consumer devices — only appeared in Sharp laptops and some PDAs
• UFIR (Ultra Fast IR, up to 100 Mbit/s): Never widely adopted. Used advanced modulation (pulse amplitude modulation) and higher-power IR emitters
• GigaIR (1 Gbit/s): Proposed standard using 850 nm VCSEL (Vertical-Cavity Surface-Emitting Laser) instead of LED. Achieved laboratory speeds of 1 Gbit/s over 1 meter. Never commercialized

Why IRDA Died

Despite its clever engineering, IRDA had fundamental limitations that made it impractical as wireless technology evolved:

• Line of sight required: You had to physically align the devices — no "background" connectivity. WiFi and Bluetooth worked through walls and without pointing
• Short range: Typically 1 meter or less for reliable data transfer at FIR speeds. SIR could reach 2+ meters but at much lower data rates
• Slow compared to WiFi: Even VFIR at 16 Mbit/s was far slower than 802.11b at 11 Mbit/s — and WiFi worked at 50+ meters without line of sight
• One-to-one only: No networking capability. You could only transfer files to one device at a time, requiring physical proximity
• Protocol complexity: The four-layer IRDA stack was complex and power-hungry. Implementing IrLAP alone required 20–50 KB of code — significant for 1990s microcontrollers
• No always-on connectivity: IRDA required active alignment and close proximity. You couldn't leave IRDA on and have it work in the background like Bluetooth

Bluetooth (introduced in 1999) solved all these problems: it worked through walls, didn't require line of sight, supported multiple simultaneous connections (piconet with 7 active slaves), and was designed from the ground up for mobile devices with low power consumption. By 2005, virtually all new laptops and phones shipped with Bluetooth instead of IRDA.

Legacy and Modern Uses

While IRDA is dead as a consumer protocol, the technology lives on in niche industrial applications where its line-of-sight requirement is actually a security feature:

• Point-of-sale terminals: Some payment terminals use IRDA-derived protocols for secure data transfer to receipt printers. The line-of-sight requirement prevents eavesdropping from adjacent positions
• Medical devices: Patient monitoring equipment, infusion pumps, and blood glucose meters use IRDA or IrSimple for data transfer where RF interference with other medical equipment is a concern
• Industrial sensors: Some industrial sensors and data loggers use IRDA interfaces for configuration and data download in hazardous environments where RF spark risk exists
• Legacy infrastructure: Many enterprise systems (ERP, warehouse management) still have IRDA interfaces for handheld scanners and mobile terminals. Migration to Bluetooth/NFC is ongoing but slow

IrDA Protocol Stack in Detail

The IrDA stack was modeled after the OSI model but condensed into four functional layers. Each layer provided specific services and communicated with adjacent layers through well-defined interfaces:

• IrLAP — Link Access: The foundation layer, derived from HDLC (High-Level Data Link Control). IrLAP managed the physical link between two IRDA devices through a state machine with five states: ndm (non-discovery mode), discovery, connection, data transfer, and shutdown. During discovery, the primary device broadcasts ID frames (containing a 32-bit device address and a 7-byte station name) and secondary devices respond. IrLAP negotiated parameters like data rate, frame size (up to 2048 bytes), window size (1–7 frames in flight), and turn-around time. The frame structure included a flag (0x7E), address field (1 byte — primary/secondary + LSAP selector), control field (1–2 bytes for I-frames, S-frames, and U-frames), information field (payload), and FCS (CRC-16)
• IrLMP — Link Management: Sat on top of IrLAP and provided service multiplexing. Each service (file transfer, printer, serial emulation) was identified by an LSAP-SEL (Layer Service Access Point Selector) — a single byte identifying the protocol endpoint. IrLMP allowed up to 127 simultaneous service connections over a single IrLAP link. The discovery information service (DIS) allowed devices to query each other for supported LSAP-SELs, enabling automatic service discovery. IrLMP also defined the Information Access Service (IAS) — a lookup database where clients could query for available services by name or class
• TinyTP — Transport: Provided segmentation, reassembly, and credit-based flow control. When an upper-layer protocol sent a data unit larger than the IrLAP frame size, TinyTP segmented it into frames at the sender and reassembled them at the receiver. Flow control used a credit window — the receiver granted credits (0–7) indicating how many frames the sender could transmit before waiting for acknowledgment. This prevented buffer overflow without requiring explicit flow control signaling
• OBEX — Object Exchange: The application-layer protocol for exchanging structured objects (files, business cards, calendar entries). OBEX was developed by IrDA but later adopted by Bluetooth (IrOBEX over RFCOMM). An OBEX session consisted of CONNECT, PUT, GET, SETPATH, and DISCONNECT operations. Each operation included a packet header with a type code and length. The vCard and vCalendar formats were the most common OBEX objects — beaming a contact from one phone to another was an OBEX PUT of a vCard object

The IrLAP discovery process was unique to IRDA. Before establishing a connection, the primary device entered a discovery phase where it transmitted ID frames at increasing power levels (up to 4 levels) with different bit rates (SIR, MIR, FIR). Secondary devices responded with their own ID frames after a random backoff delay. This collision-avoidance mechanism allowed up to 7 secondary devices to be discovered on a single piconet, though point-to-point (2-device) connections were far more common

IrDA Protocol Stack:

  ┌─────────────────────────────────┐
  │  Application (OBEX, IrCOMM)     │  ← Business cards, serial, printing
  ├─────────────────────────────────┤
  │  TinyTP (Transport)             │  ← Segmentation, flow control
  ├─────────────────────────────────┤
  │  IrLMP (Link Management)        │  ← Service multiplexing, IAS lookup
  ├─────────────────────────────────┤
  │  IrLAP (Link Access)            │  ← Framing, discovery, error recovery
  ├─────────────────────────────────┤
  │  IrPHY (Physical)               │  ← IR optical, RZI/4PPM encoding
  └─────────────────────────────────┘

IrDA Data Rates and Encoding

Each speed tier used a different modulation scheme on the optical carrier. The encoding choice was driven by the tradeoff between bandwidth efficiency, hardware complexity, and the limited modulation bandwidth of IR LEDs at the time:

• SIR — RZI (Return-to-Zero Inverted): At 115.2 kbit/s, each bit occupied an 8.68μs window. A logical 1 was represented by a light pulse in the first half of the bit period followed by a space. A logical 0 was a space for the full bit period. The RZI scheme ensured frequent transitions for clock recovery, even with long runs of identical bits. The carrier burst was 3/16 of the bit period (1.63μs), which allowed the IR LED to run at reduced duty cycle and extend its lifespan. SIR was compatible with standard 16550 UART hardware — the UART handled serialization, and the IR transceiver handled modulation
• FIR — 4PPM (Pulse Position Modulation): Each 4PPM symbol divided a 500ns symbol period into 4 time slots of 125ns each. A single pulse occupied one of the four slots, encoding 2 bits per symbol (00, 01, 10, 11 mapped to slot positions 0, 1, 2, 3). At 4 Mbit/s, this required 8 million symbols/second, with each slot lasting 125ns — pushing the limits of commercially available IR LED switching speeds. The photodetector required a bandwidth of at least 4 MHz, and the transceiver chip (typically National Semiconductor's PDIrDA series) included an integrated AGC (automatic gain control) to handle the large dynamic range between near-field (10cm) and far-field (1m) signals
• VFIR — 2-PPM: Used 2-PPM (binary PPM) with 31.25ns slots. Each symbol encoded 1 bit in one of two time slots, doubling the data rate from FIR while keeping the same peak optical power. However, the 31.25ns slot width required IR LEDs with rise/fall times under 10ns — only achievable with advanced edge-emitting LEDs (not the cheap surface-mount types). The VCSEL (Vertical-Cavity Surface-Emitting Laser) variant used 850nm laser diodes instead of LEDs, achieving the 1 Gbit/s GigaIR target but at prohibitive cost for consumer devices
• Manchester vs RZI timing: SIR used RZI (pulse width = 3/16 bit period) while MIR/FIR used 4PPM. This incompatibility meant SIR and FIR devices could not communicate directly — the discovery process included rate negotiation to determine the highest common speed tier. A FIR-capable device would fall back to SIR when connecting to a SIR-only device

IrDA Encoding Comparison:

  SIR (115.2 kbps):  RZI encoding
  ┌───┐     ┌───┐
  │   │     │   │
  ─┘   └─────┘   └─────  = 1 0 1
  ←1.63μs→← 8.68μs →
  (3/16 duty)

  FIR (4 Mbps):  4PPM encoding
  Slot:  [0] [1] [2] [3]
  00  =  █░░░░░░░
  01  =  ░░░█░░░░
  10  =  ░░░░░░█░
  11  =  ░░░░░░░█
  Each symbol = 2 bits in 500ns

IRDA in Practice

Understanding the practical experience of using IRDA reveals why it succeeded briefly and why it was replaced so thoroughly:

• The IrDA port on old laptops: A small dark-red or black plastic window (typically 8mm × 3mm) on the side or front edge of the laptop housing. Inside was a Vishay TFBS4556 or similar transceiver module containing an IR LED and photodiode in a single package. The port was wired to a 16550 UART at 115.2 kbit/s. Windows 95/98 included built-in IrDA support — enabling the port in Device Manager would make the laptop discoverable and allow file transfer via the "Wireless Link" feature. Setup was notoriously finicky: drivers conflicted, discovery failed repeatedly, and transfer speeds of 115 kbit/s meant a 1MB file took over a minute to beam
• Legacy uses that survived: The IrDA port on old Toshiba and Dell laptops could still be found in enterprise environments as late as 2012, used for inventory scanning in warehouses. Barcode scanners from Symbol and Honeywell maintained IrDA interfaces for compatibility with legacy warehouse management systems. Medical device manufacturers (GE Healthcare, Philips) kept IrDA on patient monitors because it provided a guaranteed point-to-point link with no RF interference — critical in MRI rooms where RF signals cause artifacts
• Why IrDA disappeared from phones: By 2003, Nokia and Motorola began removing IrDA ports from phones in favor of Bluetooth. The practical experience was decisive: IrDA required physically pointing two phones at each other within 1 meter, while Bluetooth worked at 10 meters through pockets and bags. NFC (Near Field Communication) provided the tap-to-transfer convenience that IrDA attempted but with much simpler hardware. By 2007, no major smartphone manufacturer included IrDA. The transition was rapid — within 3 years (2003–2006), IrDA went from standard to extinct in mobile devices
• The Palm Pilot experience: The quintessential IrDA use case. Two Palm Pilot owners would sit across a table, align the IR windows, and tap "Beam" in the address book. A progress bar would appear as the vCard transferred at 115.2 kbit/s. The process took 2–5 seconds for a typical business card. It felt futuristic in 1997 but was quickly superseded by Bluetooth beaming (2002) and eventually by QR codes and NFC (2010s) which required zero alignment