Serial (RS-232) and USB Programming Interfaces

Two-Way Radio Concepts and Electronics Fundamentals · Last updated · About 4 min read

RS-232 Basics

RS-232 is the decades-old standard for point-to-point serial data between a computer (DTE — Data Terminal Equipment) and a device (DCE — Data Communications Equipment). On the common DB9 (9-pin D-subminiature) connector, the essential pins from the PC's point of view are:

  • Pin 2 — RD (Receive Data): data into the PC
  • Pin 3 — TD (Transmit Data): data out of the PC
  • Pin 5 — SG (Signal Ground): the shared reference

The remaining pins carry hardware handshaking signals (RTS/CTS — Request To Send/Clear To Send, DTR/DSR — Data Terminal Ready/Data Set Ready) that some equipment uses for flow control or even repurposes for keying functions.

Both ends must agree on the line settings:

  • Baud rate — bits per second (9600 is a very common default for maintenance ports; other common values include 19200, 38400, 57600, 115200)
  • Data bits, parity, stop bits — most equipment today uses 8-N-1 (8 data bits, no parity, 1 stop bit)
  • Flow control — none, hardware (RTS/CTS), or software (XON/XOFF); a flow-control mismatch typically shows as a connection that works briefly then hangs

Straight-through vs null-modem cables: a straight-through cable connects a DTE (PC) to a DCE (device) — each transmit pin lands on the other end's receive pin because the two device types define the pins oppositely. Connecting two like devices (PC to PC, or a device wired as DTE) requires a null-modem cable, which crosses TD/RD (and usually the handshake pairs). Symptom of using the wrong one: dead silence in both directions with all settings correct.

USB-to-Serial Adapters

Modern PCs lack real RS-232 ports, so USB-to-serial adapters are everywhere in radio work. Realities to know:

  • The adapter contains a chipset — FTDI and Prolific are the two most common — and needs a matching Windows driver, which presents the adapter as a virtual COM port.
  • Counterfeit chips are a real problem, particularly in cheap cables. Official FTDI and Prolific drivers have historically refused to work with (or deliberately disabled) counterfeit chips, so a cable that worked for years can die after a driver update via Windows Update. If a previously working cable stops after an update, suspect this before suspecting the radio.
  • Adapter quality varies in less visible ways too: some do not implement handshake lines correctly or add latency that timing-sensitive programming protocols dislike. Keep a known-good adapter in the kit and treat it as reference hardware.

Windows COM Port Behavior

  • Windows assigns each serial device a COM port number (COM1, COM3, COM7, …). See what's present in Device Manager → Ports (COM & LPT); unplugging and replugging while watching the list identifies which entry is your cable.
  • The COM number can change when the same adapter is plugged into a different USB port — Windows may treat it as a new device and assign the next free number. Programming software configured for COM3 then fails until repointed. Plugging the adapter into the same physical USB port each time keeps the number stable; the number can also be manually reassigned in the device's advanced port settings.
  • A device shown with a warning icon in Device Manager means a driver problem — resolve that before troubleshooting anything in the radio software.
  • Only one program can open a COM port at a time; a background application holding the port produces "access denied" or "port in use" errors in the programming software.

Radio Programming Cables Are Not Just Cables

Many radio programming cables contain active electronics — level shifters, USB-to-serial chips, or vendor-specific interface circuitry — molded into the connector or a bump in the cable. Consequences:

  • Cables are vendor- and model-family-specific and not interchangeable, even when the connectors physically fit. A cable for one radio line may enumerate on the PC yet fail (or worse, misbehave) on another.
  • The cable itself is a failure candidate: strain at the radio-end connector and broken conductors are common. Swap-test with a known-good cable early.
  • Genuine versus third-party cables matter for the same counterfeit-chipset reasons described above.

See Programming Motorola MOTOTRBO Radios and Programming Kenwood NEXEDGE Radios for vendor-specific programming workflows, and CodePlug for what is actually being read and written.

Troubleshooting Checklist

  1. Wrong COM port selected — verify in Device Manager which COM number the cable holds right now, and match the software to it.
  2. Driver missing or broken — warning icon in Device Manager, or no new COM port appears when the cable is plugged in. Reinstall the chipset driver.
  3. Port in use — close other terminal/programming software; reboot if the owner can't be found.
  4. Line-settings mismatch (direct RS-232 gear) — verify baud/parity/stop bits/flow control against the device's documentation.
  5. Cable/adapter hardware — swap in the known-good adapter and cable before condemning the radio or the software.
  6. Radio-side issues — radio not powered, not in the required mode for programming, or battery too low (some radios refuse programming on low battery).

This article is part of the CTI Products Knowledge Base. Questions about RadioPro or MCN products? Call +1 (513) 595-5900 or email info@ctiproducts.com.

Informational only. This article is general background and is not engineering, safety, legal or regulatory advice. Verify requirements with the equipment manufacturer and the applicable authority before relying on it. Product names and trademarks belong to their respective owners.