What Makes a Fault Code Intermittent
An intermittent fault code is one that appears under some conditions and is absent under others. The underlying hardware or condition that caused the fault has not completely failed — it is degraded to the point where failure occurs under certain stressors (vibration, temperature change, humidity, high load) but recovers when those stressors are removed. Intermittent faults are among the most challenging to diagnose because they often cannot be reproduced in the shop environment under normal diagnostic conditions.
Common physical mechanisms for intermittent faults include: a connector with a terminal that makes and breaks contact under vibration, a sensor wire that is chafed and makes intermittent contact with a chassis ground, a sensor element that fails above a certain temperature and recovers as it cools, and a J1939 bus connection that has high resistance when cold but improves as the connector warms from operation. Each mechanism requires a different diagnostic approach.
Patterns That Help Identify Intermittent Fault Causes
Correlation between the fault's appearance and specific conditions is the most useful diagnostic information for intermittent faults. Faults that appear only after the truck has been running for 30 minutes or more (warm-start faults) often indicate a heat-sensitive condition — the component fails when hot and recovers when cold. Faults that appear at highway speeds but not at low speeds suggest vibration sensitivity or a speed-dependent electrical condition. Faults that appear only in rain or after a car wash suggest moisture intrusion into a connector or wiring.
Faults that appear only when the truck is loaded and disappear empty suggest load-induced vibration or flex in the vehicle structure is affecting a harness or connector routing. A symptom that appeared only after a specific maintenance event (wheel bearing replacement, harness repair, trailer connection change) suggests that the maintenance activity disturbed a component that was marginally functional.
Recording Intermittent Faults for Diagnostic Purposes
For intermittent faults, the driver's log is more valuable than the ECM's current state. The ECM stores inactive codes, but it cannot capture the driver's description of the pattern — when it appears, under what conditions, how long it lasts, and how it resolves. A driver who tracks the fault's occurrence in a simple note (date, time, temperature, operating conditions, duration) over several appearances creates a pattern that the technician can use to design a targeted diagnostic test.
The ECM's fault occurrence timestamps (visible in OEM diagnostic tools) can supplement the driver's log. If the ECM records the first occurrence, last occurrence, and number of occurrences for a stored fault, this data shows how long the fault has been present and how frequently it has recurred. A fault that has occurred 47 times in the past three months points to a chronic degraded condition rather than an isolated event.
Diagnostic Approaches for Intermittent Faults
Because intermittent faults often cannot be reproduced on demand, diagnostic techniques include: performing the diagnosis under the conditions that correlate with the fault (driving at highway speed, operating in cold weather, connecting a specific trailer), using a diagnostic tool with data logging capability to capture the moment the fault occurs in live data, and performing physical stress tests on connectors and harnesses (flexing connectors while monitoring live data for signal dropouts).
Connector inspection is particularly important for intermittent faults. A connector that looks acceptable in a static inspection — no obvious damage, no visible corrosion — may have terminal tension that has reduced, allowing the terminal to move slightly under vibration. Terminal tension can be measured with a pull-force gauge but is also often apparent when the connector is disassembled: a terminal that slides out too easily has inadequate retention force. Replacing a suspected intermittent connector is sometimes a justified diagnostic action even without definitive evidence of failure.
Related Pages
Sources
- SAE J1939 Standards Collection SAE International · official · accessed 2026-05-05 · confidence medium
Source: SAE International, SAE J1939 Standards Collection. This page paraphrases factual fields only and is not a substitute for the original document.
Open source - 49 CFR Part 393 - Parts and Accessories Necessary for Safe Operation Electronic Code of Federal Regulations · government · accessed 2026-05-05 · confidence high
Source: Electronic Code of Federal Regulations, 49 CFR Part 393 - Parts and Accessories Necessary for Safe Operation. This page paraphrases factual fields only and is not a substitute for the original document.
Open source
FAQ
If a code clears on its own and the truck runs fine, does it still need a shop visit?
That depends on what the code was for. An intermittent ABS code or brake system code warrants investigation regardless of whether it cleared. An intermittent aftertreatment code may be an early indicator of a DEF quality issue or dosing problem before it becomes consistent. A one-time electrical blip from a cold-start battery voltage dip may be less concerning. The pattern (how often it recurs, under what conditions) determines urgency.
What operating conditions help reproduce an intermittent fault for diagnosis?
Try to recreate the conditions under which the code first appeared: same load, route type, temperature, duration of driving, and any recent maintenance or fueling. If it appeared after a fuel fill, try the same DEF or diesel source. If it appeared only on long grades, drive a loaded grade. The freeze-frame data from the fault history can also show what the truck's parameters were when the code set, which helps identify the trigger.
Is freeze-frame data still useful for an intermittent code that already cleared?
Yes — if the ECM captured freeze-frame data when the code first set, that data remains in the fault history even after the code goes inactive. The technician can retrieve the operating conditions (speed, load, temperature, fuel pressure, etc.) at the moment of the fault. Not all ECMs capture freeze-frame for all codes, but for major emissions and protection faults it is usually available.