One of the more common questions when analyzing or simulating SAE J1939 traffic is surprisingly simple: “How accurate must a J1939 message frequency be?” If a message is supposed to be transmitted every 100 milliseconds, does that mean exactly 100 milliseconds? Can it be 101 milliseconds? 105 milliseconds? What happens…
Posts published in “JCOM1939 Practical Guide”
The JCOM1939 Practical Guide is a growing collection of hands-on tutorials, technical articles, and real-world examples designed to help engineers, developers, technicians, and enthusiasts get the most from the JCOM1939 Monitor Software and JCOM1939 gateways.
If you are new to SAE J1939, the first thing you will probably do is search for the official standards documents. That usually leads to an immediate moment of confusion. You discover that SAE J1939 is not a single document. It is an entire collection of standards. Hundreds of pages.…
SAE J1939-22 is the CAN FD evolution of the J1939 family. In SAE’s own high-level description, it brings CAN’s flexible data rate capability into J1939 to support higher efficiency, parallel transactions, functional safety, and cybersecurity-oriented extensions, while preserving the J1939 application model built around PGNs, SPNs, source addresses, requests, diagnostics,…
When engineers, telematics providers, and fleet managers discuss SAE J1939 for fleet management, one truth becomes immediately apparent: Not all PGNs are created equal. Modern heavy-duty vehicles broadcast hundreds of parameter groups across the network, but in real-world fleet management applications, only a relatively small subset of PGNs carries the…
SAE J1939 is a standardized, CAN-based in-vehicle communications suite widely used in heavy-duty and off-highway domains, enabling interoperable exchange of operational telemetry (e.g., speed, engine hours, fuel rate) and a structured diagnostic ecosystem (Diagnostic Messages “DMs” and Diagnostic Trouble Codes “DTCs”). Its core fleet-management value is not “a single feature,”…
SAE J1939 defines a comprehensive framework for message formatting, transport, and network behavior in heavy-duty vehicle systems. While many Parameter Group Numbers (PGNs) are publicly standardized, a substantial portion of real-world J1939 traffic consists of proprietary messages. These messages are intentionally undocumented by OEMs and are often central to machine…
SAE J1939 networks are widely used in heavy-duty vehicles, agricultural machinery, construction equipment, and stationary engines. Although J1939 is often described as a standardized protocol, real-world implementations are tightly controlled, highly validated, and frequently intolerant of unexpected devices. Engineers connecting third-party hardware to these networks often assume Ethernet-like openness or…
John Deere agricultural vehicles, such as this modern tractor, utilize J1939 CAN networks for critical systems. These in-vehicle networks carry engine, transmission, hydraulic, and safety data, and are designed to be robust and reliable. John Deere’s implementation of J1939 is closed and tightly controlled, reflecting the company’s emphasis on safety,…
Network management refers to the set of services and protocols that supervise the nodes (devices) on a CAN-based network – handling tasks like node addressing, status monitoring, and controlling node state. Two prominent higher-layer protocols, SAE J1939 and CANopen, approach network management very differently. SAE J1939 was created for heavy-duty…
When people talk about SAE J1939, they often jump straight to CAN frames, PGNs, or diagnostic trouble codes. But all of those live downstream from the most important part of the standard: the application layer. The application layer is where J1939 stops being a transport mechanism and becomes a language.…
