kb
New Member
Posts: 5
|
Post by kb on Aug 13, 2020 15:40:28 GMT
I have a 2020 Passat purchased in Australia few weeks ago. I was trying some long coding and noticed the car started throwing an error that the ACC was "Unavalable". I started reversing the changes I made but the error persisted. I then went through and reversed every setting I have *ever* made, and I still have the same error. I've triple-checked Even made a spreadsheet of the settings, and checked they had all been set back to the original values. I have attached the history. I'd appreciate any assistance! Seems relevant - somehow "Gateway Coding" removed a bunch of stuff for some reason: UPDATE 1:From the history Gateway coding Removed: (0A) null (15) Airbag (4E) Control Head Rear Right (4F) Central Electrics 2 (57) TV Tuner Mileage: 1689 km Date: 2020-08-13 22:14 What does this mean? Why would it do this? UPDATE 2:Ok, figured out that bit. I'm not sure why the Gateway AutoCode feature removed those modules - maybe the ignition was off? But that was sort of a red herring. I've re-run the AutoCoding and the list all looks good now (This cupra280.co.uk/obd11.html#Autocode was incredibly helpful!). I still have the original problem - ACC has the error. Attachments:history.txt (31.04 KB)
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Aug 15, 2020 8:18:11 GMT
kb sorry I don't know your car and its on a different platform to my MQB one.
However looking through your history i note you did a basic setting on the ACC
Basic settings Control unit: 13 Adaptive Cruise Control Name: Reset personalization settings Status: active Mileage: 1689 km Date: 2020-08-13 21:31
as I say I don't know this car but are you able to update personalization stuff via the MIB unit.
|
|
kb
New Member
Posts: 5
|
Post by kb on Aug 16, 2020 22:22:09 GMT
Hi testeronline,
Thanks for taking a look!
I have been back into the settings on the infotainment unit and turned off/on ACC. I also tried switching some of the other options, too. I haven't tried going through every single option. Worth a try I guess!
I think the error started when I wanted to enable High Beam Assist. It came up with the list of headlight technology to chose from and I picked MatrixBeam then it started getting the error. I tried changing it back and tried every other headlight type but the error has been there since that change.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Aug 18, 2020 9:27:04 GMT
Sorry did not see your reply, I am guessing (and it is only a guess) that because you have changed the headlight type you lost the factory basic settings, if you look in you basic settings menu do you have anything about your lights - If you see anything with factory reset on it please DO NOT use it as some of these can cause lots of issues
|
|
kb
New Member
Posts: 5
|
Post by kb on Aug 19, 2020 0:09:23 GMT
Hi testeronline,
That sounds like what might have happened. I didn't know that was possible.
In the Basic Settings menu I see:
Resetting of all adaptation values Search calibration target ... several "online calibration" options - "Assembly line", "Customer Service", "Trailing End"... Initial data input with construction data Partial softare test Testing communication relationships Release of a SWaP function Deletion of a SWaP function ... there several that appear related to ethernet connectivity Reset_of_EEPROM_fault_memory Delete developer event memory structure Start calibration mode
Do any of those appear promising?
Update The above Basic Settings were in the A5 Driver Assistance module. In the Central Electrics 09 module I see a Basic Setting called "Basic Headlamp Setting". Could that be relevant? There's also "Reseting counter for headlight range adjustment"
|
|