J1939 Data Logger - Easy Truck Fleet Telematics (WiFi, 4G)

Need to collect J1939 data from your heavy-duty vehicle fleet?

In this guide, you will learn how to set up a complete J1939 data logging solution for your heavy-duty vehicles - from device configuration to data visualization.

In particular, we cover how the CANedge enables modern J1939 telematics with zero monthly fees and 100% free software/APIs - as well as use cases and case studies.

Teaser: You will e.g. learn about powerful J1939 dashboards like this playground!

1: Select device & adapters

First you need to select which CANedge to use. If your goal is to deploy e.g. a J1939 blackbox for offline logging over extended periods, the CANedge1 is a good fit. If you also wish to automate your data collection, consider the CANedge2 (with WiFi) or CANedge3 (with LTE). All devices optionally come with GPS/IMU, adding data like position, speed, acceleration, distance and more.

Next, you need to determine what adapter cable(s) to use. This depends on the vehicle, how many CAN buses you need to record - and how you prefer to connect your device. Below we outline the most common adapters used in J1939 logging. If in doubt, start out with a DB9-J1939 adapter and a contactless CAN reader.

Tip: See also our vehicle lookup tool to see if we have PDF guides for your model.

2: Configure your device

J1939 data is generally broadcast, meaning that you do not need to request it. By default the CANedge simply auto-detects the bit-rate and starts logging - meaning it can be used seamlessly across 250K/500K J1939 networks.

You may later wish to reduce your file size via filters and triggers. For example, you can configure your CANedge to only record specific 29-bit CAN IDs or 18-bit PGNs. You can also e.g. setup the device to only record data when EngineSpeed is above 500 RPM.

If needed, you can configure the CANedge to periodically request specific data via the J1939 request PGN 59904 (0xEA00). To transmit data, the CANedge must be directly connected to the CAN bus (i.e. not via a contactless CAN reader).

Tip: See our J1939 on-request PGN list for examples of on-request PGNs

3: Record J1939 data

In most trucks/buses, you can simply connect the CANedge via a DB9-J1939 adapter to power the device and start recording the full J1939 CAN bus trace. Under normal circumstances you should expect to see 500-1500 frames/second and ~30-150 unique CAN IDs (all of them 29-bit). You can easily view the raw data in asammdf.

However, in practice you may encounter 4 key challenges when recording J1939 data:

4: DBC decode J1939 data

To decode J1939 data you need the relevant DBC file. If you are not the equipment manufacturer, you can purchase our J1939 DBC file, which contains 1800+ PGNs and 12000+ SPNs. The DBC is based on the J1939 Digital Annex in official collaboration with SAE (Society of Automotive Engineers).

For most J1939 networks, the J1939 DBC lets you decode the majority of the parameters as per the illustration below. Further, several J1939 signals go across the vast majority of e.g. trucks/buses. This implies that you can often rely on a 'common set' of data even in mixed fleet J1939 data logging.

Tip: If you send us your raw CANedge MF4 log file samples we can DBC decode them via our J1939 DBC free-of-charge - this way you can check what PGNs can be decoded before deciding whether to purchase the J1939 DBC file.

5: Auto-upload J1939 data to your own server

The CANedge2/CANedge3 supports 100% secure upload of data to your own server via WiFi/LTE (incl. support for over-the-air updates). You can use practically any cloud server (AWS, Google Cloud, Azure, ...) or even a self-hosted server (e.g. MinIO). To manage devices/data you can use CANcloud or API tools.

Tip: See our CAN telematics article for details on effective fleet deployments.

6: Automate data processing and visualization

Once you have deployed your basic J1939-to-cloud data collection workflow, you can optionally enhance it with automatic data processing. In the CANedge Intro we provide step-by-step guidance on setting this up in <15 min (zero coding required).

For example, if you use AWS you can use our plug & play Lambda functions to automatically DBC decode your J1939 data into a Parquet data lake (via our MF4 decoders). The data lake can then be used for multiple use cases as illustrated below.

Predictive maintenance via periodic uploads

Need to predict breakdowns across construction or mining vehicles?

Some heavy-duty vehicles operate e.g. in mines with no 3G/4G connectivity (see e.g. our mining telematics intro). Others operate in specific areas like construction yards or warehouses. In these cases, the CANedge2 can be set up to connect via 1-4 WiFi access points in the area. When a vehicle gets in range of a WiFi access point, data from the SD card is auto-pushed to your server (self-hosted or cloud). Here, it can be easily DBC decoded using our J1939 DBC for visualization. In particular, users can deploy our plug & play event detection integrations to automatically receive notifications when e.g. signal thresholds are crossed or DM1 DTCs become active.

OEM vehicle blackbox / event data recorder (EDR)

Need to record a rolling window of J1939 data from all your vehicles?

The CANedge1 is ideal for logging data over long periods from OEM heavy-duty vehicle fleets. With filters, compression, data encryption and cyclic logging you can safely log the latest months or years of data. This makes the device well-suited as an automotive data logger for e.g. diagnostics, warranty dispute handling and legal compliance. In particular, the CANedge1 can also serve as a low cost event data recorder (EDR) for e.g. UN R160 or UN R169 requirements.