Modern heavy-duty vehicles and industrial equipment often contain dozens of Electronic Control Units (ECUs) communicating over an SAE J1939 network. During manufacturing, every ECU must be verified before it leaves the production line. Whether the product is an engine controller, telematics unit, instrument cluster, display, gateway, data logger, or sensor…
Posts tagged as “J1939 ECU simulator”
If you are new to SAE J1939 development, you may believe that access to a truck, engine, generator, or agricultural machine is required before you can write any meaningful software. While eventually you will want to test your application on real equipment, the majority of J1939 software development can be…
If you spend enough time around CAN Bus and SAE J1939 discussions, you’ll eventually encounter a statement along these lines: “Why implement a J1939 stack in firmware when Linux already supports J1939?” It’s a fair question. Modern Linux kernels include native J1939 support as part of the SocketCAN framework, and…
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…
This post refers to a simplified version of our SAE JCOM1939 Monitor – JCOM1939 Monitor, Analyzer, and ECU Simulator, a C# application created in Visual Studio. The JCOM1939 Monitor Software, a unique and powerful tool, allows you to monitor, analyze, and simulate SAE J1939 data traffic. It works seamlessly with…
