Member: Detroit Diesel Corporation
Featured Standard: ASAM MCD-2 MC, ASAM MDF
For over 70 years, Detroit Diesel has designed and built the heavyduty engines that fuel commerce and transportation across North America and around the world. The engines power a wide range of heavy-duty vehicles. To ensure the high level of quality and reliability of its engines, Detroit Diesel carries out extensive testing before they go into production. This includes on-vehicle testing on test tracks and public roads. Continuous logging of data from powertrain controllers and subsequent evaluation and analysis of the data plays a vital role in this process.
Challenge: Daimler Trucks North America with its subsidiaries Freightliner and Detroit Diesel used a variety of tools to log data from its engineering vehicle fleets. Due to the lack of having a common data format and ability to log measurements from more than 20 CAN based devices, another tool was needed for recording and displaying data.
Solution: A new tool has been identified and the first migration phase has been successfully completed. The main interest for this Case Study is logging data; other capabilities from the tools described are irrelevant.
Key Benefits: The migration process has been very smooth because all tools are compatible with ASAMa2l files. Without being much aware of it, Daimler Trucks North America is benefiting from ASAM standards by having common data formats and using interchangeable software tools.
I support ASAM because it enables plug and play of software tools
Chris Niessen, Senior Engineer, Powertrain Integration, Detroit Diesel Corporation
Freightliner and Detroit Diesel operate 3 truck fleets:
Freightliner and Detroit Diesel need the ability to handle data streams from multiple connected devices and show live data from 100’s of channels, which are displayed on a 50” screen inside a class 8 sleeper cab vehicle.
None of the existing tools were able to handle all tasks. In addition, having one common tool would ease the process of managing and sharing configuration, training and measurement lists.
Vector CANcase XL modules are used as the interface between the CAN bus and data loggers.
During remote testing, all data is saved on a server that resides within a modified coach bus for post processing. The bus is equipped with a mesh network that automatically receives data from nearby vehicles.
The main processing modules are for engine, aftertreatment, transmission and chassis. In addition, other modules handle tasks such as instrumentation and fault code management, adding up to 20 modules.
None of the existing tools were able to connect 20+ devices, log data in MF4 format and display live data. A new tool was needed for recording and displaying data. Vector CANape can handle all required task and it is compatible with ASAM *.a2l files. ASAM MCD-2 MC (aka ASAP2) defines a description format for internal ECU variables used for measurement and calibration purposes. Any replacement data logger had to be compatible with a2l files because they are also used with MARC I, CSM and CANcase. Most engineers are not aware that the ASAM MCD-2 MC standard plays a major role in making this a smooth migration. No adjustments have to be made to the existing *. a2l files.
The migration timeline includes a dual phase where both legacy and CANape recorders are simultaneously active. Phase 1: Ramp up Powertrainvalidation usage of CANape and keep logging data with MARC I. This dual-phase ensures that no data is lost during any unanticipated problems with CANape. After this short period of time, MARC I logging is stopped. In a similar approach, Phase 2 replaces the CSM loggers at Chassis validation, which is currently in the dual logging phase. The Reliability Growth fleet continues to work with CANcase loggers who have a similar functionality as CANape without the ability or need to display live data.
It took 1 year of testing andvalidation for the implantation at the Powertrain validation. CANape runs on a rugged dedicated invehicle computer. Due to the high demands on the CPU initially running constantly on 100%, the in-vehicle computers had to be upgraded twice to newer and more powerful models, currently running on the 3rd iteration. In addition, the heavy burden on the CPU was furthermore reduced by limiting the number of simultaneously recording channels at various sampling rates to currently 1073. Many engineers became accustomed to .famos files recorded in MARC I. Since CANape stores data in ASAM MF4 format, some engineers are reluctant to use CANape recordings and still use MARC I on occasion for secondary data logging.
Although running without issues, the Chassis and Powertrainvalidation fleets are considered to be a high level user within Vector, testing the upper limits of the system with currently 20+ connected devices.
The migration process is nearly completed. Due to the ever increasing number of devices andmeasurement channels, more powerful in-vehicle computers are needed with USB 3.0 interface to accommodate additional data throughput.