Coding for dashboard 2016 S3

[brandons3]

Hi I have an 2016 S3 is anyone able to share their dashboard coding please because I must have input the wrong coding and now that control unit isn't working properly now. Please help it would be much appreciated🙏

[Thirsty]

Please check your coding history to get the old value

[brandons3]

I did put my old coding history but now my optical parking system app isn't working now. Won't let me add the feature say faulty in red at bottom corner😢

[dv52 (Australia)]

^^^brandon: Hi. On your first post - simply using the long-coding string from someone else's Dashboard module for a 2016 S3 won't work because the values vary greatly depending on the country of sale and factory fitted options.

In your last post - can you provide a copy of the before and after values that you changed from your history report? And, if you have any error messages, post them as well.

Don

[brandons3]

Thank u for ur reply I’ll go through my history
Also in control unit should the long coding byte 22 wheel drive should this be set as front, rear or all wheel drive? Mine is set to front I thought this is an all wheel drive car?
Also my information control unit isn't available to be accessed any more. When I do the scan it says fault (09) central electrics but after I clear the scan iut says neither active or inactive fault
Also in the scan it says the cruise control has 10 inactive faults

[brandons3]

Oct 15, 2019 22:17:03 GMT dv52 (Australia) said:

^^^brandon: Hi. On your first post - simply using the long-coding string from someone else's Dashboard module for a 2016 S3 won't work because the values vary greatly depending on the country of sale and factory fitted options.

In your last post - can you provide a copy of the before and after values that you changed from your history report? And, if you have any error messages, post them as well.

Don

How do you add screenshots?

[brandons3]

Oct 15, 2019 22:17:03 GMT dv52 (Australia) said:

^^^brandon: Hi. On your first post - simply using the long-coding string from someone else's Dashboard module for a 2016 S3 won't work because the values vary greatly depending on the country of sale and factory fitted options.

In your last post - can you provide a copy of the before and after values that you changed from your history report? And, if you have any error messages, post them as well.

Don

Whenever i do a scan adaptive cruise control comes with fault but active or inactive fault comes up as 0. And when I click the fault it says databus error value received. What does this mean? Also central electrics comes up as fault alsk but active or inactive comes up as 0 as well.

How do I add my history log BTW? Also when I try to activate cruise control should I see 3 (...) at the bottom of the instrument cluster?

[brandons3]

Oct 15, 2019 22:17:03 GMT dv52 (Australia) said:

^^^brandon: Hi. On your first post - simply using the long-coding string from someone else's Dashboard module for a 2016 S3 won't work because the values vary greatly depending on the country of sale and factory fitted options.

In your last post - can you provide a copy of the before and after values that you changed from your history report? And, if you have any error messages, post them as well.

Don

-------------------------
Fault
Control unit: 5F Information Control Unit
Active faults: 0
Inactive faults: 1
System description: MU-H-N-RW
Software number: 8V0035045G
Software version: 0398
Hardware number: 8V0035045C
Hardware version: H45
Serial number: A307E0F7550633
ODX name: EV_MUHig6C3HBAS
ODX version: 001040
Faults:
U112100 - Databus missing message
Passive


Mileage: 32215 km
Date: 2019-10-14 23:41

---------------------------------------------------------------
App
Name: Seat belt warning
Old value: EU
New value: OFF
Mileage: 32215 km
Date: 2019-10-14 23:39

---------------------------------------------------------------
App
Name: Open door alarm
Old value: Driver door
New value: OFF
Mileage: 32215 km
Date: 2019-10-14 23:39

---------------------------------------------------------------
App
Name: Windows function from remote
Old value: Original
New value: ON
Mileage: 32215 km
Date: 2019-10-14 23:36

---------------------------------------------------------------
Adaptation
Control unit: 09 Central Electrics
Name: Access control 2
Values:
Menuesteuerung Regenschliessen:
Old value: not active
New value: active
Regenschliessen_art:
Old value: once
New value: permanent
Regenschliessen_ein_aus:
Old value: not active
New value: active
Mileage: 32215 km
Date: 2019-10-14 23:04

---------------------------------------------------------------
Long coding
Control unit: 42 Door Electronics Driver Side
Old value:
005D1A204101040000001003
New value:
005D1A205101040000001003
Mileage: 32215 km
Date: 2019-10-14 22:57

---------------------------------------------------------------
App
Name: Scandinavian DRLs
Old value: OFF
New value: ON
Mileage: 32215 km
Date: 2019-10-14 22:15

---------------------------------------------------------------
Adaptation
Control unit: 09 Central Electrics
Name: Leuchte23SL HLC10
Values:
Lichtfunktion D 23:
Old value: nicht aktiv
New value: Tagfahrlicht
Mileage: 32215 km
Date: 2019-10-14 22:08

---------------------------------------------------------------
Adaptation
Control unit: 09 Central Electrics
Name: Access control 2
Values:
SAD Richtung Komfortoeffnen:
Old value: tilting
New value: open
Mileage: 32215 km
Date: 2019-10-14 21:58

---------------------------------------------------------------
Fault
Control unit: 09 Central Electrics
Active faults: 0
Inactive faults: 1
System description: BCM MQBAB H
Software number: 5Q0937084AS
Software version: 0175
Hardware number: 5Q0937084AN
Hardware version: H24
Serial number: 01061520305978
ODX name: EV_BCMMQB
ODX version: 015001
Faults:
U101400 - Control module incorrectly coded
Active


Mileage: 32215 km
Date: 2019-10-14 21:53

---------------------------------------------------------------
App
Name: Static Cornering Lights
Old value: OFF
New value: ON
Mileage: 32215 km
Date: 2019-10-14 16:30

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

---------------------------------------------------------------
Fault
Control unit: 03 Brakes
Active faults: 0
Inactive faults: 0
System description: ESC
Software number: 3Q0907379AB
Software version: 0723
Hardware number: 3Q0907379G
Hardware version: H42
Serial number: 61775000002419
ODX name: EV_Brake1UDSContiMK100IPB
ODX version: 034036
Faults:
No trouble codes found

Mileage: 32215 km
Date: 2019-10-14 16:27

---------------------------------------------------------------
Long coding
Control unit: B7 Access Startsystem Interface
Old value:
030C0C
New value:
030C1C
Mileage: 32215 km
Date: 2019-10-14 16:25

---------------------------------------------------------------
Long coding
Control unit: 17 Dash Board
Old value:
278D181A7F9800080181E8001000000000000000
New value:
278D181A7F9800080181EA001000000000000000
Mileage: 32215 km
Date: 2019-10-14 16:24

---------------------------------------------------------------
Full scan
Control Units: 25
Fault count: 1
Control Units:
BC Door Electronics Rear Passenger Side
System description: TSG HBFS
Software number: 5Q0959395E
Software version: 0041
Hardware number: 5Q0959395B
Hardware version: 020
Serial number: 160715BGG09003
ODX name: EV_DCURearPasseMINKLO
ODX version: 006003
Faults:
No trouble codes found


52 Door Electronics Passenger Side
System description: TSG BFS
Software number: 5Q0959592E
Software version: 0041
Hardware number: 5Q0959592B
Hardware version: 020
Serial number: 240715BGN11071
ODX name: EV_DCUPasseSideEWMAXKLO
ODX version: 006003
Faults:
No trouble codes found


BB Door Electronics Rear Driver Side
System description: TSG HFS
Software number: 5Q0959395E
Software version: 0041
Hardware number: 5Q0959395B
Hardware version: 020
Serial number: 160715BGG09198
ODX name: EV_DCURearDriveMINKLO
ODX version: 006003
Faults:
No trouble codes found


42 Door Electronics Driver Side
System description: TSG FS
Software number: 5Q0959593E
Software version: 0041
Hardware number: 5Q0959593B
Hardware version: 020
Serial number: 070715BG70126A
ODX name: EV_DCUDriveSideEWMAXKLO
ODX version: 006003
Faults:
No trouble codes found


B7 Access Startsystem Interface
System description: VWKESSYMQB
Software number: 5Q0959435A
Software version: 0604
Hardware number: 5Q0959435
Hardware version: 021
Serial number: 0374846152
ODX name: EV_KessyHellaMQBAB
ODX version: 002011
Faults:
No trouble codes found


A9 Actuator For Structure-Borne Sound
System description: SAS-GEN 2
Software number: 8V0907159
Software version: 0012
Hardware number: 4H0907159A
Hardware version: H06
Serial number: 150701200470
ODX name: EV_SoundActuaGen2AU64X
ODX version: 003010
Faults:
No trouble codes found


A5 Front Sensors Driver Assistance System
System description: MQB_MFK
Software number: 5Q0980653G
Software version: 0060
Hardware number: 5Q0980653
Hardware version: H06
Serial number: 10000396302
ODX name: EV_MFKBoschAU370
ODX version: 001001
Faults:
No trouble codes found


76 Parking Assistance
System description: PARKHILFE PLA
Software number: 5Q0919298K
Software version: 0054
Hardware number: 5Q0919298
Hardware version: H12
Serial number: 39431519202080
ODX name: EV_EPHVA2CAU3700000
ODX version: 003021
Faults:
No trouble codes found


6C Camera System Rear View
System description: MQB RVC Mid
Software number: 5Q0907441A
Software version: 0140
Hardware number: 5Q0907441A
Hardware version: H07
ODX name: EV_2CamSysRearPASE
ODX version: 006016
Faults:
No trouble codes found


55 Headlight Regulation
System description: AFS-ECU
Software number: 7P6907357C
Software version: 0110
Hardware number: 7P6907357B
Hardware version: H01
Serial number: --------------
ODX name: EV_HeadlRegulAFSMQBMLB
ODX version: 001001
Faults:
No trouble codes found


44 Steering Assistance
System description: EPS_MQB_ZFLS
Software number: 3Q0909144H
Software version: 5061
Hardware number: 3Q0909144H
Hardware version: 505
ODX name: EV_SteerAssisMQB
ODX version: 012140
Faults:
No trouble codes found


3C Lane Change Assistant
System description: SWA Master
Software number: 5Q0907566A
Software version: 0080
Hardware number: 8T0907566B
Hardware version: H05
Serial number: 0372877068
ODX name: EV_LaneChangAssis
ODX version: 001020
Faults:
No trouble codes found


2B Steering Column Locking
System description: ELV-MQBA
Software number: 5Q0905861A
Software version: 0120
Hardware number: 5Q0905861A
Hardware version: H01
Serial number: 15000179151009
ODX name: EV_ELVMarquMQB
ODX version: 004111
Faults:
No trouble codes found


22 All Wheel Control
System description: Haldex4Motion
Software number: 0CQ907554D
Software version: 7082
Hardware number: 0CQ525130
Hardware version: H52
Serial number: HA1-00016.06.1500010195
ODX name: EV_AllWheelContrHA1VW37X
ODX version: 002013
Faults:
No trouble codes found


19 Gateway
System description: GW MQB High
Software number: 5Q0907530AF
Software version: 2223
Hardware number: 5Q0907530M
Hardware version: 212
Serial number: 21071510801419
ODX name: EV_GatewConti
ODX version: 013020
Faults:
No trouble codes found


17 Dash Board
System description: KOMBI
Software number: 8V0920872A
Software version: 6420
Hardware number: 8V0920872A
Hardware version: H03
ODX name: EV_DashBoardVDDMQBAB
ODX version: 009046
Faults:
No trouble codes found


16 Steering Column Electronics
System description: Lenks. Modul
Software number: 8V0953521GR
Software version: 0110
Hardware number: 5Q0953549E
Hardware version: 003
Serial number: 02081508490047
ODX name: EV_SMLSKLOMQB
ODX version: 017001
Faults:
No trouble codes found


15 Airbag
System description: AirbagVW20
Software number: 5Q0959655AB
Software version: 0388
Hardware number: 5Q0959655AB
Hardware version: 015
Serial number: 003MMR0ZEPYA
ODX name: EV_AirbaVW20SMEVW37X
ODX version: 002130
Faults:
No trouble codes found


14 Wheel Dampening Electronics
System description: DAEMPFUNGS-SG
Software number: 8V0907376E
Software version: 0072
Hardware number: 8V0907376E
Hardware version: H09
Serial number: 2807150098
ODX name: EV_AudiMagneRide
ODX version: 002003
Faults:
No trouble codes found


13 Adaptive Cruise Control
System description: ACC3
Software number: 5Q0907567N
Software version: 0400
Hardware number: 5Q0907567N
Hardware version: H10
Serial number: 10071503091323
ODX name: EV_ACCBoschMQB
ODX version: 001024
Faults:
No trouble codes found


09 Central Electrics
System description: BCM MQBAB H
Software number: 5Q0937084AS
Software version: 0175
Hardware number: 5Q0937084AN
Hardware version: H24
Serial number: 01061520305978
ODX name: EV_BCMMQB
ODX version: 015001
Faults:
No trouble codes found


08 Air Conditioning
System description: AC Automat
Software number: 8V0820043D
Software version: 0060
Hardware number: 8V0820043D
Hardware version: H13
Serial number: 00000000704210
ODX name: EV_AirCondiFrontVaAU37X
ODX version: 008020
Faults:
No trouble codes found


03 Brakes
System description: ESC
Software number: 3Q0907379AB
Software version: 0723
Hardware number: 3Q0907379G
Hardware version: H42
Serial number: 61775000002419
ODX name: EV_Brake1UDSContiMK100IPB
ODX version: 034036
Faults:
C102D00 - Tire pressure warning
Passive



02 Transmission
System description: DQ250-6A MQB
Software number: 0D9300012
Software version: 4912
Hardware number: 02E927770AQ
Hardware version: H53
Serial number: TFK01507151014�
ODX name: EV_TCMDQ250021
ODX version: 001001
Faults:
No trouble codes found


01 Engine
System description: 2.0l R4 TFSI
Software number: 8V0906259F
Software version: 0002
Hardware number: 06K907425B
Hardware version: H13
ODX name: EV_ECM20TFS0208V0906259F
ODX version: 001004
Faults:
No trouble codes found

Mileage: 32215 km
Date: 2019-10-14 16:23

---------------------------------------------------------------
Long coding
Control unit: 52 Door Electronics Passenger Side
Old value:
005D12204101040000001003
New value:
005D12204D01040000001003
Mileage: 32215 km
Date: 2019-10-14 16:07

---------------------------------------------------------------
App
Name: CH/LH Lights
Old value: OFF
New value: ON
Mileage: 32215 km
Date: 2019-10-14 15:33

---------------------------------------------------------------
App
Name: Scandinavian DRLs
Old value: OFF
New value: ON
Mileage: 32215 km
Date: 2019-10-14 15:30

---------------------------------------------------------------
App
Name: DRL settings in head unit
Old value: OFF
New value: ON
Mileage: 32215 km
Date: 2019-10-14 15:27

---------------------------------------------------------------
App
Name: XDS interaction
Old value: Standard
New value: Medium
Mileage: 32215 km
Date: 2019-10-14 15:25

---------------------------------------------------------------
App
Name: Central lock with IGN
Old value: OFF
New value: ON
Mileage: 32215 km
Date: 2019-10-14 15:25

---------------------------------------------------------------
App
Name: Start/Stop system deactivation
Old value: Start-Stop active
New value: Start-Stop not active
Mileage: 32215 km
Date: 2019-10-14 15:24

---------------------------------------------------------------
App
Name: Oil temperature in DIS
Old value: OFF
New value: ON
Mileage: 32215 km
Date: 2019-10-14 15:23

---------------------------------------------------------------
App
Name: Auto lock
Old value: OFF
New value: ON
Mileage: 32215 km
Date: 2019-10-14 15:22

---------------------------------------------------------------
App
Name: Mirror Dip

Old value: Original
New value: ON
Mileage: 32215 km
Date: 2019-10-14 15:

[brandons3]

Oct 15, 2019 22:17:03 GMT dv52 (Australia) said:

^^^brandon: Hi. On your first post - simply using the long-coding string from someone else's Dashboard module for a 2016 S3 won't work because the values vary greatly depending on the country of sale and factory fitted options.

In your last post - can you provide a copy of the before and after values that you changed from your history report? And, if you have any error messages, post them as well.

Don

After this my information control unit control wasn’t able to access anymore in control module fault says ‘data is missing message’ and central electrics will sometimes come up with a fault that says ‘control module incorrectly coded’

[brandons3]

Oct 15, 2019 16:41:36 GMT Thirsty said:

Please check your coding history to get the old value

Can u please look at my control unit history and if u can see where the problem is please?

[dv52 (Australia)]

Oct 21, 2019 23:20:33 GMT brandons3 said:

Can u please look at my control unit history and if u can see where the problem is please?

OK - so here is the ONLY record for the Dashboard module @ address hex17 from your history file above:

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

Long coding
Control unit: 17 Dash Board
Old value:
278D181A7F9800080181E8001000000000000000
New value:
278D181A7F9800080181EA001000000000000000
Mileage: 32215 km
Date: 2019-10-14 16:24
------------------------------------------------------------------------------

The Old value is as shown in highlight

And here's a more readable version of the change that was made on 14th October 2019 @ 16:24hrs:


Name old module code   new module code
Byte Hex Binary        Hex Binary
0 27 00100111 27 00100111
1 8D 10001101 8D 10001101
2 18 00011000 18 00011000
3 1A 00011010 1A 00011010
4 7F 01111111 7F 01111111
5 98 10011000 98 10011000
6 00 00000000 00 00000000
7 08 00001000 08 00001000
8 01 00000001 01 00000001
9 81 10000001 81 10000001
10 E8 11101000 EA 11101010
11 00 00000000 00 00000000
12 10 00010000 10 00010000
13 00 00000000 00 00000000
14 00 00000000 00 00000000
15 00 00000000 00 00000000
16 00 00000000 00 00000000
17 00 00000000 00 00000000
18 00 00000000 00 00000000
19 00 00000000 00 00000000



So  Byte 10, Bit 1 was set which is the software switch for enabling the oil temperature display. Given that you used the Oil temperature in DIS APP earlier in the day @ 15:23 hrs - I suspect that the 16:24 hrs record simply confirms the change that the APP made.

Doesn't seem to be a radical change - what precisely did you mean by "that [i.e. Dashboard] control unit isn't working properly" in your first post?

Don

[brandons3]

Oct 15, 2019 22:17:03 GMT dv52 (Australia) said:

^^^brandon: Hi. On your first post - simply using the long-coding string from someone else's Dashboard module for a 2016 S3 won't work because the values vary greatly depending on the country of sale and factory fitted options.

In your last post - can you provide a copy of the before and after values that you changed from your history report? And, if you have any error messages, post them as well.

Don

I meant the first fault control unit: 5F Information Control Unit doesn’t show up and isn’t there anymore in the control units to long code and access. I didn’t do anything drastic by changing codes just bought some apps.

[brandons3]

Oct 22, 2019 8:34:42 GMT dv52 (Australia) said:

Oct 21, 2019 23:20:33 GMT brandons3 said:

Can u please look at my control unit history and if u can see where the problem is please?

OK - so here is the ONLY record for the Dashboard module @ address hex17 from your history file above:

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

Long coding
Control unit: 17 Dash Board
Old value:
278D181A7F9800080181E8001000000000000000
New value:
278D181A7F9800080181EA001000000000000000
Mileage: 32215 km
Date: 2019-10-14 16:24
------------------------------------------------------------------------------

The Old value is as shown in highlight

And here's a more readable version of the change that was made on 14th October 2019 @ 16:24hrs:


Name old module code   new module code
Byte Hex Binary        Hex Binary
0 27 00100111 27 00100111
1 8D 10001101 8D 10001101
2 18 00011000 18 00011000
3 1A 00011010 1A 00011010
4 7F 01111111 7F 01111111
5 98 10011000 98 10011000
6 00 00000000 00 00000000
7 08 00001000 08 00001000
8 01 00000001 01 00000001
9 81 10000001 81 10000001
10 E8 11101000 EA 11101010
11 00 00000000 00 00000000
12 10 00010000 10 00010000
13 00 00000000 00 00000000
14 00 00000000 00 00000000
15 00 00000000 00 00000000
16 00 00000000 00 00000000
17 00 00000000 00 00000000
18 00 00000000 00 00000000
19 00 00000000 00 00000000



So  Byte 10, Bit 1 was set which is the software switch for enabling the oil temperature display. Given that you used the Oil temperature in DIS APP earlier in the day @ 15:23 hrs - I suspect that the 16:24 hrs record simply confirms the change that the APP made.

Doesn't seem to be a radical change - what precisely did you mean by "that [i.e. Dashboard] control unit isn't working properly" in your first post?

Don

What do u mean by hex 17?

[brandons3]

Oct 22, 2019 8:34:42 GMT dv52 (Australia) said:

Oct 21, 2019 23:20:33 GMT brandons3 said:

Can u please look at my control unit history and if u can see where the problem is please?

OK - so here is the ONLY record for the Dashboard module @ address hex17 from your history file above:

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

Long coding
Control unit: 17 Dash Board
Old value:
278D181A7F9800080181E8001000000000000000
New value:
278D181A7F9800080181EA001000000000000000
Mileage: 32215 km
Date: 2019-10-14 16:24
------------------------------------------------------------------------------

The Old value is as shown in highlight

And here's a more readable version of the change that was made on 14th October 2019 @ 16:24hrs:


Name old module code   new module code
Byte Hex Binary        Hex Binary
0 27 00100111 27 00100111
1 8D 10001101 8D 10001101
2 18 00011000 18 00011000
3 1A 00011010 1A 00011010
4 7F 01111111 7F 01111111
5 98 10011000 98 10011000
6 00 00000000 00 00000000
7 08 00001000 08 00001000
8 01 00000001 01 00000001
9 81 10000001 81 10000001
10 E8 11101000 EA 11101010
11 00 00000000 00 00000000
12 10 00010000 10 00010000
13 00 00000000 00 00000000
14 00 00000000 00 00000000
15 00 00000000 00 00000000
16 00 00000000 00 00000000
17 00 00000000 00 00000000
18 00 00000000 00 00000000
19 00 00000000 00 00000000



So  Byte 10, Bit 1 was set which is the software switch for enabling the oil temperature display. Given that you used the Oil temperature in DIS APP earlier in the day @ 15:23 hrs - I suspect that the 16:24 hrs record simply confirms the change that the APP made.

Doesn't seem to be a radical change - what precisely did you mean by "that [i.e. Dashboard] control unit isn't working properly" in your first post?

Don

I meant the first fault control unit: Hex 5F Information Control Unit doesn’t show up and isn’t there anymore in the control units to long code and access and when I click what the fault is for it says ‘databus missing message’. I didn’t do anything drastic by changing codes just bought some apps.

[dv52 (Australia)]

Oct 22, 2019 14:33:38 GMT brandons3 said:

I meant the first fault control unit: Hex 5F Information Control Unit doesn’t show up and isn’t there anymore in the control units to long code and access and when I click what the fault is for it says ‘databus missing message’. I didn’t do anything drastic by changing codes just bought some apps.

hmm......... OK - my response "hex17 module" was related to your first post about your Dashboard module problem. That's why I analyzed the long code changes in the hex 17 module - because you said that the problem was in that module,

It's not clear from the history report that you included why there is a fault in the hex 5F module (none of the records in the History report refer to changes to the hex 5F module)

When you say "Hex 5F Information Control Unit doesn’t show up" - do you mean that it is not included in the module list (as below)?

Don

[brandons3]

Oct 22, 2019 20:44:45 GMT dv52 (Australia) said:

Oct 22, 2019 14:33:38 GMT brandons3 said:

I meant the first fault control unit: Hex 5F Information Control Unit doesn’t show up and isn’t there anymore in the control units to long code and access and when I click what the fault is for it says ‘databus missing message’. I didn’t do anything drastic by changing codes just bought some apps.

hmm......... OK - my response "hex17 module" was related to your first post about your Dashboard module problem. That's why I analyzed the long code changes in the hex 17 module - because you said that the problem was in that module,

It's not clear from the history report that you included why there is a fault in the hex 5F module (none of the records in the History report refer to changes to the hex 5F module)

When you say "Hex 5F Information Control Unit doesn’t show up" - do you mean that it is not included in the module list (as below)?

Don

Yes it’s not included in the module list. And when I do try to add it after I do a scan the Hex gateway removes it as u see in my history

[brandons3]

Oct 22, 2019 20:44:45 GMT dv52 (Australia) said:

Oct 22, 2019 14:33:38 GMT brandons3 said:

I meant the first fault control unit: Hex 5F Information Control Unit doesn’t show up and isn’t there anymore in the control units to long code and access and when I click what the fault is for it says ‘databus missing message’. I didn’t do anything drastic by changing codes just bought some apps.

hmm......... OK - my response "hex17 module" was related to your first post about your Dashboard module problem. That's why I analyzed the long code changes in the hex 17 module - because you said that the problem was in that module,

It's not clear from the history report that you included why there is a fault in the hex 5F module (none of the records in the History report refer to changes to the hex 5F module)

When you say "Hex 5F Information Control Unit doesn’t show up" - do you mean that it is not included in the module list (as below)?

Don

-------------------------------------------------------------
Fault
Control unit: 5F Information Control Unit
Active faults: 0
Inactive faults: 1
System description: MU-H-N-RW
Software number: 8V0035045G
Software version: 0398
Hardware number: 8V0035045C
Hardware version: H45
Serial number: A307E0F7550633
ODX name: EV_MUHig6C3HBAS
ODX version: 001040
Faults:
U112100 - Databus missing message
Passive


Mileage: 32276 km
Date: 2019-10-19 00:30

---------------------------------------------------------------
Gateway coding
Removed:
(56) Radio
(0E) Media Player Position 1
(07) Display Control Unit
(8B) Adaptive Cruise Control 2
Mileage: 32276 km
Date: 2019-10-19 00:30

---------------------------------------------------------------
Gateway coding
Added:
(0E) Media Player Position 1
(07) Display Control Unit
(8B) Adaptive Cruise Control 2
(56) Radio
Mileage: 32276 km
Date: 2019-10-19 00:30

[brandons3]

Oct 23, 2019 9:12:34 GMT brandons3 said:

Oct 22, 2019 20:44:45 GMT dv52 (Australia) said:

hmm......... OK - my response "hex17 module" was related to your first post about your Dashboard module problem. That's why I analyzed the long code changes in the hex 17 module - because you said that the problem was in that module,

It's not clear from the history report that you included why there is a fault in the hex 5F module (none of the records in the History report refer to changes to the hex 5F module)

When you say "Hex 5F Information Control Unit doesn’t show up" - do you mean that it is not included in the module list (as below)?

Don

-------------------------------------------------------------
Fault
Control unit: 5F Information Control Unit
Active faults: 0
Inactive faults: 1
System description: MU-H-N-RW
Software number: 8V0035045G
Software version: 0398
Hardware number: 8V0035045C
Hardware version: H45
Serial number: A307E0F7550633
ODX name: EV_MUHig6C3HBAS
ODX version: 001040
Faults:
U112100 - Databus missing message
Passive


Mileage: 32276 km
Date: 2019-10-19 00:30

---------------------------------------------------------------
Gateway coding
Removed:
(56) Radio
(0E) Media Player Position 1
(07) Display Control Unit
(8B) Adaptive Cruise Control 2
Mileage: 32276 km
Date: 2019-10-19 00:30

---------------------------------------------------------------
Gateway coding
Added:
(0E) Media Player Position 1
(07) Display Control Unit
(8B) Adaptive Cruise Control 2
(56) Radio
Mileage: 32276 km
Date: 2019-10-19 00:30

When I click the red circle 🔴 at the bottom to see what’s added Hex 5F information control unit is ticked but it’s not showing up in the module lists. Also my central electrics Hex 09 says faults: U101400 - control module incorrectly coded

OBDeleven vehicle history log

Date: 2019-10-23 20:58

VIN: WAUZZZ8V5G1029156
Car: Audi S3
Year: 2016
Body type: Saloon
Engine: CJXF 210 kW (286 HP) 2.0 l
Mileage: 32322 KM

---------------------------------------------------------------
Fault
Control unit: 09 Central Electrics
Active faults: 0
Inactive faults: 1
System description: BCM MQBAB H
Software number: 5Q0937084AS
Software version: 0175
Hardware number: 5Q0937084AN
Hardware version: H24
Serial number: 01061520305978
ODX name: EV_BCMMQB
ODX version: 015001
Faults:
U101400 - Control module incorrectly coded
Active


Mileage: 32336 km
Date: 2019-10-23 20:51