|
|
Post by crunch81 on Jun 19, 2020 17:10:01 GMT
Good day People,
Can somebody help me with a hard to find DTC?
I have had this DTC in both my clusters (retrofitted AID)
The DTC is deletable and then comes back within a few minutes.
It says: “Function restriction due to communication interruption”
I do not have a backup because the fault was already there from the beginning.
Some module info:
J285
Hardware number: 5G1920795B
Hardware version: 402
Software: 4191
Long coding:
072510082B800008000868001600000000000000
All help is appreciated!
Greetings Crunch
|
|
|
|
Post by dv52 (Australia) on Jun 19, 2020 23:46:26 GMT
crunch: Hi
J285 is the dashboard insert module that lives address hex17. Clearly something in this module is amiss. Given that "the fault was already there from the beginning" - there is no point looking in your History recods for an incorrect change. I suggest that you start by checking the settings in the module's long code; go to the descriptor part of long code and satisfy yourself that each bit entry is correct for the equipment that has been factory installed in your car.
Don
|
|
|
|
Post by crunch81 on Jun 20, 2020 6:29:11 GMT
Hi Don,
Thanks for your reply.
I already did that for multiple times. I think that everything is correct.
Is it possible that this DTC is triggering because of a fault in 5F? I mean can a wrong setting in the 5F module trigger a DTC in the 17? Or is this excluded?
I have these codes present in 5F:
Navigation System Database not enabled B126CF2
Function Limitation due to missing message U111100
Greetings Crunch
|
|
|
|
Post by dv52 (Australia) on Jun 20, 2020 20:42:46 GMT
crunch: yes DTCs in one module can cause consequential errors in other modules - this often happens. the Navigation error suggests a problem with SATNAV - does your car have this (meaning was it factory fitted to the car??
Don
|
|
|
|
Post by crunch81 on Jun 20, 2020 20:53:52 GMT
Good Day Don, Nope, it was factory fitted with a MIB1 and changed it for a MIB2. I was always convinced it was a hacked unit but I guess it's not because I have updated nav maps last week and all of my CP protection DTC's in 5F and 19 are gone  But I checked the history backup 5F and also in the very beginning this was a DTC, never found out what is wrong. I read somewhere that there are 3 suffix for the same unit if it comes to NAV maps but when I check our VW website, there only one version I can download for the MIB. Maybe it is a MIB2 from another country and maybe that's the reason why it tells me in other words that I have the wrond maps for my unit. Everything in the 5F is working as it should be though. Greetings Crunch |
|
|
|
Post by dv52 (Australia) on Jun 20, 2020 22:33:18 GMT
crunch: Go to Byte3 on the long code for the hex5F module and check the setting of the software switches. This Byte tells the MIB which country the SATNAV maps should use. Here's the list to decode the Bit patterns to country entries. The picture is from VCDS, but the hex values equally apply to OBD11.  Don |
|
|
|
Post by crunch81 on Jun 21, 2020 7:35:59 GMT
Hello Don,
Thanks!
I made a change in Byte 03, navigation was not starting anymore. (it was on the right bit (Bit 01 EU), but wanted to see if it made any changes)
So this setting is correct. Do you have more options which I cannot see in OBD but are relevant to NAV?
Greetings Crunch
Added Later:
FYI: The communication interruption in module 17 was the setting with "show compass in bottom or top" Not very logical, but it is solved.
one DTC in the 5F is also solved; it was the missing message DTC. Cause: It had VPS activated in the Gen2 Bap Car Funtion list. It was hard to find but it had something to do with a front camera.
Now there's only one dtc left in 5F, which is the Nav Database not enabled.
|
|
|
|
Post by dv52 (Australia) on Jun 21, 2020 14:14:13 GMT
^^^^ crunch how about Byte 24, Bit 2?  |
|
|
|
Post by crunch81 on Jun 21, 2020 14:18:23 GMT
Hi Don, Yes, it is enabled.  Greetings Crunch |
|
|
|
Post by rafaelsgon on May 23, 2022 2:21:53 GMT
@ crunch81 , dv52 (Australia)Friend, I have this same problem on my Golf GTI 2017 since I bought it used, it has MIB2 Discovey 8".. I always clear this error and a few days later it returns.. Could you tell me step by step in OBD11 how can I solve this problem?    I really appreciate your attention and help... Added Later: According to your comment I have checked here and the compass display in the dashboard is selected as bottom, if I change it to top will the error go away? 
attachment log: OBDeleven_Log.txt (208.79 KB) thanks in advance!!! |
|
