RS232 to Ethernet Cable Pinout: Two Common Wiring Diagrams

• Facebook
• Twitter
• Reddit
• LinkedIn

🔍 Technical Review & Standards Reviewed by the Valtoris Industrial Networking Team. > The wiring diagrams provided in this guide strictly adhere to EIA/TIA-232-F serial communication standards and TIA/EIA-568-B Ethernet cabling specifications to ensure safe signal transmission.

If you looked up “rs232 to ethernet cable pinout ” you are probably thinking of two things.

• You have a device with an RS232 port that uses an RJ45 connector (common on industrial PLCs, network gear, and access control systems). You need to connect it to your computer’s DB9 serial port.

• You want to use cheap Ethernet cable to extend an RS232 connection beyond the standard 15-meter limit, because official RS232 cables are expensive.

Either way you need to know which wire goes where.

Lets be clear: RS232 and Ethernet are different. You can’t plug an RS232 device into an Ethernet port. Don’t expect it to work just by plugging it in. However, you can use the internal wires of an Ethernet cable to carry RS232 signals. The trick is getting the RS232 to ethernet pinout right.

⚠️ Crucial Note Before You Wire: A DIY RS232-to-RJ45 cable is a passive connection. It simply uses Ethernet wires to carry serial signals up to 15 meters. It will NOT put your RS232 device onto your local IP network (LAN). > If you need to access your serial device via an IP address, or want to connect it to an Ethernet switch, a passive cable will fail (and may burn your board if plugged into PoE). True network access requires an active conversion architecture to encapsulate serial payloads into TCP/IP packets.

Here’s a number that might surprise you: RS232 is still used in 30–40% of industrial equipment —PLCs, scales, CNC machines, medical devices, and test equipment. It’s been around since 1969, and it’s not going away anytime soon.

But here’s the frustrating part: 25–30% of communication failures in serial networks come from simple wiring errors. Another 15–20% come from grounding mistakes. If you’ve ever connected everything “correctly” and gotten nothing but garbage data or dead silence, you’re not alone. This guide covers not just what connects where, but why it works that way, and—most importantly—what to check when it doesn’t.

The “TX/RX Cross” Mystery: Null Modem vs. Straight-Through

The most common reason for a “silent” connection is getting the TX and RX lines backward.

Three wires are all you need for basic communication:

The Rule: TX on one end connects to RX on the other. Data needs a path, and ground gives it a reference. Why cross them? Because one device’s “transmit” must go to the other device’s “receive.” If you connect TX to TX, nothing happens—they are both trying to talk, and nobody is listening.

Identifying Your Device: DTE vs. DCE

To get the wiring right, you must identify your device type:

• DTE (Data Terminal Equipment): Like your PC or a PLC.
• DCE (Data Communication Equipment): Like a modem or some Ethernet converters.

When to cross: If you connect two DTE devices (like a PC to a PLC), you must use a Null-Modem cable to cross pins 2 and 3. It is essential to keep these roles seperate to avoid damage or communication silence.

⚠️ Stuck on RX/TX Swap? Check your Frame with our Modbus CRC Calculator

Core Connector Pinouts: DB9 and RJ45

DB9 Connectors (The Traditional Standard)

Most RS232 devices use a DB9 connector. DB9 pins are numbered, and for standard communication, you only care about three:

If both ends are DB9: You need a null-modem cable that crosses pins 2 and 3.

• Converter pin 3 → Device pin 2
• Converter pin 2 → Device pin 3
• Pin 5 → Pin 5

RJ45 Pinout (T568B Standard)

Ethernet cable uses 8 wires with standard colors. The T568B wiring is most common:

For RS232, we only need a few of these wires. You can assign colors yourself—just write down what you used.

👇 Skip the confusing tables! Use our interactive pinout generator below to instantly map your DB9 to RJ45 connections—and verify if your DIY setup is physically safe:

A3 Printable

🛠️ RS232/RS485 Field Cheat Sheet (PDF)

The complete physical layer reference guide. Formatted for high-res A3 printing. Download it directly for your toolbox—no email required.

Download High-Res PDF

Feel free to print it out and pin it on your server rack.

Three Common Industrial Scenarios

Scenario 1: DB9 to RJ45 (The Console Standard)

Many devices, such as PLCs, door controllers, and network switches, use RJ45 jacks for their serial ports. To connect these to your computer, you need a cable going from the RJ45 port on the device to the DB9 port on your computer.

Standard DB9 to RJ45 Pinout:

This wiring follows the standard DTE (Data Terminal Equipment) configuration, which is the case for almost all modern computers.

If your device is DCE (Modems or specific converters):

Always check the manual of your specific equipment. Manufacturers like Cisco, Digi, and Siemens often have their own pinout standards.

Scenario 2: Terminal Blocks

Common in industrial converters, these feature three screws labeled TX, RX, and GND:

Scenario 3: Using Ethernet Cable as RS232 Extension

The RS232 standard technically limits communication to 15 meters (roughly 50 feet). Beyond that, signal degradation and noise become significant issues. Ethernet cable (Cat5e or better) is an excellent option for extending this range because its twisted pairs help negate interference.

For Longer Runs: If you must go further using Cat5 or Cat6, you need to lower the baud rate (e.g., from 115200 to 9600) to compensate for signal loss and capacitance.

💡 Pro Tip for Distances Over 15m: Extending RS232 passively over long Cat5e runs introduces severe voltage drops and electromagnetic interference (EMI). In these scenarios, standard practice shifts from physical wiring extension to network encapsulation. By moving the RS232 signal onto the LAN at the edge, distance-based voltage drop is completely eliminated.

If both ends are DTE (computer to computer, or computer to most equipment):

This is a null modem crossover cable. TX on one end goes to RX on the other.

If one end is DTE and the other is DCE (rare):

Professional Tip: To maximize the anti-interference benefits of Cat5/6 cable, never put TX and RX on the same twisted pair. Instead, pair TX with a Ground wire and RX with another Ground wire. This gives the signal better protection and it is more stable when it has to travel a long way which is really important in noisy industrial environments.

What About Flow Control (RTS/CTS)?

The setups above use only three wires, which is sufficient for most applications as many devices don’t require hardware flow control. However, if your device requires RTS/CTS:

Use the same color scheme throughout and document it. You’ll thank yourself later when troubleshooting.

The $5,000 Grounding Mistake

You have to connect ground every time. Without it, the signals have no reference. Data will be garbled or completely missing. But here’s the nuance: shield ground is not the same as signal ground.

• Signal ground (pin 5 on DB9) carries the reference voltage for the data. It must be connected.
• Connecting the shield at both ends creates ground loops—current flows through the shield, inducing noise on your data lines. This is a common but costly mistake.

A $5,000 Lesson: A factory once put in a long RS232 cable that was connected to the ground at both ends.  Every time a nearby machine started, the computer screen would flicker and crash. They lost over five thousand dollars in downtime while trying to find the error. When they removed the ground from one end of the RS232 cable the problem with the RS232 cable went away away. 

Systematic Troubleshooting: The Loopback Test

When your wiring seems okay but nothing is working, do not guess. Test it. The Loopback Test is a way to isolate the problem on your own without special tools.

1. Disconnect the cable at the device end.
2. Jumper TX to RX: Use a small wire to connect the Transmit pin to the Receive pin on the connector.
3. Send Data: Use a terminal program (like Putty). If what you type appears on the screen, your converter and cable are perfect. If not, the link is broken.

Decision Flowchart: When It Doesn’t Work

• Step 1: Verify Continuity Use a multimeter to confirm that TX on one end connects to RX on the other (not to itself), RX connects to TX, and GND connects to GND .
• Step 2: Check Power Confirm both the converter and the end device are powered. If they are not, nothing works.
• Step 3: Verify Serial Settings Baud rate, parity, data bits, and stop bits must match perfectly . A common mistake is a device at 9600 baud while the converter is at 19200.
• Step 4: Check Software & Addresses If using Modbus, is the device ID correct? Ensure your software points to the correct COM port or IP address.
• Step 5: Local Loopback Perform a loopback test directly on the device ports. If the device cannot read its own transmission, the problem lies within the device hardware, not the cable.

Frequently Ask Questions

🛡️ Why Valtoris Shares This Pinout Guide

“At Valtoris, we design and manufacture active industrial networking gear (like LTE routers and IP serial servers). So why provide a DIY passive wiring guide? Because our engineers started in the field, too. We know what it’s like to be stuck on a factory floor at 2 AM, desperately needing to splice a CAT5 cable to a DB9 port just to get a legacy PLC talking again. We provide these diagrams to help you get out of a jam today. Because we understand the value of knowing the physical layer inside and out. When your topology outgrows passive cabling and requires active TCP/IP routing, you’ll know exactly why.”

📚 Related Industrial Connectivity Guides

If you are redesigning your serial network topology, these guides cover advanced methods to bypass physical cabling limitations: