Quick Answer
Intermittent fault codes are best diagnosed with continuous data logging rather than a single snapshot scan — because the fault, by definition, isn't present when the truck is sitting in the bay. Freeze frame data, a road test with a logging tool attached, and correlating the fault timestamp against live parameters (voltage, temperature, vibration prone connectors) is what actually isolates the cause.
Why Intermittent Codes Are Hard to Catch
A code that sets on the road and clears by the time the truck reaches the bay is the single most time consuming diagnostic scenario in a heavy duty shop. A static scan only tells you the fault happened at some point — it won't tell you what conditions triggered it, which is the actual information you need to fix it rather than just clear it.
Start With Freeze Frame Data
Before doing anything else, pull the freeze frame (or "snapshot") data attached to the code — most J1939-compliant ECUs capture engine speed, load, coolant temperature, and voltage at the moment the fault set. This narrows the search significantly: a code that only freeze frames under high load points somewhere very different than one that freeze frames at idle with low voltage.
Set Up a Road Test Data Log
If freeze frame data isn't conclusive, the next step is a live logging session during an actual road test replicating the conditions the driver reported. Most dealer level tools (VOCOM2+, SDP3, DAVIE) support continuous parameter logging that can be reviewed after the drive rather than needing someone to watch a screen in real time. Log at minimum: the suspect SPN/PGN, system voltage, and any parameter physically linked to the suspected component (temperature, pressure, position).
Correlate the Fault Against Conditions
Once you have a log with the fault timestamp, look at what changed in the seconds immediately before it — a voltage dip often points to a connector or ground issue rather than the sensor itself; a fault that only appears over rough road or at certain RPM ranges often points to a chafed harness or a loose connector shaking loose under vibration.
Common Culprits
- Corroded or loose connectors — especially at harness junctions exposed to road spray.
- Chafed wiring against frame rails or moving components, causing intermittent shorts.
- Marginal ground points that only fail under vibration or thermal expansion.
- Voltage sag from a failing alternator or battery under load, which can trigger multiple unrelated looking codes at once.
Key Takeaways
- Freeze frame data is the first thing to pull — it tells you the conditions at the moment the fault set.
- A static shop scan rarely resolves an intermittent fault on its own; a logged road test usually will.
- Voltage dips right before a fault often point to a connector or ground issue, not the sensor itself.
- Multiple unrelated codes appearing together is a common signature of a voltage or ground problem, not several simultaneous sensor failures.
Frequently Asked Questions
Most ECUs automatically clear an active code to "inactive" or "historic" status once the triggering condition is no longer present, even though the underlying cause may still exist. That's why freeze frame data and live logging matter more than the code itself.
A logged road test that replicates the conditions the driver reported — load, speed, road surface — is far more effective than repeated static scans in the bay.
Yes, most dealer level tools support background logging that can be reviewed afterward, which is the practical way to capture a fault during a real road test.