OBDeleven ACC Fault Code removal help.

[pfgray2008]

I’m hoping someone with more experience with OBDeleven can help me out in finding a permanent way to remove a particular reoccurring Adaptive Cruise Control Fault code on VW 2019 VW Golf R NA spec car. At the moment the fault code is passive, the car seems to be functioning fine but the code keeps coming back for nearly a year now. I’m not sure what to do about? I have limited experience with troubleshooting errors. There are so many functions within the App I don’t fully understand what they and I certainly don’t want to make anything worse. How do I permanently get this removed? I don’t believe I’ve made any App purchase or coding changes for ACC system so I’m unsure what to do? I’ve attached my vehicles Diagnostic information below.

13 Adaptive Cruise Control



System description: ACC BOSCH MQB

Software number: 5Q0907572P

Software version: 0682

Hardware number: 3QF907572A

Hardware version: H11

ODX name: EV_ACCBOSCHVW416

ODX version: 002008

Long coding: 330000C159FFC728949C810580401600000000000000000004



Trouble codes:

U112100 - Databus missing message

Intermittent

Date: 2024-05-11 14:26:48

Mileage: 53872 km

Priority: 6

Malfunction frequency counter: 15

Unlearning counter: 7

Dynamic environmental data: 028D58028591101106F81012F4CC102E02

[dv52 (Australia)]

Paul: hi.

Good - as I say in my signature below, the forum is the proper place for these type of questions!

So, I'm really not sure if I can help with this matter because the ONLY error in the SCAN that you posted in your PM is U112100. 

The problem with this error message as a diagnostic prompt is that it's a general fault-code which really only identifies that for some reason, the module is expecting data that it never receives.

Sometimes a clue to the cause can be found in error messages in other modules - but whilst your SCAN does contain other error-codes, none line-up with the date/time stamp for the 13-module!

Normally I would suggest looking at the History records for the car and investigate coding changes related to the 13 -module - but you say this problem has persisted for a long period, so I suspect this approach might be problematic!!

Maybe your History records identify a very early version of the long-code string on the 13-module. If so, you could try reverting the long-code to this value and see if the error-code reappears

Also, since the error code is "Passive", it should be able to be cleared albeit it likely will reappear. Another approach is the clear the error and attempt to identify what feature on the 13-module is triggering the reappearance of the error-code!

Again, I admit that my suggestions are not strong - but as I say, the error-code doesn't provide much assistance in this instance!!

Don