[Roger Oz]

2013 V8 deisel Toureg RLine with only 145,000 kms in excellent condition.
Love this car however. ACC (radar cruise control) not working. Previous original owner had it to multiple dealers under warranty and after warranty and no one was ever able to fix it. I am not willing to waste hard earned dollars and time making the same expensive mistake. Last time I posted this I was advised to have the battery tested. Did that and it was perfect. Have not taken it to a dealer for a scan as I dont like being ripped off and they cant fix it anyway. Anyone out there with a similar issue who knows how to fix it ?

Please dont suggest getting a scan as thats been done by experienced service departments at various VW dealers in Melbourne and was 100% unsuccessful

Also the only other issue is the drivers door red warning light which appears on the dash for no apparent reason occasionally, and you cant lock the car with the door sensor or the fob. It usually settles down by next morning and is fine for a few days until it happens again. I though it was being caused by the high pressure car wash, but it happened on a dry day recently and no water had been near the car for 4 days.
Any clues guys ?

Neither of these issues are battery related. It even happens after long trips.

 

[rgh0]

Read my previous posts on fixing this on my 2013 R Line V8 . Probably cable from camera to image processor but also could be camera or radars. This is why you need a VCDS scan to help pin it down, the VW dealers scans are crap and just say replace everything at huge cost.

The door warning is probably an independent issue

cheers
Rohan

 

[chewblekka]

Posting the results of a complete auto scan are detrimental. To suggest otherwise is ignorant.

 

[manu144x]

You need to drive the car with the scanner live, and monitor all the parameters and see exactly where and when it goes wrong.

You need to see what data is going in, what data is going out, as you drive.

The issue is that not everything that goes wrong is actually logged, the software it has to be intentionally written that way, maybe it's an issue they didn't anticipate, and a static scan log in the shop afterwards for logged errors won't be much help.

 

[pglennon.au]

Was there a solution found for the problem ?