Developing, testing, or diagnosing SAE J1939 networks requires more than simply connecting a CAN interface to a PC. Engineers often need to monitor network traffic, decode messages, simulate electronic control units (ECUs), request diagnostic data, and verify that embedded software behaves correctly under real-world conditions. The market offers a wide…
Posts tagged as “Vehicle diagnostics”
Fleet management has evolved far beyond simply knowing where a vehicle is located. Modern commercial vehicles continuously transmit enormous amounts of operational data through the SAE J1939 network, while GPS receivers provide precise positioning information. Together, these technologies form the foundation of telematics, enabling fleet operators to monitor vehicle performance,…
If you work with SAE J1939 long enough, there comes a point where generic CAN monitoring software is no longer enough. You need an application that is tailored to your own project, whether that means displaying proprietary parameters, automating diagnostics, logging data, testing ECUs, or integrating J1939 into a larger…
If you’ve worked with SAE J1939 long enough, you’ve probably experienced the frustration of connecting two devices to a CAN bus and seeing… absolutely nothing happen. No engine data. No diagnostic messages. No responses to requests. Just silence. The good news is that most J1939 communication problems are caused by…
In previous quick demos, we focused on SAE J1939 parameters that are transmitted periodically, such as engine speed, vehicle speed, fuel level, and engine temperatures. These messages are broadcast automatically at predefined intervals, allowing any node on the network to receive the data without explicitly asking for it. The Vehicle…
As heavy-duty vehicles become increasingly connected, engineers are looking for ways to integrate vehicle data into fleet management systems, cloud applications, industrial control systems, and enterprise databases. The hardware needed for such integrations is readily available. Products from companies such as Red Lion, Moxa, HMS, Sierra Wireless, and many others…
If you’re learning SAE J1939, you’ll quickly run into two acronyms that show up everywhere—in diagnostic messages, simulation tools, engine logs, and OEM documentation: SPN (Suspect Parameter Number) FMI (Failure Mode Identifier) Together, SPNs and FMIs explain what went wrong and how it went wrong.They form the core of every…
If you’re new to SAE J1939, one of the first things you’ll encounter is how heavy-duty vehicles report problems. They do this using standardized diagnostic messages, and the two most important are: DM1 — Active Diagnostic Trouble Codes DM2 — Previously Active Diagnostic Trouble Codes Understanding these two messages will…
SAE J1939 is a standardized communication protocol used in heavy-duty vehicles like trucks, buses, construction equipment, and agricultural machinery. It defines how electronic control units (ECUs)—such as engines, transmissions, and brakes—talk to each other over a shared data network. Think of it as a common language that allows different vehicle…
In modern commercial vehicle operations, efficient fleet management and telematics are crucial for optimizing performance, reducing operational costs, and ensuring regulatory compliance. A key technology enabling this ecosystem is the SAE J1939 protocol, a standardized communication network that facilitates data exchange among electronic control units (ECUs) in heavy-duty vehicles. This…
