An Aston Martin that spoke Mercedes
A DBX arrived with four warnings on the cluster at once:
- Active Distance Assist inoperative
- Fault: drive at max. 80 km/h
- Malfunction: see owner's manual
- 48V on-board electrical system malfunction
It left with none of them.
The interesting part is not that they cleared. It is that an owner reading that cluster is being spoken to in a language that belongs to another manufacturer, and nobody told him that was normal.
Why does an Aston Martin throw faults written in Mercedes language?
Because a great deal of what is underneath is Mercedes.
The DBX runs the Mercedes-AMG M177, the 4.0 litre twin-turbo V8, rated at 550 PS and 700 Nm in this application. The relationship does not stop at the engine. The driver assistance and electrical architecture come across from the same source, which is why the cluster says Active Distance Assist rather than whatever Aston Martin's marketing department would have called it. That is Mercedes wording for adaptive cruise control.
This matters for one practical reason. An owner who searches that phrase finds Mercedes forums, Mercedes fault codes and Mercedes advice, and reasonably concludes that either the search is wrong or the car is. Neither is true. It also means a workshop that only knows Aston Martin will be reading a system it has never seen, and a workshop that knows Mercedes will recognise it immediately.
What is the 48V system on a DBX actually doing?
This is the one most people get wrong, because "48 volt" has come to mean "mild hybrid" and here it does not.
The DBX uses a 48 volt electronic active roll control system, rated at roughly 1,400 Nm. It stiffens and releases the anti-roll bars actively as the car loads up in a corner, and it slackens them off completely when the car is crawling over rough ground so the axles can articulate. It is the reason a two tonne SUV with a high roof does not lean like one.
That takes real force, and real force takes current. Running it at 48 volts instead of the usual 12 is what makes the electrical side of it practical.
So a 48V on-board electrical system malfunction on this car is not a vague electrical grumble. It sits on the system that controls how the vehicle behaves in a corner. That is worth knowing before anyone offers to clear it and hand the keys back.
Why did the car limit itself to 80 km/h?
Almost certainly it did not decide that on its own account. A speed restriction is a protective response, not an independent fault.
The logic is straightforward once you see it from the car's side. Something that affects stability at speed has stopped reporting. The vehicle cannot verify that it will behave the way it was designed to at 140 km/h, so it restricts the driver to a speed where the consequences of being wrong are smaller. On a tall, heavy SUV that is a sensible thing for it to do.
Which is why "drive at max. 80 km/h" is the wrong thing to chase. It is a symptom. Clear it without addressing what caused it and the car will simply set it again, having been proved right.
Is "Active Distance Assist inoperative" a radar fault?
It can be. It very often is not.
Adaptive cruise depends on a radar or camera seeing the road, on the network carrying that information, and on the module having stable power to do anything with it. Any one of those failing produces the same message on the cluster. The message tells you a function is unavailable. It does not tell you why.
That is the general shape of modern diagnosis and it is worth stating plainly: the warning names the function that stopped, not the part that failed. Those are different questions, and only the second one is a repair.
Why four warnings usually mean one cause
Modules on a car like this share power supplies, share a network, and depend on each other's data. One genuine fault therefore lights up several systems at once, each of them reporting honestly that it can no longer do its job.
Chasing four lights as four separate jobs is how a diagnosis turns into an open-ended bill. The useful first move is separating cause from consequence, and that comes out of the freeze frame data, the conditions the car recorded at the moment each fault set, rather than out of the fault list itself.
Sometimes the timestamps alone tell you. One fault sets, and three more follow within a second. The first one is the job.
What a generic scan tool sees here, and what it misses
A generic OBD reader is built around emissions-related powertrain codes. That is what the standard requires it to see, and on this car it is a small fraction of what is going on.
Chassis, body and driver assistance modules need manufacturer level access, and on a DBX that access is Mercedes. We read this car on Xentry over a C4 or C5 multiplexer, and drop into Vediamo where the job needs parameters Xentry will not expose. Same software the wording on the cluster came from.
And a good deal of what actually matters is not a stored code at all: supply voltages under load, which modules can still see each other on the network, whether a value is missing or merely implausible, and what the conditions were when it all went wrong.
That is the difference between reading a car and scanning it.
When does ADAS need recalibrating rather than clearing?
Whenever the sensor has moved relative to the road, or the car has.
Windscreen replacement is the common one, because the forward camera usually sits on it. So is anything that changes ride height or geometry: suspension work, a different tyre size, an accident repair. The sensor can be electrically perfect and still be aiming at the wrong part of the world, and a system that measures distance while pointed slightly high or low is worse than one that admits it is unavailable.
Clearing a distance assist fault after that kind of work, without recalibrating, produces a car with no warning light and a system quietly measuring the wrong thing. That is a job in its own right: ADAS calibration, and there is a longer piece on what a windscreen replacement moves if that is how your car got here.
What we actually did
Read the whole car, not the four lights. Established which fault set first and which followed it. Fixed the cause, confirmed the dependent systems came back on their own, and re-ran the scan to make sure nothing was still logged.
The car went out with a clean cluster. That part is not remarkable. What makes the difference is that it went out knowing why, which is the only version where it stays fixed.
If your car is showing several warnings at once and someone has offered to clear them, ask which one they think came first. It is a fair question and the answer tells you a lot.
