You’ve had this conversation. You bring the car in because something isn’t right — a warning light, a noise, a hesitation that keeps happening on your commute. The garage takes it in, runs the diagnostics, has a look, drives it around the block. They call you. Everything is fine. No fault found. You pick the car up and drive it home — and within twenty minutes, it does exactly what it’s been doing all along.
This experience is one of the most frustrating in car ownership. It can make you feel dismissed, or that you’re being fobbed off, or — more insidiously — that you might be imagining the problem. Most owners who’ve been through it have a residual wariness about whether any garage will actually resolve it, because the history of bringing it in and leaving with the same issue has eroded confidence.
The frustration is entirely valid. But in most cases, the explanation is not that the garage missed something obvious or didn’t bother to look properly. It is something more specific — a set of technical reasons why certain categories of fault are genuinely difficult to reproduce in workshop conditions, and why a diagnostic scan run on a cold, parked car captures a different picture than the car presents during your normal drive.
Understanding those reasons doesn’t make the problem easier to live with. But it does explain what’s happening, and more importantly, it points toward what a proper investigation actually looks like.
The Diagnostic Window Problem
A standard diagnostic scan reads fault codes that have been stored in the ECU — records of events where a measured value exceeded a defined threshold and the system logged a fault. This is a snapshot, taken at a moment in time, of what the car’s systems have registered as definite faults.
The problem is that many real-world faults are not definite. They are intermittent. The sensor reading goes out of range under specific conditions — a certain engine temperature, a certain load, a certain combination of operating parameters — and then returns to normal when those conditions change. The ECU may or may not log a fault depending on how far the reading exceeded the threshold, how long it persisted, and whether the system reached its defined trigger point for storing a code.
An intermittent fault that has not yet crossed the logging threshold will not appear on a diagnostic scan. An intermittent fault that crossed the threshold under driving conditions, stored a code, and then cleared itself when the conditions changed may show as a pending code — a code that was seen once but not confirmed — or may have already been overwritten in the code buffer by other events. A garage running a scan on a car that arrived at ambient temperature, parked, may be looking at a clean log that tells them nothing about what was happening at 80°C on the dual carriageway.
This is not a failure of the diagnostic tool. It is a fundamental limitation of code-reading as a diagnostic method — one that experienced technicians understand and work around, and that less experienced ones sometimes treat as the whole story.
Heat Cycles and Why They Change Everything
Temperature is one of the most significant variables in how a Mercedes behaves — and it is the variable most likely to be different between the fault occurring in normal use and the car being examined in the workshop.
Thermal expansion. Metal expands when it heats up and contracts when it cools. In an engine with a developing crack, a degrading gasket, or a component at the borderline of its tolerance, the difference between cold and hot dimensions can be the difference between a system that holds and one that doesn’t. A hairline crack in an intake manifold that is tight when cold may open fractionally under thermal expansion at full operating temperature, allowing a small air leak that creates a lean mixture fault and a hesitation under load. Cold, at rest in the workshop, the crack is closed, the manifold holds pressure, and the diagnostic scan finds nothing.
This is a real and documented failure mode on several Mercedes engine families. The OM651 diesel and the M272/M273 V6/V8 petrol engines both have known sensitivities to intake and exhaust component behaviour that changes between cold and hot conditions. An experienced Mercedes specialist knows to test these systems at temperature — not cold on the ramp.
Sensor drift under heat. Many sensors that read accurately when cold drift slightly as they warm up. A sensor with a marginal fault may read within specification at ambient temperature and outside specification once the engine has been running for twenty minutes. The ECU will not register a fault during the workshop scan. It will register one — or simply run the engine on incorrect data without registering a fault — during the drive home.
Mass airflow sensors on petrol Mercedes units are particularly prone to this pattern. They function correctly at startup and begin to under-read as temperature builds, causing the fuel trim to compensate with a progressively richer mixture, creating the flat, unresponsive feeling under load that the driver reports but the garage cannot find.
Cooling system behaviour. Thermostat faults, water pump wear, and coolant temperature sensor inaccuracies often manifest only once the engine is under sustained thermal load. A thermostat that is opening too early — a common Mercedes fault that causes the engine to run below optimal temperature — will allow the engine to warm to a superficially normal temperature during a short workshop test drive, then allow it to cool during motorway running. The driver experiences the effect: poor fuel economy, sluggish performance, occasional rough running. The scan shows a coolant temperature within range, because it was within range when the car was assessed.
Intermittent Electrical Faults: The Hardest Category
If heat-dependent mechanical faults are difficult to diagnose in workshop conditions, intermittent electrical faults are harder still.
Modern Mercedes vehicles contain dozens of control modules, connected by a network of CAN bus communication lines. Every module talks to the others, and the health of that communication network affects how the whole car behaves. Faults in the communication network — a loose connector, a pin that has partially backed out of its housing, a wire with a developing break in the insulation — typically manifest as intermittent disruption, not constant failure.
A connector that is marginally loose may make good contact when the car is cold and stationary. Once the car has been driven for twenty minutes, thermal expansion of the connector housing, vibration from the road, and the mechanical flex of the engine bay under load combine to break the contact. The module that relies on that connection loses its data feed. A fault is logged — or isn’t, if the disruption is brief enough — and the symptom the driver experiences appears.
At the workshop, the car is cold and stationary. The connector is making contact. The scan shows a pending code from the previous event, or nothing at all. The technician wiggles the harness, sees no movement, replaces nothing. The fault returns within a day.
Finding this kind of fault requires a different approach. Not a scan, but a live data session — monitoring the communication between modules in real time, looking for the dropout that occurs under specific conditions. It requires knowing which modules are involved based on the symptom, understanding the architecture of the CAN network on that vehicle generation, and having the patience to reproduce the conditions under which the fault occurs.
This is diagnostic work in the real sense — not running a tool and reading a result, but building a picture of what is happening and designing a test that will catch it. It is the kind of work that distinguishes a specialist from a general garage, and an experienced technician from someone running through a checklist.
“It Was Fine When We Drove It”
The test drive is the most common response to an intermittent fault report, and it is also the most commonly inadequate one.
A test drive around the block from a cold start tells a technician how a car behaves at low temperature, low load, and low speed, for a short duration. If the fault occurs on a warm engine, under sustained load, at motorway speeds, or after a specific sequence of conditions — a cold overnight soak followed by immediate motorway driving, for example — a brief local test drive will not reproduce it.
A test drive designed to diagnose an intermittent fault looks different. It replicates the conditions under which the driver experiences the fault as closely as possible. If the fault occurs after twenty minutes on a dual carriageway, the test drive is twenty minutes on a dual carriageway. If it occurs specifically on cold mornings in the first five minutes, the car needs to be tested after an overnight soak, in those ambient temperatures, at that point in the warm-up cycle.
This takes time. It requires a technician who understands what they are looking for and has connected the right equipment to monitor live data during the drive, not just before and after. It is not always practical, and not every garage structures their workflow around it. But it is the only reliable way to catch an intermittent fault in the act.
Why This Matters for Who You Choose
The practical consequence of all of the above is that diagnosing intermittent faults requires more than a diagnostic tool and a willingness to look at the codes. It requires knowledge of the specific failure modes and thermal sensitivities of Mercedes engines and electrical systems, the ability to read live data and recognise what deviates from normal, and the methodology to test under conditions that actually reproduce the fault.
It also requires honesty with the customer. If a fault cannot be reproduced in a single workshop visit, the right response is to explain why, describe what conditions are needed to catch it, and agree a plan — whether that means a longer loan of the car, an extended test under specific conditions, or a targeted inspection of the most likely causes given the symptom pattern.
What is not acceptable, and what erodes trust quickly, is “we couldn’t find anything” delivered without explanation — as if the customer’s experience of a genuine fault is simply mistaken.
The customers who bring intermittent faults to a garage are not imagining things. They are describing real events that their car is producing under real conditions. The job is to find the conditions that reproduce those events and stay with the diagnosis until they’re caught.
What to Tell Your Garage Next Time
If you are bringing a Mercedes in for an intermittent fault, the information that makes the technician’s job most productive is:
- When exactly does it happen — cold start, warm engine, sustained motorway driving, specific gear changes, hard acceleration?
- How long into a journey does it typically appear?
- Does it go away on its own, and if so, how quickly?
- Has it been more frequent recently, or is the pattern consistent?
- Is there any warning light, even briefly, or is it purely a felt symptom?
This information narrows the diagnostic territory considerably. An intermittent fault described as “it happens on my morning commute, about ten minutes in, when the engine is warm but not hot, always under hard acceleration from a roundabout” is a fault with a defined set of conditions to test against. “It just feels wrong sometimes” is not — and while both are legitimate experiences, only the first gives a technician the map they need to find it.
The problem with intermittent faults is not that they are unfindable. It is that finding them requires the right approach, the right conditions, and someone who knows enough about the car to know where to look.
MB Wirral are Mercedes-Benz specialists on the Wirral. If you’ve been told nothing was found and you know that’s not the whole story, bring it to us. We have the equipment, the experience, and the time to find what others miss.
