Problem whit cluster and other

momo94tn
New Member

Posts: 17

Problem whit cluster and other Sept 22, 2024 18:39:08 GMT via mobile

Quote

Post by momo94tn on Sept 22, 2024 18:39:08 GMT

Hello everyone, I have some errors in the car, such as the two errors P169800 on the steering wheel controls because I have a customized steering wheel with modified buttons, while U112100 related to the air conditioning concerns the rain sensor that I temporarily installed without a humidity sensor. U10F500 should be linked to the humidity sensor, and the dashboard errors like U200041, I think, are related to the fact that I had purchased a digital dashboard from China where my cluster's logic board had to be inserted, and underneath there was another cluster of the digital dashboard that didn't require any programming; it was plug-and-play. Recently, the car won't start anymore, so I had to reinstall the original analog cluster of my Golf 7. The error can't be cleared because it's static, and even the mechanic couldn't perform diagnostics related to the cluster because the cluster itself wouldn't allow it. U006500, the error in the gateway, I don't know what it's related to. If anyone can help me solve it, I would be grateful. I would like to mention that the speaker of my cluster works because I can hear the sounds, and there are no visible errors in the cluster; I only see the errors in OBDeleven.

OBDeleven data log

Date: 2024-09-22 20:38

VIN: WVWZZZAUZEW084758
Car: Volkswagen Golf
Year: 2014
Body type: 5-dr hatchback
Engine: CRBC
Mileage: 134815 KM

---------------------------------------------------------------
01 Engine

System description: R4 2,0L EDC
Software number: 04L906021DS
Software version: 5514
Hardware number: 04L907309D
Hardware version: H22
ODX name: EV_ECM20TDI01104L906021DS
ODX version: 002009
Long coding: 01190012032405082000

Trouble codes:
P169800 - Steering Column Electronics Read out DTC
Intermittent
U112300 - Databus error value received
Intermittent

---------------------------------------------------------------
03 Brakes

System description: ESC
Software number: 5Q0907379CK
Software version: 0472
Hardware number: 5Q0907379G
Hardware version: H31
Serial number: 62153000000BF0
ODX name: EV_Brake1UDSContiMK100IPB
ODX version: 033001
Long coding: 01FA62A124280970037E060541CB2980462490C0608294F300600074C002

Trouble codes:
No trouble codes found

---------------------------------------------------------------
08 Air Conditioning

System description: Climatronic
Software number: 5G0907044T
Software version: 0705
Hardware number: 5G0907044T
Hardware version: H02
ODX name: EV_ACClimaBHBVW37X
ODX version: 003018
Long coding: 00020104202100011005004000101000

Trouble codes:
U112100 - Databus missing message
static
Date: 2024-08-20 22:58:07
Mileage: 132528 km
Priority: 6
Malfunction frequency counter: 1
Unlearning counter: 247

---------------------------------------------------------------
09 Central Electrics

System description: BCM MQBAB M
Software number: 5Q0937084S
Software version: 0112
Hardware number: 5Q0937084S
Hardware version: H14
Serial number: 00011321800387
ODX name: EV_BCMCONTI
ODX version: 011001
Long coding: 00000842C24102FB4BE4400000040308100A000000000000000000000000

Subsystems:
System description: WWS 130727
Software version: 0551
Hardware version: 042
Serial number: 130807161318
Long coding: 0E4DDD

System description: RLS
Software version: 0105
Hardware version: 050
Serial number: S3Y18M05D23H20M54S44
Long coding: 008F77

Trouble codes:
U10F500 - Humidity sensor No communication
static
Date: 2024-09-23 02:11:13
Mileage: 134815 km
Priority: 2
Malfunction frequency counter: 1
Unlearning counter: 47
Terminal 15 status: On
Terminal 50 status: Off
Voltage: 12.1 V
Outside air temperature: 19.0 °C
Status Bremslichtschalter (HW): Off
Status Bremslichtschalter (CAN): Off
Off: operated
Parking light: not activated
Automatic high beam assist: not activated
Low beam: not activated
Parking light left: not activated
Parking light right: not activated
Letzte Weckursache/ Werte [00;2E]: gültiges Funktelegramm
CAN-Bus_aktiv: On

---------------------------------------------------------------
15 Airbag

System description: AirbagVW20
Software number: 5Q0959655C
Software version: 0361
Hardware number: 5Q0959655C
Hardware version: 011
Serial number: 003F5R06Y4DL
ODX name: EV_AirbaVW20SMEVW37X
ODX version: 002126
Long coding: 98CCC000000000005C0000CF004800000065

Subsystems:
System description: SideSensor_Df
Software version: 0887
Hardware version: 001
Serial number: 35767000000878815D0Z
Long coding: 2D2D2D

System description: SideSensor_Pf
Software version: 0887
Hardware version: 001
Serial number: 35867000000BF66C5D0B
Long coding: 2D2D2D

System description: SideSensor_Dr
Software version: 6149
Hardware version: 001
Serial number: 3516502C31074481E1E5
Long coding: 2D2D2D

System description: SideSensor_Pr
Software version: 6149
Hardware version: 001
Serial number: 3526502C51074481A2D4
Long coding: 2D2D2D

System description: FrontSensor_D
Software version: 6149
Hardware version: 001
Serial number: 3556502B30D3608330F5
Long coding: 2D2D2D

Trouble codes:
No trouble codes found

---------------------------------------------------------------
16 Steering Column

System description: Lenks. Modul
Software number: 5Q0953507AA
Software version: 0070
Hardware number: 5Q0953549
Hardware version: 007
Serial number: 23071304221064
ODX name: EV_SMLSKLOMQB
ODX version: 009001
Long coding: 0400

Trouble codes:
No trouble codes found

---------------------------------------------------------------
17 Dashboard

System description: KOMBI
Software number: 5G0920861A
Software version: 3390
Hardware number: 5G0920861A
Hardware version: 204
ODX name: EV_DashBoardJCIMQBAB
ODX version: 008011
Long coding: 07A419002380000C00083A00040000

Trouble codes:
B200041 - Ctrl. module faulty
static
Date: 2024-02-20 00:00:00
Mileage: 119918 km
Priority: 2
Malfunction frequency counter: 1
Unlearning counter: 255
U111000 - Function restriction due to communication interruption
Intermittent
Date: 2024-09-23 02:10:59
Mileage: 134815 km
Priority: 6
Malfunction frequency counter: 6
Unlearning counter: 87
U111000 - Function restriction due to communication interruption
Intermittent
Date: 2024-09-23 02:11:00
Mileage: 134815 km
Priority: 6
Malfunction frequency counter: 5
Unlearning counter: 87

---------------------------------------------------------------
19 Gateway

System description: GW MQB Mid
Software number: 5Q0907530L
Software version: 1144
Hardware number: 5Q0907530E
Hardware version: 124
Serial number: 0000905429
ODX name: EV_GatewLear
ODX version: 009013
Long coding: 030100040B087300EF000248080F00010001000000000000000000000000

Subsystems:
System description: J367-BDMHella
Software version: 8042
Hardware version: H03
Serial number: 1557131103

System description: E221__MFL-DC1
Software version: 0101
Hardware version: H10
Serial number: 29150001071680055216
Long coding: 29FFFF

Trouble codes:
B114E96 - tiptronic downshift button on steering wheel Internal malfunction
static
Date: 2024-08-20 22:58:22
Mileage: 132529 km
Priority: 2
Malfunction frequency counter: 206
Unlearning counter: 47
Supply voltage, terminal 30: 12.9 V
Terminal 15: On
B114F96 - tiptronic upshift button on steering wheel Internal malfunction
static
Date: 2024-08-20 22:58:22
Mileage: 132529 km
Priority: 2
Malfunction frequency counter: 206
Unlearning counter: 47
Supply voltage, terminal 30: 12.9 V
Terminal 15: On
U006500 - Vehicle Communication Bus E Performance
Intermittent
Date: 2024-08-20 23:26:24
Mileage: 132542 km
Priority: 2
Malfunction frequency counter: 207
Unlearning counter: 87
Supply voltage, terminal 30: 12.3 V
Terminal 15: Off

---------------------------------------------------------------
42 Driver Door

System description: TSG FS
Software number: 5Q0959593A
Software version: 0006
Hardware number: 5Q0959593
Hardware version: 012
Serial number: 18071306070024
ODX name: EV_DCUDriveSideEWMAXKLO
ODX version: 006003
Long coding: 003B0320D000040000001000

Subsystems:
System description: Fond FHSG DRV
Software version: 0002
Hardware version: 007
Serial number: 00000000000002325504
Long coding: 010000

Trouble codes:
No trouble codes found

---------------------------------------------------------------
44 Steering Assistance

System description: EPS_MQB_ZFLS
Software number: 5Q0909144L
Software version: 1021
Hardware number: 5Q0909144M
Hardware version: 127
ODX name: EV_SteerAssisMQB
ODX version: 008022
Long coding: 01

Trouble codes:
No trouble codes found

---------------------------------------------------------------
52 Passenger Door

System description: TSG BFS
Software number: 5Q0959592A
Software version: 0006
Hardware number: 5Q0959592
Hardware version: 012
Serial number: 30071304080325
ODX name: EV_DCUPasseSideEWMAXKLO
ODX version: 006003
Long coding: 003B0120DE00040000801000

Subsystems:
System description: Fond FHSG PSG
Software version: 0002
Hardware version: 007
Serial number: 00000000000002329511
Long coding: 090000

Trouble codes:
No trouble codes found

---------------------------------------------------------------
5F Multimedia

System description: MU-S--ER
Software number: 5G0035819A
Software version: 0421
Hardware number: 5G0035819A
Hardware version: 040
Serial number: V1C00808131329
ODX name: EV_MUStd4CPASE
ODX version: 002039
Long coding: 02730000FF00000011110001000800001F0100840100010001

Trouble codes:
No trouble codes found

---------------------------------------------------------------
76 Parking Assistance

System description: PARKHILFE 8K
Software number: 5Q0919294C
Software version: 0033
Hardware number: 5Q0919294A
Hardware version: H02
Serial number: 94231321701793
ODX name: EV_EPHVA18AU3700000
ODX version: 002019
Long coding: 0031051001

Trouble codes:
No trouble codes found

dv52 (Australia)
Moderator

Posts: 6,054

Problem whit cluster and other Sept 22, 2024 21:34:32 GMT

Quote

Post by dv52 (Australia) on Sept 22, 2024 21:34:32 GMT

momo94tn : Hi.

hmm....................I'm not sure that I agree that the dashboard module error B200041 - Ctrl. module faulty "should be linked to the humidity sensor". The date of this error is much earlier and it seems to be unconnected to the humidity sensor. From my reading of your SCAN, B200041 error is stand alone - and I suspect that the CAN network is unhappy with an internal problem in the 17 module!

As for the "U006500, the error in the gateway" - this is the pertinent portion of CAN network for this car:

The Gateway module in my picture is J533 - notice that the module has the term "Master".

Also notice in my picture that while the module for the "steering wheel controls" (which is J453) is routed via the module that in your SCAN is called 16 Steering Column (which is J527) - J453 is actually connected to the Gateway module.

Unlike previous model Golfs, on MQB platform cars like the mk7/mk7.5 - the steering wheel buttons are controlled via LIN protocol. LIN= Local Interconnect Network. It's a low-speed, single wire communications protocol and in this case, the Gateway module is the LIN master.

The reason why I have included the LIN discussion above is so you can hopefully see why the U006500 error is telling you that the Gateway module is unhappy with the UP/Down steering-wheel paddle-shifters. The U006500 - Vehicle Communication Bus E Performance error appears the related to the paddles.

Don

Last Edit: Sept 22, 2024 21:36:22 GMT by dv52 (Australia)

Please don't ask questions about car coding/repair via the forum "Message" function. The better place for such dialogue is in the forum proper. That way, the wider expertise of the entire forum community can be applied to solve your problem - thank you

momo94tn
New Member

Posts: 17

Problem whit cluster and other Sept 23, 2024 10:46:00 GMT via mobile

Quote

Post by momo94tn on Sept 23, 2024 10:46:00 GMT

Sept 22, 2024 21:34:32 GMT dv52 (Australia) said:

momo94tn : Hi.

hmm....................I'm not sure that I agree that the dashboard module error B200041 - Ctrl. module faulty "should be linked to the humidity sensor". The date of this error is much earlier and it seems to be unconnected to the humidity sensor. From my reading of your SCAN, B200041 error is stand alone - and I suspect that the CAN network is unhappy with an internal problem in the 17 module!

As for the "U006500, the error in the gateway" - this is the pertinent portion of CAN network for this car:

The Gateway module in my picture is J533 - notice that the module has the term "Master".

Also notice in my picture that while the module for the "steering wheel controls" (which is J453) is routed via the module that in your SCAN is called 16 Steering Column (which is J527) - J453 is actually connected to the Gateway module.

Unlike previous model Golfs, on MQB platform cars like the mk7/mk7.5 - the steering wheel buttons are controlled via LIN protocol. LIN= Local Interconnect Network. It's a low-speed, single wire communications protocol and in this case, the Gateway module is the LIN master.

The reason why I have included the LIN discussion above is so you can hopefully see why the U006500 error is telling you that the Gateway module is unhappy with the UP/Down steering-wheel paddle-shifters. The U006500 - Vehicle Communication Bus E Performance error appears the related to the paddles.

Don

The error B200041 is almost certainly linked to the cluster and not to humidity. This error is problematic because I don't know if it's responsible for the issues I was having with the virtual cockpit (LCD digital cluster) since the seller tested it for three days before shipping it to Italy. That said, I searched the entire web regarding this static error and the only solution suggested was the speaker, but my speaker works fine. Finding a solution for the error B200041 is like a lottery because, due to this error, diagnostics on the dashboard, like the analog needles and other diagnostics performed by the mechanic, can't be done. I'm desperate.

dv52 (Australia)
Moderator

Posts: 6,054

Problem whit cluster and other Sept 23, 2024 22:54:46 GMT momo94tn likes this

Quote

Post by dv52 (Australia) on Sept 23, 2024 22:54:46 GMT

momo94tn :hmm........ yes, I empathize with your desperation! Maybe the following will help?

From your brief words - it appears that the module motherboard has undergone a number of different changes (I'm guessing both physical and software based).

Perhaps a clue regarding the cause for the B200041 fault might be gleaned from how VCDS describes the error? My reason for looking at VCDS is because the fault data their SCAN report is far more informative (IMO, of course)!

So, here is an extract from VCDS for the dashboard in a Tiguan 2013 which includes 2 x errors that OBD11 describes as B200041.

-------------------------------------------------------------------------------
Address 17: Instruments (J285) Labels:| 5K0-920-xxx-17.clb-SRI1
Part No SW: 5N0 920 883 A HW: 5N0 920 883 A
Component: KOMBI H05 0505
Serial number: 00000000000000
Coding: 111F01
Shop #: WSC 01357 011 00200
ASAM Dataset: EV_Kombi_UDS_VDD_RM09 A04716
ROD: EV_Kombi_UDS_VDD_RM09_004_VW32.rod
VCID: 32601FCD650E330105-8066

10485825 - Internal Control Module Memory Check Sum Error
B2000 41 [10001001] - General Checksum Failure
MIL ON - Confirmed - Tested Since Memory Clear
Freeze Frame:
Fault Priority: 2
Fault Frequency: 1

10485824 - Internal Control Module Memory Check Sum Error
B2000 41 [10001001] - General Checksum Failure
MIL ON - Confirmed - Tested Since Memory Clear
Freeze Frame:
Fault Priority: 2
Fault Frequency: 1

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

In VCDS speak, the 17 Dashboard module is called Address 17: Instruments module and of course the details of the module in my example above will be different to the module in your car. Note that VCDS reports the error as B2000 41 whereas OBD11 uses B200041

Notice in my extract that VCDS reports B2000 41 error as a General Checksum Failure, which is a more specific descriptor than OBD11's words "Ctrl. module faulty"

Not sure if you are familiar with the concept of "Checksum" - but it's a commonly used diagnostic facility for testing the integrity of the information in a file. A checksum is a string of numbers that’s used to “check” whether data or a file has been altered during storage or transmission. Checksums often accompany software downloaded from another source so that the module can ensure the data in the downloaded file was not modified in transit.

I don't understand your words "since the seller tested it [the Dashboard module] for three days before shipping it to Italy" - did the seller download new software into the Dashboard/Instruments module?

Anyway and based on VCDS speak, the error is telling you that for some reason the software in the Dashboard/Instruments module has been corrupted. I have no idea why - but you have a better understanding of the history of this module - so you can probably make more sense of why!

So, and again using the VCDS reasoning, the normal way to solve Checksum errors is by re-flashing the module software. Alas OBD11 can not do this!

Don

Last Edit: Sept 23, 2024 23:11:40 GMT by dv52 (Australia)

Please don't ask questions about car coding/repair via the forum "Message" function. The better place for such dialogue is in the forum proper. That way, the wider expertise of the entire forum community can be applied to solve your problem - thank you

momo94tn
New Member

Posts: 17

Problem whit cluster and other Sept 24, 2024 0:19:38 GMT via mobile

Quote

Post by momo94tn on Sept 24, 2024 0:19:38 GMT

Thank you very much for your comprehensive answers, basically this virtual cockpit I bought is plug and play it just needed to be detached the logic board from my analog cluster and added to the Chinese one, it was ready to use without any further modification I just added some wiring and connected my logic board to the new digital cluster. The problems started from here and I think that b200041 as well. Slowly it started to give me more and more communication problems when I was doing the analysis with obdeleven I had more and more communication errors in the various buses until one day the car would not turn on anymore because precisely the digital cockpit would not turn on then I put the original analog back on and it always starts perfectly with no errors.. My fear that precisely the digital cluster has maybe written in the memory and then as you say a clean flash should be done so as to restore the operation. Do I have to go to Volkswagen or even one experienced in ECUs and programming and what exactly should I tell them? Unfortunately I don't have the vcds device so I wouldn't know how to do the analysis

Last Edit: Sept 24, 2024 0:51:26 GMT by dv52 (Australia)

dv52 (Australia)
Moderator

Posts: 6,054

Problem whit cluster and other Sept 24, 2024 1:09:05 GMT momo94tn likes this

Quote

Post by dv52 (Australia) on Sept 24, 2024 1:09:05 GMT

Sept 24, 2024 0:19:38 GMT momo94tn said:

Do I have to go to Volkswagen or even one experienced in ECUs and programming and what exactly should I tell them? Unfortunately I don't have the vcds device so I wouldn't know how to do the analysis

momo94tn :It doesn't matter that you "don't have the vcds device" because VCDS won't be able to re-flash the module either!

In answer to your question above, yes - you will need to go to a dealer because the Dashboard module also contains the immobilizer for the car (ignition key registration) and stuff like the odometer reading for the vehicle needs to be retained during the re-flash process.

However, please understand that my analysis about the checksum being the reason for your error is a guess. The fact is that the motherboard from the original Dashboard module has been subjected to both physical and software stresses from the digital dashboard module. I have no idea what effect the non-OEM equipment has had on the VW module - so no guarantee that this is definitely the cause.

Don

Last Edit: Sept 24, 2024 1:09:45 GMT by dv52 (Australia)

Please don't ask questions about car coding/repair via the forum "Message" function. The better place for such dialogue is in the forum proper. That way, the wider expertise of the entire forum community can be applied to solve your problem - thank you

momo94tn
New Member

Posts: 17

Problem whit cluster and other Sept 24, 2024 10:34:24 GMT via mobile

Quote

Post by momo94tn on Sept 24, 2024 10:34:24 GMT

Sept 24, 2024 1:09:05 GMT dv52 (Australia) said:

Sept 24, 2024 0:19:38 GMT momo94tn said:

Do I have to go to Volkswagen or even one experienced in ECUs and programming and what exactly should I tell them? Unfortunately I don't have the vcds device so I wouldn't know how to do the analysis

momo94tn :It doesn't matter that you "don't have the vcds device" because VCDS won't be able to re-flash the module either!

In answer to your question above, yes - you will need to go to a dealer because the Dashboard module also contains the immobilizer for the car (ignition key registration) and stuff like the odometer reading for the vehicle needs to be retained during the re-flash process.

However, please understand that my analysis about the checksum being the reason for your error is a guess. The fact is that the motherboard from the original Dashboard module has been subjected to both physical and software stresses from the digital dashboard module. I have no idea what effect the non-OEM equipment has had on the VW module - so no guarantee that this is definitely the cause.

Don

"Thank you for the response. I would like to try first with VCDS; do you know where I can purchase it in Europe? This way, I can better analyze the issue and possibly understand what the real problem is."

whataboutthis Ultimate Member Posts: 1,163	Problem whit cluster and other Sept 24, 2024 22:15:14 GMT Quote Select Post Deselect Post Link to Post Back to Top Post by whataboutthis on Sept 24, 2024 22:15:14 GMT Sorry to jump in and not being rude but took me 5 seconds to fine this www.ross-tech.com/distributors.php
	Check out www.vwvortex.com/threads/obd11-obd-eleven-outstanding-bug-list.9493017/ for a good list of outstanding issues and www.vwvortex.com/threads/obd11-hidden-features.9487991/ for hidden features

dv52 (Australia)
Moderator

Posts: 6,054

Problem whit cluster and other Sept 24, 2024 22:50:58 GMT whataboutthis likes this

Quote

Post by dv52 (Australia) on Sept 24, 2024 22:50:58 GMT

momo94tn

HMM..........obviously you have every right to spend your money any way you see fit and I would not presume to interfere in your decision making process!

But, before proceeding - I make the following one-time only proposal for your consideration:

The cheapest VCDS product is the 3 x VIN limit HEX-V2, which costs $199 USD (plus postage).
My offer is that you do NOT buy a VCDS device and instead, keep half of this cost and send me the remaining $100?

To help in deciding whether to accept my offer - I provide a copy of the simple sentence below from Uwe Ross (the CEO of Ross-Tech) regarding this matter:

"You can't flash modules with VCDS" - these words come from HERE

Of course I'm kidding - I suggest that you keep the entire $199 USD (plus postage)

Nevertheless, if you must spend your hard earned money in this manner, the official distributor-list can be found HERE

Don

EDIT: thanks whataboutthis

Last Edit: Sept 24, 2024 22:54:57 GMT by dv52 (Australia)

Please don't ask questions about car coding/repair via the forum "Message" function. The better place for such dialogue is in the forum proper. That way, the wider expertise of the entire forum community can be applied to solve your problem - thank you