- Joined
- May 27, 2017
- Messages
- 3,335
- Reaction score
- 2,086
- Location
- Finland
- VCDS Serial number
- C?ID=280813
And here's my ACC coding as promised :
I see a few databus missing messages on some of the modules. That, like error says, indicates mismatch in communication which could be due to hardware incompatibility, too old software in the module or incorrect adaptation value. Also too old CAN gateway module can cause this.
That might cause noticeable disruption in operation. In my case when ACC retrofit was complete, it was noticed that ABS missing message errors were due to a too old instrument cluster hardware which did not support ACC graphics. So I could not change ACC distance from the stalk and also city safety was not operating at all.
When I bought and had a new instrument cluster installed and I updated the CAN gateway module software to a much newer one, all errors went away.
Code:
Address 13: Auto Dist. Reg (J428) Labels:. User\5Q0-907-567.lbl
Part No SW: 5Q0 907 567 L HW: 5Q0 907 567 L
Component: ACC3 H10 0098
Serial number: 14051403090731
Coding: 00011400FE030B
Shop #: WSC 12345 124 12345
ASAM Dataset: EV_ACCBoschMQB 001024
ROD: N/A
VCID: 44BEC25ACFD31766EE-8010
I see a few databus missing messages on some of the modules. That, like error says, indicates mismatch in communication which could be due to hardware incompatibility, too old software in the module or incorrect adaptation value. Also too old CAN gateway module can cause this.
That might cause noticeable disruption in operation. In my case when ACC retrofit was complete, it was noticed that ABS missing message errors were due to a too old instrument cluster hardware which did not support ACC graphics. So I could not change ACC distance from the stalk and also city safety was not operating at all.
When I bought and had a new instrument cluster installed and I updated the CAN gateway module software to a much newer one, all errors went away.