The wording on the cluster is the one part of the car that never varies, and it still leaves out the one thing you need to know: is this a pull-over-now message, a book-it-this-week message, or a message that is simply telling you something? We sort all three below, then work through each one properly.
Mercedes clusters use the same three-colour system across every generation on Singapore roads, and it is a better guide to urgency than the words underneath it. These are the eighteen you will see most, grouped by what they are actually asking of you. Wording is quoted as it appears in the owner’s literature and forum reports for these cars; a small number of cars phrase a line slightly differently, and where that happens we say so.
Mercedes writes its dash messages for consistency across the range, not for diagnosis. “Malfunction, visit workshop” covers the power steering, the fuel system and a suspension fault with the same three words, because the cluster software is shared across models built years and continents apart. The car is not being unhelpful on purpose. It genuinely does not know which of several possible faults raised the flag until someone plugs into the actual module and reads what it logged.
The auxiliary battery message is the clearest example of this on our own pages: the same wording covers a small battery, a sealed converter module with no cells in it, a tired main battery, a charging fault, or current quietly draining overnight, and each needs a completely different fix. We take that one apart in full on the auxiliary battery page rather than repeating it here.
It works the other way too. Once one system starts struggling, modules that have nothing wrong with them can log their own complaint simply because the supply they depend on has gone unsteady. A single real fault can arrive on the cluster looking like three or four, and reading them in the order they appeared, rather than reacting to whichever is newest, is usually what separates a short visit from a long one.
Owners naturally use the ignition switch as a first test. It is a fair instinct, but it settles less than it feels like it does, because a Mercedes cluster only shows what it is actively checking right now, not everything sitting in the fault memory.
The practical test is not whether the light goes out. It is whether the fault memory is empty when someone actually reads it, and whether the same message comes back within a week of ordinary driving. A message that keeps returning after every restart is telling you the underlying fault is still there and simply waiting for the right conditions to show itself again.
Not sure which tier your message belongs in, or whether it matches anything above? Send a photo of the cluster and your model, and we will tell you what to expect before you drive over.
WhatsApp us a photoThe wording, whether it is steady or flashing, and roughly when it first showed. A photo of the cluster settles more of this than a description does.
The newest complaint is read alongside the older ones. Older stored faults often explain why the new one turned up, and reading them out of order sends the diagnosis the wrong way.
A fault memory tells you what happened. Live data from sensors and modules tells you what is happening right now, which is what a stored code alone cannot show.
Some faults only show under load, at a particular speed, or after the car has been running a while. Reproducing that here beats guessing at what triggers it.
Which system raised the message, what the readings actually showed, and what that points to. This is the itemised quote, with labour kept apart from components.
A cleared code that reappears within a week means the underlying fault is still there. The car goes back out and gets read again before anyone calls the job finished.
A handful of these messages carry enough behind them that they have earned a full page of their own. This table is the short version and the signpost; the linked pages go through the systems, the generations affected and the checks in proper depth.
A message not on this table is not necessarily minor; some of the most generic wording, such as the plain “malfunction, visit workshop” line, covers too many different systems to sensibly cover on one page. Send us the exact words and we will tell you what to expect.
Auxiliary battery and 48V faults raise a family of codes read from the battery, charging and gateway modules rather than one single number. We keep the full breakdown of what these mean on the page each message belongs to rather than a bare code list here, because the same digits can mean different things depending on which module logged them.
A code that starts with a letter other than P (a body or network code) usually means one module could not get a sensible answer from another, which is exactly the pattern behind an unsteady electrical supply. It is a clue to chase the wiring, not proof of a single failed part.
A code reader in a phone app gives you the digits and a generic one-line description. What actually decides the fix is the freeze-frame data logged alongside it: the voltage, the load and the conditions at the moment it was recorded. That is what gets read here before anything is ordered.
Red asks you to stop driving as soon as it is safe, because continuing risks damage or a breakdown, such as an overheating engine or a transmission fault telling you to stop. Amber means the car can still be driven for now but wants attention within days, covering things like the auxiliary battery, Airmatic and ESP messages. White or blue is purely informational, such as a service reminder or a tyre pressure note, with no immediate safety concern.
Usually yes, for a short while, and most owners do exactly that. Amber messages tell you a system has logged a fault without demanding you stop immediately. The exception is a flashing check-engine symbol, which behaves like a red message even though the icon itself is amber-coloured, because an active misfire can damage the catalytic converter within minutes rather than days.
Because several modules can react to the same underlying issue and each files its own complaint. An unsteady electrical supply, for example, can upset modules that have nothing wrong with them individually. Reading the newest message first often points in the wrong direction, so the order the warnings arrived in matters more than how many there are on screen.
Sometimes, but a light going out is not proof the fault is gone. A restart clears what the cluster is showing right now, not necessarily what sits in the fault memory. Messages such as auxiliary battery or Airmatic warnings often fade after the car has been running a while and then reappear at the next cold start, because the underlying condition was never actually resolved.
Mercedes uses its own extended code format on top of the standard OBD-II codes, read from whichever module logged the fault: the battery, the charging system, or the network gateway linking modules together. The digits alone rarely tell the full story; what matters is the freeze-frame data recorded alongside each one, which is why we read the memory properly rather than quoting a code off a generic app.
We do not put a figure on it before the car has been read, because the same message can mean a short reset or a longer chase through several modules. Once the readings exist you get an itemised quote with labour apart from components, and nothing is ordered until you agree to it. Servicing here does not cost you your warranty, because the Competition and Consumer Commission of Singapore has required authorised dealers to drop terms that tie servicing to their own workshops; our page on your right to service where you want has the detail.
Servicing set for this climate, oil leaks sorted by engine family, the gearboxes, the suspension, and what else sits on that page.
Open the brand page →Where a current drain gets traced, and what we do about looms, earths and connectors that have gone unreliable.
See the electrical work →What a steady versus a flashing symbol means, and why clearing the code without reading it first solves nothing.
Read what to do →