[maiquelaugusto]

Originally Posted by MartijnS

Unfortunately the flickering is not FDL coding. It's a hardware problem as I described above.

Only chance is swapping the HUD to a 2014+ version (the newer the better).

But I noticed that When you dimmer bright he don’t stop to work !!! Today I drove for 2 and a half and he worked without stopped.
But thank you for attention, I will try mora thing to avoid swapping !! Pray for me lololololo

. Thanks my friend.

[MartijnS]

Originally Posted by maiquelaugusto

But I noticed that When you dimmer bright he don’t stop to work !!! Today I drove for 2 and a half and he worked without stopped.
But thank you for attention, I will try mora thing to avoid swapping !! Pray for me lololololo

. Thanks my friend.

So you are saying when you dim it more it continues to work? Or when your make it brighter?

[maiquelaugusto]

Originally Posted by MartijnS

So you are saying when you dim it more it continues to work? Or when your make it brighter?

Yes. I noticed it , I believe that problem is energy, same thing get more energy ( (voltage or ampere ) and the system believes that HUD is over temperature!!
Because with have it when bmw change voltage from CIC/NBT to EVO.
Evo screen use 12v with lower ampere and NBT works with 9v !!!! I will try same test on this weekend!!!

I will try too reduce consumption of energy from cluster , like turn off same control bright or another thanks.
If you need same thing or idea please tell me my WhatsApp +5562996116262
I’m work hard so solve it without replacing hud !!
Praying for me lolololololololo

Thanks

[maiquelaugusto]

Originally Posted by MartijnS

So you are saying when you dim it more it continues to work? Or when your make it brighter?

Yesterday I drove for around 2 hours at night and low brightness!!
But today during a day with brightnesss flat after around 15 minutes the HUD stops to work!!!

Thanks

[jeffijaffa]

so I thought id jump onto this thread...
and id like to thanks everyone in advance.
as it seems to be the most up to date with 6WB coding advice
so I've purchased a 6WB to upgrade from the 6WA I know my istep is 2018 so
I'm thinking of

1. I won't need to update the car istep.
2. change the production date in esys to 2017 or later
3. VO the car with the 6WB.
4. FDL coding
5.
6.


I don't suppose someone could fill in the important bits I might need that I don't know about yet.
Do I need to inject cafds or something


The 6WB I'm getting is lower mileage so I'm just going to change the VIN ONLY via an R270 EEPROM programmer. I've heard you cant reset the milage but the cluster will update to the higher mileage of my car which is an F33 2014

[benjiF30]

Hi,

Could i kindly please check where could i please find a guide to code the 6wb on a F30. I have just purchased a set and it is on the way to me. Would love to hear from you guys so as i could learn and grow with you guys.

Thanks in advance.

[benjiF30]

Originally Posted by chp10

Hi,

because some of us installed already the 6WB Kombi i would like to start this tread. Here you can share your experience and findings with us.

Some of you asked me for the compass function. This can be found in section

3003 FZG Ausstattung -> Kompass Graph Enable -> set to aktiv.

I found also Motorleistung Enable which should show the engine power used (only workingin sportmodus). Unfortunately it is not working in my car. Maybe someone can try it and confirm. As it seems it is working at least for the F10 series cars.

In my 2013 F31 is still the HUD not working, i guess a coding mistake (resolution, wrapping...?), so if someone can help me would be nice.

Would you by any chance be able ti provide a guide to code 6wb? Thank you.

[RBN_EU]

]I have my 6wb coded, all working good, except the navi indications, it seems to have a lost graphics zone in the right side. also seems displaced to right like one in the photo. some one can help me with parameters to code



https://ibb.co/BC6DwfT

[natlbar]

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.

[MOEMB]

Originally Posted by shawnsheridan

FDL Code HU_NBT => KOMBI_CIC = kombi_high.

Hi there,
I have opposite case that I just retrofit NBT ENTRY_NAV with navigation

FDL KOMBI_CIC = low as can't set time & date and it didn't work

Any idea what else I have to change?

Should I VO code Kombi after?

[jkwhar]

I have a virginzed 6wb if anyone is interested!

[mbasic2]

Originally Posted by maiquelaugusto

My friends I solved one problem about it . When the car has combox module you need put loop connection on most cable to bypass combox module !!! . Now I just solve the problem of flicker on HUD !!! I believe that will be fdl coding !!!
My friend shawnsheridan can you help us ?

Can you please provide more info about bypassing combox module?

Something like diy for dummies

Thank you

[fredde85]

Originally Posted by RBN_EU

]I have my 6wb coded, all working good, except the navi indications, it seems to have a lost graphics zone in the right side. also seems displaced to right like one in the photo. some one can help me with parameters to code



https://ibb.co/BC6DwfT

I have the same problem

[328iking]

Hi. I just had 6wb installed but I don't have the instrument cluster settings on the idrive?

Any ideas?[IMG][/IMG]

[atzebmw]

Originally Posted by 328iking

Hi. I just had 6wb installed but I don't have the instrument cluster settings on the idrive?

Any ideas?[IMG][/IMG]

As I had already written several times.
Code the headunit with 6WA.

[328iking]

Originally Posted by atzebmw

As I had already written several times.
Code the headunit with 6WA.

That was done on Tuesday as far as I aware cos I got the service requirements etc back.

Edit: apparently as my car 2013 I do not have the option for "instrument cluster" on the idrive?

[atzebmw]

Originally Posted by 328iking

That was done on Tuesday as far as I aware cos I got the service requirements etc back.

Then play around with these settings

MFID_KOMBI_VARIANT set to aktiv

then see what happens and check again if all menus are available.
If something is missing you can try also these settings

CALMING_KOMBI
KOMBIGUIDING_SCHALTBAR
KOMBI_CIC

And yet, even with 6WB cluster, your car has the menu item "Instrument Cluster"

[328iking]

Originally Posted by atzebmw

Then play around with these settings

MFID_KOMBI_VARIANT set to aktiv

then see what happens and check again if all menus are available.
If something is missing you can try also these settings

CALMING_KOMBI
KOMBIGUIDING_SCHALTBAR
KOMBI_CIC

And yet, even with 6WB cluster, your car has the menu item "Instrument Cluster"

All fixed!!!

Now I know what m view does. Can it be coded the other way whereby you have m view in comfort. Currently You can untick it and have comfort view in sport mode.

[chrbmw]

I have just installed the 6WB cluster in my 2015 F31

I Modified the FA, added 6WB and removed 6WA. And changed Zeitkriterium from 0315 to 1117. Then after a little bit of difficulties getting the "DKombi" to show up. I finally got it visible instead of the "Kombi", I then VO coded the "DKombi", and "HU_Entrynav" by Detect CAF for SWE. and then CODE.
The 6WB looks to be working flawlessly, not red dot, and everything working fine incl. navi.

BUT the DKombi module folder is showing up Red/Blue and it is saying Hardware conflict.







I have at the same time added FA 610 (HUD), and I cannot get this to power up either. I have tried to remove the FA 610 (HUD) to see if this was causing the problem, but its still the same.

My main reason for replacing the cluster was to retrofit HUD.

Does anyone know why the DKombi is showing hardware conflict?

My Intergration Level is still the original 03.15. could this be the reason? ( I got a feeling this could be related). Or have I overlooked something very obvious?
Sorry if my explanation lacks the proper technical terms, I am a bit of a novice regarding coding with E-sys. Although I have managed to retrofit FCW and LDW and Touch controller.

Any advise is greatly appreciated. I am also willing to pay someone for a remote coding session.

My Psdzdata vers is: 4.16.22
E-sys version 3.27.1

[atzebmw]

Originally Posted by chrbmw

I have just installed the 6WB cluster in my 2015 F31



BUT the DKombi module folder is showing up Red/Blue and it is saying Hardware conflict.


I have at the same time added FA 610 (HUD), and I cannot get this to power up either. I have tried to remove the FA 610 (HUD) to see if this was causing the problem, but its still the same.

My main reason for replacing the cluster was to retrofit HUD.

Does anyone know why the DKombi is showing hardware conflict? And also why I can´t get the HUD to light up?

What does this setting look like in your E-Sys?
Is the hook set?

With the 610 in FA you have coded DKombi and HU_Entrynav?

[chrbmw]

Originally Posted by atzebmw

What does this setting look like in your E-Sys?
Is the hook set?

With the 610 in FA you have coded DKombi and HU_Entrynav?

Thank you for taking time to answer.
The "UPDATE VCM after TAL execution" was NOT ticked. What difference does this do?

I have tried to code the two modules again. With the box ticked. But I keep getting issues with the KOMBI showing and not the DKOMBI, and now I am not even able to access FDL coding in the DKOMBI. It is like the instrument cluster is unreachable. (It still works fine though)

[atzebmw]

Originally Posted by chrbmw

Thank you for taking time to answer.
The "UPDATE VCM after TAL execution" was NOT ticked. What difference does this do?

I have tried to code the two modules again. With the box ticked. But I keep getting issues with the KOMBI showing and not the DKOMBI, and now I am not even able to access FDL coding in the DKOMBI. It is like the instrument cluster is unreachable. (It still works fine though)

The VCM includes a list of your ecus.
But if you change an ecu (Kombi --> DKombi) the VCM doesn't notice that if the hook in the settings isn't set because the VCM will not be updated automatically.
I think that's why you still see the Kombi.
You can do the following to update the VCM with the DKombi.
Set the hook in the settings and then code the ZBE.
ZBE because that's an ecu that does not have a big effect if you code it.
After that hit again the button "Read VCM".
You can also try to hit the button Read Ecu.
Because this button always reads the currently available ecus.