Golf R Fault Codes - CAN Gateway

[Reedy]

Hey folks, not wanting to sound like too much of an amateur but I have these Fault codes in the Gateway section on the obd11. Unsure whether they were there before I started tweaking but just happened to come across them. The car has no engine on and runs perfect.
Tweaks performed
3 to 4 blinks
Auto coming home lights with drivers door
Lock unlock chirp
Sunroof open fully on unlock
Few based traffic. (Does not work)
Auto close with rain. (Does not work)
Help would be appreciated or just I've nothing to worry about or stop messing you amateur.

OBDeleven data log

Date: 2016-10-27 19:52

VIN: WVWZZZAUZFW075389
Car: Volkswagen Golf
Year: 2015
Engine: CJXB
Mileage: 36815 KM

---------------------------------------------------------------
19 Gateway

System description: GW MQB High
Software number: 5Q0907530T
Software version: 1188
Hardware number: 5Q0907530F
Hardware version: 128
Serial number: 0002316346
ODX name: EV_GatewLear
ODX version: 011016
Long coding: 030100042B085900EF00027E880F0001000105000000000000 0000000000

Subsystems:
System description: J367-BDMHella
Software version: 8043
Hardware version: H03
Serial number: 3025284003

System description: E221__MFL-DC1
Software version: 0038
Hardware version: H10
Serial number: 29140001488650084304
Long coding: 2CFFFF

Trouble codes:
U106600 - Radio No Communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2
U104000 - Axle differential lock control module No communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2
U114600 - Control module for special function 2 No communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2
U100F00 - Special purpose vehicle control module No communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2
U112600 - Undefined control module No communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2
U112600 - Undefined control module No communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2
U112600 - Undefined control module No communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2
U112600 - Undefined control module No communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2
U104C00 - Rearview camera system control module No communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2
U106A00 - Digital sound system control module No Communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2
U103D00 - Trip recorder control module No communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2
U112600 - Undefined control module No communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2
U112600 - Undefined control module No communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2
U112600 - Undefined control module No communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2



Tab2A7-20F


Sent from my iPhone using Tapatalk

[DV52]

Reedy: Wow - that's an impressive list of trouble-codes on the CAN gateway!

My suggestion (for what it's worth) is that you try to clear all the DTCs, then re-poll the module. If any trouble codes reappear, post-up your history report.
Use the
tag at the start of the cut-and-paste and the [ /code] tag at the end if your history report is long.
If you do this correctly, you should get something that looks like this:

[code]

This is a copy of Reedy's history report from his/her OBD11 dongle



Use the Reply with Quote option to see how the tags work

Don

[Reedy]

Each time I clear them they come back within seconds, for example I can almost clear them all using the bin button all the way down to about 2 left and then the module refreshes and they all come back. Funny thing is I've no engine light and the car runs fine. Would this be a trip to the main stealer?


Sent from my iPhone using Tapatalk

[Reedy]

Kicking myself I didn't scan the car first before I started tweaking!!! Then I would know if my tweaking has caused these faults.


Sent from my iPhone using Tapatalk

[Umai Naa!!]

Incorrect coding in the Gateway, by the looks of things.

To me, it seems to be looking for control modules that aren't installed.

[DV52]

Umai Naa!! I agree that there appears to be something odd! That's why I want to see the history report. My suspicion is that there has been either a code-string error, or perhaps the gateway list has a few extra modules that shouldn't be there (perhaps)

Don

[Reedy]

Umai Naa!! I agree that there appears to be something odd! That's why I want to see the history report. My suspicion is that there has been either a code-string error, or perhaps the gateway list has a few extra modules that shouldn't be there (perhaps)

Don
First of all thanks for being patient with me, I'm very much a novice which is dangerous because I like to tweak and tinker.

Looking at faults more closely I do recognize them, they seem to be from when I tried to open the modules but the obd11 wouldn't let me, as though that funtion is not enabled on the obd11 and the the car is still trying to talk to those modules that I tried to open and don't exist. I did a hard reset on this module but they never went away. I've managed to clear them all but as soon as I refresh they all come back. Each fault though is from a module that failed to work on the obd11.

Sent from my Tab2A7-20F using Tapatalk

[Reedy]

Wonder if there is a way to reset the obd11 and start again?

Sent from my Tab2A7-20F using Tapatalk

[The One]

Hey folks, not wanting to sound like too much of an amateur but I have these Fault codes in the Gateway section on the obd11. Unsure whether they were there before I started tweaking but just happened to come across them. The car has no engine on and runs perfect.
Tweaks performed
3 to 4 blinks
Auto coming home lights with drivers door
Lock unlock chirp
Sunroof open fully on unlock
Few based traffic. (Does not work)
Auto close with rain. (Does not work)
Help would be appreciated or just I've nothing to worry about or stop messing you amateur.

OBDeleven data log

Date: 2016-10-27 19:52

VIN: WVWZZZAUZFW075389
Car: Volkswagen Golf
Year: 2015
Engine: CJXB
Mileage: 36815 KM

---------------------------------------------------------------
19 Gateway

System description: GW MQB High
Software number: 5Q0907530T
Software version: 1188
Hardware number: 5Q0907530F
Hardware version: 128
Serial number: 0002316346
ODX name: EV_GatewLear
ODX version: 011016
Long coding: 030100042B085900EF00027E880F0001000105000000000000 0000000000

Subsystems:
System description: J367-BDMHella
Software version: 8043
Hardware version: H03
Serial number: 3025284003

System description: E221__MFL-DC1
Software version: 0038
Hardware version: H10
Serial number: 29140001488650084304
Long coding: 2CFFFF

Trouble codes:
U106600 - Radio No Communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2
U104000 - Axle differential lock control module No communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2
U114600 - Control module for special function 2 No communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2
U100F00 - Special purpose vehicle control module No communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2
U112600 - Undefined control module No communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2
U112600 - Undefined control module No communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2
U112600 - Undefined control module No communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2
U112600 - Undefined control module No communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2
U104C00 - Rearview camera system control module No communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2
U106A00 - Digital sound system control module No Communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2
U103D00 - Trip recorder control module No communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2
U112600 - Undefined control module No communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2
U112600 - Undefined control module No communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2
U112600 - Undefined control module No communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2



Tab2A7-20F


Sent from my iPhone using Tapatalk

Defiantly incorrect coding in gateway. If dealer is nice enough they will recode the gateway online for you (you will loose all your tweaks), but you will still call them a stealership...

Otherwise find a comparable Golf R and re-code your gateway yourself, next time save a autoscan/log before you tweak things. Goodluck.

[Reedy]

Cheers mate, I'm going to use VW for my next service so might see how I go. Are these faults effecting my car and the way it drives?

Sent from my Tab2A7-20F using Tapatalk

[The One]

Cheers mate, I'm going to use VW for my next service so might see how I go. Are these faults effecting my car and the way it drives?

Sent from my Tab2A7-20F using Tapatalk

You've got:

Trouble codes:
U106600 - Radio No Communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2
U104000 - Axle differential lock control module No communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2

Golf 7 MQB uses high speed CAN, so no communication in radio (5f) will shut it down completely, does your radio work? I assume so as you're saying no isses - than no, not effecting your vehicle. Your car is basically just looking for modules that it thinks are there (coding) but they are not, so it's saying no communication faults as it can not communicate with them, all is okay, just be nice to your dealer (I assume Australs?) and they may be happy to help since online coding doesn't take long.

[Reedy]

You've got:

Trouble codes:
U106600 - Radio No Communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2
U104000 - Axle differential lock control module No communication
static
Terminal 15: On
Supply voltage, terminal 30: 11.7 V
Unknown ambient data:
Date: 2016-10-27 19:46:44
Malfunction frequency counter: 1
Unlearning counter: 202
Mileage: 36815 km
Priority: 2

Golf 7 MQB uses high speed CAN, so no communication in radio (5f) will shut it down completely, does your radio work? I assume so as you're saying no isses - than no, not effecting your vehicle. Your car is basically just looking for modules that it thinks are there (coding) but they are not, so it's saying no communication faults as it can not communicate with them, all is okay, just be nice to your dealer (I assume Australs?) and they may be happy to help since online coding doesn't take long.
Cheers mate, no issues what so ever, everything appears to be working. Norris is where I go.

Sent from my Tab2A7-20F using Tapatalk

[DV52]

reedy: Of course you can try your dealer, but you don't get to learn anything by doing this - if, indeed you can find a dealer that is sympathetic to your problem and who is willing to fix the issue gratis. I'm sure such dealers exist, but I've not found one yet and I suspect that they are as rare as hen teeth!

It's extremely likely that the answer is in your history file because it retains a record of every change that you have made with the dongle. You indicate that you are a newbie, so it might be that you are not aware of the treasure-trove of information that lies in your history file. My apology if you already know how to access the file, but here's how it's done with OBD11:


Start OBD11 and select the 19- Gateway module
Scroll down the main screen until you see the "History" panel (as below).


http://www.vwwatercooled.com.au/forums/images/imported/2016/10/zYhSQEfpng-2.jpg


3. After you press the History panel, you will then see a report like the screen-shot below (this is the first part of the large History file for the Gateway from my test bench):
http://www.vwwatercooled.com.au/forums/images/imported/2016/10/xkeQ5BApng-2.jpg

Notice the structure of the records - in particular, the "old value" and the "new value". No need to search for a code string from another mk7 like yours because your original code string is written in your history file (no offense intended to the advice from the-One)

My preference is to view the history report on A4 paper, or to view it on the large screen on my PC (rather than trying to read data from the crappy small screen on my Android tablet). To do this, I press the envelope icon and then I email myself a copy of the report. This also gives me a digital version of the data that I can add to forum posts!!



I suggest that you go through this process and then CAREFULLY look through the list for changes that have been made to the Gateway. Pay particular attention to changes that have occurred to the code-string and also focus on any additional modules that may have been inadvertently, and incorrectly added to the Gateway list. Of course, the old value in earliest record in your history file will be the original factory code string for the Gateway.

Or, if you are confused by all this data - simply post a copy of the history file on this forum, and I'm sure someone here will be able to help

Don

[Reedy]

Tapatalk Cloud - Downlaoad File history.txt (http://cloud.tapatalk.com/s/581807dbe3e33/history.txt)

Hi this is the history log of everything I've done. If this post works I'll do the same with the Gateway Module History.

Thanks again.


Sent from my Tab2A7-20F using Tapatalk

[Reedy]

Hey folks. There is no history for 19 Gateway. Even more confused.....


Sent from my iPhone using Tapatalk

[DV52]

Hey folks. There is no history for 19 Gateway. Even more confused.....


Sent from my iPhone using Tapatalk

Reedy:

OK - Not confusing at all - in fact, this is very good news indeed!!

The file that you stored on tapatalk site was produced from the "My Garage" page on OBD11 which means that it shows the changes that you made across ALL of the control modules. The fact that this list does NOT show any changes that were made to the Gateway module confirms the observations that you made when you tried to create a sub-set of this same information through the Gateway history mechanism.

In short, both your tapatalk file and your inability to create a Gateway history listing simply means that no changes were made to the Gateway module in your car with your current OBD11 dongle! I assume that you have not used any other cable on your car (i.e VCDS, VCP, or another OBD11 dongle)

So - the good outcome from your process is that it suggests that the fault lies elsewhere - or, more specifically, I suspect that the problem is with the control modules that are registered in your Gateway list. My hunch is that there are more control modules in your Gateway list than there are actual modules installed in the car.

Not sure how familiar you are with the [CAN] Gateway list on mk7s, but here is a short explanation that I have set-up on my test-bench to illustrate how the Gateway list works:
Introduction
My test-bench has just 3 x control modules at present - these are Central Electrics - (09), Steering Column Electronics - (16) and Gateway (19). For this purpose, I deliberately added the following additional control modules to the Gateway list on my test bench, Special Function 2 -(30), Sound System (47) and Camera System Rear View (6C) - some of these modules may be familiar as they occur in the trouble codes on your first post. Note my test-bench does not have these 3 x control modules, but I added them to illustrate the workings of the Gateway list.

After I polled my test bench I got the 1st screen-shot below:



http://www.vwwatercooled.com.au/forums/images/imported/2016/11/mCPyG3xpng-2.jpg

On the 1st screen, notice that the first three control modules have coloured hex address identifiers - these are the modules that are actually installed on the test bench. But notice that the hex identifiers for the aberrant (non existent) control modules are coloured black in the control module list (I have circled the 3 x hex identifiers with a yellow circle to highlight the non existent modules). An important point to also note is that when changes are made to the Gateway list, no records are added to the History report by OBD11 - I don't know why !.

Does the control module list on the 1st screen shot above for your car have any black coloured hex identifiers?

If the answer is yes, then proceed CAREFULLY as follows:


On a separate piece of paper, write-down the numbers for ALL the black coloured hex identifiers
Select each of these control module in turn - if the selected module is aberrant, you should get the second screen shot in my picture above . If so, select CANCEL and the module will be removed from the list on your screen (but it will not be removed from the actual Gateway list)
Mark the hex address on your piece of paper to indicate that this module needs to be removed from the gateway list
After you have completed (2) and (3) above for ALL of the black coloured hex identifiers your list should show just coloured hex identifiers and your piece of paper should indicate the modules to be removed from the Gateway list
Select the PENCIL in the red dot which I circled in blue on the first screen above - this will get you access to Gateway list
Scroll down the long list of modules and remove the tick next to ALL the module addresses that are indicated on your piece of paper as requiring removal. BE EXTRA SPECIALLY CAREFUL NOT TO REMOVE ANY OTHER TICKED MODULES - THIS IS VERY IMPORTANT.
Clear all the DTCs and re-poll for errors


Don

PS: Here's a picture of the test-bench on which the above process was developed (for interest only) - the ECU was not included for this post

http://www.vwwatercooled.com.au/forums/images/imported/2016/07/LDmGRy7png-1.jpg

[Reedy]

All I can say is WOW! I'll have to try this Friday as I'm working the rest of the week, but thank you in advance.

Sent from my Tab2A7-20F using Tapatalk

[Reedy]

Ok done, along with a few more tweaks. This is what I'm left with. It doesn't seem important at all. But it won't clear?

OBDeleven data log

Date: 2016-11-05 06:01

VIN: WVWZZZAUZFW075389
Car: Volkswagen Golf
Year: 2015
Engine: CJXB
Mileage: 37375 KM

---------------------------------------------------------------
19 Gateway

System description: GW MQB High
Software number: 5Q0907530T
Software version: 1188
Hardware number: 5Q0907530F
Hardware version: 128
Serial number: 0002316346
ODX name: EV_GatewLear
ODX version: 011016
Long coding: 030100042B085900EF00027E880F0001000105000000000000 0000000000

Subsystems:
System description: J367-BDMHella
Software version: 8043
Hardware version: H03
Serial number: 3025284003

System description: E221__MFL-DC1
Software version: 0038
Hardware version: H10
Serial number: 29140001488650084304
Long coding: 2CFFFF

Trouble codes:
U112400 - Data bus Additional installations detected
static
Terminal 15: On
Supply voltage, terminal 30: 12.0 V
Unknown ambient data:
Date: 2016-11-05 06:00:16
Malfunction frequency counter: 1
Unlearning counter: 217
Mileage: 37375 km
Priority: 2



Adam


Sent from my iPhone using Tapatalk

[DV52]

Ok done, along with a few more tweaks. This is what I'm left with. It doesn't seem important at all. But it won't clear?

OBDeleven data log


Date: 2016-11-05 06:01

VIN: WVWZZZAUZFW075389
Car: Volkswagen Golf
Year: 2015
Engine: CJXB
Mileage: 37375 KM

---------------------------------------------------------------
19 Gateway

System description: GW MQB High
Software number: 5Q0907530T
Software version: 1188
Hardware number: 5Q0907530F
Hardware version: 128
Serial number: 0002316346
ODX name: EV_GatewLear
ODX version: 011016
Long coding: 030100042B085900EF00027E880F0001000105000000000000 0000000000

Subsystems:
System description: J367-BDMHella
Software version: 8043
Hardware version: H03
Serial number: 3025284003

System description: E221__MFL-DC1
Software version: 0038
Hardware version: H10
Serial number: 29140001488650084304
Long coding: 2CFFFF

Trouble codes:
U112400 - Data bus Additional installations detected
static
Terminal 15: On
Supply voltage, terminal 30: 12.0 V
Unknown ambient data:
Date: 2016-11-05 06:00:16
Malfunction frequency counter: 1
Unlearning counter: 217
Mileage: 37375 km
Priority: 2



Adam


Sent from my iPhone using Tapatalk

Adam: Hi. Excellent news - you have whittled down the trouble-codes to just one - well done!!

OK, now for the last step - the kind of thing that causes the remaining trouble code in your report is (normally) the opposite problem to that which caused the first lot of issues: that is - not enough ticks in the CAN Gateway list. Again I'm guessing, but given the nature of the error message, I suspect that it's a fairly important control module that hasn't been registered in the Gateway list - perhaps the one @ address hex09 which OBD11 calls Central Electrics?

So, this is what I suggest that you do - after you start the OBD11 software and you connect to the dongle - go to the control module list with the colored hex identifiers (the 1st screen shot on my previous post). Write down ALL the numbers - I assume that there are now no module numbers in a black circle. Then press the Pencil-in-the-red-dot. Make sure that each of the numbers that you wrote-down has a tick on the Gateway list (I suspect that at least one number isn't ticked)

But it's still a good outcome - now just this last matter to get you a clean scan report!

Don

[Reedy]

Cheers mate, will give it a go.


Sent from my iPhone using Tapatalk

[Reedy]

Ok, there were a few numbers that were not ticked and one that when I ticked it was a black one so I took it off. The fault is still there. Does this mean that there is still a control module that needs ticking? And would it be easier to just tick them all and then go through and remove the black ones again?
Cheers

Sent from my Tab2A7-20F using Tapatalk

[Reedy]

Fixed. Thanks for everyone's help. DV52, cheers mate. I added most of the modules and then deleted the black ones and it left a yellow one that I could enter and open but the fault still showed but then when I went to the red pencil the yellow one had no tick so I ticked it and perfect no more fault.

P.S Love the pace car blinkers but still no auto close with rain. I wonder whether it's got something to do with my drivers side auto open and close forgetting it's settings and stops working sometimes? I read somewhere that VW know of this issue but have no fix yet. All other windows work fine but every so often the drivers side needs resetting by holding open and holding close.


Sent from my iPad using Tapatalk

[DV52]

Adam:Sorry - I can't help with the auto rain-close tweak (some can get this to work, others can't).

But an excellent outcome on your trouble codes - I do like a clean diagnostic report!!

Good job!!
Don