|
|
Post by coons88 on Sept 7, 2023 8:23:13 GMT
Hi guys
--------
This was resolved. Solution posted further down the thread.
--------
Long time user first time poster.
Yesterday when I got in my car and turned it on I got an error on the dash "Instrument Cluster Error. Please visit workshop". It then leaves an orange [!] light and the word 'Error' where the trip milage displays, and I have also got a "Front assist unavailable" error which I assume is linked. Otherwise the car and dashboard seems to function and drive fine.
Video here of the error:
The code doesn't clear on OBDeleven, and there is very little information on the internet about the error. I have messaged that company in the video to see if they can share some insight.
Has anyone come across this error or can share any thoughts or insight?
Thank you!
|
|
|
|
Post by dv52 (Australia) on Sept 7, 2023 23:08:24 GMT
Post-up a copy of the SCAN report for this car so we can see the exact error details. Also, has there been any coding changes made to this car lately? Go to History and then follow the instructions below. After you receive the email that you sent to yourself from the last screenshot below - copy and paste the contents in a new post:
Don
|
|
|
|
Post by coons88 on Sept 9, 2023 20:40:19 GMT
Hi Don,
See below for full scan. It's the virtual cockpit code and the ACC code which are the issues. I don't believe the other codes are related, they seem to be intermittent.
There was no coding or adaptations done immediately prior to this error appearing. The last thing I did was maybe two days prior where I changed some radio text and frequency settings for module 5F (radio).
But my thoughts were the same, it almost seems like there is some sort of coding error, but I don't think what I changed has any link to this. I will post the adaption log below.
|
|
|
|
Post by coons88 on Sept 9, 2023 20:44:54 GMT
Here is the adaption log. Last thing changed was to module 5F on the 5th September, this virtual cockpit error occurred on the 9th. So I don't think it's related.
|
|
|
|
Post by dv52 (Australia) on Sept 9, 2023 22:34:40 GMT
hmm.........Dashboard error looks odd (and concerning). Here are the salient aspects of the fault (from my perspective): - Date of SCAN = 2023-09-09 20:11:06.
- Date of Dashboard error = 2023-09-06 16:57:35.
- Malfunction frequency counter =1
These points mean that notwithstanding that the error was "static" when first registered - in the 3 x day period from when the fault was first registered to the date of the SCAN - the same error has NOT been re-registered on a subsequent ignition cycle (I assume that the car was used in this period). Normally this fault-code is accompanied by a "check sum error" descriptor - not sure why this is absent on your car!
There are Technical Service Bulletins about this fault code on Dasgboard modules the say that the cause is over-sensitive response to the diagnostic device (dealer's ODIS device) -see HERE and HERE But I can't find a TSB with your part number.
Don
|
|
|
|
Post by coons88 on Sept 9, 2023 23:59:27 GMT
Ah yes you're right on the date of error vs. date of scan. Yes the car was used on all days in between.
I thought the same thing, it seems to have only logged it once. But it cannot be cleared.
I too found that TSB release, for Audi, doesn't seem to be any from VW (that are easily found online anyway). I will send this info to the local dealer and see if they have any knowledge of the error or any sort of software update available for the virtual cockpit unit.
I haven't heard back from that company who posted the Youtube video as of yet.
Any other thoughts from your technical perspective/background Don?
|
|
|
|
Post by dv52 (Australia) on Sept 10, 2023 21:42:10 GMT
Alas no "other thoughts"! I'm also not sure about the ACC error - it seems that 2023-09-06 was a pivotal date for this car. The ACC error happened about 30 minutes after the Dashboard module error and it generated the mating error on the Engine module. Interestingly, the fault frequency counter for the ACC error is ONE, but the Engine fault is SIX.
My only suggestion is that you contact a dealer and ask if there has been a similar TSB for this dashboard module. Hopefully the answer is yes and the problem can be fixed simply by a software patch.
Don
|
|
|
|
Post by coons88 on Sept 13, 2023 19:10:05 GMT
Thanks for your help thus far. I’m talking with VW currently, as well as some gurus in our local VW club. VW’s indication is the cluster needs to be replaced….
I’m also liaising with a couple of VAG coding companies in Europe.
I will update this thread once I have the problem fixed. It seems like a software issue, so surely the answer can’t be throwing away the physical unit and replacing it. But we’ll see.
|
|
|
|
Post by coons88 on Sept 22, 2023 23:11:08 GMT
Well I have a great update to share - after a lot of research I managed to find the solution to this, and have successfully removed the error on my vehicle. I continued to drive the car around with the error present while I was trying to still find a solution. It took me a few days to realise that there were no chimes anymore. Indicators, seatbelt warnings, etc. So I started to suspect that there was some sort of failure with the speaker. I started googling virtual cockpit speaker replacement, and finally stumbled upon the solution! This mini tools article confirmed my suspicion, and they sell a replacement speaker. Article hereReplacement speaker here
The speaker arrived promptly via DHL, it's plug and play, no soldering, and bingo - all errors gone! Including the ACC error. VW's solution was replace the cluster at anywhere from $1,500-6,500 depending on if a used or new one was sourced. So am happy to have solved it for $100. Hopefully this thread is helpful for anyone else that suffers the same problem. |
|
|
|
Post by dv52 (Australia) on Sept 23, 2023 2:31:44 GMT
coons88 : Well done!! This is a new learning for me - thanks for sharing your information. I suspect that the most difficult part of the repair was removing the cluster from the dashboard!!
Don
|
|
|
|
Post by coons88 on Sept 23, 2023 3:27:07 GMT
You’re not wrong - that was indeed the hardest part, it’s clipped in there pretty well!
I also read somewhere that the fan in the unit can also fail and cause a similar error.
|
|
|
|
Post by davorko on Nov 8, 2023 13:26:59 GMT
thank your for your post and links. after over a year with this issue on my passat b8 i finally managed to fix it.
i can confirm issue was speaker. Minitools shipped it and delivered speaker within 5 days using dhl. 20 min of work and everything working fine again. blinker and warning sounds back, acc error gone, everything working fine...
easy fix, and much cheaper than changing compete virtual cockpit.
-Thank you
|
|
|
|
Post by blacster on Nov 13, 2023 19:34:51 GMT
I had the same problem, thanks to your tutorial I fixed it just like you did. But the static error B200041 remained and cannot be deleted. Otherwise everything works. How did you deal with it?
|
|
|
|
Post by dv52 (Australia) on Nov 13, 2023 20:47:04 GMT
blacster : Hi. So, here's the thing - the accompanying words for the B200041 fault is " Ctrl. module faulty". This means that this is a general, catch-all error (i.e. it's not specific to just the speaker replacement issue in coons88 response).
If you have correctly replaced the speaker and the fault won't delete, it clearly means that the error is elsewhere - maybe the module memory is faulty. or perhaps there is a CRC error (I'm guessing, of course).
Are there any other fault codes on this car? Has the fault appeared following any work to this vehicle - equipment retrofit maybe? Has there been any dataset updates to the hex17 module, or any other coding changes? Does this fault have a back-story?
Don
|
|
|
|
Post by blacster on Nov 14, 2023 9:14:36 GMT
I had exactly the same problem as above. The car stopped making sounds from the alarm clocks, this turned off all the assistants and a yellow triangle appeared on the display. After replacing the speaker, the exclamation mark immediately disappeared and all assistants activated. The car is otherwise faultless and works as it should. Only error B200041 remained in the display and it cannot be deleted.
|
|
scavi
New Member
Posts: 2
|
Post by scavi on Dec 23, 2023 19:25:10 GMT
Hi guys,
got this error today as well  thanks for your write up here. I have the same symptoms: Error in Cluster when Ingittion is on and no chimes. Also a error code in Engine(01) and ACC => faulty received data with code U112300
Today I tried to fix a different issue in the Infotainment (5F) and did some error code deletion and just restarted the car. The chimes came back. Deleted all error codes again and restarted => No error in the cluster anymore (WTF). Did a testdrive and tested ACC all worked fine. The error B20041 stayed in OBD11.
Later the day I put Xmas presents in the car and tried the ingation and everything was back again. No Chimes, Error in Cluster and what so ever.
No im so confused if its actaully the speaker or something else. Truly fearful going to a VW workshop with this error.
Any tipps how I can pin that error down?
Also good video/instruction how to disassembly to get the cluster out ?
Best Regards and nice XMas.
|
|
|
|
Post by cangvik on Jan 20, 2024 18:54:43 GMT
Hi,
Also experiencing this error on my car. No sounds when starting up car, indicators etc, and infotaintment-error coupled with ACC-error. OBD-eleven show the generic B200041-error and I'm not able to delete it.
Was about to order a new speaker when I experienced that after driving the car on GTE-mode for a while, I got sound from indicators all of a sudden, and after turning the car on/off all errors was gone. Until next day when errors was back. I have since experienced the same many times (not working when starting up, but manage to get it working after driving for 30-60 mins on GTE-mode), almost as if the errors dissappears when the car is driven warm on GTE-mode. Live in Norway, and it's been pretty cold here since I first got the error.
I've tried to charge 12V-battery aswell just to rule that out. I have no clue what to try next. I mean, it doesn't seem to be speaker-related when it all of a sudden works after been driven for some time - just to stop working when it's "cold"?
|
|
scavi
New Member
Posts: 2
|
Post by scavi on Feb 5, 2024 19:27:13 GMT
Hi again, wanted to give feedback and BIG props to the thread creator. Bought the speaker from italy from minitools and installed it. Worked like a charm. Error in control unit wont disapaer even with developer mode. But I dont acuallty care. Active Info does all the chimses again and no error on ingition. And it acutally makes sense. Cars with ACC have a feature called City Break assist. Display beeps and show red danger symbol in cockpit if the sitation is dangerous. IMO this is a safty feature from VW. If VW cant chime in danger == no feature. So it disables to ACC completly at startup. All caused by the speaker. Use this to see how to remove the panels and the actual Display unit: Attention! Its not that easy to take out the actual unit like in the video. The display is hooked into the dashboard with 4 clips. 2 at the top and 2 and the bottom. You need some hooks to get a grip behind the unit to carefully hook the unit out of the clips. Be kind of gentle and unclip them one by one with firm pulls. Use a pair of this tool to unclip : www.hs-werkzeughandel.de/de/Audi-VW-Seat-Skoda-Haken-fuer-Handbremse-VAG-3438.html |
|
|
|
Post by bridgee302 on Mar 1, 2024 16:58:44 GMT
I am getting the same code in my 2017 Audi A4 Technik with the virtual cockpit. Everything works as it should. I have sound from the instrument cluster. I have an Autel code reader which i hooked up this morning and tried to cycle the instrument cluster fan and didn't hear anything. Could that also cause the "B200041 Ctrl module faulty" code?
|
|
|
|
Post by dv52 (Australia) on Mar 1, 2024 22:21:16 GMT
bridgee302 : Hi. As I said in a previous reply "B200041 fault code = Ctrl. module faulty", which means that this is a general, catch-all error. So lots of possible reasons for the fault code!!
Whilst I'm sure that your Autel code reader is OK - maybe try polling the self test facilities within the Dashboard module directly using OBD11. Select the 17 Dashboard module from the Control Units screen - then scroll-down to Output test. You should see a bunch of poll-able functions.
Your A4 is built on a MLB-evo platform, so I'm not sure what functions will be displayed. However, on MQB platform cars (which apply to this thread) - activation of fan housing is an option. This test returns the measurement of the fan speed (as a % reading).
Don
|
|
|
|
Post by bridgee302 on Mar 4, 2024 23:01:02 GMT
dv52: THank you for your response. My Autel code reader does allow me to test the fan (activation of fan housing) and adjust the %. I tried it at 30% and it worked. I tried it at 100% and it was louder and sounded like it was moving faster. I didn't try any other % because it is quite cold here today. I'm assuming it might be a software update??
|
|
|
|
Post by dv52 (Australia) on Mar 5, 2024 22:22:56 GMT
bridgee302 : OK - based on your words, it appears that the fan is operating correctly. So it's likely that the error is caused for another reason. It should be possible to also test the speaker in the hex17 module via your Autel device. The speaker test function is in the Output Test part of OBD11 software - I'm not sure what the equivalent facility is called on the Autel device.
The speaker test is called Gong by the 17 module - when activated, this test should allow the user to select a warning tone and play that sound. I suggest that you select "ALL acoustics" - this option cycles all sound-tones
Don
|
|
|
|
Post by gillidee on May 22, 2024 23:09:53 GMT
Just wanted to say thanks for sharing this. I was quoted over £2000 to replace instrument panel by VW for a 2017 Tiguan. Talked to 2 other local garages that couldn't figure out the issue. Then came across this discussion, managed to order from Mini tools approx £80 and finally had speaker fitted for £120, so 10% of what the dealer would have charged. They also refused to replace only the speaker.
Celebrating people power!
|
|
|
|
Post by coons88 on Jun 9, 2024 9:16:43 GMT
Happy to see so many people solving this issue, glad I could help.
My vehicle also had the code remain when scanned by OBDeleven, however functionality was fine and no errors on the dash. I assumed it was because the speaker was not OEM, or it’s a hard code, as in once it’s been thrown once it can never be cleared. Anyway it worked fine so who cares
|
|
|
|
Post by nour12 on Jun 17, 2024 21:50:38 GMT
Hi, Also experiencing this error on my car. No sounds when starting up car, indicators etc, and infotaintment-error coupled with ACC-error. OBD-eleven show the generic B200041-error and I'm not able to delete it. Was about to order a new speaker when I experienced that after driving the car on GTE-mode for a while, I got sound from indicators all of a sudden, and after turning the car on/off all errors was gone. Until next day when errors was back. I have since experienced the same many times (not working when starting up, but manage to get it working after driving for 30-60 mins on GTE-mode), almost as if the errors dissappears when the car is driven warm on GTE-mode. Live in Norway, and it's been pretty cold here since I first got the error. I've tried to charge 12V-battery aswell just to rule that out. I have no clue what to try next. I mean, it doesn't seem to be speaker-related when it all of a sudden works after been driven for some time - just to stop working when it's "cold"? Has the error been fixed? I have the same error and my car also has gte |
|
|
|
Post by vwjap on Jun 29, 2024 15:28:26 GMT
Hi again, wanted to give feedback and BIG props to the thread creator. Bought the speaker from italy from minitools and installed it. Worked like a charm. Error in control unit wont disapaer even with developer mode. But I dont acuallty care. Active Info does all the chimses again and no error on ingition. And it acutally makes sense. Cars with ACC have a feature called City Break assist. Display beeps and show red danger symbol in cockpit if the sitation is dangerous. IMO this is a safty feature from VW. If VW cant chime in danger == no feature. So it disables to ACC completly at startup. All caused by the speaker. Use this to see how to remove the panels and the actual Display unit: Attention! It’s not that easy to take out the actual unit like in the video. The display is hooked into the dashboard with 4 clips. 2 at the top and 2 and the bottom. You need some hooks to get a grip behind the unit to carefully hook the unit out of the clips. Be kind of gentle and unclip them one by one with firm pulls. Use a pair of this tool to unclip : www.hs-werkzeughandel.de/de/Audi-VW-Seat-Skoda-Haken-fuer-Handbremse-VAG-3438.htmlAlso wait for the display to go off before unplugging as otherwise it can bring the airbag light on as the car hasn’t actually turned off Cant work out why he’s using a screwdriver tho, as he has trim tools 🤷♂️ |
|
|
|
Post by jarkkot on Sept 16, 2024 16:46:17 GMT
Hi, thanks a lot, saved me about 2200 euro.
Got an offer for replacing it for that price, bought a speaker, replaced it and voila, everything works. I'm so glad right now.
My car: Volkswagen Passat Alltrack from 2018.
|
|
|
|
Post by unclegreg on Sept 18, 2024 8:01:56 GMT
cangvik nour12 I have very similar problem, after some time of a driving (passat b8 2016) speaker starting to work, but never on cold engine. Did anyone try to replace speaker with similar symptoms?
|
|
thanks for your write up here.
