Mercedes lost communication fault codes: U0100 to U0235

U-codes are network codes. When your Mercedes stores U0100, U0101, U0102, U0103, U0104, U0105, U0192, U0197, U0198, U0222 or U0235, it is not telling you that a component has failed. It is telling you that one control module has stopped hearing from another over the vehicle’s CAN bus.

What each code means

• U0100 – Lost communication with the engine control module (ECM/PCM)
• U0101 – Lost communication with the transmission control module
• U0102 – Lost communication with the transfer case control module
• U0103 – Lost communication with the gear shift module
• U0104 – Lost communication with the cruise control module
• U0105 – Lost communication with the fuel injector control module

U0192, U0197, U0198, U0222 and U0235 sit in the same family and follow the same logic, covering communication with further modules on the network including telephone, telematics, body and driver assistance systems. Mercedes applies some codes in this range to its own modules, so the exact module named can vary by model and year — which is precisely why these need reading against the correct Mercedes data rather than a generic code list.

Why these codes are different

A P-code usually points you at a component. A U-code points you at a conversation that has stopped. The module being complained about is frequently in perfect working order — the message simply is not arriving.

That is why swapping the named module is such an expensive mistake on these faults. Replacing an engine control module because the car reported U0100 can cost a great deal and change nothing at all.

Symptoms you are likely to notice

• Multiple warning lights appearing together, often across unrelated systems
• A dashboard that lights up like a Christmas tree on start-up, then partly clears
• Gearbox stuck in limp mode, or refusing to shift normally
• Cruise control, parking sensors or driver assistance features dropping out
• Intermittent no-start, or a car that starts perfectly one day and not the next
• Faults that appear in wet weather and disappear when everything dries out

What actually causes them

In our experience the common causes, roughly in order, are a weak or failing battery and poor charging voltage; corroded earth points and damaged connector pins; water ingress, especially into connectors in the wheel arches, boot and under the scuttle; chafed CAN wiring where a loom passes through a bulkhead or across a moving part; and only then an actually failed module.

Low system voltage deserves a special mention. Modules drop off the network when voltage sags, and a tired battery will set a spread of U-codes that look alarming and clear the moment the battery is replaced. Checking battery and charging health first is not us being slow — it is the cheapest thing on the list.

How we diagnose it

Network faults are found with the right equipment and a methodical approach, not by guesswork. We start with battery and charging system health, then scan every module rather than just the engine, because the pattern of which modules can and cannot be seen tells you where on the network the break is. From there we test the CAN circuits directly for resistance, continuity and interference, and we check the connectors and earths that experience says fail first.

We invested heavily in a dedicated electrical diagnostic bay for exactly this kind of work. Intermittent network faults are the jobs many garages turn away because they take time and proper equipment to trace.

Book your Mercedes in

We are an independent garage on Sloper Road in Cardiff working on all makes. If your Mercedes is showing communication faults, call 02920 220 380 and describe what the dashboard is doing — the pattern often tells us where to start.

See also our vehicle diagnostics service, our electrical fault finding, and the full Mercedes fault code list.