Why We Created the J1939 Community If you work with SAE J1939, you already know that finding reliable information isn’t always easy. While the standard itself is comprehensive, applying it to real-world embedded systems, diagnostics, CAN bus monitoring, or software development often raises questions that aren’t answered by the specification…
Posts tagged as “CAN-FD”
If you are serious about developing CAN or CAN FD applications, there is one tool that will save you more time, eliminate more frustration, and improve your software quality more than almost anything else: a professional CAN analyzer. Many engineers begin by connecting a microcontroller to a CAN network, sending…
One of the first questions engineers ask when starting with SAE J1939 development is: “Which hardware platform should I use?” The good news is that there is no shortage of choices. Over the years I have worked with numerous embedded platforms, development environments, and operating systems. They all have their…
When the first versions of SAE J1939 emerged in the late 1980s and early 1990s, the objective was straightforward: provide a standardized communication protocol for electronic control units (ECUs) in heavy-duty trucks. At the time, vehicle manufacturers were rapidly increasing the number of electronic subsystems, creating a need for a…
SAE J1939 development has evolved far beyond traditional automotive Electronic Control Units (ECUs). Today, engineers can build J1939-enabled systems using low-cost embedded platforms such as the ESP32 and the Raspberry Pi. While both platforms can successfully communicate on a J1939 network, they serve very different purposes. The question is not…
Why Your Car Is Smarter Than You Think—and How You Can Learn to Speak Its Language It began with a deceptively simple question: why can a modern vehicle detect a low tire pressure in seconds, yet the average driver has no idea how that information travels from a spinning wheel…
Overview of CAN Protocol Fundamentals A Controller Area Network (CAN) is a robust serial communication protocol originally developed by Bosch for in-vehicle networking. It is a multi-master, message-based network that allows microcontrollers and devices (nodes) to communicate over a shared bus without a central host computer. All CAN nodes are…
Introduction SAE J1939 is the dominant in-vehicle network protocol for medium and heavy-duty vehicles, traditionally running on Classical CAN at 250 kbps (or 500 kbps) with 8-byte frames. As modern trucks and buses integrate more electronics – from advanced engine controls to ADAS sensors – the bandwidth limitations of classical…
Introduction The Controller Area Network (CAN bus) is a robust serial communication bus originally developed for automotive applications in the 1980s. It allows microcontrollers and electronic control units (ECUs) in a vehicle or machine to communicate with each other without a central host computer. Since its inception, CAN bus has…
A Controller Area Network (CAN) requires termination resistors to ensure signal integrity, prevent reflections, and maintain proper bus impedance. Here’s why they are needed and where to install them: Why Are Termination Resistors Needed? Prevent Signal Reflections: CAN is a differential signaling system where signals travel along a twisted-pair cable…
