The RS232C pin layout defines the physical and electrical connections for legacy serial communication between data terminal equipment and data communication equipment. Understanding each signal helps engineers troubleshoot, design adapters, and maintain industrial and point-of-sale systems that still rely on this standard.
Below is a quick reference table summarizing key aspects of the RS232C pin configuration and typical usage in modern implementations.
| Pin Number | Signal Name | Direction | Common Use |
|---|---|---|---|
| 2 | TXD (Transmit Data) | Out | Send data from DTE to DCE |
| 3 | RXD (Receive Data) | In | Receive data at DTE |
| 4 | DTR (Data Terminal Ready) | Out | Indicates terminal is ready |
| 5 | Signal Ground | Reference | Common ground reference |
| 6 | DSR (Data Set Ready) | In | Indicates device is ready |
| 20 | DTE Ready (DCD Carrier Detect) | In | Carrier signal detected |
| 22 | RI (Ring Indicator) | In | Incoming call signal |
| 23 | RTS (Request To Send) | Out | Request permission to send |
| 24 | CTS (Clear To Send) | In | Device ready to receive |
RS232C Pin Function Definitions
Each pin in the RS232C connector carries a specific logical function that governs handshaking and data flow. Correct mapping prevents communication failures and interface damage.
Data Pins TXD and RXD
TXD on pin 2 carries serial data from the terminal to the device, while RXD on pin 3 receives data from the device to the terminal. Both operate in asynchronous mode with agreed baud rate, parity, and stop bits.
Hardware Handshake Signals
RTS and CTS manage flow control so that the sender pauses when the receiver buffer is full. DTR and DSR indicate readiness, ensuring that both sides are powered and initialized before data transfer begins.
RS232C Pinout Connector Types
Different form factors such as DB-9 and DB-25 define pin positions and signal assignments. Adapters must respect these layouts to avoid cross-wiring that leads to intermittent faults or permanent hardware issues.
Wiring and Signal Integrity Considerations
Correct wiring requires attention to shielding, return paths, and cable length limits to maintain signal integrity. Long or poorly shielded cables can introduce noise, causing framing errors or corrupted data in industrial environments.
Practical Recommendations for RS232C Deployment
Following best practices reduces integration issues and protects legacy equipment from electrical stress caused by incorrect hookups or environmental interference.
- Always verify pin mapping between devices before connecting cables.
- Use shielded twisted pair cables for longer runs to minimize noise pickup.
- Test handshaking lines in loopback mode to confirm proper DTE/DCE signaling.
- Keep cable lengths under recommended limits to preserve voltage levels.
- Label connectors and diagrams in field installations for quick maintenance.
FAQ
Reader questions
What is the correct RS232C wiring between two DTE devices without a modem?
You typically cross TXD with RXD, connect signal ground, and may loop back RTS to CTS and DTR to DSR to emulate carrier presence when testing null modem communication.
Why does my RS232C communication fail after cable replacement?
Check pin mapping, signal integrity, and voltage levels; verify that handshaking lines such as RTS/CTS and DTR/DSR are properly connected and that terminations match the cable length and environment.
Can RS232C operate at very high baud rates over long distances?
Standard RS23C is limited to relatively low baud rates over long cables due to rise time and noise susceptibility; in such cases, use drivers or opt for balanced interfaces like RS485 for extended reach.
How do I identify RS232C pin numbers on a DB-9 connector?
On a male DB-9 connector, pin numbers start at the top right as 1 and increase clockwise around the connector, with common signals such as TXD, RXD, and GND located on predictable positions.