Module 5F long coding help

[nordic_b]

Hey guys,

First post, apologies if has been already asked.

I've got a 2015 A6 C7 2.0 tdi manual, recently did MMI update + maps, all went well, however I have a feeling with the update the coding may have changed, because tweeters stopped playing or the sound has changed (for the worse, too much bass)
It also has 2 faults, that cannot be wiped.
Otherwise everything works.

The module is: 4G1 035 043 M

I have VCDS, however it has no coding helper for this module, therefore I cannot really check if anything is off.

Kicking myself for not taking a copy of the original coding prior the update.

Thanks in advance

[VAG-Abound]

If you saved a scan the coding should be there, like this:


Address 37: Navigation (J0506) Labels:. 1T0-035-680.clb
Part No SW: 1T0 035 680 D HW: 1T0 035 680 A
Component: RNS-MID H04 4020
Revision: AB001001
Coding: 00000400040000210000

If you Google something like this (from my example, but adjusted for whatevr your scans say) you may find examples to try:

"Labels:. 1T0-035-680.clb" "Part No SW: 1T0 035 680 D"

[nordic_b]

Sorry for the delay - weekend away from PC.

Thanks for that. I did quite a bit of research online and very little comes up, only few examples, as if this module is more rare than any other.
Here is what I have at the moment anyway. From what I could find, byte 4, 5 and 11 may be responsible for sound settings, system setup.



Address 5F: Information Electr. Labels: None
Control Module Part Number: 4G1 035 043 M HW: 4G1 035 043
Component and/or Version: MU-H-N-EU 040 1425
Software Coding: 01750201FF0A000013110001000A00002F0006E7F1700100DF
Work Shop Code: WSC 02391 785 00200
ASAM Dataset: EV_MUHig6C3Gen2HBAS 001115 (AU57)
ROD: EV_MUHig6C3Gen2HBAS_AU57.rod
VCID: 285F4DA74BF312C66A-807C
2 Faults Found:


1543 - Control Module Incorrectly Coded
U1014 00 [008] - -
Intermittent - Confirmed - Tested Since Memory Clear
Freeze Frame:
Fault Status: 00000001
Fault Priority: 4
Fault Frequency: 1
Reset counter: 67
Mileage: 167569 km
Date: 2022.08.16
Time: 17:21:49


Voltage terminal 30: 12.3 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


1555 - Check Software Version Management
B201A 00 [009] - -
[New feature! Extended UDS fault detail is only supported by current gen. interfaces]
Confirmed - Tested Since Memory Clear
Freeze Frame:
Fault Status: 00000001
Fault Priority: 6
Fault Frequency: 1
Reset counter: 13
Mileage: 167569 km
Date: 2022.08.16
Time: 17:21:54


Voltage terminal 30: 12.3 V
Status_Software_Version_Management-module_name: MDUA009/Front

[VAG-Abound]

This is very similar to you: 5F config error ? | Ross-Tech Forums (https://forums.ross-tech.com/index.php?threads/31477/)

Did you find it and try the coding they worked out?

EDIT: They have a labels file as well. Are you using a genuine interface? If so see if you can get help there.

[nordic_b]

Thanks, looks similar indeed, unfortunately I don't have the original coding...
One thing though, how do they select the label 4G1-035-MIB-HGH2.clb, I do have this file, but it does not get pulled in automatically, nor I can specify to use it. I recall in older VCDS versions there was an option to specify the label file...

[VAG-Abound]

I'd assume the key thing is to play with the bytes that made a difference for them. Plot them in Excel if you have it and use HEX2BIN(), etc to untangle what is what.

If I'm reading correctly, in bytes 13, 14, 15...

They originally had 0A, 00, 03 and found that 0B, 00, 03 worked in the end.

You have 0A, 00, 00, which is presumably the original coding. So try 0B, 00, 00 perhaps?

The other thing they don't mention (so maybe there was some auto-flipping of bits) that may be important too:

Byte 8 went from 13 to 33
Byte 24 went from 9F to BF (setting bit 5), which would be DF to FF for you.


See my note in edit above re asking Ross Tech about the labels - they may have to align it with the reporting version.

[nordic_b]

Thanks for all the help. I ended up updating VCDS and does give me coding helper.
As suspected, bytes 4, 5 and 11 correspond to audio settings, all will have some sort of EQ applied to the end sound. I've changed byte 11 to 02 and while it doesn't sound as before, it brought up some midrange that I prefer more than just bassy or fatiguing V shaped sound.

I'll have to address the coding error and the other fault some time, but as far as I can see and hear, these do not effect anything it seems.

Kind regards!

[nordic_b]

Just wanted to add, until faults were present I could not get it sound right, which is odd.
On B201A 00, there are some tips on youtube, basically needed a new key.
The U1014 00 got cleared after clearing fault above and selecting correct byte 11, which was "01 - Internal Amp" in my case.
It looks like after coding, the MMI needs to be reset, or coding may have no effect.