The Rise and Fall of IrDA: When Infrared Ruled Short-Range Communications

Light has always been humanity's most visible tool for communication, from ancient signal fires to modern fiber optics. Yet between these extremes lies a less-traveled path: free-space optical (FSO) communications—the use of modulated light without a confined guide. While FSO might seem like a niche technology today, it once enjoyed a golden age as the foundation for IrDA (Infrared Data Association), the standard that briefly dominated short-range wireless connections before being eclipsed by radio frequency alternatives.

Origins: From Calculator Printers to Industry Standard

The story of IrDA begins not with grand ambitions for wireless networking, but with a practical problem faced by Hewlett-Packard in the 1980s. As scientific calculators evolved toward pocket-sized computers, users needed a way to transfer data without cables. HP's solution was the 82240B wireless printer, which used infrared light to communicate with calculators. This simple unidirectional protocol, called "RedEye," evolved into HP SIR (Serial InfraRed), a bidirectional system that emulated RS-232 serial connections through infrared pulses.

By 1993, HP recognized that this technology had broader potential. The company hosted an industry meeting that led to the formation of the Infrared Data Association, bringing together over fifty companies from consumer and industrial electronics. Within years, IrDA's membership grew to include tech giants like IBM, Microsoft, and Apple. Commercial adoption followed quickly—by the late 1990s, IrDA transceivers were ubiquitous in phones, printers, and computers.

Technical Architecture: A Layered Approach

IrDA's protocol stack reflected both its origins and its aspirations:

Physical Layer: From SIR to GigaIR

The foundation of IrDA was its physical layer, which evolved significantly over time:

• SIR (Serial Infrared): The original 115 kbps standard derived directly from HP's implementation
• MIR (Medium Infrared): Introduced in IrDA 1.1 (1995), operating at 1 Mbps
• FIR (Fast Infrared): Increased to 4 Mbps in 1998
• VFIR (Very Fast Infrared): Reached 16 Mbps by 2001
• UFIR/GigaIR: Theoretical standards reaching 96 Mbps and 1 Gbps, though never widely implemented

Each iteration addressed limitations of its predecessor. For example, MIR incorporated bit-stuffing from IBM's SNA/HDLC protocols to solve clock synchronization issues at higher speeds. By the VFIR era, the "basically RS-232 over an LED" approach had given way to more sophisticated line coding similar to radio protocols.

Link Layer: IrLAP and Discovery

The IrLAP (Link Access Protocol) handled discovery and connection establishment. When a device wished to communicate, it transmitted random 32-bit IDs in a beaconing process. Other devices detected these beacons and responded in randomly selected time slots, negotiating supported speeds in the process.

This approach reflected a fundamental limitation of infrared communication: the line-of-sight requirement. IrDA specifications accommodated connections of up to one meter within a 30-degree cone at each device. While the protocol theoretically supported multi-point connections, practical constraints limited it to point-to-point applications in most implementations.

Management and Transport Layers

IrLMP (Link Management Protocol) operated above IrLAP, providing two key services:

• LM-IAS (Link Management Information Access Services): A discovery protocol for applications
• LM-MUX (Link Management Multiplexing): Allowed multiple logical connections over a single IrLAP interface

TinyTP, a transport protocol similar to TCP, provided reliable delivery and segmentation for large payloads. Notably, TinyTP and IrLMP used the same LSAP (Link Service Access Point) selector format, creating an interesting architectural constraint where connections to the same service couldn't be differentiated between the two protocols.

Application Protocols

The IrDA stack supported several application protocols:

• IrCOMM: Emulated traditional serial and parallel ports over IrDA
• IrJetSend: Enabled complex printer interactions from client devices
• OBEX (Object Exchange): A general-purpose protocol for file transfer and object manipulation

OBEX deserves special attention as it represented IrDA's most successful attempt at interoperability. Operating over TinyTP, OBEX used simple GET and PUT operations similar to HTTP, enabling applications like business card exchange and photo sharing between devices—a functionality that would later be called "squirting." This term, popularized by Microsoft's Zune but actually originating from HP's CoolTown research project, captured the brief, direct nature of these transfers.

Applications and Ecosystem

IrDA found success across several domains:

Printing and Industrial Use

HP's leadership in printers made IrDA natural for wireless printing applications. Industrial diagnostics and programming also adopted IrDA as a drop-in replacement for serial ports, leveraging IrCOMM's full emulation of RS-232 control signals.

Mobile Device Communication

The rise of PDAs created a perfect use case for IrDA. Early digital cameras used IrDA for image transfer, and PDAs employed it for synchronization. In Japan, IrDA even enabled sending images over specially equipped payphones—a reflection of the country's unique technological adoption patterns.

File Sharing and "Squirting"

Perhaps the most visible application was file sharing between mobile devices. Users could exchange business cards, photos, and other small files by simply pointing their devices at each other. This functionality, while limited by IrDA's speeds and line-of-sight requirements, represented an early vision of ad-hoc device-to-device communication that would later be realized through technologies like Apple's AirDrop.

Technical Limitations

Despite its success, IrDA faced inherent limitations:

Physical Constraints

The line-of-sight requirement imposed strict orientation constraints. Devices needed to be precisely aligned and within one meter of each other, making multi-device networking impractical. Sunlight could also interfere with communication, a significant limitation for mobile devices used outdoors.

Architectural Limitations

The LSAP selector's seven-bit limitation (128 possible values) constrained the number of concurrent connections. The inability to differentiate between IrLMP and TinyTP connections to the same service created additional complexity.

Speed Evolution

While IrDA speeds increased from 115 kbps to 16 Mbps, this progress couldn't keep pace with emerging RF technologies. The theoretical GigaIR standard arrived too late to make a practical impact, as IrDA's ecosystem was already in decline.

Decline and Legacy

Several factors contributed to IrDA's decline:

Competition from RF Technologies

Bluetooth and Wi-Fi offered greater flexibility without line-of-sight requirements. Wi-Fi enabled connection to networks, eliminating the need for device-to-device synchronization. Bluetooth, despite its own complexities, provided more convenient pairing and multi-device support.

Economic Factors

As mobile devices incorporated Bluetooth and Wi-Fi, the cost of adding IrDA became less justifiable. Integration of RF modules meant Bluetooth was effectively "free" in many devices, making IrDA's cost advantage disappear.

The iPhone Effect

The iPhone's launch in 2007 marked a turning point. By omitting IrDA support, Apple effectively ended IrDA's relevance in the mobile space. Without mobile devices, IrDA became a solution without a problem.

Unfulfilled Potential

IrDA had promising developments that never reached maturity:

• IrLAN: Attempted to implement IP over IrDA with Wi-Fi-like architecture
• AIR (Advanced Infrared): IBM's overhaul to support multi-point networking
• IrSimple: 2005 improvements focused on Japanese market needs

Enduring Applications

Despite its decline in consumer devices, IrDA found lasting applications in specialized domains:

• Embedded Systems: Power meters, medical devices, and industrial equipment
• Security Applications: Where physical opacity provides inherent security
• Regulatory Environments: Where RF communications are restricted
• Cost-Sensitive Implementations: IrDA can be implemented with minimal components using bit-banged GPIO or unused UARTs

Lessons from IrDA

The story of IrDA offers several insights into technology adoption and obsolescence:

1. Ecosystem Effects: A technology's success depends not just on its technical merits but on the ecosystem that supports it. Once mobile device manufacturers dropped IrDA support, the standard's relevance diminished rapidly.

2. Physical Limitations Matter: Technologies that impose physical constraints (like line-of-sight) face significant adoption challenges compared to more flexible alternatives.

3. Standardization vs. Innovation: While standardization enabled interoperability, IrDA's evolution was sometimes constrained by its early design decisions, particularly in multi-point support.

4. The Problem Without a Solution: IrDA excelled at device-to-device communication but arrived just as mobile devices were shifting toward network-centric connectivity.

Conclusion

IrDA represents an interesting case study in technological evolution. It was a technically sound solution that addressed real problems in its time, with a sophisticated protocol stack that enabled various applications. Yet it ultimately couldn't compete with the flexibility and ecosystem advantages of RF technologies.

The infrared communication standard's legacy lives on in specialized applications and in the DNA of subsequent short-range wireless technologies. Its brief golden age reminds us that even well-designed technologies can fade when they no longer fit the evolving needs of users and the devices they employ.

As we explore new frontiers in wireless communication—from Li-Fi to ultra-wideband—IrDA's story offers valuable lessons about the interplay between technical capabilities, user needs, and market forces that shape which technologies thrive and which become footnotes in technological history.