Glossary termGPS Fleet Tracking

J1939

A SAE standard communication protocol used in heavy-duty commercial vehicles that transmits engine, transmission, and vehicle data over the Controller Area Network (CAN bus), enabling telematics systems to read fault codes, RPM, fuel consumption, and more.

Written by Rajat GuptaRajat GuptaEditorRajat Gupta runs FleetOpsClub and writes its software reviews, comparisons and pricing pages. Every tool on the site is assessed against the vendor's own published documentation and pricing, and each pricing figure carries the date it was last verified so readers can judge how current it is. Where a vendor does not publish a price, the page says so rather than estimating one.Reviewed Nov 6, 2026
Category: GPS Fleet TrackingOpen GPS Fleet TrackingPublished October 23, 2026

Compare gps fleet tracking platforms on verified pricing and deployment detail before you shortlist: every gps fleet tracking platform we have reviewed.

What J1939 Is and Why It Matters for Fleet Telematics

J1939 is the SAE International standard that defines how electronic control units (ECUs) in heavy commercial vehicles communicate with each other. Think of it as the language that the engine, transmission, ABS module, instrument cluster, and aftertreatment system all speak on the same CAN bus network. When a telematics device plugs into the 9-pin Deutsch connector (the standard heavy-duty diagnostic port), it joins the J1939 network and can listen to, or request, any Parameter Group Number (PGN) published by the ECUs. This is how a fleet management system reads live fuel consumption, engine RPM, coolant temperature, odometer, and active fault codes from a Kenworth T680 or a Freightliner Cascadia without any integration with the truck manufacturer.
Commonly Used J1939 Parameter Group Numbers (PGNs) in Fleet Telematics
PGNNameKey Data PointsTypical Use in Fleet Management
61444Electronic Engine Controller 1Engine RPM, torque mode, driver demandIdle detection, over-rev alerts, acceleration coaching
65266Fuel EconomyFuel rate (L/hr), instantaneous economyFuel cost allocation, idle fuel burn calculation
65253Engine Hours, RevolutionsTotal engine hours, total engine revolutionsPreventive maintenance scheduling
65217High Resolution Vehicle DistanceTotal vehicle distance (odometer)Mileage-based service intervals
65110Active Diagnostic Trouble CodesSPN, FMI, occurrence countReal-time fault alerting, maintenance dispatch
65265Cruise Control / Vehicle SpeedVehicle speed, cruise control statusSpeed compliance, driver coaching
64892Air Supply PressurePrimary, secondary air pressureBrake system monitoring on air-braked vehicles

J1939 vs OBD-II: Understanding the Distinction

Fleet operators running mixed fleets encounter both protocols. OBD-II governs light-duty vehicles (cars, pickups, cargo vans under 8,500 lb GVWR) and uses a 16-pin connector. J1939 governs heavy commercial vehicles (Class 6–8 trucks, buses, construction equipment) and uses a 9-pin Deutsch connector. The underlying network for both is CAN bus, but the message structure, addressing, and parameter definitions are completely different. A telematics device designed for OBD-II will not read J1939 data even if forced onto the 9-pin connector. Vendors that support both must ship different hardware or a multi-protocol adapter.

Fault Code Reading: SPN and FMI Explained

When a J1939-compatible telematics device reads fault codes, it retrieves two numbers that together identify the problem: the Suspect Parameter Number (SPN) identifies which component or system has the fault, and the Failure Mode Identifier (FMI) describes the type of failure. For example, SPN 110 is always engine coolant temperature; an FMI of 0 means the value is above normal range. A fleet platform that translates SPN/FMI pairs into plain-English descriptions, 'Engine coolant temperature above normal', saves maintenance managers significant diagnostic time. Platforms that only surface raw SPN/FMI numbers require technicians to look up codes manually, which slows response time. When evaluating telematics platforms for heavy fleets, always check whether fault code descriptions are human-readable or raw.

Real-World Example: Preventing a Catastrophic Engine Failure

A Midwest freight carrier running 34 Class 8 sleeper trucks deployed J1939-connected telematics on their entire fleet. Within 60 days, the system surfaced SPN 111 / FMI 1 (engine coolant level low) on a truck operating a loaded regional haul 280 miles from the nearest terminal. The dispatcher received an alert, contacted the driver, and the truck was pulled off at a truck stop before coolant level dropped to a level that would have caused engine damage. The driver had not noticed the coolant warning lamp because of direct sunlight on the instrument cluster. The value of the intervention is the difference between a coolant top-up at a truck stop and the head gasket failure or seized engine that low coolant leads to, and that gap is wide enough that a single catch of this kind can outweigh a year of subscription. Price it from your own engine rebuild quotes and your own revenue per truck per day rather than a generic range, and note the real lesson: the driver missed the dash warning lamp, and the telematics alert reached a dispatcher who was looking at a screen.

  • Confirm your telematics device uses a 9-pin Deutsch J1939 connector, not an OBD-II 16-pin connector
  • Verify the platform translates fault codes into human-readable descriptions rather than bare SPN/FMI numbers
  • Check which PGNs the device requests, fuel economy, engine hours, and odometer are essential for maintenance workflows
  • Ask whether the system distinguishes active faults from inactive (stored) faults
  • Confirm J1939 data updates in real time vs batched, real-time matters for fault alerting
  • Test fault code reading with a known fault before full deployment
  • Ensure the 9-pin connector does not interfere with dealer diagnostic tools. Most quality devices are passive listeners

Terms like this one decide what a vendor is really quoting for, so it is worth checking the fleet software profiles that document how each platform handles it, and modelling the cost with a fleet cost calculator before a vendor call.

Platforms to check against J1939

These are eight of the 26 products we have reviewed in GPS Fleet Tracking, ordered by how closely each one’s published research covers J1939. Being in that category is what puts a product on this list; the order is relevance to this term, not a score against each other.

  • Best fit: 50 to 500 vehicles in construction and utilities

    PriceQuote onlyNo published pricePer vehicle, equipment included in the subscription · Minimum term: Not published, set on the work order
  • Best fit: School bus and government fleets

    Published price$14.70 per bus/mo, district contractPer vehicle per month, modular, quote only · Minimum term: Three years by default
  • Best fit: DOT-regulated US fleets, compliance first

    Published price$14.99 per vehicle/mo, DC contractPer vehicle per month, quote only
  • Best fit: Maintenance-first fleets, 5 to several hundred

    PriceQuote onlyNo published pricePer vehicle per month, unlimited users · Minimum term: Annual on Professional and Premium
  • Best fit: FMCSA-regulated fleets running logs, cameras and fuel

    PriceQuote onlyNo published pricePer vehicle, quote based · Minimum term: Set on the Order Form, not published
  • Best fit: Dispatch-led field service fleets

    Published price$15.95 per vehicle/mo, GSA ratePer vehicle per month, à la carte by module
  • Best fit: 5 to 50 vehicles, tracking only

    Published price$13.95 per vehicle per monthPer vehicle, month to month, published · Minimum term: None, 30 days' notice either way
  • Best fit: Carriers and brokers past 200 vehicles

    PriceQuote onlyNo published pricePer module, by fleet or user count

J1939 FAQ

Quick answers to the questions buyers usually ask once the category, software, or rollout details start getting more specific.

All major OEM Class 8 trucks sold in the US after 2000 support J1939. Pre-2000 trucks may use the older J1708/J1587 protocol. Some specialty vehicles and older equipment use proprietary protocols that require manufacturer-specific adapters. Confirm protocol compatibility before ordering hardware for older fleets.

A properly designed telematics device is a passive listener on the J1939 network and does not send commands to the engine ECU. It cannot alter engine parameters, clear fault codes, or affect vehicle operation. Actively commanding the ECU, for remote engine shutdown via J1939, requires specific OEM authorization and is a separate, more advanced integration.

J1708 is the older SAE protocol that preceded J1939. It uses a different physical layer (RS-485 vs CAN) and slower data rates. Many trucks from the 1990s and early 2000s run J1708. Some still carry both networks. Telematics vendors supporting older fleets need devices that can read J1708/J1587 in addition to J1939.

J1939 is the CAN-based message standard that lets a heavy truck's engine, transmission and aftertreatment controllers talk to each other and to anything plugged into the diagnostic port. EPA regulation makes it one of only two permitted OBD scan-tool protocols for heavy-duty engines, and it may be used only on diesel vehicles; the matching connector specification is SAE J1939-13. It is why a telematics gateway can read fault codes, odometer and engine hours from any compliant diesel truck without vendor-specific wiring (40 CFR 86.010-18(k)).