Strange fault after fitting 8” screen

[Carlosfandang0]

EDIT:

Having now plugged in VCDS this is the code I’m getting b201a00 - check software version management,
There is more info about this code online so disregard the earlier post below as I should hopefully be able to now sort this out in 5F adaptations using info from Ross tech! I’ve no idea where carista was pulling the strange codes from but they don’t appear with VCDS!



Has anybody seen this code before??
I’ve just fitted the pre facelift 8inch touchscreen to my (non pro) mib2 system, all works as it should accept I now get a persistent fault code, (01555 - motors for central locking, SAVE.)

This was checked with Carista, I’ll plug in VCDS when I get a chance!

Once cleared 01555 returns and does so straight away, the locking works fine!

I’ve searched the web but can’t find any info so was hoping someone here had come a cross it before! Thanks.


Sent from my iPhone using Tapatalk

 

[Somnus]

The easiest way I've found to clear it is to use this post: https://forums.ross-tech.com/showthread.php?3998-Does-VAG-recognize-VCDS-as-diagnostics-tool&p=96873&viewfull=1#post96873

If you want to make it a little easier, you can use http://xor.pw/ instead of Windows Calculator

 

[Navi]

That's interesting.. after fitting the glass 8inch screen, i was getting this fault:

VCDS Version Release 18.9.0 (x64) Running on Windows 10 x64(Parallels)
www.Ross-Tech.com

Address 5F: Information Electr. Labels: 5G0-035-MIB-STD2.clb
Control Module Part Number: 3Q0 035 844 A HW: 3Q0 035 844 A
Component and/or Version: MU-S-S-US 710 0751
Software Coding: 027300000000000051220002001808009F0203F40120010002
Work Shop Code: WSC 00066 790 00199
ASAM Dataset: EV_MUStd4CDELP 001001 (VW37)
ROD: EV_MUStd4CDELP_VW26.rod
VCID: 2D04033E7D9E729F053-8079
2 Faults Found:

1555 - Check Software Version Management
B201A 00 [009] - -
[Check software version management]
Confirmed - Tested Since Memory Clear
Freeze Frame:
Fault Status: 00000001
Fault Priority: 6
Fault Frequency: 1
Reset counter: 188
Mileage: 32996 km
Date: 2018.12.18
Time: 11:46:13

Voltage terminal 30: 14.8 V
Status_Software_Version_Management-module_name: C


I went to the dealership and they just replaced the radio brain and I haven't had the fault since. Seems like it may have something to do with the radio screen change?

 

[southpawboston]

I've got the same fault code after installing the OEM 8" screen. The infotainment module is detecting a different hardware subsystem (the screen) and reporting it as a mismatch, presumably for warranty purposes (this way the dealer can keep track if a piece of hardware is original to the car or not-- to prevent, say, you going to the dealer for warranty replacement of that nice 8" screen if it goes bad). It presents no functionality issues whatsoever. I read somewhere that to get the code to go away, you have to enter some calculated value in the long coding that will allow the infotainment module to "accept" the screen as "original", but figuring out how to calculate that code change is challenging.

 

[Carlosfandang0]

That's interesting.. after fitting the glass 8inch screen, i was getting this fault:

VCDS Version Release 18.9.0 (x64) Running on Windows 10 x64(Parallels)
www.Ross-Tech.com

Address 5F: Information Electr. Labels: 5G0-035-MIB-STD2.clb
Control Module Part Number: 3Q0 035 844 A HW: 3Q0 035 844 A
Component and/or Version: MU-S-S-US 710 0751
Software Coding: 027300000000000051220002001808009F0203F40120010002
Work Shop Code: WSC 00066 790 00199
ASAM Dataset: EV_MUStd4CDELP 001001 (VW37)
ROD: EV_MUStd4CDELP_VW26.rod
VCID: 2D04033E7D9E729F053-8079
2 Faults Found:

1555 - Check Software Version Management
B201A 00 [009] - -
[Check software version management]
Confirmed - Tested Since Memory Clear
Freeze Frame:
Fault Status: 00000001
Fault Priority: 6
Fault Frequency: 1
Reset counter: 188
Mileage: 32996 km
Date: 2018.12.18
Time: 11:46:13

Voltage terminal 30: 14.8 V
Status_Software_Version_Management-module_name: C


I went to the dealership and they just replaced the radio brain and I haven't had the fault since. Seems like it may have something to do with the radio screen change?

Interesting that they would change the main infotainment unit seeing that you had switched screens! As mentioned there are no functionality issues with this code present, I’m going to see if I can calculate a different code with the info in one of the earlier posts, hopefully it works!!


Sent from my iPhone using Tapatalk

 

[Carlosfandang0]

The easiest way I've found to clear it is to use this post: https://forums.ross-tech.com/showth...diagnostics-tool&p=96873&viewfull=1#post96873

If you want to make it a little easier, you can use http://xor.pw/ instead of Windows Calculator

Thanks for the links, can you however explain what values are entered into Input1 and Input2 of the calculator please, is it the original value from the adaptation channel split in half or is there another value I need to find? Thanks.



Sent from my iPhone using Tapatalk

 

[Somnus]

Thanks for the links, can you however explain what values are entered into Input1 and Input2 of the calculator please, is it the original value from the adaptation channel split in half or is there another value I need to find? Thanks.



Sent from my iPhone using Tapatalk

I should have specified, Sorry about that.

NOTE: I am using the values from my car in the explanation, please make sure you use the one from your car. for the calculation

1) First input is the value you got from the adaptation channel Confirmation of Installation Change: (my car was 95 E2) but remove the space and make it lowercase (so 95 E2 becomes 95e2)

2)Second input is c9d2 (not sure why this works, must be voodoo)

3) take the output and add the space back in (my output was 5c30, which changes to 5c 30) and then put that as a new value in the adaptation channel and save it.

4) enjoy no more random fault code

 

[Carlosfandang0]

I should have specified, Sorry about that.

NOTE: I am using the values from my car in the explanation, please make sure you use the one from your car. for the calculation

1) First input is the value you got from the adaptation channel Confirmation of Installation Change: (my car was 95 E2) but remove the space and make it lowercase (so 95 E2 becomes 95e2)

2)Second input is c9d2 (not sure why this works, must be voodoo)

3) take the output and add the space back in (my output was 5c30, which changes to 5c 30) and then put that as a new value in the adaptation channel and save it.

4) enjoy no more random fault code

Top man! Thanks very much for clarifying,
I’ve done the calculation using your instructions and no more fault code!
Also worth mentioning for anybody else who may have this issue and find themselves here is that the value may instantly return to the old value after clicking Do It! This is normal, the new value will have taken without showing.


Sent from my iPhone using Tapatalk

 

[Somnus]

Glad it worked for you!

 

[southpawboston]

I am trying this tonight!

 

[southpawboston]

Worked like a charm! No more persistent fault code for 5F with the updated screen!!! I am perpetually amazed at the level of collective hive wisdom on this platform.

 

[mk3vr6me]

Thanks guys! Worked a charm. I actually didn't even notice the code in there as I must not have scanned 5F since I installed it. I did know I didn't have any errors prior to doing the mod which unlocks the menus while driving. Side Note: Need some help if anyone can take the time.

I have another error in my 5F due to me changing a couple values in the fb_misc/fb_tuner/fb_car/fb_media/fb_phone. I must have changed an inappropriate value to 'non_blocked' and now this error follows.

1543 - Control Module Incorrectly Coded
U1014 00 [009] - -
Confirmed - Tested Since Memory Clear
Freeze Frame:
Fault Status: 00000001
Fault Priority: 4
Fault Frequency: 1
Reset counter: 202
Mileage: 78249 km
Date: 2019.01.23
Time: 15:05:55

Voltage terminal 30: 14.5 V
Byte_Coding_Condition-byte_0_condition: OK
Byte_Coding_Condition-byte_1_condition: OK
Byte_Coding_Condition-byte_10_condition: ERROR
Byte_Coding_Condition-byte_11_condition: ERROR
Byte_Coding_Condition-byte_12_condition: ERROR
Byte_Coding_Condition-byte_13_condition: ERROR
Byte_Coding_Condition-byte_14_condition: ERROR
Byte_Coding_Condition-byte_15_condition: ERROR
Byte_Coding_Condition-byte_16_condition: ERROR
Byte_Coding_Condition-byte_17_condition: ERROR
Byte_Coding_Condition-byte_18_condition: ERROR
Byte_Coding_Condition-byte_19_condition: ERROR
Byte_Coding_Condition-byte_2_condition: OK
Byte_Coding_Condition-byte_20_condition: ERROR
Byte_Coding_Condition-byte_21_condition: ERROR
Byte_Coding_Condition-byte_22_condition: ERROR
Byte_Coding_Condition-byte_23_condition: ERROR
Byte_Coding_Condition-byte_24_condition: ERROR
Byte_Coding_Condition-byte_25_condition: ERROR
Byte_Coding_Condition-byte_26_condition: ERROR
Byte_Coding_Condition-byte_27_condition: ERROR
Byte_Coding_Condition-byte_3_condition: OK
Byte_Coding_Condition-byte_4_condition: OK
Byte_Coding_Condition-byte_5_condition: OK
Byte_Coding_Condition-byte_6_condition: OK
Byte_Coding_Condition-byte_7_condition: OK
Byte_Coding_Condition-byte_8_condition: OK
Byte_Coding_Condition-byte_9_condition: OK

I know this would be time consuming for somebody but can anyone report the values that I would need for all the other bytes that aren't in SouthPaws VCDS tweaks sheet?
I think that is the only way for me to get rid of this error unfortunately as I didn't write my coding down prior to changing. Stupid me. Everything seems to function fine regardless.

EDIT: This code may be totally unrelated to the menu block settings change as I've googled people who have changed every setting to 'non_blocked' without this error popping up. So back to square one. I do have an MIB2 retrofit in my 2015 but I swear after I coded it all to my car I did not have this error code.

 

[Somnus]

That fault should be unrelated to the adaptation changes. the Infotainment system seems to think there is an issue with bytes 10-27 of your coding.

could you post the coding string your 5F unit has currently?

 

[mk3vr6me]

That fault should be unrelated to the adaptation changes. the Infotainment system seems to think there is an issue with bytes 10-27 of your coding.

could you post the coding string your 5F unit has currently?

Sure, it's 02730000FF00000051220001001808009F0200C40120010012

I'm 2015 GTI S with MIB2 conversion + 8" Glass screen. Non Nav unit 3Q0035844A from 17' GTI. Software version 0753. The car was configured exactly as mine so I didn't have to change a whole lot. Non fender system and no nav. Pretty simple swap and Jack was able to get everything functioning.

He did install Performance Monitor on it as well and a few things function but Oil/Coolant Temp and Boost do not read out. I'm guessing a gateway issue maybe as this car isn't meant to come with MIB2 is my best guess.

 

[Somnus]

Try changing your coding to 02730000FF00000051220001001808009F0200C40120010002

then clear faults and see if the code comes back.

Also, if you have an Adaptation map for your Infotainment system i would love to take a look at it.