When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Hi all.
My son has a 2018 Vantage (Merc 4.0V8 TT) with an intermittent ABS fault. It's coming up with C0503 so he replaced the relevant ABS sensor but is still getting the intermittent fault. With a deeper scan he's also getting codes B1589, B1592, B1593, U0415 and U0416, but some of these may be historic.
My questions are... Has anyone else come across the same problem with a similar vintage Vantage and know of any particular common issues? ...and other than AM online, is anyone aware of a workshop manual including wiring diagrams for this model?
Many thanks in advance for any help.
Regards, Rob.
Hi all.
My son has a 2018 Vantage (Merc 4.0V8 TT) with an intermittent ABS fault. It's coming up with C0503 so he replaced the relevant ABS sensor but is still getting the intermittent fault. With a deeper scan he's also getting codes B1589, B1592, B1593, U0415 and U0416, but some of these may be historic.
My questions are... Has anyone else come across the same problem with a similar vintage Vantage and know of any particular common issues? ...and other than AM online, is anyone aware of a workshop manual including wiring diagrams for this model?
Many thanks in advance for any help.
Regards, Rob.
if he replaced thy sensor did he clear all thy codes including permanent or old codes?
after I've cleared codes if some old stubborn codes remain (especially if the keep triggering the CEL) i disconnect both battery leads and hold the ends together for about 60 seconds and reconnect them... not sure if it works on late model AM but Do this on all my vehicles from on 2009 aston to my 2021 volvo
He is describing doing a "hard reset" by disconnecting the battery leads, touching the cable ends together (completely off the battery posts) for about 1 minute. This quickly causes the latent capacitance in the modules to drain off and will force all modules to completely reboot upon reconnection.
Further - whenever I see multiple codes with U-codes present, address the U-codes first (which the hard reset does). U-codes are networking codes. They occur when a module(s) lose their way on the CAN-BUS (can be for various reasons). Often the U-codes cause the other codes which can be C-codes (chassis), B-codes (body/security) and even P-codes (although these tend to be more uncommon).
If it were me, I would first do a global code delete (this can only be done with a deep scan tool, and not just an OBDII code reader). Then do the hard reset. Once the hard reset is done, start back up, do a short drive to warm up, Recheck the codes (or messages). If all the U-codes are cleared and do not come back, and if then you still have any B,C,P-codes, then those are real issues. If the U-codes return, then those are probably the real problems.