OBD2 vs J1939: Which System for Your Fleet?

You will very often read that "OBD-II has been standard on all vehicles since 2001". That sentence circulates through much of the industry's marketing content, and it is wrong as soon as heavy vehicles enter the conversation. What is accurate: OBD-II is a regulatory requirement tied to emissions diagnostics on light vehicles. In North America it applies to cars and light trucks from the mid-1990s. In Europe, EOBD covers petrol vehicles from 2001 and diesels from 2004. What is not: none of that concerns a road tractor, an excavator or a mining haul truck. Those vehicles fall under a different framework and generally expose their data through SAE J1939. The practical consequence is immediate. A manager who orders fifty OBD-II devices for a fleet of road tractors ends up with fifty devices that have nowhere to plug in.

Connector OBD-II: 16-pin trapezoidal connector (SAE J1962), under the dash. J1939: round 9-pin Deutsch connector, sometimes 6-pin on older vehicles. Vehicles concerned OBD-II: cars, pickups, light commercial vehicles, some commercial vehicles. J1939: road tractors, buses, heavy machinery, industrial and agricultural equipment. Original purpose OBD-II: emissions diagnostics. J1939: communication between the vehicle's control units. Physical layer OBD-II: several protocols depending on year, including ISO 15765-4 (CAN), ISO 9141-2, KWP2000 and SAE J1850. J1939: CAN with 29-bit extended identifiers, 250 kbit/s or 500 kbit/s. Fault code format OBD-II: five-character code such as P0217. J1939: SPN + FMI pair with an occurrence count. Data richness OBD-II: powertrain and emissions-related parameters. J1939: engine, transmission, braking, aftertreatment, PTO and body parameters, depending on what the manufacturer broadcasts. Installation OBD-II: direct plug-in, a few seconds. J1939: cable matched to the connector, more preparation on a heavy vehicle.

A real fleet rarely splits into two clean categories. Here are the situations that come up regularly. Medium commercial vehicles A class 3 to 5 truck may carry an OBD-II port, a J1939 connector, or both. It depends on the manufacturer and the powertrain. FMS interface On many European heavy vehicles, manufacturers expose a standardised subset of data through an FMS gateway. That simplifies integration but deliberately limits what is reachable. J1708 / J1587 On older vehicles, data travels over this earlier standard, often through a 6-pin connector. Proprietary interfaces Some manufacturers reserve part of the data for their own diagnostic tooling. No third-party device will read it, whatever the protocol. Factory-fitted telematics Some recent vehicles leave the factory with manufacturer telematics. Access to the data then sometimes runs through an application interface rather than a physical connection.

The question "OBD-II or J1939?" has no general answer. It has an answer per vehicle. The method that avoids unpleasant surprises: 1. List the fleet with each vehicle's manufacturer, model and year. 2. Identify the physical connector on each one. A photo of the connector is usually enough. 3. For heavy vehicles, check whether the 9-pin connector is green (250 kbit/s) or black (250 and 500 kbit/s). 4. Confirm with the vendor which parameters are actually readable on those models, rather than which parameters appear in the standard. 5. Handle the unusual vehicles separately: older, imported, refurbished or fitted with factory telematics. A mixed fleet is not a problem. A mixed fleet whose composition you discover after the hardware ships is. At Tralogit this check is part of deployment: the device supports both OBD-II and J1939, and every vehicle's compatibility is confirmed before the order goes out.