OBD-II Port Guide: Location, Pinout, and Fleet Use (vs. J1939)
Where the OBD-II port is, how the 16-pin J1962 connector works, OBD-II vs. heavy-duty J1939, and how fleets use it for diagnostics, ELDs, and telematics.
For a mixed fleet, knowing exactly what connector each class of vehicle uses, and what plugs into it, is the difference between a smooth device rollout and a yard full of dongles that do not fit.
It also walks through reading and clearing fault codes, the ELD connection, and the port problems that surface most often in the field.
Connector locations and pin assignments follow standards, but exact placement and any vehicle-specific quirks vary by OEM. Confirm against the service manual or device installation guide for the specific make, model, and class before installing anything.
What is the OBD-II port?
OBD-II stands for On-Board Diagnostics, second generation: a standardized system that has been required on light-duty vehicles sold in the U.S. since the 1996 model year. The OBD-II port is the physical connector that gives access to that system.
Standardization is the whole point: a single scanner works across makes because the port, the connector, and the core code set are common.
Where is the OBD-II port located?
On most light-duty vehicles, the OBD-II port sits under the dashboard on the driver's side, within about three feet of the steering column and reachable without tools.
Common spots are just below the steering wheel, behind a small cover or trim panel, near the hood release, or tucked above the pedals.
The standard intends it to be accessible from the driver's seat, which is exactly why ELD and [telematics](/categories/telematics) dongles plug in there and stay put.
Heavy-duty trucks are different. Their diagnostic connector is often near the driver's left knee, under the dash, or on a lower panel, but it is frequently a different connector type entirely, which is the distinction the next sections cover.
The 16-pin J1962 connector and pinout basics
The standard light-duty OBD-II connector is the 16-pin trapezoidal connector defined by SAE J1962. Sixteen pins are arranged in two rows of eight. Some pins are standardized across all vehicles, while others are reserved for manufacturer-specific use.
The pins you can count on regardless of make are the power and ground pins and the communication pins that carry the diagnostic data.
| Pin | Function | Notes |
|---|---|---|
| Pin 4 | Chassis ground | Standard across vehicles |
| Pin 5 | Signal ground | Standard across vehicles |
| Pin 16 | Battery power (12V) | Often live even with key off |
| Pins 6 & 14 | CAN bus (high / low) | Most common modern protocol |
| Pin 7 | K-line (ISO 9141 / KWP) | Older communication protocol |
| Pins 2 & 10 | J1850 bus | Older GM/Ford protocol |
| Other pins | Manufacturer-specific | Vary by make |
The practical takeaways: pin 16 is usually powered even with the ignition off, which is how plug-in devices stay alive, but it is also why a parasitic dongle can drain a battery on a vehicle that sits.
And the communication protocol varies by vehicle, so a device has to support the protocol the vehicle uses. Most vehicles from the mid-2000s onward use CAN on pins 6 and 14.
OBD-II vs. J1939: the critical fleet distinction
This is the section that saves fleets from buying the wrong hardware. Light-duty vehicles use OBD-II over the J1962 connector. Heavy-duty trucks use a different diagnostic network, J1939, over a different physical connector.
Researching fleet maintenance software software?
Compare platforms on verified pricing and deployment detail, with no sales call required. The fleet operations glossary covers the terms used in this guide, and the Fleet Maintenance Software comparison lists which vendors publish a price.
A device built for a passenger-car OBD-II port will not simply plug into a Class 8 truck. Mixed fleets have to spec devices for both.
Light-duty: OBD-II / J1962
Cars, pickups, vans, and most light-duty fleet vehicles use the 16-pin J1962 connector with standardized OBD-II diagnostics. This is the port most consumer scanners, ELD dongles, and GPS trackers are designed for.
If your fleet is all light-duty, the standard 16-pin connector is what you spec.
Heavy-duty: J1939 (9-pin and Green/Black Deutsch)
Heavy-duty trucks communicate over the SAE J1939 network, accessed through a round Deutsch connector: most commonly a 9-pin.
There are two common variants: the older Type 1 (often called Green) at a slower data rate and the newer Type 2 (often called Black) at a higher data rate. Many trucks also have a 6-pin connector on older equipment.
The data available over J1939 is richer than light-duty OBD-II for fleet purposes, which is why heavy-duty [telematics](/categories/telematics) and ELDs are built around it.
When ordering devices or cables for trucks, you must specify the connector type (9-pin Green, 9-pin Black, or 6-pin) to get a unit that physically fits and communicates.
| Vehicle class | Diagnostic standard | Connector |
|---|---|---|
| Light-duty car / van / pickup | OBD-II | 16-pin J1962 (trapezoidal) |
| Older heavy-duty truck | J1708 / J1587 | 6-pin Deutsch (round) |
| Heavy-duty truck (older J1939) | J1939 Type 1 | 9-pin Deutsch, Green |
| Heavy-duty truck (newer J1939) | J1939 Type 2 | 9-pin Deutsch, Black |
| Some medium-duty / mixed | OBD-II or J1939 | Varies: verify per unit |
What you plug into the port
The port is a data tap, and a lot of devices use it. Diagnostic scanners read and clear fault codes. ELDs pull engine data (engine hours, miles, and motion status) for hours-of-service logs.
[Telematics](/categories/telematics) and GPS dongles stream location and engine data to a fleet platform for routing, utilization, and maintenance. Dash cams with telematics integration may tie in as well.
On a fleet vehicle it is common to have a permanently installed device in the port and still need to connect a scanner alongside or in place of it for diagnostics.
The ELD mandate connects here
For commercial fleets subject to hours-of-service rules, the electronic logging device (ELD) connects to the vehicle through this port: the J1962 connector on light-duty units or the J1939 connector on heavy-duty trucks.
When you spec ELDs across a mixed fleet, match the device's connector and protocol to each vehicle class.
Reading and clearing fault codes (DTCs)
Ready to compare your options?
Narrow the shortlist, run a fleet cost estimate, and head into vendor demos with better questions. For methodology details, see how we review software or go straight to the Fleet Maintenance Software comparison.
To read codes, plug a scanner or [telematics](/categories/telematics) device into the port, power up the vehicle as the tool directs, and retrieve stored diagnostic trouble codes.
The tool returns the code and usually a description; from there you look up what it means and chase the named component. Clearing codes erases the stored trouble codes and turns off the check-engine light, but it does nothing to fix the underlying fault.
Generic vs. manufacturer-specific codes
OBD-II codes come in two flavors. Generic codes are standardized across all makes: a P0 powertrain code means the same thing on any vehicle, which is what lets one scanner work everywhere.
Manufacturer-specific codes (often P1 ranges) are defined by the individual OEM and require make-specific information to interpret fully. A basic scanner reads generic codes; a more capable tool or OEM software is needed to fully decode manufacturer-specific ones.
For fleet diagnostics, knowing which type you are looking at tells you whether a generic lookup is enough or whether you need OEM resources.
Common OBD-II port problems
Port issues are common in the field, especially with permanently installed devices. The most frequent complaints and their usual causes are below.
- No power to a plugged-in device: check the port's power pin, the related fuse, and battery condition.
- Loose or intermittent ELD/telematics connection: the connector backs out from vibration, reseat and secure it.
- Scanner will not communicate: confirm the device supports the vehicle's protocol (CAN, K-line, J1939, etc.).
- Battery drain on parked vehicles: a device on the always-live power pin can draw down a battery that sits.
- Physical damage or bent pins: inspect the connector before assuming the device or vehicle is at fault.
- Device fits but reads nothing on a heavy truck: wrong connector type. You need J1939, not light-duty OBD-II.
For ELDs specifically, a loose connection is the most common service call, because the device lives in the port through constant vibration. A device that backs out stops logging, which becomes a compliance problem fast. Securing the connection at installation prevents most of these.
Managing a mixed light- and heavy-duty fleet
Most real fleets run a mix, light-duty vans and pickups alongside medium- and heavy-duty trucks, which means two diagnostic ecosystems under one roof.
Standardize on a [telematics](/categories/telematics) and ELD vendor that supports both the J1962 and J1939 connectors, keep the correct cables and adapters stocked for each class, and label which connector each vehicle uses in your asset records so technicians and installers grab the right hardware the first time.
Frequently asked questions about the OBD-II port
Where is the OBD-II port located?
On most light-duty vehicles it is under the dashboard on the driver's side, within about three feet of the steering column and reachable without tools: commonly just below the steering wheel, behind a small trim panel, near the hood release, or above the pedals. Heavy-duty trucks place their connector near the driver's left knee or on a lower panel, and it is often a different connector type entirely.
What does the OBD-II port do?
It is the standardized access point to the vehicle's On-Board Diagnostics system. Through it, a tool can read diagnostic trouble codes stored by the engine control module, view live sensor data, and check emissions readiness. It is also where ELDs, telematics dongles, and GPS trackers tap the vehicle's data stream. Standardization means one scanner works across makes.
What is the difference between OBD-II and J1939?
OBD-II over the 16-pin J1962 connector is the light-duty standard used on cars, vans, and pickups. J1939 is the heavy-duty network used on trucks, accessed through a round Deutsch connector, most often a 9-pin. They are different protocols on different physical connectors, so a light-duty OBD-II device will not simply plug into a Class 8 truck. Mixed fleets must spec devices for both.
What is the 16-pin connector called?
It is the SAE J1962 connector: a trapezoidal connector with 16 pins in two rows of eight. Some pins are standardized across all vehicles (power, grounds, and certain communication lines), while others are reserved for manufacturer-specific use. Pin 16 supplies battery power, pins 4 and 5 are grounds, and pins 6 and 14 carry the CAN bus on most modern vehicles.
What connector do heavy-duty trucks use?
Most heavy-duty trucks use a round Deutsch connector for the J1939 network, commonly a 9-pin. There are two main variants: the older Type 1 (often Green, slower data rate) and the newer Type 2 (often Black, higher data rate). Older equipment may use a 6-pin connector. When ordering devices or cables for trucks, you must specify the exact connector type to get a unit that fits and communicates.
Can I clear fault codes through the OBD-II port?
Yes: a scanner can clear stored diagnostic trouble codes and turn off the check-engine light. But clearing does not fix anything. If the underlying fault is still present, the code returns. Clearing without repairing hides the problem rather than solving it, so log the code and the cause on a work order and repair the fault before clearing.
What is the difference between generic and manufacturer-specific codes?
Generic codes are standardized across all makes: a generic powertrain code means the same thing on any vehicle, which is why one scanner works everywhere. Manufacturer-specific codes are defined by the individual OEM and need make-specific information to interpret fully. A basic scanner reads generic codes; a more capable tool or OEM software is needed to fully decode manufacturer-specific ones.
Does the ELD connect to the OBD-II port?
Yes. For fleets subject to hours-of-service rules, the electronic logging device connects through the diagnostic port: J1962 on light-duty vehicles or J1939 on heavy-duty trucks. The ELD draws authoritative engine data such as engine power, motion, miles, and engine hours directly from the vehicle, which is exactly what the port provides. Match the ELD's connector to each vehicle class across a mixed fleet.
Why does my plugged-in device have no power?
Check the port's power pin (pin 16), the related fuse, and the battery. Pin 16 is usually live even with the key off, so if a device gets no power, a blown fuse, a damaged connector, or a dead battery is the usual cause. Bent or corroded pins can also break the connection. Inspect the connector before assuming the device itself failed.
Can an OBD-II device drain the battery?
Yes. Because the port's power pin is often live with the ignition off, a permanently installed dongle keeps drawing current. On a vehicle that sits for long stretches, that parasitic draw can run a battery down. It is worth knowing which units in a fleet have plugged-in devices and ensuring vehicles that park for extended periods are managed for it.
Why won't my scanner read a heavy-duty truck?
Almost always because it is the wrong tool for the connector. Heavy-duty trucks use J1939 over a Deutsch connector, not light-duty OBD-II over the 16-pin J1962. A scanner or device built only for light-duty OBD-II will not communicate with a truck even if you can force a physical connection. You need a J1939-capable device and the correct 6-pin or 9-pin cable.
How do fleets use the OBD-II port for telematics?
A telematics or GPS device plugs into the port and streams location and engine data to a fleet platform, where it drives routing, utilization tracking, and maintenance. The same data stream surfaces fault codes the moment they set, can trigger a work order automatically, and feeds the preventive maintenance schedule, turning the diagnostic port into the front door to vehicle health for a data-driven fleet.
If you are narrowing vendors, the side-by-side software comparisons pair tools on pricing and deployment fit, and the software directory covers every platform we track.
From our network
- FinanceOpsClub — independent research for finance and accounting software buyers, from audit management to expense tracking.
- SalesOpsClub — software guides for revenue leaders evaluating CRM, sales engagement, and forecasting tools.
- PeopleOpsClub — software guides and comparisons for HR, payroll, and people operations teams.
- ITCommons — software guides for IT operations teams evaluating endpoint management, help desk, and asset tracking tools.
- CreatorStackClub — independent research for content creators evaluating video editors, scheduling tools, and analytics platforms.