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.









 
#827 ·
Hello everybody

I am Richi and new on this forum. I own a F10 523i 6 cylinder from 07/2011 with the basic cluster.

I decided to get a 6wb, bought one virginised and and my VIN number has already been programmed in to it.

I have not retrofitted it yet. Because I need some information, maybe someone can answer my questions.

My current i-step is F010-11-03-511. Is this too old, or should it work ? I read somewhere that if the i-step is not minimal from 07/2012 or later, cruise control will not function.

And what should i have to code after installation of the cluster ? I have a CIC professional navi and no hud. I have a laptop with E-sys and cable.

If someone could send me in the right direction, that would be much appreciated.

Thanks a lot!
 
#829 ·
#831 ·
Hello, just an update. I installed the 6wb today. And everything works. The coder said everything is already coded to my vin so I did not have to do a thing.

Just one thing does not work as expected, the cruise control. So this friday I will update the software so the car has the latest i-step level to solve this problem.

But it is worth every penny. Total cost of 6wb with coding and updating the car is 1000 euro exactly.
 
#832 · (Edited)
Hi Shawn,

first I wish you and all memebers a merry christmas!

Maybe you remember to my problem witht retrofit 6WB in a F30 (05/2013)

I had coded this car many times try to get it working.
But unfortunally I have still the issues with trailer warning and it it not possible to set the time and date.

So what can I do to try?
What kind of information you need to locate the issue?

Attached find the document..

Thanks in advance and
best regards from germany!

Joerg
 

Attachments

#833 ·
For 6WB in F30, 17-07-502 is minimum I-Step. You show to have 17-03-509. Car must be updated. And afterwards, when you VO Code DKombi and HU_NBT, FA must have build date >= 0717.
 
#835 · (Edited)
Hello, I***8217;ve done this 6WB retrofit on my 2012 F30, about your errors, for hour set, check in NBT what kombi is set at kombi_cic , It must be set on high , not low. Navigation is displayed in kombi?
About the trailler tow hitch, I saw same error on F10 pre LCI when coding 6WB with LCI FA. I don't know if it works but you can try like this : code kombi with tow hitch , save coding, then code it without tow hitch and save file. Compare the codings and see what parameter is changed between those two codings, then in the coding with tow hitch change that parameter until there you will not get any error.
Good luck, hope to hep you a little with my ideas.
Happy holidays to everyone!
 
#839 ·
Hello friends,

I have a problem to code the 6WB dkombi to my BMW F30.

VO already coded and built date changed to 0717.

BKOMBI disappeared and DKOMBI appeared all red.

Screenshot:


Tried to inject a different cafd but get this error: SVT-Ist must have at least one BTLD.

Does anyone have the right BTLD or CAFD or any other idea?

I-Stufe: F020-18-07-547

PsdzData: Extracted from ISTA-P version 63.3.003

E-Sys 3.33.0 Launcher Pro V3.2.1.153

Thank you very much.

Happy New Year from Germany!
 
#843 ·
Can someone please help? Massive failure when trying to upgrade my 6WA to 6WB.

My car has production date July 2015 and the i-Step (Current, Last, Shipment) is F020-15-07-502.

After a programming attempt, the iDrive screen shows me that

"Update required.
Have the system checked by the nearest BMW Service Partner."

I have all the errors on the new cluster: tampered dot, SOS error, Parking brake error. I'm not even sure if I did the coding correctly.

So first of all, do I need to update my car at the dealer? If so, how do I go about asking them to do this? Can I just request without any reason beside "I want my car to be on latest firmware?"

Any info would be appreciated.
 
#844 ·
Can someone please help? Massive failure when trying to upgrade my 6WA to 6WB.

My car has production date July 2015 and the i-Step (Current, Last, Shipment) is F020-15-07-502.

After a programming attempt, the iDrive screen shows me that

"Update required.
Have the system checked by the nearest BMW Service Partner."

I have all the errors on the new cluster: tampered dot, SOS error, Parking brake error. I'm not even sure if I did the coding correctly.

So first of all, do I need to update my car at the dealer? If so, how do I go about asking them to do this? Can I just request without any reason beside "I want my car to be on latest firmware?"

Any info would be appreciated.
I replied to your same PM. For 6WB in F30, 17-07-502 is minimum.
 
#847 ·
I have 6wb led swapped out for my car too. everything works just fine. only one issue that the navigation arrows direction won't show up on the HUD anymore. Can anyone know how to fix this problem? I will pay for the coding.
I never done any coding at all so don't show me how to do the code cuz I have zero knowledge about this coding thing.
thanks
 
#849 ·
The fix is really simple, I found the answer searching the forums yesterday. I had lost my Nav on the hud also but the answer is this

CIC => KOMBI_CIC = kombi_high
DKOMBI => NAVI_NBT_ENABLE = kein_nbt
(Thanks to a post by Shawn Sheridan)

You either need an ENET cable and esys and do this yourself or pay someone who can code it for you. The above coding will solve your issue.


Sent from my iPhone using Tapatalk
 
#850 ·
The fix is really simple, I found the answer searching the forums yesterday. I had lost my Nav on the hud also but the answer is this

CIC => KOMBI_CIC = kombi_high
DKOMBI => NAVI_NBT_ENABLE = kein_nbt
(Thanks to a post by Shawn Sheridan)

You either need an ENET cable and esys and do this yourself or pay someone who can code it for you. The above coding will solve your issue.

Sent from my iPhone using Tapatalk
can you help me? or do you know someone who can do this code?
 
#851 ·
I have never coded remotely my friend but I am sure there are plenty of people in the community that would be happy to help. I just know what coding you need to solve it.


Sent from my iPhone using Tapatalk
 
#852 ·
so what software or program do I need to download and where?
 
#853 ·
#854 ·
Can anyone help with my Nav display on my HUD after retrofitting a 6WB. The Nav symbols are not displaying correctly on roundabouts. On the Kombi they display as they should and with my old kombi attached they display correctly but with the 6WB they red circle that usually encompasses the roundabout is missing. See pictures. I’m hoping it’s a coding issue, I had something similar on my 6WA retrofit on my old F30 and updated I level fixed it. All current units are on the latest ilevel.
 

Attachments

#855 ·
Can anyone help with my Nav display on my HUD after retrofitting a 6WB. The Nav symbols are not displaying correctly on roundabouts. On the Kombi they display as they should and with my old kombi attached they display correctly but with the 6WB they red circle that usually encompasses the roundabout is missing. See pictures. I'm hoping it's a coding issue, I had something similar on my 6WA retrofit on my old F30 and updated I level fixed it. All current units are on the latest ilevel.
Set KOMBI_Aufloesung = Aufloesung_1 and HUD_Komprimierung_Art = RLE 1.
 
#856 · (Edited)
That didn't solve it Shawn, they were already set as you mentioned so I played around with the settings. Changing HUD_KOMPIMIERUNG_art brought in the correctly circled roundabouts but they were a lot smaller and then on other images they overlapped. Setting it back as described also Chops parts of the arrows off

Sent from my iPhone using Tapatalk
Image
 
#857 ·
That didn't solve it Shawn, they were already set as you mentioned so I played around with the settings. Changing HUD_KOMPIMIERUNG_art brought in the correctly circled roundabouts but they were a lot smaller and then on other images they overlapped. Setting it back as described also Chops parts of the arrows off...
And KOMBI_CIC = kombi_high is also set?
 
#858 · (Edited)
Yes, it was VO coded initially. I'm just trying the instructions here to see if they help.

Edit:they didn't

Code:
 The coding is not correct. You cannot add 6WB to your FA and VO code it since 6WB was not an option with NBT units, assuming that is what you have. You can only do it with NBT EVOs. To code a NBT to display navigation correctly with the 6WB, you must FDL code the following:

FPK_COMING_ROAD_BMP Werte=00
KOMBIGUIDING_SCHALTBAR Werte=00 
HIST_GAS_CONSUMP Werte=01 
BASIS_KOMBI_MMI_LIST Werte=00 
HUD_KOMPRIMIERUNG_ART Werte=00 (rle_1)
HUD_AUFLOESUNG Werte=01 (aufloesung_2)
KOMBI_AUFLOESUNG Werte=01 
LOUPE_TACHO_KOMBI Werte=01 
DRIVE_MODE_KOMBI Werte=01 
CALMING_KOMBI Werte=00 
MFID_KOMBI_VARIANT Werte=01 
KOMBI_CIC Werte=00 
SETTINGS_INFO_DISPLAY Werte=01
Sent from my iPhone using Tapatalk
 
#861 · (Edited)
SOLVED IT!!!

After lots of trial and error and looking at the previous CAFDs for my 6WA KOMBI and NBT I drew a few conclusions!

First was the 6WA is L7 and the 6WB is FPK(Micromap, I think this is in reference to the NAV displayed on the KOMBI) after initial coding and VO coding the images didn't quite fit and parts of arrows were missing.

Second was that with the 6WA installed the NBT was set
NAVI_HUD_AVAILABLE
nicht_aktiv (not active) = 00
when 6WB is installed you must set this to
NAVI_HUD_AVAILABLE
aktiv (active) = 01
Third, in order to display the images correctly on the KOMBI you must set this
KOMBI_AUFLOESUNG
aktiv (active) = 00
with 6WA this is set to nicht_active as this KOMBI is L6/L7. The 6WB is FPK micromap.

Fourth, you need to set
HUD_KOMPRIMIERUNG_ART
rle_1 = 00
again with my 6WA this was set to rle_2=Jade, I'm not sure what this means but HUD NAV would not show until rle_1 was selected.

Almost there....

Next you need to set
HUD_AUFLOESUNG
aufloesung_1 = 00
with the 6WA fitted this was set to aufloesung_2 but with the 6WB it needs to be set to aufloesung_1

Finally in KOMBI you must find
NAVI_NBT_ENABLE
nbt_anzeige = 01
and set it as so. This says that NBT is available for NAV.

That should be it. During my trial and error resolving this I managed to recreate the pixelation issues that one of the forum members had and it was evident in both the KOMBI and HUD NAV images, and before I had this my KOMBI NAV was just like NooL had, not quite centred with arrows cut short.

I really hope these steps help to fix other peoples similar issues, i know it has been driving me crazy! The 6WB KOMBI has been nothing but trouble so far!

Thanks to Shawn for pointing me in the right direction and always being there to offer advice and thanks to the other guys that highlighted they had similar issues which made me dig a little deeper.

Aslo......I've attached my CAFDs if anyone wants to look through.
 

Attachments

  • Like
Reactions: dncomputech
#862 ·
...
Thanks so Shawn for pointing me in the right direction and always being there to offer advice and thanks to the other guys that highlighted they had similar issues which made me dig a little deeper....
:thumbup:
 
#863 ·
Image


Is the circle a new feature with the 6WB? It wasn't present with the 6WA KOMBI?!? It basically shows your moving location in relation to the junction and is displayed on the KOMBI and the HUD.

Sent from my iPhone using Tapatalk
 
#865 ·
This was for my F10 that came with NBT and 6WA with a now retrofitted 6WB. I can’t imagine there is too much difference between FDL coding for the F30 and F10. Maybe use the CAFD tool to compare the CAFDs, mine and the F30 one.


Sent from my iPhone using Tapatalk