RS232 VERSUS USB
If you have purchased a new computer recently you may have noticed the complete lack of a conventional RS-232 COM port. The domestic market’s embrace of USB does not however mean that the serial COM port is dead.
Serial communication was originally developed for the teletype (nickname for a teletypewriter and trademark of the Teletype Corporation USA), an electro-mechanical marvel that emerged in the 1920’s for transmitting messages from one point to another. Some even used punched paper tape so you could relay information output from one teletype and feed the strip into another. The photo here is of the famous model ASR-33 manufactured by the Teletype Corporation USA from 1968 (courtesy of NADCOMM)
Teletypes were adapted as the means of getting information into and out of early computers and in 1969 the RS-232-C standard emerged. The first VDU terminals (or ‘Glass Teletypes’ as they were originally called) were developed to be compatible with the old mechanical teletypes and the RS-232 protocol along with start/stop and parity bits was reborn into our computer age as the COM port. The photo here shows the VT05 manufactured by Digital in 1970 (courtesy of Paul Williams at VT100.net)
The ability for RS-232 to be implemented mechanically made it easy to synthesise electronically. The protocol’s simplicity meant that unsophisticated devices could be controlled without internal firmware and led to its widespread adoption in industrial automation. Programmable Logic Controllers were configured using a serial device like you see here, the 5TI Programmer from Texas Instruments in 1974 (courtesy of Joerg Woerner at Datamath.org). This programmer doesn’t have a microcontroller inside, instead it uses discrete logic integrated circuits.
In 1995, speed and elegance eventually inspired the USB protocol and the concept of universal ‘plug-and-play’. USB devices identify themselves upon connection to a host OS which then configures itself to communicate with that device by installing the appropriate drivers or by ‘graceful failure’, prompting the user to insert a disk.
USB is an unnecessary complication in dedicated environments such as a vehicle installation. A taxicab may have a taximeter that communicates its fare and tariff information via RS-232 to a data terminal or printer. The popular Aquila T2 taximeter shown here is only one example. These devices need to be compatible but don’t require the overhead of plug-and-play intelligence.
Although low cost serial to USB semiconductors may make the concept of a USB taximeter possible, creating the USB host for it becomes a nightmare. Any unit with a USB host socket on it implies acceptance of a whole range of USB devices. Deciding what devices to support, communicating a lack of support to the user (graceful failure), and then installing that support, brings pointless complication and cost.
Like USB, integrating multiple RS-232 devices requires a communications hub. However, because RS-232 is not ‘universal’, integration may require some processing and device configuration via a simple human interface. The demand for more elaborate RS-232 environments has now prompted the emergence of devices like the Datax3 terminal which fills the gap between multiple serial devices and an ergonomic interface flexible enough to cater for interaction with that environment.
USB is great for the domestic computer market but in dedicated environments the traditional serial RS-232 communications port is still very much alive.