[MSlv]

Hi, I have searched and read through all threads I could find, but still no definitive fix for this problem.

So I have a 2018 F30 with 6wa and hu_entrynav2 (entry evo or evo light, small display), no HUD, vin ending A605596, and have recently retrofitted 6wb.

All is well, except the navi info in the kombi, the arrows or graphics show slightly off centre to the right, and also the right side of the graphics is cut off.

Did anyone with F3x manage to get the correct navi graphics, centred and no longer cutoff on the right side, after retrofitting the 6wb? Or is it something we just have to live with?

Please share your experience if you have the same problem or if you managed to find fdl coding for fixing this.

I only request people with F3x to reply, it seems there is a fix for similar problem for F1x cars but it’s not working for F3x (I know, I tried).

[LA1Z24]

The answer to this is in the 6WB coding thread

[MSlv]

Trust me, I have read through maybe more than 100 pages of different 6wb coding threads and I have yet to see anybody with F3x confirm that some specific coding fixes this issue.

What I did see is people suggesting different coding options which I tried, to no effect.

As I mentioned, people I saw confirming that they fixed the navi graphics with FDL coding have F1x 5 series cars. That information is of no use to me.

This thread is ONLY about F3x cars and specific to this one issue regarding 6wb retrofit/coding.

[Ibo24]

Isn’t all the data for the 6WB come from the HU?
Try flashing that to the latest psdzdata.

That did solve issues for 6WB with HUD on NBT headunits.

[RuleNormaliai]

VO Code your HU with 6WB and you will see the magic happens.

[MSlv]

Originally Posted by Ibo24

Isn’t all the data for the 6WB come from the HU?
Try flashing that to the latest psdzdata.

That did solve issues for 6WB with HUD on NBT headunits.

I will try to talk to my guy who did the coding, thanks for the advice.

Originally Posted by RuleNormaliai

VO Code your HU with 6WB and you will see the magic happens.

During coding I believe he did VO code the KOMBI and HU. But I have entry evo, I believe 6wb was option only for id6 navi professional.

[RuleNormaliai]

Originally Posted by MSlv

I will try to talk to my guy who did the coding, thanks for the advice.



During coding I believe he did VO code the KOMBI and HU. But I have entry evo, I believe 6wb was option only for id6 navi professional.

nope, i have done lots of 6WB retrofits to all kinds of cars, and if there is MOST connection in HeadUnit it will work as it should do. so my guess is that he didn't code HU, or made some mistakes while doing that.

[chrbmw]

I also have the same issue with my graphic being cut off to the right. As far as I can read there is nothing that can be done. I have tried all sorts of changes for fix the issue, but so far no luck.

[SniPro]

Originally Posted by RuleNormaliai

VO Code your HU with 6WB and you will see the magic happens.

I did it from the very beginning coded hu and then dkombi with 6WB and didn’t see a magic. More of it, navi hints weren’t shown at all till FDL coded dkombi with NAVI_NBT_ENABLE kein_nbt.

I have Entrynav2 with istep level end 2018 and totally new 6wb with istep 2019 and I don’t have HUD

P.S
I saw today someone suggested to “play” with following FDL values for HU. Did topic starter tried them?

Kombi_Aufloesung: aktiv <--> nicht_aktiv
MFID_KOMBI_VARIANT: aktiv <--> nicht_aktiv

[Xwag]

Here is a fix:

In NBT:
HUD_AUFLOESUNG -> aufloesung_1
HUD_KOMPRIMIERUNG_ART -> rle_1
KOMBI_AUFLOESUNG -> aktiv
NAVI_HUD_AVAILABLE -> aktiv

In Kombi:
NAVI_NBT_ENABLE -> nbt_anzeige

HUD lines are necessary for displaying road names properly on cluster. I don’t even have HUD.

Keep this:
MFID_KOMBI_VARIANT -> nicht_aktiv
otherwise it will remove some settings under “Instrument Cluster” in iDrive

[AndrewC1989]

Originally Posted by Xwag

Here is a fix:

Thank you!

[MSlv]

Originally Posted by Xwag

Here is a fix

Thank you very much, looking forward to trying it when I get back home! Happy New Year!

[MSlv]

Originally Posted by Xwag

Here is a fix:

In NBT:
HUD_AUFLOESUNG -> aufloesung_1
HUD_KOMPRIMIERUNG_ART -> rle_1
KOMBI_AUFLOESUNG -> aktiv
NAVI_HUD_AVAILABLE -> aktiv

In Kombi:
NAVI_NBT_ENABLE -> nbt_anzeige

HUD lines are necessary for displaying road names properly on cluster. I don’t even have HUD.

Keep this:
MFID_KOMBI_VARIANT -> nicht_aktiv
otherwise it will remove some settings under “Instrument Cluster” in iDrive

Well, I tried this and it did not work. Setting NAVI_NBT_ENABLE -> nbt_anzeige completely removed navi info in 6wb and had to keep it as kein_nbt or something. All other settings didn’t change anything, I still have the picture cut off on the right side.

This was disappointing…

EntryEvo id6 with retrofitted 8.8” screen.

[Xwag]

Originally Posted by MSlv

Well, I tried this and it did not work. Setting NAVI_NBT_ENABLE -> nbt_anzeige completely removed navi info in 6wb and had to keep it as kein_nbt or something. All other settings didn’t change anything, I still have the picture cut off on the right side.

This was disappointing…

EntryEvo id6 with retrofitted 8.8” screen.

Sorry to hear that.
This fix is for NBT only and not for NBT EVO/entryEvo.
What you want to do is to do some additional research for NBT Evo and apply some of the codes from there. Do remember that you have to remove 6WA from VO completely.

[MSlv]

I start to strongly believe that there is no fix for EntryEvo (maybe even Entrynav/CIC) and you need NBT or full EVO ID6 to have navigation info correctly displayed.