[theteej]

Hi all,

I've done the HU swap from a 6,6 to 8,8 screen and it is working great however I did have to use the BimmerCode app in order to enable the 8,8 display before it would work.

After reading many threads here its become apparent that if the service people update the car at the dealership it will reset any settings I've changed with BimmerCode as that app does not make VO code changes. This would mean my HU would essentially be black until I recode it.

Seeing as I plan to stick with the 8,8 screen I've looked into this more and found I have to VO code this in so it appears like the car has come with this to begin with however I have not much clue on how to go about this..

I have a VGATE OBD Connector and just got myself an E-SYS cable as I apparently need that in order to do this VO coding. I don't have any E-sys software yet so that probably isn't going to get me far so I may need a bit of assistance getting that sorted please.

Is someone able to please guide me a bit on proceeding from here?
The car is a 2015 220D however I've posted over here in the 3series section as I've received some good advice here before.


Thanks.

[ramparts]

606 -> 609

[cjn]

Originally Posted by davidoff86

606 -> 609

If he has Business Nav (606) and HU_ENTRY_NAV then changing to Professional Nav (609) will reset the screen size and resolution to the correct values for the 8.8" screen.

However, the car will now be expecting a whole set of features that are unsupported, or supported differently, by the current HU. That seems likely to cause some problems!

Simply FDL coding the two screen parameters gave me no problems (2014 F30) and allowed some extra stuff, like split screen.

I suspect that dealing with a blank screen after dealer programming is potentially less hassle.

[atzebmw]

Originally Posted by theteej

Seeing as I plan to stick with the 8,8 screen I've looked into this more and found I have to VO code this in so it appears like the car has come with this to begin with however I have not much clue on how to go about this..

Good idea, but not possible because there's no equipment code for the 8,8 inch screen.
To code from 606 -> 609 is no good idea.

[theteej]

Originally Posted by cjn

If he has Business Nav (606) and HU_ENTRY_NAV then changing to Professional Nav (609) will reset the screen size and resolution to the correct values for the 8.8" screen.

However, the car will now be expecting a whole set of features that are unsupported, or supported differently, by the current HU. That seems likely to cause some problems!

Simply FDL coding the two screen parameters gave me no problems (2014 F30) and allowed some extra stuff, like split screen.

I suspect that dealing with a blank screen after dealer programming is potentially less hassle.

Thanks all for the responses so far.

by other features... What would these necessarily be? And would it matter really if these features were enabled by changing this 606 to 609 but not present...

It's probably easier that I deal with a blank screen however I don't want to be placed in that situation where my dealer starts asking me questions if they do a software update and it resets my 8,8 screen setting. Plus I'll always have that 8,8 screen now and it seems a shame I can't vo code this in permanently..

[cjn]

Originally Posted by theteej

Thanks all for the responses so far.

by other features... What would these necessarily be? And would it matter really if these features were enabled by changing this 606 to 609 but not present...

I don't think you'll get better advice than that which you are so keen to ignore.

It's not likely that anyone has an informed answer, so why don't you go ahead and try it. Please let us know what problems you encounter.

[theteej]

Originally Posted by cjn

I don't think you'll get better advice than that which you are so keen to ignore.

It's not likely that anyone has an informed answer, so why don't you go ahead and try it. Please let us know what problems you encounter.

Never ignoring advice just wanting to seek possible complications and weigh up whether its worth going ahead and further how to go about doing this process

[mig2830]

Originally Posted by atzebmw

Good idea, but not possible because there's no equipment code for the 8,8 inch screen.
To code from 606 -> 609 is no good idea.

Could you explain why. what will be the consequence? Thanks in advance

[mrpingu]

Originally Posted by mig2830

Could you explain why. what will be the consequence? Thanks in advance

It depends if youre head unit (the block below) is changed too.
609 consists of two parts; the bigger screen and a ”tall” headunit.
If you only replaced screen you should not code this as the tall headunit supports more functions.

[mig2830]

Mrpingu, thanks for reply-could you be more specific-what additional function is comming with the "tall" HU?

[mrpingu]

Originally Posted by mig2830

Mrpingu, thanks for reply-could you be more specific-what additional function is comming with the "tall" HU?

Read this article from bimmertech: https://www.bimmer-tech.net/blog/ite...evo-vs-nbt-evo

[mig2830]

Most interesting reading. It looks like the differens is functions of the HU and dot to the driving funktionalities.

Most of the HU2 functions are supported wiyh the entry EVO- 8.8" screen, Touch screen, Touch controller, split screen, Enhansed Bluetooth with 2 phones paring, Connected drive, voice control- so maybe 609 is a easy way to set the parameters for the 8.8" screen, touch and touch idrive?

[mrpingu]

Originally Posted by mig2830

Most interesting reading. It looks like the differens is functions of the HU and dot to the driving funktionalities.

Most of the HU2 functions are supported wiyh the entry EVO- 8.8" screen, Touch screen, Touch controller, split screen, Enhansed Bluetooth with 2 phones paring, Connected drive, voice control- so maybe 609 is a easy way to set the parameters for the 8.8" screen, touch and touch idrive?

Enhanced bluetooth is not part of '609' but '6NS', like you said. I don't know which 8.8, touch & touch controller


More info on finding out which HU you have: https://www.bimmer-tech.net/blog/ite...bmw-navigation

From searching on Touch, Display I found these FDL values you might need to change.

For upgrade to 8.8 screen
DISPLAY_SIZE_RESOLUTION: 8.8_1280x480 [01]
DISPLAY_VARIANTE: breites_display [02]

And maybe:
CID_DISPLAY_RES: 1280_480 [02]
CID_DISPLAY_SIZE: 8_8 [03]
CID_DISP_AR: ratio_1_00 [0F]

To enalbe touch on screen it is probably one of these values
CID_TOUCH: aktiv [01]
CID_HMI_TOUCH: aktiv [01]


For controller it is this I believe
ZBE_TOUCH: aktiv [01]

If you have bimmerutility you can see exactly what a VO-code changes on the different ECU's in terms of FDL entries using SVT-compare. Then you know for sure which FDL values are changed.

But before you do anything, you have to know which navigation system / you have.

For EntryNav2 / ENAVEVO I could do a SVT compare for you on my F48(x1) if interested. Switching between 6UN 6UP which is basically screen and touch controller upgrade.

[Zheez]

I'm not sure trying to code an EntryNav2 unit with 609 in the VO would even work. I haven't tried it but would it not fail on TAL calculation due to being an impossible combination? For 609 to work it would be expecting NBT or NBT2.

6UP may work though as that is the option code for the larger screen with EntryNav or EntryNav2.

[mrpingu]

Originally Posted by Zheez

I'm not sure trying to code an EntryNav2 unit with 609 in the VO would even work. I haven't tried it but would it not fail on TAL calculation due to being an impossible combination? For 609 to work it would be expecting NBT or NBT2.

6UP may work though as that is the option code for the larger screen with EntryNav or EntryNav2.

True, didn't think of that. But in the end lots of FDL entries are same either EntryNav2 or NBT, but not all settings work. So VO-coding 'could' fail on TAL calculation yes, but probably the headunit ECU can be coded using and 8.8 inch will be enabled.

Probably better to code 6UP instead of 609. Or just only FDL code, only need to find the entries.

[mig2830]

Thanks for your assistance, I think I will stay with FDL coding