rpj83
New Member
Posts: 16
|
Post by rpj83 on Aug 26, 2016 17:16:04 GMT
I have this code and I can not clearit. It just comes right back. I'm not sure if this was originally there or after I had made tweaks. Everything in the vehicle seems to be functioning properly, especially the audio system. Any ideas what this might be caused by??
|
|
|
Post by dv52 (Australia) on Aug 26, 2016 23:48:31 GMT
I have this code and I can not clear it. It just comes right back. I'm not sure if this was originally there or after I had made tweaks. Everything in the vehicle seems to be functioning properly, especially the audio system. Any ideas what this might be caused by?? rpj83: Hello. I'm making an assumption that your mk7 doesn't have the high-end sound system. In Europe (and here in Australia), it's called DYNAUDIO, and in the US it's called the Fender System - it has a sub-woofer in the wheel well. The high end sound system gets it's information signal (the audio signal) from the unit in the glove-box ( J794) via a pair of optical fiber cables and the VW protocol that is used for this process is called MOST (Media Oriented System Transport). The optical cables are connected from J794 to an amplifier that sits under the front seat which VW calls the Digital Sound System control module ( J525). MOST communication between J525 and J794 is managed by the CAN Gateway (J533). So, the reason that I mention this stuff is to provide a rationale for my hypothesis regarding the DTC in your picture: since you say that the infotainment system is working OK , and because the error message says that J533 can't communicate with J525, I suspect that you may have inadvertently turned-on the MOST protocol in J794. If you don't have the high end sound system, MOST is turned off by default because the optical cables and J525 aren't installed. MOST is enabled/disabled in the code-string for the Information Electr control module @ address hex5F: Byte 19, Bit 5. I suggest that you check the status of this Byte on your car. You can either do this using the short-coding screen, on OBD11, or you can use the Long coding screen below. If the MOST setting is disabled, I suggest that you check your HISTORY file and that you look in particular for any changes made in the control module at address 5F Don
|
|
rpj83
New Member
Posts: 16
|
Post by rpj83 on Aug 27, 2016 0:29:18 GMT
I should've mentioned in my original post that I do in fact have the fender audio system. That's why it's confusing as to why I would have that drc since all speakers are working fine. Sorry about that.
|
|
|
Post by dv52 (Australia) on Aug 27, 2016 0:33:38 GMT
I should've mentioned in my original post that I do in fact have the fender audio system. That's why it's confusing as to why I would have that drc since all speakers are working fine. Sorry about that. rpj83: Hello again. Yes, that would have been useful information!!! Still check the status of the MOST setting (which should be "enabled" in your case) and look through your HISTORY file Don
|
|
rpj83
New Member
Posts: 16
|
Post by rpj83 on Aug 28, 2016 2:01:21 GMT
Hey Don. Thanks for all the information. I checked to make sure that the MOST protocol was on, and it was. So I then checked the history for that module. The only long coding changes that I made were for the startup screen and enabling driving school mode. Could this be caused by changes to any of the other modules. I have a pretty long history log that I would have to backtrack. Thanks again.
|
|
|
Post by dv52 (Australia) on Aug 28, 2016 13:31:07 GMT
The only long coding changes that I made were for the startup screen and enabling driving school mode. Could this be caused by changes to any of the other modules. I have a pretty long history log that I would have to backtrack. hmm.......... Driving School Mode involves adaptation channel changes rather than changes to the module's code-string!! If your HISTORY file is large then I find it useful to email the file to myself, then print-off a copy (looking though a list on sheets of A4 is much better than using the screen on a tablet/mobile-phone). To do this select the "Envelope" symbol as shown on the screen below, which should open-up your email apps Don
|
|
rpj83
New Member
Posts: 16
|
Post by rpj83 on Aug 29, 2016 18:15:44 GMT
The Driving School Mode was done in adaptation, which I put back to "not available", but still no luck. I printed out my history report and will go through it one by one to see if to has anything to do with this at all. Thanks for the help!
|
|
rpj83
New Member
Posts: 16
|
Post by rpj83 on Sept 2, 2016 19:44:46 GMT
*UPDATE*
DTC is now cleared. The problem was caused by adding address A7 to the gateway coding list, which is "sound system." I was curious to see if any coding could be done on that module... I realized this when I added a couple more modules to the list and ended up with 2 more faults for unidentified module. Moral of the story is don't add anything to the gateway list
|
|
wj
New Member
Posts: 11
|
Post by wj on Sept 21, 2019 17:40:29 GMT
My Dynaudio in my 2010 Tiguan is also dicked. Any help would be HUGE.. Here is a thread I started for my specific issue, Thx! forum.obdeleven.com/thread/6753/audio-modules-grayed-dynaudio-rns310 I have this code and I can not clear it. It just comes right back. I'm not sure if this was originally there or after I had made tweaks. Everything in the vehicle seems to be functioning properly, especially the audio system. Any ideas what this might be caused by?? rpj83: Hello. I'm making an assumption that your mk7 doesn't have the high-end sound system. In Europe (and here in Australia), it's called DYNAUDIO, and in the US it's called the Fender System - it has a sub-woofer in the wheel well. The high end sound system gets it's information signal (the audio signal) from the unit in the glove-box ( J794) via a pair of optical fiber cables and the VW protocol that is used for this process is called MOST (Media Oriented System Transport). The optical cables are connected from J794 to an amplifier that sits under the front seat which VW calls the Digital Sound System control module ( J525). MOST communication between J525 and J794 is managed by the CAN Gateway (J533). So, the reason that I mention this stuff is to provide a rationale for my hypothesis regarding the DTC in your picture: since you say that the infotainment system is working OK , and because the error message says that J533 can't communicate with J525, I suspect that you may have inadvertently turned-on the MOST protocol in J794. If you don't have the high end sound system, MOST is turned off by default because the optical cables and J525 aren't installed. MOST is enabled/disabled in the code-string for the Information Electr control module @ address hex5F: Byte 19, Bit 5. I suggest that you check the status of this Byte on your car. You can either do this using the short-coding screen, on OBD11, or you can use the Long coding screen below. If the MOST setting is disabled, I suggest that you check your HISTORY file and that you look in particular for any changes made in the control module at address 5F Don
|
|
|
Post by dv52 (Australia) on Sept 21, 2019 21:38:41 GMT
^^rpj83: hmm.........OK, new information - are you sure that a 2010 Tiggy (NAR?) actually has a Dynaudio? I hadn't thought that MQB platform design was fitted to American Tiggys until much later - so the Dynaudio series MIBs won't apply. If so- ignore anything that I have suggested because it only applies to MQB platform vehicles - which is the subject of this particular forum
The "no communications" error can have many causes. As a totally wild guess, I suspect that in the opening ODB11 screen that shows a list of small pictures of all the modules with their address locations in the top right-hand corner, the address location for the Digital Sound System Control is surrounded by a black colored circle. If I'm correct, the black circle means that the Digital Sound system module has been registered in the Gateway module installation list - but when polled it didn't respond. Generally, but not always, this usually means that the polled module isn't physically connected to the CAN bus - because it isn't actually fitted in the car. Not sure about your car - but try eyeballing the module to confirm that it's there and if it is installed, check the connector (particularly the CAN-high and CAN-low wires). Don
|
|
wj
New Member
Posts: 11
|
Post by wj on Sept 21, 2019 22:02:17 GMT
Thx a Million Don! Any help is awesome. I simply don't know these systems yet, and trying to gain knowledge to be more self sufficient. Just looked under the seat(s)...and from my very limit understanding, this maybe in fact is NOT the Dynaudio amp, etc...? Speakers all say Dynaudio, and the head unit displayed Dynaudio on bootup...but not always. These seems messed up to me.. Someone cobbled it up before I bought it? If true, is the best path forward to procure the proper Dynaudio amp...or code the current system to work..if possible? Under Drivers seat: Under Pass seat: Head unit info: THANK YOU! my root thread: forum.obdeleven.com/thread/6753/audio-modules-grayed-dynaudio-rns310
|
|
|
Post by dv52 (Australia) on Sept 21, 2019 23:31:32 GMT
Thx a Million Don! Any help is awesome. I simply don't know these systems yet, and trying to gain knowledge to be more self sufficient. Just looked under the seat(s)...and from my very limit understanding, this maybe in fact is NOT the Dynaudio amp, etc...? Speakers all say Dynaudio, and the head unit displayed Dynaudio on bootup...but not always. These seems messed up to me.. Someone cobbled it up before I bought it? If true, is the best path forward to procure the proper Dynaudio amp...or code the current system to work..if possible? THANK YOU! my root thread: forum.obdeleven.com/thread/6753/audio-modules-grayed-dynaudio-rns310wj: Yep - definitely NOT a MIB (i.e. MQB platform) based infotainment unit. Your hardware number 1K0035274A in the module @ address hex37 (Navigation) is more generally known as RNS-315 and it has an entirely different architecture to the MIB units in Golf mk7's - albeit it does have an option called "Dynaudio", but this is very different to the unit that has the same name on MIB/MMI modules (which apply to this forum). I've done a bit of research for you in the time between your last post and this reply (so what I'm about to say is NOT well informed)- but I suspect that you may need to pay attention to the code-string on the hex37 module. here is how the code-string values for the hex37 module look from your link: Byte Hex Binary 0 00 00000000 1 06 00000110 2 04 00000100 3 01 00000001 4 01 00000001 5 00 00000000 6 00 00000000 7 00 00000000 8 00 00000000 9 00 00000000 10 00 00000000 11 00 00000000
There is some dialogue on the RT forum about this module here - so it might be worth reading how the authors suggest that the module code-string should be set (particularly for the Dynaudio option) There is also some stuff here - showing some long coding screens related to the RNS-315. But as a more general suggestion - why not go to the Coding section of the control module - and invoke the "description" option (not the Byte/Bit tick boxes option). You should get something that looks like this (note: the picture is from a BCM for a mk7 - so the entries don't apply for your car- but the general layout should be similar):
If you don't get this screen - press the 0/1 symbol at the top center right-side of the screen (it's on left-side next-to the "?" symbol)
The entries in these screen should describe what each software switch in the long code does. For example, according to one of the authors on the RT forum there is a setting in Byte 1 for the Dynaudio Sound System which ultimately results in the value hex05 for this byte - which is equivalent to binary 0101.
As you can see from my table above, the current value for Byte 1 in your module is hex06 which is equivalent to binary 0110. So- each digit in the binary numbers that I have shown is a separate software switch. As you can see - the last 2 x digits are different in the 2 x binary numbers (which is suspicious - to me at least)
But I'm just guessing (as I have said)
Don
|
|
wj
New Member
Posts: 11
|
Post by wj on Sept 22, 2019 2:33:12 GMT
Gonna take me a bit of time to digest all of this stuff you've unearthed for me. Plz forgive my sidetracking this thread...I got here by searching for "Dynaudio", and foolish me assumed Dynaudio is Dynaudio is Dynaudio...but now know at least a little better. I'll plow thru this new info and try to make better sense of it all...then ping back for your further thoughts if you're still up for it.
You're the friggin Wikipedia Don! I don't know that I'll make it to the promised land on this one yet, but you've unlocked several important doors to help me solve this puzzle.
As I inch forward, I'll post my findings. Thanks a ton!
|
|
wj
New Member
Posts: 11
|
Post by wj on Sept 22, 2019 22:28:58 GMT
Read the posts you linked to and followed some of the suggestions, specifically this one from the Dynaudio problem post, where "He" got success by using this coding: Byte 1 - 05 (Dynaudio Sound System) Byte 2 - 00 (Sound System, Active Speakers) Byte 4 - 01 (Speaker Monitoring inactive (sound system) Mine was: Byte 1 - 06 Byte 2 - 04 Byte 4 - 01 but... nothing changed. Still no sound, Still dead/inaccessible modules with black circles for: Hex46 Central Module Comfort System Hex47 Sound System Hex56 Radio Seemed like a good plan, but in the end pooped out. Got a reply from my original post: forum.obdeleven.com/thread/6753/audio-modules-grayed-dynaudio-rns315?page=1&scrollTo=29722from a guy that linked to an older post of urs, showing how to reactivate module 5F in the Gateway. Sounded like a good plan, but then... more poop My system does not even offer a 5F model option on my Gateway check list... I uploaded screen caps of my Gateway list in that post if you wanna see them: forum.obdeleven.com/thread/6753/audio-modules-grayed-dynaudio-rns315?page=1&scrollTo=29722 Not sure whats the next logical path to take. Any more ideas? As before... Thanks for your brainwaves on this!
|
|
|
Post by dv52 (Australia) on Sept 23, 2019 0:12:04 GMT
^^wj: I'm not surprised that my ill informed suggestions have not resulted in a road-to-Damascus epiphany (to carry-on your "make it to the promised land" analogy). As I said, my understanding of pre Golf mk7 networks is literally non existent. So the outcome of your efforts is entirely of my doing - apology. Not sure what other suggestions I can make to send you down more rabbit holes - but the following are further observations of a philosophical, rather than a technical nature: 1, Generally, the presence of a black circle around the hex address for a module (in the pics in your link) means that the module has been registered in the Gateway installation list - but for some reason the module has not responded (or, has incorrectly responded) to the Gateway's challenge/reply interrogation. What you call "the grayed out modules" (i.e. hex46, hex47, hex56) clearly are in this category. 2. In terms of moving forward - my suggestion is that you ask yourself the question: are the black circles the cause of your problem, or are they the consequential result of another problem in the car's CAN network? I don't know the answer to this pivotal question, but the answer does constrain how you will focus your efforts to find a solution. 3. To help in answering the question in 2., you do have some further guiding information: First, notwithstanding the black circles, your scan does report the 3 x troublesome modules with the message "No trouble codes found". This tends to suggest that at least some CAN protocols are successfully being communicated by these modules with the Gateway module. Which means that the 3 x troublesome modules are alive and well from a CAN perspective only. Second, your scan also reports "U101400 - Control module incorrectly coded" for the hex37 module.
Now, and again with the caveat of my complete ignorance about the RNS-315 - for VW infotainment systems generally, add-on options like external amplifiers need to have certain software switches set to tell the prime module (in this case I suspect, the hex37 module) to start using the additional gear. For example, without an external amplifier, it's normal for the speaker wiring loom to be directly connected to the prime module. In this configuration, the prime module sends the audio signal to the pins on its rear connector and hey-presto, sound comes out of the speakers! But with an external amplifier, the speaker wiring loom is physical routed to the socket on the amp in-stead. One of the consequences of correctly setting the software switches on the prime module is to tell it not to use the normal speaker pins on its rear sockets. If these switches are not correctly set, the prime module keeps sending the audio signal to the normal speaker pins - but these pins are not connected to anything - so no sound! Of course this is just one example - there are lots of other reasons for no sound. 4. When it comes to diagnostic analysis, I'm a devotee of Occum's Razor - which basically preaches that when faced with options in fault finding, take the most obvious approach. I guess that you must decide how to answer the question in 2, above Don PS: ..........and, I suggest that you not pursue the hex5F option - this addressing protocol for infotainment modules doesn't appear to apply to the RNS-315, I suspect.
PPS: my final suggestion is to grab yourself a copy of the wiring diagram for your car. My experience has been that WD's can be heaven-sent! All of the stuff considered thus far has been about coding - but there may be physical problems. In any event, comparing the wire colors and the pin connections on the sockets of the relevant modules with the information in the WDs will tell you if the audio options are correctly wired and likely they will tell you if the modules have been factory fitted, or retrofitted,
|
|
wj
New Member
Posts: 11
|
Post by wj on Sept 25, 2019 3:07:47 GMT
Got yanked out of town, temporarily disrupting the flow on this. Thanks again Don for the advice and suggestions.
Yep, your question #2 is pivotal ... too early for me to know if the blacked modules are causes or symptoms. CANbus issue does seem possible.
and I'll purge further energies about hex5F as you've suggested. I'll dig back in and try to generate more info to post.
Thanks tons for the help so far... I hope you'll still be willing to help me throw more poop at the wall, assuming something will stick before long?? Thank you!
-WJ
|
|