[gnolivos]

Does anyone know if there is a coding option to change the amount of dimming when switching to night mode? I find it too bright at night even with the thumb wheel all the way down.

[fcx56]

I recently installed a brand new 6WB in my 2015 F36. I used a new 6WB to avoid red-dot tamper issues. The new KOMBI took my VIN and mileage with no coding.

The 6WB was built in early 2019, and I am still not sure what the iStep shipment date is for DKOMBI. My F36 had been previously updated to 16-07-507. After installation, I received Check Control messages indicating “Update Required”, at which time I flashed FEM_GW with a DHCP server, ESYS, and an ENET cable to 19-07-###. Then I updated DME and attempted to update HU_NBT, but no updates for HU_NBT were available between my 16-07-507 and 19-07-###. There were also no updates available to DKOMBI and HWEL was black using iStep shipment of 19-07-###. It was now on to FDL coding. I could not set the time until I coded KOMBI_CIC mid -> high in DKOMBI.

I had the arrow cutoff on the right when displaying navigation instructions on DKOMBI, and also the overlap of the distance until turn bar and the speed units on the HUD. To even get these to display, I had to code NAVI_NBT_ENABLE to kein_nbt in DKOMBI. I was not satisfied with this coding because I thought the value conflicted with the vehicle, surely this value should be nbt_anzeige with 609 Pro Nav. I decided to compare CAFD (.ncd) files with a F15 that came equipped with NBT and DKOMBI. I found helpful files on bimmerpost. The F10 DKOMBI contained mismatched FDL coding on the first entry in 3003, NAVI_VERBAUT. The F10 value was navi, while my DKOMBI was coded ohne_nbt. This roughly translates to Installed Nav: without NBT. I was unable to find this coding using ESYS, and realised the mapping was trimmed from newer psdzdata. I was able to confirm this by renaming my newer CAFD files to an older version that matched the F10's. I changed the name of the CAFD from my 2019 6WB from "CAFD_00001060_008_000_008.ncd" to "CAFD_00001060_005_001_051.ncd", and this allowed me to see the trimmed variable in the NCD / CAFD Tool V0.5.2.203. I used Windows calculator to convert HEX to binary and coded the missing value in eSys editor while retaining the other entries that summed to the HEX. I also changed NAVI_NBT_ENABLE to nbt_anzeige and various MICROMAP and AUFLOESUNG settings in HU_NBT. Navigation instructions once again appeared on the display.

Not only did they appear, but they filled the centre portion and it was immediately apparent that these were the correct settings. Interstate icons also appeared on DKOMBI when applicable. Now, the only issue lies in the newer, better micromap being cut off on the HUD (when enabled). I am not sure if this is just something that has to be lived with using DKOMBI, HUD, and NBT on an F30, or if there is another setting that will finally fix the cutoff HUD. In order to get next turn arrows to display (on the Control Display, DKOMBI, or HUD) I had to set HUD_AUFLOESUNG to aufloesung_1 (which, according to the notes, is for a HUD with 208x149 resolution, as used in the l6 HUD). The bottom part of the arrow is missing, consistent with the HUD actually being 184x89 pixels instead of the 208x149 that was required to get next turn arrows to display. Even though the HUD is cut-off on the bottom, there is no longer an overlap between speed units and the upcoming turn bar (the speed units disappear appropriately), which says to me this coding is closer to what should be. Either the HUD cutoff is a tradeoff made when using DKOMB, HU_NBT, and HUD over apix instead of CAN on F30 or there is another setting that I have not found yet.

I can say that if you are trying to get navigation arrows to display on DKOMBI, this is much preferred to the “non-nav” arrow display. If anyone can expand on this post and provide the correct FDL codes for DKOMBI and apix HUD we will have a complete answer to navigation on F30 DKOMBI using NBT.

If posting CADF (.ncd) files is allowed on this forum (I haven't read the rules and don't want any problems), I will attach mine to this post.

[Zorn]

Originally Posted by fcx56

I recently installed a brand new 6WB in my 2015 F36. I used a new 6WB to avoid red-dot tamper issues. The new KOMBI took my VIN and mileage with no coding.

The 6WB was built in early 2019, and I am still not sure what the iStep shipment date is for DKOMBI. My F36 had been previously updated to 16-07-507. After installation, I received Check Control messages indicating “Update Required”, at which time I flashed FEM_GW with a DHCP server, ESYS, and an ENET cable to 19-07-###. Then I updated DME and attempted to update HU_NBT, but no updates for HU_NBT were available between my 16-07-507 and 19-07-###. There were also no updates available to DKOMBI and HWEL was black using iStep shipment of 19-07-###. It was now on to FDL coding. I could not set the time until I coded KOMBI_CIC mid -> high in DKOMBI.

I had the arrow cutoff on the right when displaying navigation instructions on DKOMBI, and also the overlap of the distance until turn bar and the speed units on the HUD. To even get these to display, I had to code NAVI_NBT_ENABLE to kein_nbt in DKOMBI. I was not satisfied with this coding because I thought the value conflicted with the vehicle, surely this value should be nbt_anzeige with 609 Pro Nav. I decided to compare CAFD (.ncd) files with a F15 that came equipped with NBT and DKOMBI. I found helpful files on bimmerpost. The F15 DKOMBI contained mismatched FDL coding on the first entry in 3003, NAVI_VERBAUT. The F15 value was navi, while my DKOMBI was coded ohne_nbt. This roughly translates to Installed Nav: without NBT. I was unable to find this coding using ESYS, and realised the mapping was trimmed from newer psdzdata. I used Windows calculator to convert HEX to binary and coded the missing value while retaining the other entries that summed to the HEX. I also changed NAVI_NBT_ENABLE to nbt_anzeige and various MICROMAP and AUFLOESUNG settings in HU_NBT. Navigation instructions once again appeared on the display.

Not only did they appear, but they filled the centre portion and it was immediately apparent that these were the correct settings. Interstate icons also appeared on DKOMBI when applicable. Now, the only issue lies in the newer, better micromap being cut off on the HUD (when enabled). I am not sure if this is just something that has to be lived with using DKOMBI, HUD, and NBT on an F30, or if there is another setting that will finally fix the cutoff HUD. In order to get next turn arrows to display (on the Control Display, DKOMBI, or HUD) I had to set HUD_AUFLOESUNG to aufloesung_1 (which, according to the notes, is for a HUD with 208x149 resolution, as used in the l6 HUD). The bottom part of the arrow is missing, consistent with the HUD actually being 184x89 pixels instead of the 208x149 that was required to get next turn arrows to display. Even though the HUD is cut-off on the bottom, there is no longer an overlap between speed units and the upcoming turn bar (the speed units disappear appropriately), which says to me this coding is closer to what should be. Either the HUD cutoff is a tradeoff made when using DKOMB, HU_NBT, and HUD over apix instead of CAN on F30 or there is another setting that I have not found yet.

I can say that if you are trying to get navigation arrows to display on DKOMBI, this is much preferred to the “non-nav” arrow display. If anyone can expand on this post and provide the correct FDL codes for DKOMBI and apix HUD we will have a complete answer to navigation on F30 DKOMBI using NBT.

If posting CADF (.ncd) files is allowed on this forum (I haven't read the rules and don't want any problems), I will attach mine to this post.

Interesting stuff. My 6WB will be here Tuesday and I'm curious to see whether I have this issue on a 2018 F36 that came with 6WA.

[atzebmw]

Originally Posted by Zorn

Interesting stuff. My 6WB will be here Tuesday and I'm curious to see whether I have this issue on a 2018 F36 that came with 6WA.

You will not have this problem.
This happens only for cars built until 6/2016 with Evo ID4 or older headunits.

[Shawzy44]

Has anyone successfully coded the “M Performance” logo on the 6WB? If so how?

[Rajy Shergill]

Anybody know someone who can do coding in the midlands area uk

[TiToyz]

Hi,

I want to change to a 6WB on my F30 2012 with HUD and CIC,

It''s working ? i read a lot of stuff and i'm confused ...

Thank's everyone and sorry for my bad english

TiToyz from France

[FinF30]

F30 2013, with HUD and CIC.

Brand new 6wb, coded and everything works.

Hud started to flicker. Does a small flicker every minute or something. And hud has disappeared few times after a driving for a while. Didnt do it with old cluster.

Anyone with same issue? I quess it something coding related. Part number for the hud has changed couple of times during the f30 prooduction.

[jkwhar]

Originally Posted by Shawzy44

Has anyone successfully coded the “M Performance” logo on the 6WB? If so how?

It will show "M550d". I think it was after a certain istep that they fixed it, but can't remember exactly.

[Skyhigh]

Don't think they ever fixed it. Not on 6WB.
I have the latest istep (or there might be one more recent one now) and it isn't fixed.

[Zorn]

Originally Posted by FinF30

F30 2013, with HUD and CIC.

Brand new 6wb, coded and everything works.

Hud started to flicker. Does a small flicker every minute or something. And hud has disappeared few times after a driving for a while. Didnt do it with old cluster.

Anyone with same issue? I quess it something coding related. Part number for the hud has changed couple of times during the f30 prooduction.

I don't get the flicker, but I do get the issue very rarely when driving that the 6WB will black out for about a second then come right back, almost like it had a quick reboot. It's so fast that by the time I get worried it's already back, and it's extremely rare for me.

[japko]

Hi, im rookie with it.
Could You Guys be so nice and can me put tutorial "what I need code it for my car?"
I have 6WA with HUD
Many Thanks

[mofo99]

So i succesfully retrofitted the 6wb in my f36 and everything works perfect.
The only thing that bothers me is the orange light at night. Is there no coding option to make the car think it is always day so that it stays white?

I cant find anything on the Internet, only for the f10 but that does not work for the f3x

[Skyhigh]

No.

[mofo99]

So the only coding for the 6wb is the compas in the middle

[Skyhigh]

And additional digital speed indicator, which IMO is useless on the 6WB. I have not enabled it. Just the compass.

[mofo99]

The Compass is also not that helpfull, but looks cool 😎

[Skyhigh]

It is as helpful as a compass can be in a car but it fills a part of that empty space nicely

[drdino]

Is there a way to code the 6WB to display navigation instructions at the same time as the HUD? Or is one or the other?

[shawnsheridan]

Originally Posted by drdino

Is there a way to code the 6WB to display navigation instructions at the same time as the HUD? Or is one or the other?

Not possible. Only one or the other as selectable via iDrive.

[drdino]

Thanks! It's a shame, as there's that wasted space between the dials, but anyway...

[Skyhigh]

That's the biggest deficiency of 6WB - lots of non-utilised space on the screen. I am missing a nav map there...