2016 A4 5F Long Coding

[pt16a4]

Hello all, 

New to the board. I had a battery replaced on a 2016 A4 Avant diesel (2.0, 150 hp), and MMI features were lost - mechanic accessed the car's settings via OBD. I Purchased the OBDeleven dongle, and found that 5F coding was set to all 0s. Unfortunately, I do not have a record of the original coding.

Voice commands lost. Bluetooth lost. MMI main screen is blank. Vehicle sensors not available (ex. oil).

I have looked at the long coding, but do not know which values to input for Car Class/Generation/Derivate/Derivate Supplement etc.

Any suggestions or help?

Thanks in advance!

[niccoo]

Hello, Can anyone help me with the origin settings for the 44, 5f, A5 modules - long coding for the Audi a4 B9 8W2 model, year 2016? Thank you

[pt16a4]

Update: Was able to bring Bluetooth and Voice Commands back to life (selected them within long coding).

However, cannot figure out how to restore "Car Settings" to the MMI. Have scoured the internet, with no luck. The Menu on the MMI screen continues blank, and when selecting the "Car" button, I get a "currently unavailable" message.

I am completely new to OBDeleven and trying to figure this out as I go.

Any suggestions on how to get these functions back up and running?

[pt16a4]

Would appreciate any advice on how to address the below faults. As mentioned, I managed to restore Bluetooth and Voice Controls, but am still unable to restore the Car settings and MMI main Menu.

A snapshot of the data pulled from a scan and subsequent long coding:

5F Multimedia
Descrição do sistema: MU-S--ER
Número do Software: 8W0035824
Versão do Software: 0621
Número de Hardware: 8W0035824
Versão do Hardware: 520
Número de Série:
Nome do ODX: EV_MUStd6C3DELP
Versão do ODX: 001013
Falhas:
U101300 - Control module not coded
static
Mileage: 92184 km
Priority: 4
Malfunction frequency counter: 1
Unlearning counter: 83
Dynamic environmental data: 028692
U101400 - Control module incorrectly coded
static
Mileage: 92184 km
Priority: 4
Malfunction frequency counter: 1
Unlearning counter: 83
Dynamic environmental data: 0286921017545551555545A9

46 Comfort System
Descrição do sistema: BCM2 MLBevo
Número do Software: 8W0907064CA
Versão do Software: 0344
Número de Hardware: 8W0907064A
Versão do Hardware: 016
Nome do ODX: EV_BCM2HellaAU736
Versão do ODX: 012013
Falhas:
B140B29 - Release button in rear lid handle Implausible signal
static
Mileage: 92184 km
Priority: 5
Malfunction frequency counter: 1
Unlearning counter: 83
Dynamic environmental data: 3A3E39DA39F539F517501B020A9802E000000000008A009501 0000000000000000011754F13E13F6

17 Dashboard
Descrição do sistema: MM--M--DSLRW-
Número do Software: 8W5920741
Versão do Software: 0265
Número de Hardware: 8W5920741
Versão do Hardware: H06
Número de Série: RW2FLNE3S
Nome do ODX: EV_DashBoardAU736
Versão do ODX: 001022
Falhas:
U105400 - Information electronics control module 1 No Communication
static
Mileage: 92184 km
Priority: 6
Malfunction frequency counter: 1
Unlearning counter: 83

Histórico do veículo no dispositivo

Data: 2020-10-19 10:46

VIN: XXXXXXXXXX
Veículo: Audi A4
Ano: 2016
Tipo de corpo: Avant
Motor: DEUA 110 kW (150 HP) 2.0 l
Quilometragem: 92188 KM

---------------------------------------------------------------
Codificação longa
Unidade de Controle: 5F Multimedia
Valor antigo:
010000000000000010000000000000005F0000000000000002
Novo valor:
010000000000000010000000000000006F0000000000000002
Quilometragem: 92188 km
Data: 2020-10-17 16:33

---------------------------------------------------------------
Codificação longa
Unidade de Controle: 5F Multimedia
Valores:
byte_16_Bluetooth_Visibility:
Valor antigo: auto
Novo valor: On
Quilometragem: 92188 km
Data: 2020-10-17 16:33

---------------------------------------------------------------
Codificação longa
Unidade de Controle: 5F Multimedia
Valores:
byte_24_Voice_Control_System:
Valor antigo: Not activated
Novo valor: activated
Quilometragem: 92188 km
Data: 2020-10-17 16:28

---------------------------------------------------------------
Codificação longa
Unidade de Controle: 5F Multimedia
Valor antigo:
010000000000000010000000000000005F0000000000000000
Novo valor:
010000000000000010000000000000005F0000000000000002
Quilometragem: 92188 km
Data: 2020-10-17 16:28

---------------------------------------------------------------
Codificação longa
Unidade de Controle: 5F Multimedia
Valores:
byte_16_Bluetooth_Audio:
Valor antigo: Not available
Novo valor: available
byte_16_Bluetooth_Visibility:
Valor antigo: Off
Novo valor: auto
byte_16_Bluetooth_Headphones:
Valor antigo: Off
Novo valor: On
byte_0_brand:
Valor antigo: no_brand
Novo valor: AUDI
byte_16_Bluetooth_Phone:
Valor antigo: Not available
Novo valor: available
byte_16_Bluetooth_Multimedia_Functionality:
Valor antigo: Not available
Novo valor: available
byte_8_AUX_IN:
Valor antigo: Off
Novo valor: On
byte_16_Bluetooth_Availability:
Valor antigo: Not available
Novo valor: available
Quilometragem: 92188 km
Data: 2020-10-17 16:28

---------------------------------------------------------------
Codificação longa
Unidade de Controle: 5F Multimedia
Valor antigo:
00000000000000000000000000000000000000000000000000
Novo valor:
010000000000000010000000000000005F0000000000000000
Quilometragem: 92188 km
Data: 2020-10-17 16:28

[pt16a4]

Is there somewhere else I should be posting this, or is the forum just not overly responsive?

I know I´m asking for help, and not offering any, but I expected some feedback from a forum on the topic of OBDeleven. Is no one on here able to provide any insight on restoring car settings/MMI? I just keep pulling info I´m able to find from other sites.

Pointless to be posting to my own thread.

[Thirsty]

It's hard to help you figure out the long coding since this can be different for other cars. The coding depends on with what features you bought your car.
I think that's the reason why nobody is answering.

[pt16a4]

I appreciate the response! That is a valid argument, which I can appreciate; hence I have been slowly working through the coding by reading/comparing what others have coded, based on my own vehicle specs. It is much better to read your explanation, than "silence".

That said, are there now hints as to why the Car settings would now be unavailable? Are those tied to a specific module? I have also purchased a female fibre optic loop bypass, but am unsure if it is required to solve this problem.  The MMI screen itself works fine, the menus are what are either unavailable or greyed-out.

[Thirsty]

I'd say you're missing some long coding and/or adaptations in your 5F. Problem is that we don't know what the original value of your 5F was.
Check your long coding and adaptations again. There must be some options regarding the car settings etc.

I'm pretty sure your long coding value (010000000000000010000000000000005F0000000000000000) is not yet correct.

[pt16a4]

Thanks for the feedback.

I have worked at the long coding, which is no longer all 0s, but it´s a slow process given the lack of knowledge on what each component represents. Still have not figured out how to activate car settings via MMI - had to change the date and time via the OBDeleven.

It would help if I know what byte or function I should be looking for.

Is there a walk-through available for the long coding/adaptations? 


Data: 2020-10-22 18:10



VIN: XXXXXXXXXX

Veículo: Audi A4

Ano: 2016

Tipo de corpo: Avant

Motor: DEUA

Quilometragem: 92402 KM



---------------------------------------------------------------

Codificação longa

Unidade de Controle: 5F Multimedia

Valor antigo:

015100000000000010110000000000005F0000000000020002

Novo valor:

015100000000000011110001000802406F0101400100020003

Quilometragem: 92402 km

Data: 2020-10-22 17:48



---------------------------------------------------------------

Codificação longa

Unidade de Controle: 5F Multimedia

Valores:

byte_13_Radio_Text_Plus:

Valor antigo: Not activated

Novo valor: activated

byte_20_display_1:

Valor antigo: not connected

Novo valor: connected

byte_16_Bluetooth_Visibility:

Valor antigo: auto

Novo valor: On

byte_18_Screenings:

Valor antigo: 0

Novo valor: 1

byte_17_Skinning:

Valor antigo: no_Skin

Novo valor: Skin_1

byte_19_USB:

Valor antigo: Off

Novo valor: charge

byte_8_Microphone_1:

Valor antigo: not connected

Novo valor: connected

byte_14_AM_disable:

Valor antigo: Not activated

Novo valor: activated

byte_24_Emergency_Call:

Valor antigo: Off

Novo valor: On

byte_15_Media_Player_1:

Valor antigo: not_connected

Novo valor: connected_without_USB_hub

byte_11_Sound_System:

Valor antigo: Sound_System_no_Allocation

Novo valor: Sound_System_internal

Quilometragem: 92402 km

Data: 2020-10-22 17:48

[pt16a4]

Update: able to set tire pressure via MMI - Car settings still not available and had to use the left more info button to access the vehicle settings. The oil level reports "sensor malfunction" and wipers are greyed-out. All car adjustments are still unavailable, and main menu blank.

Can anyone share what the first values of codings should be for a 2016 A4 Avant
Brand: Audi
Car Type: ?
Generation: ?
Derivate: ?
Supplement: ?

[donny]

From my 2016 A4 B9 (8W2) 3.0 saloon the data is as follows

Byte 0 Brand. AUDI
Byte 1 car class. 4. (As in A4)
Byte 1 car generation. 9. (As in B9)
Byte 2 car derivate. 1. (1st year of productio of this model)
Byte 2 car derivate supplement. 0

Hope this helps.

[pt16a4]

Thanks Donny, great help! I´ll update accordingly.

I´ve been making progress on various fronts, restoring tire pressure settings/wipers, with some issues on others. Have recovered many Car features, and gained a few new ones (greyed), but still trying to figure out what the vehicle is actually equipped with in terms of driver assistance - pre-sense is still working but I believe I had a level of lane assist before the coding was wiped and trying to restore those functions, without going beyond my standard equipment and resulting error messages.

Still cannot restore the main Menu screen - where each feature is displayed via MMI - anyone have any tips?

[pt16a4]

Update: I've been able to restore all functions, after many hours reading through threads and trying my hand at coding/adaptations.

Finally wrapping my head around how the 5F module works, and to an extent, the links between each module.

Really appreciate the coding provided above for the A4 B9, that was a massive help.

Tried applying ALA and Park Assist; removed both as had faults - EFP would not code. Audi pre sense adjustment has been removed from my MMI options, and potentially disabled completely, not sure. Not a big fan of the setting to begin with, but will look to recover the setting selection.

Have not used any credits, and I actually prefer to make the changes myself, to know what's being done. With my settings recovered, can now look at what else is available to activate.

[donny]

I too am fairly new to using OBD11 on my 2016 A4 B9 Saloon.
Currently I have no errors.
I too prefer to use the coding rather than the apps although I have used a few which worked.
If you need any more settings From my vehicle just ask.

[pt16a4]

Thanks Donny, I appreciate the support.

I am still trying to figure out what each line of coding stands for/does within the long coding. The more I look at print-outs online, I see some options that I should change, or think I should change.

Currently faultless, but that doesn't mean I have the system back to what it was; pre-sense and speed warnings menus are missing for example. I had date & time back, but they were greyed-out and I ended up removing - will need to restore. My main settings are back however, which was the objective.

Would be great if a description of each long code/adaptation item were available.

[arnau]

If it's useful for you I have an Audi A4 B9 2.0 TDI 190 Quattro (June 2016) with MMI Basic, Navigation, Android auto/Applecarplay, parking sensors front and rear, no rear camera, adaptative cruise control and line assist, no blindspot assist, multifunction plus steering wheel and wireless charging

My 5F long coding is 01940201FF00000053110001000A00332F001CE4017001008E

[pt16a4]

Arnau,
Really appreciate the post.

You have some options that I do not, but will have a look through my coding compared to yours, and see what changes may be needed.




Question regarding the initial sequence - Donny above posted: car type as 4 (as in A4) while you have 1.

By using Donny's initial coding I did recup functions via MMI.

Anyone know the difference in changing this? 4 vs. 1?

[arnau]

No, you need to read by bytes, and transform from hex to binary

0194...

Hex 01 means 1 in binary, which means bit 0 on (audi), the rest of bits all off

Hex 94 means 10010100 in binary, which means from right to left bit 0 off, bit 1 off, bit 2 on, bit 3 off, bit 4 on, bit 5 off, bit 6 off, bit 7 on

In this case on byte 1, 94 means, generation 9, car class 4, on other bytes it means some options on or off.

Transforming to binary you know which bits i have activated on every byte.


It should be quicker to use my long coding as a base (many of the info contained is the same on every A4 regardless of the options) and modify it to add/remove the options that correspond to your car than building your long coding from scratch.

[dv52 (Australia)]

pt16a4 : I've just read your plight. I'm by no means an expert on your A4 - but in the hope that it will help, here are some long code examples for the hex 5F modules with the part number in your post above (which is 8W0035824). Note: these extracts are from VCDS - but that shouldn't matter. Also note that OBD11= 8W0035824 is the same as VCDS=8W0 035 824

Car from Estonia
Address 5F: Information Electr. (J794)
Part No SW: 8W0 035 824 C HW: 8W0 035 824 C
Component: MU-S--ER 721 0840
Serial number:
Coding: 01940100FF00000053110001000A00002F0001440170010002
Shop #: WSC 06335 790 00001

Car from Croatia

Address 5F: Information Electr. (J794)
Part No SW: 8W0 035 824 HW: 8W0 035 824
Component: MU-S--ER 520 0621
Serial number:
Coding: 01940100FF00000013110001000A00002F0001C40170010002
Shop #: WSC 06325 790 00001

As Thirsty has advised, the long-code values are particularly sensitive to the equipment that's factory fitted to the car - so I'm certainly NOT suggesting that duplicating the long code strings above will be simply plug-and-play. But hopefully it will help

So, my suggestion is that you start by using the Byte values that are the same in both modules -based on the assumption that these hex values form a base for EU vehicles. Then selectively apply the byte values that are different - perhaps the OBD11 descriptors screens for the module long-code can help in selecting which Bits to set (and which to not-set) for each Byte.

For this second step, I would favor the Croatian car because it also has the same software/hardware details as your car - see highlighted values on both

Your car

5F Multimedia
Descrição do sistema: MU-S--ER
Número do Software: 8W0035824
Versão do Software: 0621
Número de Hardware: 8W0035824
Versão do Hardware: 520

To further help with this process, here's how the 2 x long-code strings (and arnau suggestion) decode into Byte hexadecimal (hex) and Binary values (remember that for Binary values, the right-most digit is Bit 0 and therefore the left-most digit is Bit 7):


       Estonia        Croatia        arnau
Byte Hex Binary        Hex Binary        Hex Binary
0 01 00000001 01 00000001 01 00000001
1 94 10010100 94 10010100 94 10010100
2 01 00000001 01 00000001 02 00000010
3 00 00000000 00 00000000 01 00000001
4 FF 11111111 FF 11111111 FF 11111111
5 00 00000000 00 00000000 00 00000000
6 00 00000000 00 00000000 00 00000000
7 00 00000000 00 00000000 00 00000000
8 53 01010011 13 00010011 53 01010011
9 11 00010001 11 00010001 11 00010001
10 00 00000000 00 00000000 00 00000000
11 01 00000001 01 00000001 01 00000001
12 00 00000000 00 00000000 00 00000000
13 0A 00001010 0A 00001010 0A 00001010
14 00 00000000 00 00000000 00 00000000
15 00 00000000 00 00000000 33 00110011
16 2F 00101111 2F 00101111 2F 00101111
17 00 00000000 00 00000000 00 00000000
18 01 00000001 01 00000001 1C 00011100
19 44 01000100 C4 11000100 E4 11100100
20 01 00000001 01 00000001 01 00000001
21 70 01110000 70 01110000 70 01110000
22 01 00000001 01 00000001 01 00000001
23 00 00000000 00 00000000 00 00000000
24 02 00000010 02 00000010 8E 10001110




Good luck!!

Don

[arnau]

Wow great summary!

Some additional notes

It looks like croatian and estonian cars have mmi basic without Navigation, while mine has mmi basic with navigation

Byte 15 looks related to wireless charging
Byte 3 is for navigation region (EU) in mine
Byte 24 is for several mmi parameters like wlan, navigation, voice control

[pt16a4]

Gents, many thanks for the input!
It´s been difficult getting feedback from users, so I genuinely appreciate the tips here.

You´re talking way above my level, so I´ll need some time to soak all this in (I only use the verbal description when long coding). Only now did I realize that the coding is displayed differently as a final code, after being input via long code - hence my question regarding 1 vs. 4.

In truth, mine is coded the same... I just didn´t realize that, as I was viewing it vertically as opposed to horizontally, for lack of a better term.

I have reviewed the coding extensively since I started to re-code the module, and this is the latest (as of Oct. 28th):
019411000000000011110001000802405F0101400100020002

[Deleted]

Not sure if the followin helps you but many years ago I put this spreadsheet together

forum.obdeleven.com/attachment/download/190

All you have to do is enter the HEX Code and it will show you the Binary value but (for me more importantly) it shows you what values will be ticked if I select that value on the obd11 screen.

If you are interested there is also a thread hear that talks about Long Coding in more detail forum.obdeleven.com/thread/102/long-coding

One last item you are able (if you use android) to add labels to the Bit's which does help to make more sense of them when you go back later.

[pt16a4]

@testosterone
Thanks, I'll try that out on my laptop - can't seem to open the file on my phone. Great ink as well; I had scanned over it before, but never really tried understanding the Hex explanation. Have always stuck to the written description, but I see how this will help.

don, thanks again for such a detailed explanation. I just read your post again (yet again) and truly realized how much effort you put into it! Will try to work through the long coding as suggested.

Much appreciated gents!

[pt16a4]

Again reading through this post and the linked forum page, and I believe I finally understand the hex/binary. What a massive difference it makes!

The descriptive long coding helps if you don't have a clue, but the hex/binary tells you exactly what needs to be ticked in a simple format.

Will adjust according to my car's specs.

Big thanks!

[pt16a4]

01940100FF00000011110001000A02002F0101C40170010002

Latest long coding, folliwing the advice above. A couple changes to bytes 17 & 18, otherwise pretty much like for like.

Adaptations: finally got the oil level working again - it kept giving me an "oil sensory failure" message via MMI when in the car functions.

I can access Object Collision Warning (pre sense) via obdeleven, but they're gone from the MMI.

Speed Warning I have recovered, but it remains "unavailable" when I try to set via MMI. Time/date does the same. Can only adjust via obdeleven.

Any ideas on how to recover these setting?

[arnau]

I think most of the options that appear or not on the MMI menu are activated through adaptations. I'm not sure if we can dump all the adaptation lists from our cars so we can share it. I will check

[pt16a4]

Not sure either, but that would certainly help. As is, I wander through the options, and activate according to what I believe is available in the car.

Finally got the date/time active again - it was greyed out.

Speed warning remains unavailable, but visible via MMI.

As of now, have recovered all functions, except the pre sense adjustment and speed warning setting.

Thanks for the help!

[Deleted]

on my MQB Platform car all you have to do is a backup of the control unit this will show you what is on/off or setting if its a value.

[dv52 (Australia)]

hmm.......... as @testeronline advises, the backup facility on OBD11 will provide a list of ALL accessible adaptation channels - not only on MQB platform cars, but on ALL cars that use UDS/ODX modules (which would also apply to most/all VAG MY16 vehicles - I think)

After you have generated the back-up file, use the process below to digitize the information, then once the email is received and opened, cut-and-paste the back-up specific information on a post here:



Don

[pt16a4]

@testeronline don

Thanks, will do a backup and post.