// September 8, 2026 · Crux Resolve LLC

DB9 does not mean RS232: how to identify a serial interface

A 9-pin D-sub connector is only a connector. Equipment manufacturers have used the same shape for RS232, RS485, CAN, TTL-level serial, video, proprietary signals, power, and custom wiring. Confirm the electrical interface before connecting a serial adapter or bridge.

Do not connect by connector shape alone. A wrong assumption about a DB9 port can produce a non-working link and, in some cases, expose equipment to signal levels or wiring it was not designed to accept.

Why DB9 and RS232 are often confused

PC serial ports made the 9-pin D-sub connector strongly associated with RS232. A common PC-style RS232 pinout uses pin 2 for receive data, pin 3 for transmit data, and pin 5 for signal ground, with other pins available for modem-control signals.

That convention is common, but the connector itself does not enforce it. The same physical shell can be wired for something completely different.

Step 1: find the device documentation

The strongest starting point is the equipment manual, service documentation, connector table, or manufacturer specification. Look for explicit wording such as:

RS232 or EIA/TIA-232,
RS485 or RS422,
TTL UART or logic-level serial,
CAN, CAN-H, or CAN-L,
TXD, RXD, and GND pin assignments,
baud rate, parity, data bits, and stop bits,
RTS/CTS or other hardware-control requirements.

If the documentation only says “serial” without identifying the electrical standard, do not assume RS232 yet.

Step 2: separate connector, electrical layer, and protocol

Three different ideas are often mixed together:

Connector: the physical DB9 shell and pins.
Electrical interface: RS232, RS485, TTL UART, CAN, or another signaling method.
Application protocol: the actual commands or binary messages exchanged by the equipment.

A WiFi-to-RS232 bridge can move serial bytes only when the equipment side is electrically compatible with RS232. It does not convert CAN or RS485 into RS232 simply because the connector looks familiar.

Step 3: check the documented pinout

For a conventional PC-style 9-pin RS232 DTE interface, pin 2 is commonly RXD, pin 3 TXD, and pin 5 signal ground. Additional pins may carry DTR, DSR, RTS, CTS, DCD, or RI.

But manufacturers can and do use nonstandard assignments. A DB9 carrying power on a pin that another device expects to be a signal line is a clear example of why documentation matters.

For the TX/RX orientation problem, see RS232 DTE vs DCE and Null-Modem Cables Explained.

Step 4: check the voltage standard if documentation is incomplete

When documentation is unavailable, electrical measurements can help distinguish interface families, but this should be done carefully and with an understanding of the equipment.

Traditional RS232 uses positive and negative voltage levels relative to ground, unlike TTL UART interfaces that typically remain between ground and a positive logic supply. RS485 uses a differential pair rather than a single TX and RX referenced in the same way as basic RS232.

Important: voltage measurements alone do not tell you the application protocol or guarantee that every pin is safe to probe. Documentation is still preferable whenever available.

Step 5: determine whether three-wire RS232 is enough

Many devices communicate using only TX, RX, and ground. Others depend on hardware flow control or modem-status lines.

If the equipment requires RTS/CTS, DTR/DSR, DCD, RI, BREAK behavior, or application-specific control-line states, a basic three-wire bridge may not be sufficient even when the port is definitely RS232.

Read 3-Wire RS232 Explained: TX, RX, and Ground for the difference between a basic data link and a full-handshake serial connection.

Common DB9 possibilities

True RS232

This is the familiar serial-port case. You still need the actual pinout, serial settings, and DTE/DCE orientation.

RS485 or RS422

These use differential signaling and need the appropriate physical-layer transceiver. A normal RS232 bridge is not an electrical substitute.

TTL or logic-level UART

The byte format may resemble ordinary asynchronous serial communication, but the voltage levels are different from RS232. Directly connecting incompatible electrical levels is not appropriate.

CAN or proprietary interfaces

A DB9 can carry CAN or a manufacturer-specific interface. The connector shape provides no protocol conversion.

Mixed signal and power

Some equipment uses otherwise familiar connector pins for power, enable signals, or custom control functions. That is another reason to verify the complete pin table first.

A practical pre-connection checklist

Find the manufacturer and exact model.
Locate the connector/pinout table in the manual.
Confirm the electrical interface explicitly says RS232.
Identify TX, RX, and signal ground.
Identify any required RTS/CTS or other control lines.
Record baud rate, data bits, parity, and stop bits.
Determine the DTE/DCE orientation or required cable crossover.
Confirm the host software can communicate through the transport you plan to use.

Where GhostBridge GB-01 fits

GhostBridge GB-01 is specifically a standard 3-wire RS232 bridge. Its current DB9 male interface uses pin 2 as RX into GhostBridge, pin 3 as TX out of GhostBridge, and pin 5 as signal ground.

The current hardware does not route RTS/CTS or the other DB9 modem-control lines. If your device documentation shows ordinary three-wire RS232 and compatible serial requirements, it is a much stronger candidate. If the manual shows RS485, CAN, TTL UART, or required hardware handshaking, the current GB-01 should not be treated as a direct electrical fit.