Reply With QuoteCheers mate, no issues what so ever, everything appears to be working. Norris is where I go.Originally Posted by The One
Sent from my Tab2A7-20F using Tapatalk
Volkswagen Enthusiast
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.
Volkswagen Fan
Cheers mate, no issues what so ever, everything appears to be working. Norris is where I go.
Sent from my Tab2A7-20F using Tapatalk
2015 Golf R. Lapiz Blue.
Volkswagen Fanatic
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).
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):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.
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!!
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
Last edited by DV52; 01-11-2016 at 08:56 AM.
Please don't PM to ask questions about coding, or vehicle repairs. The better place to deal with these matters is on-line, in the forum proper. That way you get the benefit of the expertise of the wider forum! Thank you.
Volkswagen Fan
Tapatalk Cloud - Downlaoad File 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
2015 Golf R. Lapiz Blue.
Volkswagen Fan
Hey folks. There is no history for 19 Gateway. Even more confused.....
Sent from my iPhone using Tapatalk
2015 Golf R. Lapiz Blue.
Volkswagen Fanatic
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:
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
Last edited by DV52; 01-11-2016 at 09:58 PM.
Please don't PM to ask questions about coding, or vehicle repairs. The better place to deal with these matters is on-line, in the forum proper. That way you get the benefit of the expertise of the wider forum! Thank you.
Volkswagen Fan
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
Last edited by Reedy; 01-11-2016 at 07:36 PM.
2015 Golf R. Lapiz Blue.
Volkswagen Fan
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
2015 Golf R. Lapiz Blue.
Volkswagen Fanatic
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
Last edited by DV52; 05-11-2016 at 05:28 PM.
Please don't PM to ask questions about coding, or vehicle repairs. The better place to deal with these matters is on-line, in the forum proper. That way you get the benefit of the expertise of the wider forum! Thank you.
Volkswagen Fan
Cheers mate, will give it a go.
Sent from my iPhone using Tapatalk
2015 Golf R. Lapiz Blue.
Bookmarks