|
Post by legendmarco on Sept 12, 2020 21:49:32 GMT
Hi all! I'm trying to code my radio to activate AUX, but most of the modules are blacked out for some reason. Why are those modules unreachable and is there a way I can fix this so I can get in their menu's? Car: Audi A4 B7 2006 App: PRO version (Android) ^Greyed out modules. ^'Module is unreachable' notification when I click a blacked out module.
Thanks in advance.Attachments:
|
|
|
Post by dv52 (Australia) on Sept 12, 2020 22:11:48 GMT
marco:Hi.
Control modules have both a name and an address - a bit like a mailing address. The number in the colored circle in your picture is the module address and it is reported using the hexadecimal (hex) numbering system (because it refers to a digital memory address on the CAN network)
The colored circles surrounding the hex address of the module have the following meaning: [EDIT - see @testeronline list below] So, for the OBD11 software to work properly, ALL the individual control modules that are connected to the CAN network on your car need to be registered in a special "installation list" that is managed by the Gateway module (which lives @ address hex19).
The easy way to align the Gateway list in the car with the modules that are physically present is to use this very helpful guide that was originally authored by @testeronline (see below - note: the pictures relate to now obsolete software, but the process is the same for the current release SW version):
Don
the autocode process can be found here cupra280.co.uk/obd11.html#AutocodeHowever to make it easier 1/ From the Main menu select Settings
| 2/ From Settings Menu ensure Autocode Gateway List is set to show, if not change it to show
| 3/ Connect to car and you should get the following popup box , Select Yes and any missing control units will be ADDED
| | | |
if the popup box does not arrive I suspect the autocode process does not think you are missing any control units. Once you have selected the control unit double check the status of it (if the number is in a Black Circle then its not being picked up as a live control unit by OBD11)
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Sept 13, 2020 11:03:37 GMT
Don dv52 (Australia) I think you have one small error in your description of the colors (and sorry if I have missunderstood what you have said)
The Black color means the control unit is shown on the Gateway but is not reachable which could be because there is an issue or if you are like me you have added the control unit but it's not on your car or OBD11 Treat this control unit as a sub control element of another control unit.
The Yellow status is showing that you have the control unit on the car but its not coded on the Gateway (and this is where the auto code process will help you
|
|
|
Post by dv52 (Australia) on Sept 13, 2020 21:19:19 GMT
@testeronline : my bad - thanks for the correction. I modified my post.
Don
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Sept 13, 2020 21:38:09 GMT
dv52 (Australia) Don you look after multiple marque's and platforms and the point of a community (good forum) is we all chip in to help plus we are all human. Ron
|
|
|
Post by legendmarco on Sept 14, 2020 20:19:47 GMT
dv52 (Australia) @testeronline Guys thanks for the replies! Based on your information I've been trying things out. I tried everything to get the autocode gateway list popup box to show up, but it won't. Marco
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Sept 14, 2020 21:25:02 GMT
legendmarco Marco are you running the app on Android or Apple
|
|
|
Post by dv52 (Australia) on Sept 14, 2020 21:51:34 GMT
^ ^^ @testeronline : Ron- he is using Android (see the module list picture on first post) legendmarco : I probably have led you astray - my apology! My interpretation of the colored circles was incorrect - as @testeronline has indicated, the black circle mean that the modules cannot be reached. Given that there are so many modules in your picture with black circles, it is highly unlikely that this is a problem with the Gateway installation list. Logic suggests that this problem is more about the central part of OBD11's software or its module polling mechanism. What type car/model car is this and what country? Is this car a 2020 build vehicle with SFD? If it's a late model Audi - have you tried opening the hood before running OBD11 software? Do you have a PRO license? Don
|
|
|
Post by legendmarco on Sept 14, 2020 22:12:05 GMT
No problem!
I use Android with a PRO licensed app. The car: Audi A4 B7 Saloon 2006. I'm from The Netherlands. I did not try opening the hood before running OBD11 yet, will try soon.
Marco
|
|
|
Post by dv52 (Australia) on Sept 15, 2020 1:43:14 GMT
marco: unlikely for the bonnet fix to be a problem for a 2006 build Audi. No offense intended, but I have to ask; do you have the car ignition turned-on when using OBD11? Also, what happens if you scan the car?
Don
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Sept 15, 2020 8:09:41 GMT
|
|
|
Post by legendmarco on Sept 18, 2020 22:00:01 GMT
dv52 (Australia) Yeah, I do have the ignition turned-on when I'm using OBD11. It works just fine with the couple of modules I can get into. @testeronline I did a data clear, cache clear, reinstalled the app and restarted the phone. Didn't change anything. The link you sent is interesting. I do have a stock radio installed (audi bns 5.0 navi) but maybe somehow it isn't connected to the ECU/OBD-port.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Sept 19, 2020 10:51:21 GMT
Not supprised it did not work but its like the PC Reboot you have to try it first.
Afraid I dont know your cars setup, I just saw the article and thought it was very similar to the problems you were having.
With regards to the other control units being black, I would try support via the app tell them what control units you can see and what is showing as black just in case they have a bug that they know about. The only other thing that I am aware that can cause odd results like this is a Battery that is on its way out but then I would expect you to get lots of errors showing.
Sorry I cant help anymore, hopefully Don may have some insight.
|
|
|
Post by dv52 (Australia) on Sept 19, 2020 21:59:03 GMT
marco: First I must apologize for not being of more help - I'm all out of ideas and it looks like neither Ron (testeronline) or I have been able to move your problem further to resolution. Like Ron, I suspect that the problem is related to the way that OBD11 interfaces with your car.
Without intending any offense, the A4 (B6 and B7) had a very peculiar OBD network architecture. Because of its age, the car is pre- CAN technology for certain engines and it used an ISO9141 bus (which is often called "K-line" protocol) for controlling modules.
Ain't nothing special about K-line protocol - many different cars used this Standard around 2006. However, on EU versions of the A4, an issue arose where the electrical specifications in the ISO9141 standard could not be sustained on cars that had lots of options installed (and therefore, lots of modules). The way that Audi solved this problem was to create a second K-line bus - which was odd.
So - In "basic" cars, all control modules on A4 models were wired to the normal K-line (called "K1 bus"). In a car loaded with many options, most control modules were connected to K1 and could be accessed using standard ISO9141 interface messages with diagnostic cables like OBD11. However, some of the "extra" modules were connected to K2 instead of K1.
The way that the dealer diagnostic tool solved the problem of polling the dual x K -lines was to introduce a special adapter between the scan-tool and the car. This device acted as an intelligent switch, making an automatic determination which K-Line a control module is connected to.
The pictures in your first post suggest that your car is option rich (your car even has a TV tuner). So, I'm assuming that your A4 is fitted with dual K- lines and I'm certain that some of the modules in your car also use KWP-2000 protocols for the data-transport layer (which has different features from the previous KWP-1281 protocols that were widely used in cars of this era).
I don't know how OBD11 handles dual K -line vehicles (or even if it is compatible with these cars) - but I suspect that it's this matter that is causing your problem (I'm guessing of course).
I suggest that you take Ron's recommendation and contact the help desk to discuss compatibility of dual K - line cars with OBD11 devices
Don
|
|
|
Post by legendmarco on Oct 9, 2020 20:32:15 GMT
@testeronline dv52 (Australia)Thanks for your replies! Appreciated! Some time has passed. In the meantime I have asked someone with about 30 years experience installing systems in cars to take care of the issue. Even with a professional OBD cable and VCDS software he couldn't connect to certain modules, same problem I had running OBD11. He's going to ask some people in his network they might know what could cause the issue.
|
|
|
Post by dv52 (Australia) on Oct 9, 2020 21:09:18 GMT
legendmarco : as I indicated in my last reply, the problem is very likely to be the dual K-line structure on the A4 B6/8E chassis. The Audi dealers use VAS-6017B as an interface between the OBD port on the car and the dealer tool (ODIS). I have no idea how OBD11 manages the same connections - perhaps an email to the help desk might be prudent?
Don
|
|
|
Post by luisfl on Oct 31, 2020 1:42:57 GMT
Hi!
I have the exactly same issue with my Seat Exeo ( A4 B7 platform), all modules are reachabel except the “Radio” and the “Navigation”.
Already comtacted the voltas support but nothing until now.
Cheers
|
|
|
Post by legendmarco on Oct 31, 2020 10:11:19 GMT
Hi! luisflI'm still trying to figure out what's causing this. Will post it here if I find something. dv52 (Australia)Went to the dealer and used the VAS-6017B, still no luck.
|
|
|
Post by largey on Apr 10, 2021 13:17:55 GMT
I am having the same issue - came across this post after posting my own post.
Did you ever have any luck resolving this - indeed it all seems to point to this K2 line.
|
|