OBD-II Port Guide: Location, Pinout, and Fleet Use (vs. J1939)

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.