An OBD connector is the vehicle-side diagnostic interface used to connect external test equipment or data devices to a vehicle’s onboard diagnostic system. In most modern passenger vehicles, this refers to the standardized 16-pin OBD-II Data Link Connector, or DLC. The connector may provide power, ground, and access to supported diagnostic communication lines. In a telematics device, the OBD connection can provide vehicle data and power, while cellular, GNSS, Wi-Fi, and radio antenna signals use separate RF interfaces when external antennas are required.
What Is an OBD Connector
OBD stands for onboard diagnostics. An OBD connector is the physical interface between a vehicle and an external diagnostic or data device. The connector gives the external device access to designated power, ground, and communication pins without opening the vehicle control unit or modifying the vehicle wiring.
The standardized OBD-II connection consists of two mating parts: a connector installed on the vehicle and a matching connector used by the external equipment. The vehicle-side connector is commonly called the Data Link Connector. A diagnostic cable, extension cable, adaptor cable, data logger, or plug-in telematics terminal can connect to this interface.
The 16-pin shape identifies the physical interface, but it does not reveal every available signal. The communication protocol, populated pins, power behavior, and accessible data can vary between vehicles. Connector appearance therefore needs to be checked together with the vehicle documentation and the connected device specification.
OBD-I, OBD-II, and Connector Types
OBD is the general name for a vehicle’s onboard diagnostic system. OBD-I refers to earlier implementations that were commonly defined by individual vehicle manufacturers. Connector shape, connector location, communication method, and available diagnostic information could vary between these systems.
OBD-II introduced a standardized physical diagnostic connection for external test equipment. It is commonly associated with the 16-position Data Link Connector defined through SAE J1962 and referenced by ISO 15031-3. The standardization makes the physical connection easier to identify, although vehicle protocols and available data still need separate confirmation.
Two physical forms are commonly described as Type A and Type B. Type A is widely associated with 12 V passenger vehicle systems. Type B was introduced to accommodate 24 V vehicle systems and uses a mechanical difference that helps distinguish the connector form.
OBD-II 16-Pin Connector Pinout
The 16 connector positions do not all have one universal function. Several positions have standardized assignments, while other positions may remain unused or carry vehicle-defined functions. The pinout table below provides a connection reference, but the final wiring still depends on the vehicle and the connected device.
| Pin | Common Assignment | Connection Check |
|---|---|---|
| 1 | Vehicle-defined or optional | Check the vehicle documentation |
| 2 | SAE J1850 Bus Positive | Used on supported J1850 systems |
| 3 | Vehicle-defined or optional | Do not assume a universal function |
| 4 | Chassis Ground | Confirm the required grounding path |
| 5 | Signal Ground | Treat separately from chassis ground unless specified |
| 6 | CAN High | Commonly paired with Pin 14 |
| 7 | K-Line | Used by selected diagnostic systems |
| 8 | Vehicle-defined or optional | Check whether the position is populated |
| 9 | Vehicle-defined or optional | Check the vehicle and device pin map |
| 10 | SAE J1850 Bus Negative | Used on supported J1850 PWM systems |
| 11 | Vehicle-defined or optional | May carry a secondary network on some vehicles |
| 12 | Vehicle-defined or optional | Confirm before wiring |
| 13 | Vehicle-defined or optional | Confirm before wiring |
| 14 | CAN Low | Commonly paired with Pin 6 |
| 15 | L-Line | Optional on selected legacy systems |
| 16 | Battery Positive | Check voltage, current draw and protection |
What an OBD Connector Carries and What It Does Not
An OBD connection may carry battery power, chassis ground, signal ground, CAN communication, K-Line, J1850, or vehicle-defined signals. The available lines depend on the vehicle. A diagnostic tool may use these connections to request trouble codes, read supported parameters, clear supported codes, or record network data.
The OBD connector is not a standard RF antenna interface. Cellular, GNSS, Wi-Fi, Bluetooth, and radio signals require a suitable antenna path inside or outside the connected telematics terminal. When external antennas are used, these paths normally include an RF connector, a coaxial cable assembly, and an antenna matched to the required frequency range and interface.
A plug-in telematics terminal may therefore use two different connection groups. The OBD side receives vehicle power and diagnostic data. The RF side connects the cellular, GNSS, Wi-Fi, or radio module to its antenna. The two groups can exist in the same device, but their electrical requirements, connector families, cable structures, and verification methods are different.
Common OBD Cable Configurations
OBD connectors are often integrated into finished cable assemblies. The cable configuration depends on whether the connection is intended for diagnostics, data logging, device integration, port relocation, or temporary measurement. The following configurations cover the most common connection purposes without treating every molded structure as a separate cable type.
| Cable Configuration | Typical Function | Main Point to Confirm |
|---|---|---|
| OBD-II extension cable | Relocates the diagnostic connection | Pin continuity, cable length, orientation and current capacity |
| OBD-to-device cable | Connects the DLC to a logger, terminal or test device | Exact source-to-destination pin map |
| OBD breakout cable | Separates selected lines for measurement or testing | Exposed contact protection and clear labeling |
| OBD splitter cable | Creates more than one device path from one port | Power draw, communication access and installation clearance |
| OBD adaptor cable | Changes the device-side connector or interface | Connector keying, pin numbering and wiring definition |
An OBD splitter requires more than a physical fit check. Multiple connected devices can draw power from the same port, attempt to communicate on the same network, or occupy limited space around the dashboard connection. Device current, standby behavior, communication method, cable direction, and connector clearance need to be reviewed together.
How to Specify an OBD Cable for a Telematics Device
An OBD cable needs to be defined from the electrical interface outward. Connector shape alone cannot determine the required cable because pin assignment, power behavior, communication lines, cable construction, and device-side termination can differ between applications.
| Item to Confirm | Required Information |
|---|---|
| Vehicle electrical system | 12 V or 24 V system and connector form |
| Communication interface | CAN, K-Line, J1850 or vehicle-defined lines |
| Pin map | Exact OBD pin to device pin correspondence |
| Power requirements | Operating current, standby current and protection method |
| Device behavior | Wake-up, sleep and battery drain requirements |
| Cable construction | Conductor size, jacket, temperature and flex requirements |
| Mechanical arrangement | Straight or angled exit, strain relief and dashboard clearance |
| Device-side termination | Connector family, keying, orientation and pin numbering |
| RF antenna connection | Separate cellular, GNSS, Wi-Fi or radio interface requirements |
The OBD cable and the RF antenna cable solve different connection requirements. The OBD cable carries vehicle power and diagnostic communication. The RF cable assembly carries high-frequency signals between the telematics module and an external antenna. For an RF path, frequency range, impedance, connector family, coaxial cable type, cable length, routing, and antenna interface require a separate review.
FAQ
Conclusion
An OBD connector provides a standardized physical access point for vehicle power and diagnostic communication, but the 16-pin shape does not define every signal or device connection. Connector type, vehicle voltage, protocol, populated pins, wiring map, power behavior, cable construction, and device-side termination need to be reviewed together. In a telematics terminal, the OBD path and the RF antenna path remain separate: one connects to vehicle data and power, while the other connects the communication module to its antenna.