Buying a USB to Serial Adaptor: A Practical Checklist
A USB to serial adaptor turns one USB port into a working RS-232 port that legacy equipment accepts. Inside, a bridge chip converts USB packets to UART framing, a level shifter raises the signals to RS-232 voltage, and a driver makes the port appear as a COM device. This guide covers what to verify before buying, from chip class to connector gender.
Quick Answer / Summary
The adaptor handles three jobs: USB device emulation, UART framing at 8N1, and level shifting to RS-232. It presents a COM port to the operating system and a DB9 to the field device. Buy for chip class, supported baud range, flow control pins, and the gender and wiring your device needs. Two adaptors in identical housings can behave differently once a driver loads.
What Happens Between USB and the DB9
The bridge chip is the core. An FTDI-class or Prolific-class part handles USB enumeration, buffers data, and drives a UART. It runs 8N1 by default and supports baud rates from about 300 up to 921600 on common parts.
Behind the UART, a level shifter converts 3.3 volt logic to RS-232 levels, roughly plus or minus 3 to plus or minus 15 volts. The DB9 exposes the nine standard signals: DCD, RX, TX, DTR, GND, DSR, RTS, CTS, and RI.
Small internal buffers, usually a few hundred bytes in each direction, absorb the difference between USB packet timing and the steady serial bit stream. Without that buffer, a host pausing between USB frames would inject gaps into the transmitted characters.
Chip Classes and Drivers
FTDI-class and Prolific-class bridges are the two families you meet most often. Each needs its own driver and reports its own COM number, so confirm driver support for your operating system before ordering.
What COM Port Emulation Means
Emulation is what keeps older software working. The driver presents a COM port with the usual baud, data bits, parity, and stop bit settings, so a program written for a hardware COM1 or COM2 opens the USB adaptor without changes. That is why DOS-era tools and legacy Windows applications still run against a modern laptop.
A First-Buyer Checklist
Confirm four items. First, the port you have: USB-A, USB-C, or a captive cable. Second, the connector your device needs, male or female DB9. Third, the wiring, straight-through or null modem. Fourth, whether the software expects hardware or software flow control.
Then check the baud rate your device actually uses. A bridge rated to 921600 covers most consoles, but older equipment running at 300, 1200, or 9600 baud needs a driver that still supports those rates cleanly.
Pins That Matter
A three-wire link needs RX, TX, and GND only. Add RTS and CTS when the device uses hardware handshaking, or DTR and DSR when those lines carry reset or presence signals.
Flow Control and Framing Basics
Flow control stops a fast host from overrunning a slow device. RTS and CTS are hardware lines: the receiver drops CTS to ask the sender to pause. XON and XOFF are characters inside the data stream, which suits three-wire links but breaks on binary data.
Framing is normally 8N1: eight data bits, no parity, and one stop bit.
Where Adaptors Fail in the Field
Two failures repeat. The first is a loose USB connection on a moving machine, which drops the COM port mid-job. The second is a wiring mismatch at the DB9, where a straight cable joins two DTE devices and nothing talks.
Strain relief and a locked connector solve the first, and a null modem crossover solves the second.
A third, quieter fault is a device that raises RTS and waits for CTS before it sends. On a three-wire lead that signal never arrives, and the device stays silent even though the wiring looks correct.
Comparison Table
| Item | What to Confirm | Why It Matters |
|---|---|---|
| Host port | USB-A, USB-C, or captive | Decides cable and housing |
| DB9 gender | Male or female device port | Prevents a gender changer |
| Wiring | Straight or null modem | Sets RX and TX roles |
| Flow control | RTS, CTS, or XON, XOFF | Controls data pacing |
| Baud rate | 300 to 921600 available | Matches device speed |
Table: Checklist points for a first serial adaptor
Practical Application Scenarios
- A technician upgrades a laptop and needs a console link to a switch at 9600 baud with 8N1.
- An integrator orders two adaptors for a lab and finds only one loads without a driver install.
- A field engineer meets a device that answers only after DSR is asserted by the host side.
- A plant team replaces a failed adaptor and must recheck wiring before the line restarts.
Related Products and Further Reading
- USB serial adaptor products – Compare adaptor housings, cable lengths, and connector options in one place.
- ask our support team – Share your device manual and we will confirm baud, framing, and wiring first.
- USB adapter and converter video guide – Watch installation steps for drivers, COM port assignment, and terminal setup.
- FTDI-class USB serial adapter – Review a bridge family that ships stable drivers across operating system versions.
Frequently Asked Questions
Do I need to install a driver?
Usually yes, though some current systems include a generic USB CDC driver. Check the bridge class your adaptor uses and confirm a signed driver exists for your operating system.
Can one adaptor work with several devices?
Yes. Baud rate and framing are set in software, so the same adaptor can serve a 9600 baud console and a 115200 baud controller, as long as the wiring matches each device.
What if the device needs 5 volt signals?
RS-232 devices accept the standard swing of roughly plus or minus 3 to plus or minus 15 volts. A bare TTL device is different and needs a level-converted port, not a raw UART pin.
Why is my COM port missing after sleep?
Some hosts unload the driver on suspend. Reconnect the adaptor, or disable USB selective suspend for that port, to keep the COM number stable across power events.