1. What is OBD2?
OBD-II (On-Board Diagnostics, Second Generation) is a standardized vehicle diagnostic interface mandated by the US EPA (since 1996) and the EU (EOBD, since 2001). The physical connector is a 16-pin female J1962 connector, typically located under the driver's side dashboard.
The OBD-II port provides access to the vehicle's ECU and, on newer vehicles, multiple other ECUs. It supports multiple communication protocols: ISO 9141-2 (K-Line), ISO 14230 (KWP2000), SAE J1850 (PWM and VPW), and CAN bus (ISO 15765). Most vehicles built after 2008 use CAN bus as the primary diagnostic protocol.
2. What is DB9?
DB9 (D-subminiature, 9-pin) is a common connector format. It is widely used for RS232 serial communication, but it is important to understand that DB9 is a connector, not a protocol. Depending on the device, a DB9 connector may carry:
- RS232 TX/RX signals
- CAN High / CAN Low
- K-Line / L-Line
- Power and ground
- Custom signals defined by the device manufacturer
Because DB9 pin assignment varies by device, you cannot assume that a DB9 connector on one device is compatible with a DB9 connector on another — even if they look identical.
3. Why OBD2 to DB9 Cables Exist
The OBD2 to DB9 cable solves a connector mismatch: your vehicle has a J1962 OBD-II port, but your diagnostic tool, GPS tracker, or telematics device has a DB9 connector. The cable is typically a passive pin-mapping adapter — it does not convert protocols. It routes selected OBD-II pins to the DB9 connector so that the device can communicate with the vehicle.
Three common scenarios:
- Fleet GPS tracking: GPS trackers use a DB9 or serial-style interface to read vehicle speed, fuel level, and diagnostic codes from the OBD-II port
- Diagnostic tools: Scan tools and test devices may use a DB9 connector for connection to vehicle-specific adapter cables
- Telematics gateways: Industrial telematics units on construction equipment, generators, and commercial vehicles use OBD-II or J1939 connectors with DB9-style interfaces
4. Example Pinout Mapping
The table below shows one common example used by some diagnostic and telematics devices. It is not a universal standard. Always verify the pinout required by your device before ordering or connecting the cable.
| OBD2 Pin | OBD2 Signal | Example DB9 Pin | Standard DB9 RS232 Signal | Use in This Example |
|---|---|---|---|---|
| 4 | Chassis Ground | 5 | GND | Ground |
| 5 | Signal Ground | 5 | GND | Ground (often tied to Pin 4) |
| 7 | K-Line (ISO 9141-2) | 2 | RX (Receive Data) | K-Line data |
| 15 | L-Line (ISO 9141-2) | 3 | TX (Transmit Data) | L-Line data (optional) |
| 16 | Battery +12V | 9 | RI (Ring Indicator) | Power (optional) |
| 6 | CAN High | 7 | RTS | CAN High, non-RS232 use |
| 14 | CAN Low | 8 | CTS | CAN Low, non-RS232 use |
OBD2 Pin Reference (Full 16-Pin)
| Pin | Signal | Pin | Signal |
|---|---|---|---|
| 1 | OEM discretion | 9 | OEM discretion |
| 2 | J1850 Bus+ (PWM) | 10 | J1850 Bus− (PWM) |
| 3 | OEM discretion | 11 | OEM discretion |
| 4 | Chassis Ground | 12 | OEM discretion |
| 5 | Signal Ground | 13 | OEM discretion |
| 6 | CAN High (ISO 15765) | 14 | CAN Low (ISO 15765) |
| 7 | K-Line (ISO 9141-2) | 15 | L-Line (ISO 9141-2) |
| 8 | OEM discretion | 16 | Battery +12V |
5. Common Applications
OBD2 to DB9 cables are used in fleet GPS tracking, diagnostic tools, telematics gateways, and ECU programming. For detailed application scenarios, cable specifications, and installation guidance, see Fleet GPS Tracker Cable Guide.
6. Cable Construction Notes
- Cable type: 3-7 conductor, 24-22 AWG stranded copper. Shielded cable is recommended for installations in electrically noisy environments or where EMC compliance is required.
- Length: For reliable communication, cable length should follow the device specification or customer drawing. RS232, CAN, and K-Line all have different electrical length limits.
- Connector retention: The OBD2 connector has a built-in latch. The DB9 may have screw-lock standoffs. Always secure connectors properly — loose connections are a common cause of intermittent communication.
- Strain relief: Overmolded strain relief or grommets at both ends reduce stress on wires and improve durability in fleet installations.
7. Custom OBD2 Cable Manufacturing
Off-the-shelf OBD2-to-DB9 cables work for some applications, but custom cables are often needed for:
- Specific pin assignments: Non-standard DB9 pin mapping for CAN, K-Line, power, or custom signals
- Power filtering: Adding an in-line fuse and transient voltage suppression on the +12V line
- Environmental sealing: IP-rated connectors for exterior-mounted GPS trackers or harsh environments
- Custom lengths and angles: Right-angle OBD2 connectors for tight dashboard clearance, extended lengths for fleet installations
Frequently Asked Questions
Q: What is an OBD2 to DB9 cable used for?
A: It is used to connect a vehicle's 16-pin OBD-II diagnostic port to a DB9-based scan tool, GPS tracker, telematics device, or test interface. In most cases, the cable is a passive pin-mapping adapter. It does not convert OBD-II, CAN, or K-Line protocols into RS232 unless active electronics are included.
Q: What is the pinout of an OBD2 to DB9 cable?
A: There is no universal OBD2-to-DB9 pinout. DB9 pin assignment depends on the diagnostic device, GPS tracker, telematics unit, or customer drawing. The example table in this article shows one common mapping only. Always verify the pinout before connecting to a vehicle or device.
Q: Can I make my own OBD2 to DB9 cable?
A: Yes, using an OBD2 male connector, a DB9 connector, and appropriate wires. For reliable operation, use a cable with proper shielding, strain relief, and verified pin-to-pin continuity. A poorly made cable can cause intermittent communication errors that are difficult to diagnose.
Q: What protocols does an OBD2 to DB9 cable support?
A: The cable itself does not support or decode protocols. It only routes wires. Protocol support depends on the connected device and vehicle, such as CAN, K-Line, J1850, or manufacturer-specific signals.
Q: Can I use a USB-to-RS232 adapter with an OBD2-to-DB9 cable?
A: A generic USB-to-RS232 adapter cannot read OBD-II, K-Line, or CAN data by itself. It can only be used when the connected diagnostic interface is designed for RS232 communication and the cable pinout matches that device. A passive OBD2-to-DB9 cable plus a generic USB-RS232 adapter will not decode CAN, K-Line, or OBD-II data.
Need a Custom OBD2 to DB9 Diagnostic Cable?
Send us your pinout, connector gender, cable length, device-side connector, and application. We can help check whether your cable should be passive pin mapping or include active interface electronics.
Send RFQ →