LLMpediaThe first transparent, open encyclopedia generated by LLMs

RS-232

Generated by GPT-5-mini
Note: This article was automatically generated by a large language model (LLM) from purely parametric knowledge (no retrieval). It may contain inaccuracies or hallucinations. This encyclopedia is part of a research project currently under review.
Article Genealogy
Parent: Modbus Hop 5
Expansion Funnel Raw 84 → Dedup 0 → NER 0 → Enqueued 0
1. Extracted84
2. After dedup0 (None)
3. After NER0 ()
4. Enqueued0 ()
RS-232
RS-232
Aeroid · CC BY-SA 4.0 · source
NameRS-232
Introduced1960
StandardEIA-232
CreatorElectronic Industries Association
Applicationserial communication
Connector25-pin D-subminiature, 9-pin D-subminiature
Voltage levels±3 to ±15 V typical
Baud rateup to 20 kbps practical, higher with extensions
SuccessorsRS-422, RS-485, USB, Ethernet

RS-232 is a standard for serial binary data transmission between data terminal equipment and data communication equipment defined by the Electronic Industries Association. It specifies electrical signal levels, timing, and connector pinouts for point-to-point communication and became foundational to early computing, telecommunications, and instrumentation. Engineers, manufacturers, and regulators in the United States and internationally adopted RS-232 for modem links, terminal interfaces, and peripheral connections.

Overview

RS-232 describes voltage-based signaling, handshaking control lines, and mechanical connector configurations that enabled interoperability among devices produced by companies such as Bell Labs, AT&T, Data General, IBM, and DEC. The standard influenced products from Hewlett-Packard, Siemens, Sony, Fujitsu, and RCA and was implemented in designs by firms including Intel, Motorola, Texas Instruments, National Semiconductor, and Western Digital. Academic and industrial laboratories at MIT, Bellcore, Stanford University, Caltech, and Carnegie Mellon University evaluated RS-232 behavior in serial links and influenced related interface research.

History and Development

Work leading to RS-232 involved committees of the Electronic Industries Association and collaboration with Bell Labs and manufacturers such as IBM and AT&T during the late 1950s and 1960s. Early telecommunications infrastructure projects at Western Electric and modem developments at Hayes Microcomputer Products and Rockwell International drove practical requirements. Military and aerospace testing at NASA facilities and procurement standards influenced robustness expectations adopted by vendors including Honeywell and General Electric. Revision cycles and reinterpretations paralleled initiatives at ANSI, IEC, ITU-T, and industry consortia that later fostered alternatives such as efforts from TIE (Telecommunications Industry Association) and standardization discussions involving IEEE committees.

Physical and Electrical Specifications

The original RS-232 defined signal voltages where logical "1" (mark) and "0" (space) correspond to negative and positive voltages respectively relative to signal common, with typical amplitudes in the ±3 V to ±15 V range. Implementations used drivers from semiconductor manufacturers including Maxim Integrated, Analog Devices, Fairchild Semiconductor, Intersil, and Exar Corporation. Character timing and bit framing followed conventions used by systems from DEC and Data General and matched serial line strategies common in terminals made by Wyse Technology and Televideo. Line protection and transient suppression practices were informed by standards and equipment from 3M, Schneider Electric, Eaton Corporation, and Philips.

Signal Protocols and Handshaking

RS-232 defines control signals such as Request To Send, Clear To Send, Data Set Ready, Data Terminal Ready, Carrier Detect, and Ring Indicator, used for modem control and device readiness negotiation. Implementations used these signals in terminal-server configurations sold by Cisco Systems, 3Com, and Juniper Networks as well as in modem products from Motorola and Zoom Telephonics. Software stacks in operating systems from Microsoft, Apple, Novell, Sun Microsystems, and Commodore provided serial port drivers that interpreted hardware handshaking for file transfer protocols like those developed by Ward Christensen and Tom Jennings, and XMODEM, YMODEM, and ZMODEM variants.

Connectors and Pinouts

While the full RS-232 specification referenced a 25-pin D-subminiature connector used in endpoints from manufacturers such as Amphenol, many personal computers and terminals adopted the 9-pin DE-9 variant popularized by IBM PC/AT clones and produced by suppliers including TE Connectivity and Molex. Pin assignments for signals were standardized so that modems from U.S. Robotics and Hayes could interoperate with terminals by DEC and Tektronix; cable wiring conventions and null-modem arrangements were documented in application notes by Intel and Microsoft.

Uses and Applications

RS-232 found widespread use connecting telecommunication modems in networks of AT&T and early internet service providers, instrumentation from Agilent Technologies and Fluke Corporation, industrial automation hardware by Siemens and Rockwell Automation, and point-of-sale terminals from NCR Corporation. Laboratory equipment at Bell Labs, Sandia National Laboratories, and Los Alamos National Laboratory often employed RS-232 for control and data logging. In broadcast and avionics, vendors like Thales Group and Northrop Grumman used RS-232 for configuration and diagnostics. Consumer electronics from Panasonic, Sony, and Sharp also included serial ports for service and firmware updates.

Limitations and Successors

RS-232's limitations include short reliable cable lengths at higher bit rates, susceptibility to ground loops and electromagnetic interference, and minimal support for multipoint topologies. These constraints motivated adoption of balanced differential standards such as RS-422 and RS-485, and later serial and network replacements like USB, Ethernet, IEEE 1394, Bluetooth, and Wi‑Fi. Industrial and embedded systems shifted toward fieldbus and serial standards including CAN bus, Modbus, PROFIBUS, and LonWorks while telecom infrastructures migrated to packet-oriented protocols championed by IETF working groups and vendors such as Cisco Systems and Juniper Networks.

Category:Telecommunications standards