ACC Not working

[Latekale]

Hello! So my problem is that the ACC isn't working. This started year ago when it was very icy roads and i accidentally drove to very soft snow pile. There weren't even any scratches or marks from the small accident. ACC stopped working then and everything else worked normally and no other fault codes were generated.

Some time after the accident, I got the ACC working again, I remember shaking its connector a bit and using it in protection mode. I don't remember exactly what I did there, but half a year after i got it working i was driving on the highway and there was a slightly bigger puddle that I drove over and the ACC didn't like that. Now since then I haven't been able to get it to work. It's winter and snow again, and I noticed that a new error code appeared which complains that there is snow in front of the ACC, so it can see ahead, but it doesn't want to start in any way. Could someone help me? I would greatly appreciate your help. Thanks!

Golf mk7, 2013, 5-dr hatchback, 1.6TDI. 

ACC faulty codes:
Cruise Control Front Distance Range Sensor Separated, B10E7F0, static
Ctrl. Module Faulty B2000F0, static
Databus missing message U112100, Intermittent

Engine Faulty codes:
Databus error value received, U112300, static
Lost Communication with Cruise Control Front Distance Range Sensor, U023500, Intermittent , Voltage Terminal 30 (11.160v)

Also faulty codes that could be helpful:

Transmission, Lost communication with Cruise Control Module, U010400, Intermittent

Gateway, Lost Communication with Control Front Distance Range Sensor, U023500, Intermittent, Terminal 15 (on)

Air Conditioning, Function limitation due to energy management, B10CD00, Intermittent

[vwjap]

Sounds like you either bent the bracket or bent it a bit

[dv52 (Australia)]

Latekale : Hi. I suspect that vwjap is correct (again)!!

Your inclusion of the fault codes on this car is admirable - but there's lots more useful information in understanding the environment on the modules in this car by providing a copy of the actual SCAN report!

I'm not sure if you are aware of the process for digitizing the SCAN report, but maybe following is of interest (I assume that you are using the iOS version OBD11 software.

First - make sure that Freeze-frame is active on your OBD account - see HERE

1. Fire-up OBD11 software -connect to dongle and SCAN the car
2. Select History
3. 
4. when you receive the email that you sent to yourself - copy-and-paste the SCAN reort in a new post (as an attachment)
   

Don

[Latekale]

history.txt (13.88 KB)

[newty]

Looks like the ACC is itself diagnosing as faulty and therefore stopping all activity.
We saw some corroded contacts and connectors even with undamaged cars, so the connection is a good starting point.

[Latekale]

Hello!

I took the acc and checked connectors, they seemed fine to me. As well the cabling. I tried to shake the acc, but it was really tight and didn't wobble in any direction at all.
So to repeat myself, acc can tell if there is something ''blocking'' the way by sending a fault code ( come up when there was snow on it ), it can as well tell its ( terminal 15) voltage, temperature, vertical and horizontal angels, misalignment angle ( 0.0 degree).
The acc tells that radar beam intensity 1-4 Function cancelled, marginal conditions have not been met.

Last time i got it working after this kind of ''nonsense'' i remember i did try to use the component protection, output test's and poked the cables with finger if there is trash in the connector or bad connection. And after doing those it magically started working after a night.

Here is a fresh faulty code list (unfortunately it's in Finnish language, but I'm afraid it might change something wrong if I translate it) and a few photo i took when i had the bumber off.

Thanks for help!

-Latekale



Faulty codes
history.txt (11 KB)

[dv52 (Australia)]

Latekale : Hmm......... The Freeze frame data on your latest SCAN report tells a story that you can be read like a book.

Look at the dates on the 13 Adaptive Cruise Control module. Notice that the B2000F0 - Ctrl. module faulty error is dated early April 2023. Also notice that Malfunction frequency counter = 119.

So, the story about this module is like this: The SCAN date is end December 2023. The hex13 module on this car first reported an internal fault about 9 months ago!

There are 149 days between the date of the SCAN and the date of first B2000F0 fault registration. Since that first registration of the B2000F0 fault, the same error has re-appeared on 119 separate occasions in a subsequent ignition cycle. 

So the faulty ACC module error on this car has occurred nearly every day since first registration for about 9 x months!!.

Entirely separate to the faulty module error - the SCAN reports that the module was separated from the CAN network on 28th December 2023 - which normally means that the pre-set calibration variables that were stored in the module have been lost

My hunch is that the ACC module needs attention - possibly replacement ( note: this module is part of the Component Protection constellation)

Don

[newty]

Yep, seems really like the sensor is broken. Consider replacing it with a newer flat sensor. The Dome-Variants are extremely seldom and expensive.
Yep, you will need to do static calibration and component protection after installation

The ACC does not lose any calibration data when being disconnected. It is not connected to Clamp 30 and the CAN is disconnected with every ignition cycle as it is a easy way to illegally access the CAN (see recent news about Toyota)

[Latekale]

Hey! It's been a while since I looked for help here. I was too lazy to do anything about it a few months ago and now I've been wondering for a while how to fix the problem. Now OBDeleven shows that the acc does not exist. So here's a new list of faults if someone could help if the fault was somewhere other than the acc itself. I also have the option to buy a new acc if needed, but I want to be sure about it.

(Here, its again Finnish language because it might translate something wrong if i translate it to english.)

Faulty list
history 1.txt (13.92 KB)


And here is a picture of newer acc which i would use instead. If someone could tell me can i use it?? 
Its from VW Golf VII 2019





Thanks for help!!
-Latekale

[newty]

Yes and no.
Yes because you do not have the A5 Camera installed, which would be an issue with that upgrade
No because there is plenty of stuff to take care of.

This sensor has SWaP and CP.
You will need somebody to remove CP via ODIS-S and also has the means to circumvent SWaP by flashing a Software for which the SWaP FECs can be generated.

So this no Job for OBD11 at all I am afraid