BMW Forum - BimmerFest BMW Forums banner

6WB Retrofit - Coding Required

505K views 975 replies 210 participants last post by  Waynos  
#1 · (Edited)
I finally got around to installing my 6WB MFID Instrument Cluster. :D

Since mine was a brand new virgin Kombi, no EEPROM work was necessary to blank the donor car's mileage and VIN. Install was a breeze, and Coding was just a matter of adding 6WB to the VO, changing VO Production date to 1211, and VO Coding DKombi and HU_CIC.

Since my car does not have ECO Pro, I get just the Comfort and Sport mode displays.

Upgrading from the basic Kombi to either 6WA or 6WB is a dramatic improvement, and worth every penny. If I already had 6WA though, I personally would stick with it rather than invest in 6WB.









 
#908 ·
I updated only the dashboard.
the panel is made 07.16 I tried i-step 16-07 -.....
It turned out i-step ship. dashboards 17-03-501 the time criterion also did not change for me 0312. I looked at the calculation on the HWEL dashboard as it remained black and TAL was correctly calculated.
A very long trial and error method, thanks to the forum I read a lot carefully and everything worked out. Especially a lot of things described shawnsheridan many thanks. It's just that everything is in different sections.
 
#911 ·
I finally got around to installing my 6WB MFID Instrument Cluster. :D

Since mine was a brand new virgin Kombi, no EEPROM work was necessary to blank the donor car's mileage and VIN. Install was a breeze, and Coding was just a matter of adding 6WB to the VO, changing VO Production date to 1211, and VO Coding DKombi and HU_CIC.

Since my car does not have ECO Pro, I get just the Comfort and Sport mode displays.

Upgrading from the basic Kombi to either 6WA or 6WB is a dramatic improvement, and worth every penny. If I already had 6WA though, I personally would stick with it rather than invest in 6WB.

View attachment 379892

View attachment 379893

View attachment 379894

View attachment 379895

View attachment 379896
hi dear
i need file 160d 35080 6wb bmw f10
 
#916 ·
Hi, anyone can help me ?
I used esys flashed 6WB (2017 made). I cancelled flash due it take too long (flashing only in UDS mode only, not HTTP). After that i can***8217;t flash again due ESYS can***8217;t see it anymore. Cluster panel all black while plugged in power.
Maybe it dead.
How to rescue it ?
Thanks in advance.
(Sorry for my English)
 
#923 ·
2013 F06 650i

These are the steps:

Updated the car to 20-03 recently, before DKOMBI retrofit.
Installed brand new DKOMBI.
Added 6WB to the FA, didn***8217;t change build date, VO Coded all ECUs, including the CIC.
Detected and injected CAFD to DKOMBI.
Calculated update, DKOMBI didn***8217;t need further update to 20-03.

Now there are two problems:

1. Mileage shows 00000, with no red dot.

2. CBS data didn***8217;t sync to the new DKOMBI.
 
#926 ·
Guessing reading over 900 posts wasn't appealing to him haha

Sent from my iPhone using Tapatalk
 
#927 · (Edited)
I just retrofitted a 6WB cluster in my 2017 BMW 340i, and everything works great except the blind spot monitor system. When I start up the car, it says it failed to start the Blind Spot Monitor system. After startup, and when I turn BSM back on, it works flawlessly. I ran ITSA+ diagnostic, and I'm getting an SWW Interface fail, I cleared it and started up the car again, and it worked once. When I started it another time, after the ECUs go to sleep, I get the same error. Also, after I startup the car and manually turn on BSM and then turn off the car, as long as the computer hasn't gone to sleep, it will start the blind spot system with no issues on the next startup; probably because it doesn't have to start the system again. I'm guessing it's a coding or I-level issue since I never had this happen before swapping the cluster. It is not a massive deal as it does still work, but it is annoying to have to turn it on manually every time. Any ideas on how to fix this issue would be appreciated.

UPDATE

Found out that it was my JB4 that was making the blind spot fail at startup. I had the needle sweep turned on with the JB4 and with the 6WB it creates an issue, I turned it off and I have not had the issue since.
 
#929 ·
Just to be sure:
I have bought a new uncoded 6WB cluster 62109442850 produced 2020-09.
I have a F30 LCI from 08-2015, no HUD, but NBT-EVO, 6WA retrofitted, MOST retrofitted. Up to date firmware on all ECU's
I think I should do the following to retrofit it:
1) Disconnect battery
2) Change cluster to 6WB
3) Connect battery
4) Remove 6WA and add 6WB from FA (VO)
5) Code NBT-EVO
6) Insert CAFD to DKOMBI using E-Sys 3.27.1 for "Detect CAF for SWE".

Is that all ?

Should I set Zeitkriterium= 1117 before coding and inserting CAFD ?
or could I just set:
MFID_KOMBI_VARIANT -> aktiv
KOMBI_AUFLOESUNG -> aktiv
LOUPE_TACHO_KOMBI -> aktiv (nice function)
DRIVE_MODE_KOMBI -> aktiv
MFID_KOMBI_VARIANT -> aktiv
EINHEITEN_MASTER -> should be on kombi_l6_new
 
#936 ·
Probably the KOMBI ilevel is higher than the rest of the car. It's a common problem. Other ECU's need updating.

Sent from my iPhone using Tapatalk
 
#939 · (Edited)
Hi all,
I have an issue with a 6WB retrofit. I have a BMW 2011 bmw F10 (without HUD).
I bought a used 6WB cluster with HUD from a guy who took out the (i think) 35160wt eeprom. When I say I think it's because the cluster is manufactured on oct-2015.I don't know if it's 35160wd or 160DOW. The other eeprom -95320WT is present . Everyone I ask says that I will get the red dot on the odometer. What are my options? I saw that there is a
Xhorse 35160DW that eliminates this problem. And what dump should I use?
Thank you.
 
#940 ·
Hello all, I have a 2017 F15 and have a virginized 6WB. Is it possible to get step by step in instruction to retrofit it into my car so I can retain all the options I have driver assistance package and drivers assistance plus and carplay, all non retrofits. I don't want to mess this process.
I posted in the wrong group earlier, sorry.
 
#944 ·
Hi, Shawn!
Im trying to replace deffective 6WB on F07 LCI. I virginize it with VVDI xprog. But during coding it gives me an error "WDBI_CPS returned with negative response" I read your other posts in other tread, where you suggest to properly revirginize it. I did that, but same error. I thought that maybe the file in eeprom was corrupted and grab the dunp from another cluster 160DOWQ eeprom (with matching part number of cause). Wright it, virginize it, and try to code again, but same error. Could you please give me the advice what else could I try. Thanks in advance