vwr
New Member
Posts: 10
|
Post by vwr on Jul 15, 2020 22:36:06 GMT
Hello, I am hoping someone might be able to help with issues on my MIB. Frequent freezing and restarts, unit will work fine for a few minutes and then freezes/ restarts again. Errors are as follows: --------------------------------------------------------------- 5F Multimedia System description: MU-S-NS-US Software number: 3Q0035876A Software version: 0753 Hardware number: 3Q0035876A Hardware version: 840 Serial number: ODX name: EV_MUStd4CDELP ODX version: 001001 Long coding: 027300020000000051220002001808009F0207F401200105C6 Subsystems: System description: ABT_Std-2_Nav Software version: 8130 Hardware version: H52 Serial number: VWZ6ZHV3520156 Trouble codes: B201A00 - Checking software version management static B11CF53 - Tuner for satellite radio Deactivated static U106A00 - Digital sound system control module No Communication Intermittent --------------------------------------------------------------- Attempted fixes - Unplug car battery for 10 mins and reconnect
- Factory reset in MIB settings
- Clearing faults with OBD several times
- Checked the Infotainment fuse (F12?) - it was fine
All with no luck and the issue persists. Where is the Digital sound control module is there someway I could test this? Any suggestions will be greatly appreciated!
M.
|
|
|
|
Post by dv52 (Australia) on Jul 15, 2020 22:49:43 GMT
^^^ ^ difficult to be precise given the information provided but the intermittent DTC about communications failure from the digital sound module (it's called "J525") is potentially informative.
The communications medium between J525 and the MIB (J794) is a pair of optical fiber cables for what's called MOST ("Media Oriented Systems Transport") protocol.
These 2 x cables form a ring-architecture -meaning that the pair of optical fiber cables create a circle where the light-pulses must travel from a module to the other module and these same light-pulses must return back to the initiating module for successful communications. So, if the ring is broken for any reason at any time - comms isn't possible!
Perhaps posting-up the complete scan report might be better. Don |
|
vwr
New Member
Posts: 10
|
Post by vwr on Jul 15, 2020 22:58:49 GMT
I am sorry Don, I didn't realize that the complete log would be useful here. Please find the complete scan attached! Thanks for your help  datalog.txt (13.3 KB) |
|
|
|
Post by dv52 (Australia) on Jul 15, 2020 23:25:25 GMT
^^^^ vwr: Thanks for responding so quickly - you probably should re-read my first response because I added some additional information about the connection between the digital sound system module and the MIB.
Your scan report is interesting - because it's missing the digital sound system module. On a mk7/mk7.5 module, the digital sound system is normally reported @ address hex47 like this:
47 Sound System
System description: MIB2_lite_amp
Software number: 5Q0035456A
Software version: 0200
Hardware number: 5Q0035456A
Hardware version: H40
Serial number: VWZ8Z1JMD03ZPKL
Faults:
No trouble codes found
As I said, on your scan this module is missing- which is odd because the software switch in the long-code on your MIB that enables MOST (which must be switched-on when a digital sound system module is installed) is switched-on.
Do you actually have an external amplifier on the car - a subwoofer in the boot, perhaps?
Don
|
|
vwr
New Member
Posts: 10
|
Post by vwr on Jul 15, 2020 23:32:52 GMT
Hmm.
That is weird as it indeed does have the subwoofer in the space were the spare tire would be in the trunk. My car has the Fender audio system. I did check the area under the drivers seat and I believe I see the module j525 and think I see the two wires you mentioned coming from that j525 unit.
I wonder why this appears to be absent from my complete scan.
Thanks again for the support.
Just thinking out loud.. if the amp it self is faulty could this cause the issues stated? I would still expect it to be in the scan though, so perhaps this is a silly suggestion?
|
|
|
|
Post by dv52 (Australia) on Jul 15, 2020 23:46:22 GMT
^^^^wri: No thanks necessary. So, perhaps try making another scan report - if the hex47 module is still missing, perhaps scroll-down on the control module screen (see below) and see if it's present in the list. Also note the color of the circle within which the number "47" is shown  Don |
|
|
|
Post by dv52 (Australia) on Jul 15, 2020 23:58:32 GMT
Just thinking out loud.. if the amp it self is faulty could this cause the issues stated? I would still expect it to be in the scan though, so perhaps this is a silly suggestion? So - here is what happens when a module is installed in the car - meaning that that module is physically connected to the car's CAN network: When you switch-on the ignition, the Gateway module (@ address hex19) verifies that ALL modules that it has recorded as being present in the car are alive-and-well. The Gateway module uses what's called an "installation list" for this purpose and when modules are newly installed, or removed from the CAN network, this installation list is updated. On your car, I assume that the installation list was created at the factory and I also assume that the hex47 module was registered when the car was newly built. If a module is registered in the installation list and it isn't actually installed, an error will result If a module isn't registered in the installation list, but it is actually connected to the CAN network, an error will result. So - a error will/should result when the installation list doesn't align with the actually installed modules. Strangely, neither of these installation list errors appear on your scan. And of course, yes an error will be generated if the module is "faulty" - it's not clear if your car has this fault error because it's missing any reports for the hex47 module!
However, I suspect that the missing hex47 module in your scan isn't the reason for your problem; it's actually a different problem (of much less consequence - I guess).
The intermittent comms error on your MIB strongly suggests a "physical" problem with the optical fiber pair somewhere on route on the ring arrangement. I suggest that you check the 2 x connectors on the back of the MIB and the connectors on the module under the seat.
Here's how the optical fibers are terminated in the plug. I'm not suggesting that you disassemble the connector - but check that the fiber cables are not loose in the housing). And of course, be aware that these are delicate cables - don't be too aggressive.
Don
|
|
|
|
Post by dv52 (Australia) on Jul 16, 2020 1:26:02 GMT
^^ ^ ^^ And........ these a bunch of dialogue here regarding how to clear the Software Version Management error. Don |
|
vwr
New Member
Posts: 10
|
Post by vwr on Jul 19, 2020 16:38:50 GMT
Don dv52 (Australia)So in one of the more bizarre fixes it appears that by removing SD card for navigation database it solves the issue of constant freezing and reboots. It was a bizarre forum post I found that suggested this and it works.I drove 2 hours yesterday without a single issue! In regards to the SVM fix this seems way above my paygrade! But I will try to wrap my head around it.Nervous! I just went into the correct channel to see what my key is set to- it appears mine is 7564 under 5f>confirmation of installation change>key - would you be able to let me know what code I should enter? ![]() |
|
|
|
Post by dv52 (Australia) on Jul 19, 2020 21:18:49 GMT
vwr: hmm........... that is strange and I fail to understand how re-locating the SD card can possibly impact the hex5F module losing communications with the digital sound system (intermittently) - but hey, anything that works is a plus so well done you!!
As for the SVM answer, try BCB6
Don
|
|
vwr
New Member
Posts: 10
|
Post by vwr on Jul 20, 2020 19:32:38 GMT
dv52 (Australia) Don So thanks for confirming that for me! That is what I got using your info on the other post but wanted to confirm it! So in regards to the original issue. It appears when I insert the Nav SD card it stops the digital compass from working and on the nav screen it says "checking navigation data" continuously until it freezes/ reboots the MIB then the cycle continues. But removing the SD card digital compass pops up immediately and the MIB works flawlessly. Any ideas why this might be? I can now verify the SD card seems to be the cause of all my issues! Mike
|
|
|
|
Post by dv52 (Australia) on Jul 20, 2020 20:33:28 GMT
vwr: clearly something on the SD is corrupted. What's the history of the SD Card - have you done any map updates?
Don
|
|
vwr
New Member
Posts: 10
|
Post by vwr on Jul 21, 2020 16:11:23 GMT
dv52 (Australia)I plugged the sd card into my computer to run a generic "scan and fix" it reported the card was fine. Never touched the SD card or done anything to it. Looking on the VW navigation updates website it says that I would need to take it to a dealer instead of being able to download and update.I think for N.America cars this seems to be the deal. Not a huge deal for me as I use carplay but this is one of those frustrating random things. I am going to get an old SD card and clone the NAV to it and see if that fixes it.
|
|
|
|
Post by dv52 (Australia) on Jul 21, 2020 21:32:42 GMT
vwr: You can't use a non OEM SD card and simply "clone" the SATNAV data onto it; there is some form of proprietary information on the OEM SD card that doesn't copy over.
Don
|
|
|
|
Post by palelb on Feb 23, 2021 22:35:02 GMT
Hey I just joined this forum because I found this thread, though it’s a bit old. I am having EXACTLY the same issue. System works fine with no nav SD card. When card is in, no nav data, and constant rebooting.
What was your eventual fix? I have an appointment with the dealer Monday and I’d like to be prepared for any shenanigans! Was it to upgrade software from 0753 to 0755?
Many thanks!
|
|
ponka
New Member
Posts: 1
|
Post by ponka on Feb 8, 2022 23:24:28 GMT
Hi guys,
I'm also have the same problem on my 2015 MK7 Gti performance pack, the mib doesn't have navigation and car play.
The problem I have is it keeps on switching off frequently. I tried resetting it by removing the battery cable but it problem would still persist.
The dealership made us buy a new unit, the problem is still there.
Please assist.
|
|
|
|
Post by dv52 (Australia) on Feb 9, 2022 20:59:33 GMT
ponka:There's a million-gazillion possible reasons for the problem- need to limit some of these. Might be useful to post-up a scan report Don
|
|
|
|
Post by vwjap on Feb 10, 2022 9:40:49 GMT
Re the sd card, do you think it can be the system is looking for it to put in the nav mode, and not finding the nav info causes the crash, and if you was to put in the og sd it would work ok (obviously not the pro system as that’s transferred to hd)
|
|
