RS-232 — Serial Control Interface
RS-232 (EIA/TIA-232)
For RS-232 troubleshooting in context, see maintenance/av-troubleshooting-methodology. For RS-232 in VISCA camera control, see glossary/visca.
RS-232 is the EIA/TIA standard for point-to-point serial communication between two devices over a cable of up to ~15 m (at standard voltages). In AV, RS-232 is the most universally supported wired control interface — virtually every commercial display, projector, DSP, matrix switcher, and PTZ camera has an RS-232 port, and every control processor (Crestron, AMX, QSC, Extron) has multiple RS-232 ports. RS-232 carries ASCII text commands (most AV protocols) or binary byte strings (VISCA) between the control processor and the controlled device.
Electrical and Physical Characteristics
- Voltage levels: +3 to +15V = logic 0 (space); −3 to −15V = logic 1 (mark)
- Maximum cable length: ~15 m at 9600 baud (specified by EIA); practical installs run 30+ m with good cable and low capacitance
- Connector: DB-9 (9-pin D-sub, most common in AV equipment); DB-25 (25-pin, legacy); 3.5mm stereo jack (some compact AV gear); captive screw terminal (many rack-mount processors)
- Topology: point-to-point only — one transmitter, one receiver; not a bus
Serial Parameters (Port Configuration)
RS-232 communication requires both devices to be configured identically:
| Parameter | Common AV Defaults | Notes |
|---|---|---|
| Baud rate | 9600, 19200, 38400, 115200 | Most common: 9600 for displays/projectors; 38400 for some cameras |
| Data bits | 8 | Universal in AV |
| Parity | None (N) | Occasionally Even or Odd; rare in AV |
| Stop bits | 1 | Almost universal; some legacy devices use 2 |
| Flow control | None | Hardware (RTS/CTS) or software (XON/XOFF) occasionally required |
Notation: 9600 8N1 means 9600 baud, 8 data bits, No parity, 1 stop bit — the most common AV configuration. Always verify these parameters against the device's installation manual before assuming defaults.
DB-9 Pin Assignments
| Pin | Name | Direction (DTE perspective) |
|---|---|---|
| 1 | DCD (Data Carrier Detect) | Input |
| 2 | RXD (Receive Data) | Input |
| 3 | TXD (Transmit Data) | Output |
| 4 | DTR (Data Terminal Ready) | Output |
| 5 | GND (Signal Ground) | Reference |
| 6 | DSR (Data Set Ready) | Input |
| 7 | RTS (Request to Send) | Output |
| 8 | CTS (Clear to Send) | Input |
| 9 | RI (Ring Indicator) | Input |
For most AV control connections, only pins 2 (RX), 3 (TX), and 5 (GND) are used. A null-modem connection crosses TX and RX: pin 3 of one device → pin 2 of the other, and vice versa. This crossing is required when connecting two DTE devices (two control systems, or a control system to a device that is also configured as DTE). Many AV devices require a null-modem adapter or crossed cable. Verify the required wiring in the device's installation manual.
Command Terminators
RS-232 protocols in AV are terminator-sensitive. The control processor must append the exact terminator character(s) the device expects:
| Terminator | Meaning | Common In |
|---|---|---|
\r (CR, 0x0D) | Carriage Return | Most displays, projectors, Sony cameras |
\n (LF, 0x0A) | Line Feed | Some Linux-based devices |
\r\n (CRLF) | Carriage Return + Line Feed | Some devices, Windows convention |
FF (0xFF) | End of VISCA command | All VISCA cameras |
| None (binary) | No terminator; fixed-length frames | Some binary protocols |
A display expecting \r that receives \r\n will ignore the command — the extra \n byte corrupts the next command. Always check the protocol document for the exact terminator.
RS-232 vs. IP Control
| Factor | RS-232 | IP Control (TCP/UDP) |
|---|---|---|
| Distance | 15 m (spec); 30+ m practical | LAN: unlimited |
| Connections per port | 1 (point-to-point) | Multiple (TCP server can handle clients) |
| Setup complexity | Simple | Requires network configuration |
| Latency | Very low (µs) | Low (< 10 ms on LAN) |
| Feedback | Polling required | Event-driven possible |
| Cable cost | Low | Requires Ethernet infrastructure |
For long distances or when network control is preferred, RS-232 to IP converters (Digi AnywhereUSB, Lantronix UDS, etc.) or TCP/IP Telnet interfaces built into the device allow IP control. Many modern AV devices offer both RS-232 and LAN (Telnet/TCP) with the same command set.
Common Pitfalls
-
Baud rate or parameter mismatch producing garbled responses or silence. If the parameters don't match, the receiving device sees noise instead of commands and either ignores them or echoes garbage. Fix: verify baud rate, data bits, parity, and stop bits against the device manual before any other troubleshooting; use a port monitor to confirm commands are being sent.
-
TX/RX not crossed, producing no communication. Both devices are transmitting on their TX pins and listening on RX — neither receives the other's signal. Fix: verify the wiring; use a null-modem cable or adapter for DTE-to-DTE connections; test by temporarily looping TX to RX on each connector to confirm the control system's serial port is functioning.
-
Wrong command terminator causing commands to be silently ignored. The device receives the command bytes but the terminator does not match its expected value, so it discards the partial frame. Fix: check the protocol document for the exact terminator; use a port monitor to verify the transmitted bytes match the expected frame including the terminator.
-
Cable longer than practical RS-232 limit causing intermittent communication. RS-232 over 30–50 m with standard cable capacitance degrades signal rise time, causing bit errors at higher baud rates. Fix: run at 9600 baud (lower baud = more tolerance for cable capacitance) for long runs; use RS-422 or IP serial extender for runs over 50 m.