What Data Is Stored in a Commercial Truck's Electronic Control Module?
The engine computer in a tractor-trailer was built to run the engine and serve fleet managers, not to investigate crashes. It often holds crash data anyway, if the data survives the hours after the collision.
After a serious crash involving a tractor-trailer, the questions that matter most are often numerical. How fast was the truck going? When did the driver come off the throttle? When did braking begin? No federal rule requires a heavy truck to carry a crash recorder, but many carry something close to one: the engine’s electronic control module, a computer built to run the engine that also keeps records for the fleet that owns it.
What that module holds depends on who made the engine, which software it runs and how the fleet configured it. What follows describes what is commonly found, how it is retrieved and how it is lost.
What the module is and why heavy trucks have one
The engine control module, usually shortened to ECM, meters fuel, manages engine timing and responds to the accelerator pedal. On many trucks it also holds the governed top speed and runs cruise control.
Engine makers added data logging for fleet customers: fuel economy, idle time, trip summaries, maintenance intervals. A NHTSA working group reported in 2002 that this data served mostly fleet management, but that such a module, though “not a dedicated crash recorder,” can act as “a surrogate Event Data Recorder,” and that the National Transportation Safety Board had used engine data in crash investigations1.
The federal event data recorder rule, 49 CFR Part 563, covers only passenger cars and other light vehicles rated at 8,500 pounds or less, and only when they are equipped with a recorder2. Heavy trucks fall outside it. No federal standard dictates which crash data a heavy-truck engine must keep, in what format or for how long. The module does touch one federal rule: an electronic logging device in a truck of model year 2000 or later must link to the engine ECM and take power status, motion status, miles and engine hours from it3.
What the records commonly include
These categories are typical, not universal. Each engine maker defines its own reports, names them differently and changes them across software generations. Some depend on settings: Detroit says that if the fleet management data page is disabled on certain controllers, trip data is not collected at all4.
Event records. Many modules save a short record when the truck slows faster than a set rate, as in hard braking or a collision. Cummins calls this a Sudden Deceleration Data report; Detroit modules record Hard Brake events56. Cummins’ PowerSpec manual says the report covers time, vehicle speed, engine speed, engine load and throttle, and “will contain between 1-3 records”7. Engineers who tested it described second-by-second speed data5. The trigger rate and the length of the recording window vary by maker and module. [Verified statistic and source required: manufacturer-documented deceleration trigger (mph per second) and recording window (seconds before and after the trigger) for current Cummins, Detroit and PACCAR engine modules]
Last stop records. Detroit modules keep a Last Stop Record16, which, as the name indicates, covers the truck’s most recent stop, with vehicle speed, engine speed and accelerator pedal position logged at intervals8.
Trip, activity and fault data. Detroit lists trip data, monthly activity, idle time, speed and RPM reports, daily engine usage and diagnostic records among its standard outputs4. Fault codes7 can matter when a mechanical failure is in question.
Settings. The module stores its configuration, which on many engines includes a governed maximum speed9. PowerSpec reads a feature settings report and keeps a history of changes to those settings7. Regulators withdrew a proposed heavy-truck speed limiter mandate in July 20259, so a governed speed remains the manufacturer’s or carrier’s choice.
Time stamps. Detroit says its controllers keep time in GMT and that “clock drift will occur no matter what”4. ECM times are treated as approximate until matched against another clock, such as an ELD log or a camera time stamp.
How the data is downloaded
The data is read through the truck’s diagnostic connector with an adapter and the engine maker’s software: PowerSpec and related tools for Cummins, DDEC Reports for Detroit, and equivalents for other makers74.
The same tools can erase what they read. PowerSpec has buttons that reset trip information and inactive fault codes7, and the 2002 NHTSA report noted that a Detroit trip file “may be reset after it is extracted”1. Careful practice puts imaging first: the data is captured before the truck is started, moved, repaired or road-tested; each step is documented; and the raw download file is kept with any printed report. The work calls for people trained on the specific software. Where several parties have a stake, a download can be scheduled so each can attend.
Standard methods need a working module6. When the crash has disabled it, researchers have shown that records can be read straight from the memory chips, recovering a Last Stop Record, two Hard Brake events and a daily engine usage log from a Detroit DDEC V6.
How the data gets lost
Later events. Event storage is small. A report holding one to three records can lose the crash record if the truck logs more hard decelerations during recovery, towing or road testing. Driving the truck and stopping it again can replace the last stop record that matters.
Power. Starting the engine creates new data. Detroit warns that “if power is cut or interrupted during the data-writing sequence, more than likely data will be lost”4, and disconnecting batteries or cutting cables to free a damaged cab can do exactly that.
Service and salvage. A shop doing routine work may clear trip data and inactive faults. A replaced or reprogrammed module, or a truck sold for salvage, can take its data with it.
Physical damage. Fire, water and impact can destroy a module. Chip-level recovery works in some cases, not all.
How ECM data differs from ELD, telematics and camera records
| Source | Built to capture | Where it is kept |
|---|---|---|
| Engine ECM | Engine data; short event records | In the module |
| ELD | Driver duty status | Device and carrier system |
| Telematics | Location, speed, alerts | Vendor and carrier servers |
| Cameras | Video of road and driver | Device memory; vendor servers |
ELD records. An electronic logging device enforces hours-of-service limits. It records each duty status change with date, time, location, engine hours, miles and driver identity, plus an hourly entry while the truck moves3. Location is kept to about a 1-mile radius during on-duty driving, and carriers keep the records six months3. It is a log of the driver’s day, not a second-by-second account of a crash. See What an Electronic Logging Device Records.
Telematics. Fleet units send location, speed and alerts such as harsh-braking events to a vendor’s servers, kept as long as the contract and settings allow. They may read speed from the same network as the ECM, so the two are not always independent checks.
Cameras. Forward-facing and driver-facing cameras commonly record on a loop that overwrites itself and save clips when an event sets them off. Video shows the road and the driver but not throttle position; the ECM shows throttle but not where the other vehicle was.
Speed data has limits. Heavy-truck recorders can understate speed during hard braking, when wheel slip makes the wheels turn slower than the truck moves10. A study of Detroit engines in Freightliner’s New Cascadia found some Last Stop and Hard Braking records spaced points two seconds apart while reporting one-second intervals, an anomaly the record itself does not reveal8.
How reconstructionists use it
ECM data gives a reconstruction a timeline: speed in the seconds before the event, when the throttle released, how quickly the truck slowed and, where reported, when the brakes came on. Engineers test that timeline against tire marks, rest positions, crush damage and the other vehicle’s recorder. When numbers and physics disagree, the gap points somewhere useful: clock error, wheel slip, a missing record or a wrong assumption about the scene. The methods are covered in How Crash Reconstruction Works.
The module cannot say where the driver was looking or what the other vehicle did. That comes from video, witnesses and the scene, which is why investigators try to secure all of it before the clocks described in Evidence After a Commercial Vehicle Crash run out.
