Truck Telematics: J1939 Data to Cloud via 3G/4G [+ MATLAB]

What problem did you solve?

We need to collect J1939 data from a fleet of customer trucks to analyze the fuel economy and conduct performance and benchmarking analysis (based on real duty cycles). As part of this, we wanted to be able to install the logging devices and let the trucks complete normal operations during 5-6 weeks, after which we would remove the devices. Because of this, wireless connectivity was a key selection criteria.

In the past, an engineer had to be physically present in the truck to collect trip data using an interface connected to the diagnostic port - which could often take several days. Due to travel restrictions caused by the covid pandemic, we had to find a reliable way to collect J1939 data through truck telematics - thus reducing physical interaction. We already had expensive data loggers for very specific requirements - but the installation of those devices was complex and the necessary investment exceeded our budget.

How did you solve it?

We install the CANedge2 in each truck together with a RUT240 cellular WiFi router, which provides internet connectivity for the device. In addition, we use a CANmod.gps extension for each CANedge2 unit to add GNSS/IMU data for our analysis. This installation setup can be done by virtually anyone without special training, thanks in part to the excellent documentation and support from CSS.

When the customer begins their trips, we no longer have physical access to the devices. However, this is not an issue as the CANedge2 units automatically offload the MF4 log files to our own AWS S3 cloud server via the 3G/4G router. We then use the asammdf GUI to DBC decode and export the MF4 data from our S3 server to MAT files for import into MATLAB - letting us process the truck data in the tools we normally use. Going forward, we expect to start loading the CANedge MF4 log files directly through MATLAB's Vehicle Network Toolbox.

What benefit has this led to?

The CANedge2 is a reliable device that can be configured remotely over-the-air - meaning that any configuration/firmware changes can be performed remotely during trips (e.g via CANcloud) - with no need to stop the truck engines or disturb the driver. In addition, the driver is not affected by the physical device installation as the device dimensions [8 x 5 x 2 cm] and wiring can be fitted easily in any vehicle dashboard. We could also receive J1939 data out-the-box and transmit custom J1939 messages with a quick configuration change [e.g. for requesting engine hours].