RS246.com Forum :: The World's #1 Audi R, S and RS Enthusiast Community

Just bought a B7 RS4 (06) and am thoughrouly impressed with the car overall, however there are one or two issues, the main being this adaptive headlight fault I'm getting.

So far the fault has been totally intermittent and I can't seem to replicate it through operation of the light controls etc. When the fault occurs a yellow headlamp symbol flashes in the top section of the information screen behind the wheel and both the headlights and the wipers stop working until the fault clears (approx 10 sec).

Anyone else experienced this or anything similar?

Don

Welcome and FON.

Really, you'll need VCDS/Vagcom (or someone who does) to run a check really. After that, it could be one of or a combination of, bulbs, ballast, auto levelling sensor or it may just need any error codes clearing with Vagcom and see if it continues to persist. I suspect it is an error with the above as it re-occurs.

A bit more detail: http://nickscarblog.com/diy/how-to-fix- ... on-an-audi

My bet would be a failing ballast.

VCDS/Vagcom is you friend and indeed is the search box on this site...

Good luck.

Mine did this before - unfortunately before I bought it so I don't know what Reading Audi did to fix it. If it is an adaptive headlight fault it shows up as a different warning symbol to bulbs etc. - it may be worth logging in via VCDS and "adjusting" the headlights to see if that resolves it.

Here is the error light if is the adaptive light rather than the bulb -

I've got that error light but mine is because the lights have been set into tourist mode in Vagcom as I recently went to Belgium

MB2's is Dynamic headlight range fault - really need Vagcom

Appreciate the rapid and insightful responses fellas. The fault symbol looked very similar to the one in MB2's image from what I can recall but I'm not positive it was. I'll try to get hold of a VAG-COM and in the mean time attempt to recreate the fault and take note of which symbol it was exactly.

Donovan wrote:Appreciate the rapid and insightful responses fellas. The fault symbol looked very similar to the one in MB2's image from what I can recall but I'm not positive it was. I'll try to get hold of a VAG-COM and in the mean time attempt to recreate the fault and take note of which symbol it was exactly.

Put a post out to see if anyone is close to you with VAG-COM... I helped a few forum members with a few re-codes with mine recently...

I've just gone and bought one from a website called Gendan. I figured this won't be the only time I'll need it and I'd ideally like to be able to fix this issue and any future issues myself with a little expert knowledge from you forum veterans

Donovan wrote:I've just gone and bought one from a website called Gendan. I figured this won't be the only time I'll need it and I'd ideally like to be able to fix this issue and any future issues myself with a little expert knowledge from you forum veterans

Nice one - I purchased mine from Gendan.

VagCom is invaluable! I used it for a bunch of stuff to diagnose and tweak adaptions

have a look here i think this guy has done a fix

http://nickscarblog.com/diy/how-to-fix- ... on-an-audi

Yeah thanks for that Rick, neilparf posted the same link and I has a look through. I figured that eventually I'd get a diagnostics tool and if that aids me in diagnosing the fault or component then I'll try that first before blindly throwing cash and parts at it until it's fixed.

Bit of an update, my VCDS came!

But with it comes a <beep> storm of incomprehensible garble, at least that's what I've come to accept it as. I ran the auto-scan feature after selecting the chassis and lo and behold there's war and peace in a text file full of errors. Most of it seems to be centered around an intermittent control module fault, but other than that I can't really make heads or tails of it.

I'm not sure how much sense it will make to anyone here but I've dumped it into a pastebin anyway for the time being: http://pastebin.com/PndYecAB

I didn't expect using the VCDS effectively would be a walk in the park but it seems I have a lot more research to do before it's much use to me

did you clear it all then scan it again?

most of that is probably a low/flat battery

No, I didn't. I'll give that a try tomorrow. I was considering clearing them. It thought there may be some useful info in there. I have it printed out now either way and will try clearing and rescanning in the morning. Cheers!

that could be ages old, might have to give it a 5 min blast to check everything, and really ignition needs to go on and off 3 times to log any serious code