Press "Enter" to skip to content

Posts tagged as “JCOM1939 Monitor”

JCOM1939 Monitor Update Adds CAN Bus Diagnostics and Silent Monitoring Mode

It has been a while since we released new functionality for the JCOM1939 Monitor software for Windows, but recent customer feedback inspired several improvements that make the software even more valuable during development, troubleshooting, and diagnostics. The latest update introduces two important features: Display of the CAN Bus network condition,…

Introducing the J1939 Community: A Forum for SAE J1939 Developers

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…

Why Every CAN Bus Developer Should Own a CAN Analyzer

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…

Why Monitoring CAN Error Counters Is Essential for Reliable CAN Bus Diagnostics

When engineers troubleshoot a CAN network, they usually focus on the messages flowing across the bus. They check identifiers, decode data bytes, and verify timing. While that is certainly important, there is another source of diagnostic information that is often overlooked—and in many cases, it provides the fastest path to…

SAE J1939 VIN Simulation and Request Demo – Understanding PGN 65260 (VIN)

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…

SAE J1939 Engine Speed Simulation (PGN 61444 / SPN 190) with JCOM1939 Monitor

Engine speed is one of the most frequently monitored parameters in any SAE J1939 network. Whether you are developing a dashboard, testing an engine ECU, validating telematics software, or learning how J1939 communication works, engine speed is often the first parameter engineers look at. In this post, we will explain…

Can You Use a J1939 Gateway to Monitor ISOBUS Networks?

One of the questions that recently crossed my mind was whether our existing SAE J1939 gateways and monitoring tools could be useful in the agricultural sector, specifically for monitoring ISOBUS networks. The short answer appears to be: Yes, in many cases they can. The longer answer is a bit more…

SAE J1939 Development Doesn’t Have to Be Complicated: From Monitoring to Full ECU Simulation

If you have recently started working with SAE J1939, chances are your search history looks something like this: How do I monitor J1939 traffic? What hardware do I need for J1939 development? How do I simulate a J1939 ECU? How can I test my software without connecting to a real…

Having Trouble Receiving J1939 PGNs

We acknowledge that some users may experience issues when trying to see SAE J1939 data traffic while connecting our gateway to a J1939 network or a single J1939 node. The following aims to provide support. Documentation User Manual: A comprehensive guide detailing all features and functionalities. Download and Installation Instructions:…

Copyright © 2024 Copperhill Technologies Corporation
wpChatIcon
wpChatIcon