[mrpingu]

I just discovered that if you just VO-code 6CP and then get the car to a online ISTA or wait till it gets updated through the ATM / connected Drive services. Then you can buy Apple CarPlay through BMW Connected Drive Store.

You still need to check if you have a WLAN port at the back of the Head Unit!

My optioncodes, inlcuding my retrofitted ones. Taken from BMW AOS / AIR portal. So this is official records from BMW servers


After a while it popped up on Connected Drive Store, ready to buy for life

[Predki]

Do you mind explaining this process to a noob?

[mrpingu]

Either use - E-sys or BimmerUtility.
BimmerUtility also let you FDL code and change some things like 5 times soft blink but for this you need VO-coding. Attaching a guide from the internet i found.

You need only the til and including step 10

[MJE60]

Very Helpful post, thank you. Just a small point I think you might mention, namely if you VO code 6CP and take the car to a BMW dealer to have an update so the revised VO code is fed into BMW servers via ISTA, make sure the hardware actually supports 6CP. You warned that WLAN is required in HU but so, I believe, is enhanced bluetooth.

For others, Not all F48 will have correct hardware to support 6CP and VO coding without this will throw fault codes and/or pi*s off the dealer service department. Whilst most post July 2017 built F48 will have wireless enabled and enhanced Bluetooth HU, i.e the required hardware a few don’t. Also make sure 6CP was an option for your F48 build date, I believe 6CP was introduced as an order option in some markets in July 2016 however f48 with old Entrynav HU (route navigation map and old display layout) continued to be build/sold after this date. I believe 6CP was not widely included until BMW flirted with Carplay subscription in mid 2018. If you VO code an option which was not actually a valid option at time of build it will throw errors on ISTA.

[MJE60]

Originally Posted by mrpingu

I just discovered that if you just VO-code 6CP and then get the car to a online ISTA or wait till it gets updated through the ATM / connected Drive services. Then you can buy Apple CarPlay through BMW Connected Drive Store.

You still need to check if you have a WLAN port at the back of the Head Unit!

My optioncodes, inlcuding my retrofitted ones. Taken from BMW AOS / AIR portal. So this is official records from BMW servers
Attachment 3508385

After a while it popped up on Connected Drive Store, ready to buy for life
Attachment 3508384

Thanks again, also that is a pretty good option price wise Nkr 3,100 or approx £225/US$290 for anyone with Esys. I did something similar when I upgraded my CDU and touch controller, namely change VO code SA6UN to SA6UP and noticed that instead of only being able to update nav maps by using usb, it the gave me wireless updates also. I did not make the connection that BMW servers and connected drive must have been updated also. Many congrats, how did you work this out?

[mrpingu]

Originally Posted by MJE60

Helpful post, thank you. Just a small point I think you might mention, namely if you VO code 6CP and take the car to a BMW dealer to have an update so the revised VO code is fed into BMW servers via ISTA, make sure the hardware actually supports 6CP. Not all F48 will have correct hardware to support 6CP and VO coding without this will throw fault codes and/or pi*s off the dealer service department. Whilst most post July 2017 built F48 will have wireless enabled and enhanced Bluetooth HU, i.e the required hardware a few don’t. Also make sure 6CP was an option for your F48 build date, I believe 6CP was introduced as an order option in some markets in July 2016 however f48 with old Entrynav HU (route navigation map and old display layout) continued to be build/sold after this date. I believe 6CP was not widely included until BMW flirted with Carplay subscription in mid 2018. If you VO code an option which was not actually a valid option at time of build it will throw errors on ISTA.

If you write VO-code to the VCM it is automatically uploaded to BMW-server through the ATM. See the screenshot of the AIR, all my retrofits are in there, this way there are no problems for the dealer because the VO matches with what is in the car.

Of course you are totally right that one should check if it can support CarPlay beforehand like you wrote in your other thread. In either case, this also applies to the 3rd party coding options aswell. Either you have EntryNAV2 with WLAN port or NBT evo or you don’t have a compatible unit. Only proceed if you have the WLAN port.


AFAIK FA/FP doesn’t even calculate correctly in E-sys if you put in a FA-option that doesn’t exist for that build date and I-level shipment is set correctly

I also posted an HWEL list in your other thread where you can see check with the HWEL which EntryNAV HU you have. Using TAL-calculation against the VO you can even see which HWEL is expected for that VO and compare which unit should have been fitted from factory.


TLR: Always check if you have WLAN port first folks.
————

The reason I wrote this post is that people let you believe there are 3 options to enable CarPlay but this actually the 4th.

1. provisioning
2. patching HU
3. OEM FSC
4. VO-code + buy in connected store

[MJE60]

Originally Posted by mrpingu

If you write VO-code to the VCM it is automatically uploaded to BMW-server through the ATM. See the screenshot of the AIR, all my retrofits are in there, this way there are no problems for the dealer because the VO matches with what is in the car.

Of course you are totally right that one should check if it can support CarPlay beforehand like you wrote in your other thread. In either case, this also applies to the 3rd party coding options aswell. Either you have EntryNAV2 with WLAN port or NBT evo or you don’t have a compatible unit. Only proceed if you have the WLAN port.


AFAIK FA/FP doesn’t even calculate correctly in E-sys if you put in a FA-option that doesn’t exist for that build date and I-level shipment is set correctly

I also posted an HWEL list in your other thread where you can see check with the HWEL which EntryNAV HU you have. Using TAL-calculation against the VO you can even see which HWEL is expected for that VO and compare which unit should have been fitted from factory.


TLR: Always check if you have WLAN port first folks.
————

The reason I wrote this post is that people let you believe there are 3 options to enable CarPlay but this actually the 4th.

1. provisioning
2. patching HU
3. OEM FSC
4. VO-code + buy in connected store

Thank you again for this, I have updated my Carplay guide and included your option (with your user name as credit). Thank you again for this. Makes me now wish I hadn’t stopped using Esys.

[mrpingu]

Also isn’t enhanced Bluetooth just a software thing?You either have Bluetooth hardware or not and it is enabled or disabled throug coding:

Atleast on both EntryNAV and EntryNAV evo; https://www.bimmer-tech.net/blog/ite...nced-bluetooth

See the table lower on that page

Not 100% sure about this because my car had EBT from factory, but I am pretty sure as HWEL values don’t change if I remove that option upon TAL-calculation.

[MJE60]

AFAIK FA/FP doesn’t even calculate correctly in E-sys if you put in a FA-option that doesn’t exist for that build date and I-level shipment is set correctly

I also posted an HWEL list in your other thread where you can see check with the HWEL which EntryNAV HU you have. Using TAL-calculation against the VO you can even see which HWEL is expected for that VO and compare which unit should have been fitted from factory.


TLR: Always check if you have WLAN port first folks.
————

The reason I wrote this post is that people let you believe there are 3 options to enable CarPlay but this actually the 4th.

1. provisioning
2. patching HU
3. OEM FSC
4. VO-code + buy in connected store[/QUOTE]

‘ AFAIK FA/FP doesn’t even calculate correctly in E-sys if you put in a FA-option that doesn’t exist for that build date and I-level shipment is set correctly ’ ——->
Very interesting point because all the E-sys forums warn that you must not update VO unless hardware, FA option and even istep are all correct.

[mrpingu]

Originally Posted by MJE60

AFAIK FA/FP doesn’t even calculate correctly in E-sys if you put in a FA-option that doesn’t exist for that build date and I-level shipment is set correctly

I also posted an HWEL list in your other thread where you can see check with the HWEL which EntryNAV HU you have. Using TAL-calculation against the VO you can even see which HWEL is expected for that VO and compare which unit should have been fitted from factory.


TLR: Always check if you have WLAN port first folks.
————

The reason I wrote this post is that people let you believe there are 3 options to enable CarPlay but this actually the 4th.

1. provisioning
2. patching HU
3. OEM FSC
4. VO-code + buy in connected store

‘ AFAIK FA/FP doesn’t even calculate correctly in E-sys if you put in a FA-option that doesn’t exist for that build date and I-level shipment is set correctly ’ ——->
Very interesting point because all the E-sys forums warn that you must not update VO unless hardware, FA option and even istep are all correct.

That is correct because you can code valid options. Take for example LED headlights, you can code that in because it is not build-date dependent as in it was available from release even if you have not correct hardware (halogen lights) fitted.

But for options that do depend on ZeitKriterium this different.E-sys does take into account build-date option codes

More info here: https://www.bimmerfest.com/threads/z...o-date.642231/

[mrpingu]

Originally Posted by MJE60

Thanks again, also that is a pretty good option price wise Nkr 3,100 or approx £225/US$290 for anyone with Esys. I did something similar when I upgraded my CDU and touch controller, namely change VO code SA6UN to SA6UP and noticed that instead of only being able to update nav maps by using usb, it the gave me wireless updates also. I did not make the connection that BMW servers and connected drive must have been updated also. Many congrats, how did you work this out?

Well there was a discussion about this on a dutch forum. There was someone who said: "I am curious what happens if you code the VO to have 6CP - CarPlay preparation"

I just thought, let's put that to a test and see what happens

Yeah pricewise not too bad, especially now the NOK is weak compared to all big currencies. A third-party coder like kubax86 also takes 200USD for the non-OEM FSC method.

[joazz1]

Originally Posted by mrpingu

Hi
Sorry to put you to contribution I did it the other way bought and fsc from bimmerutility now need to change the fdl any guidance would be great
Thanks


I just discovered that if you just VO-code 6CP and then get the car to a online ISTA or wait till it gets updated through the ATM / connected Drive services. Then you can buy Apple CarPlay through BMW Connected Drive Store.

You still need to check if you have a WLAN port at the back of the Head Unit!

My optioncodes, inlcuding my retrofitted ones. Taken from BMW AOS / AIR portal. So this is official records from BMW servers
Attachment 3508385

After a while it popped up on Connected Drive Store, ready to buy for life
Attachment 3508384

[mrpingu]

Just posting HWEL list here so I have quick access to it if needed.
You can check your HWEL with e-sys or by taking a photo of the HU sticker.


BMW EntryNav2/EntryNav Evo HWEL version description.
0000277C Nav ECE Full (CD, DAB, GPS, Most, USB1, USB2, BT, WLAN, 2xMicIn, Video, OABR, Ethernet)
0000277D Nav US Full (CD, SDARS, IBOC, GPS, Most, USB1, USB2, BT, WLAN, 2xMicIn, Video, OABR, Ethernet)
00002F4F Media ECE Full (USB1, BT, Video, OABR, Ethernet)
00002F50 Media US Full (SDARS, IBOC, USB1, BT, Video, OABR)
000036C8 Med ECE 0380 (USB1, BT, Video, OABR)
000036C9 Med ECE 03F9 (DAB MOST USB2 WLAN 2MICIN CVBS1 ETH OABR1 RAM-2GB BT USB1)
000036CA Med ECE 03FB (DAB MOST USB2 WLAN 2MICIN CVBS1 ETH OABR1 RAM-2GB BT USB1 CD)
000036CB Nav ECE 0782 (CD CVBS1 ETH OABR1 HW_NAV RAM-2GB BT USB1)
000036CC Nav ECE 07FF (DAB CD NAV_GPS MOST USB2 WLAN 2MICIN CVBS1 ETH OABR1 HW_NAV RAM-2GB BT USB1)
000036CD Med US 1382 (SDARS, IBOC, USB1, BT, Video, OABR, CD)
000036CE Med US 13F8 (SDARS IBOC MOST USB2 WLAN 2MICIN CVBS1 ETH OABR1 RAM-2GB BT USB1)
000036CF Med US 13FA (US SDARS IBOC CD MOST USB2 WLAN 2MICIN CVBS1 ETH OABR1 RAM-2GB BT USB1)
00003A05 Med US 17FA (SDARS, IBOC, USB2, HW_NAV, MOST, WLAN, 2MICIN, BT, Video, OABR)
00003A06 Med US 17FC (SDARS, IBOC, USB2, HW_NAV, MOST, WLAN, 2MICIN, BT, Video, OABR)
000040D5 Med ECE 0302 (CD ETH OABR1 BT USB1)
000040EA Med ECE 03F0 (USB2 WLAN 2MICIN CVBS1 ETH OABR1 RAM-2GB BT USB1)
000040E9 Med ECE 0372 (USB2 WLAN 2MICIN ETH OABR1 RAM-2GB BT USB1)
000040E8 Med ECE 038B (DAB CD MOST CVBS1 ETH OABR1 BT USB1)
000040E7 Med ECE 0200 (OABR1 BT USB1)
000040E6 Med ECE 0100 (ETH BT USB1)
000040E5 Med ECE 0102 (CD ETH BT USB1)
000040E4 Nav ECE 07F4 (NAV_GPS USB2 WLAN 2MICIN CVBS1 ETH OABR1 HW_NAV RAM-2GB BT USB1)
000040E3 Nav ECE 0776 (CD NAV_GPS USB2 WLAN 2MICIN ETH OABR1 HW_NAV RAM-2GB BT USB1)
000040E2 Nav ECE 07FD (DAB NAV_GPS MOST USB2 WLAN 2MICIN CVBS1 ETH OABR1 HW_NAV RAM-2GB BT USB1)
000040E1 Med US 1200 (SDARS IBOC OABR1 BT USB1)
000040E0 Nav US 17FC (SDARS IBOC CD MOST USB2 WLAN 2MICIN CVBS1 ETH OABR1 HW_NAV RAM-2GB BT USB1)
000040DF Nav US 17FA (US SDARS IBOC NAV_GPS MOST USB2 WLAN 2MICIN CVBS1 ETH OABR1 HW_NAV RAM-2GB BT USB1)
000040DE Med CHI 2382 (CHI CD CVBS1 ETH OABR1 BT USB1)
000040DD Med CHI 23F8 (CHI MOST USB2 WLAN 2MICIN CVBS1 ETH OABR1 RAM-2GB BT USB1)
000040DC Med CHI 23FA (CHI CD MOST USB2 WLAN 2MICIN CVBS1 ETH OABR1 RAM-2GB BT USB1)
000040DB Med CHI 2200 (CHI OABR1 BT USB1)
000040DA Med CHI 2300 (CHI ETH OABR1 BT USB1)
000040D9 Nav CHI 2780 (CHI CVBS1 ETH OABR1 HW_NAV RAM-2GB BT USB1)
000040D8 Nav CHI 2782 (CHI CD CVBS1 ETH OABR1 HW_NAV RAM-2GB BT USB1)
000040D7 Nav CHI 27F8 (CHI MOST USB2 WLAN 2MICIN CVBS1 ETH OABR1 HW_NAV RAM-2GB BT USB1)
000040D6 Nav CHI 27FA (CHI CD MOST USB2 WLAN 2MICIN CVBS1 ETH OABR1 HW_NAV RAM-2GB BT USB1)
00005D0F Med ECE 03D0 (USB2 2MICIN CVBS1 ETH OABR1 BT USB1)
00005D10 Med ECE 03DA (CD MOST USB2 2MICIN CVBS1 ETH OABR1 BT USB1)
00005D11 Med ECE 03F1 (DAB USB2 WLAN 2MICIN CVBS1 ETH OABR1 RAM-2GB BT USB1)
00005D12 Nav ECE 0788 (MOST CVBS1 ETH OABR1 HW_NAV RAM-2GB BT USB1)
00005D14 Nav ECE 05F4 (NAV_GPS USB2 WLAN 2MICIN CVBS1 ETH HW_NAV RAM-2GB BT USB1)
00005D16 Nav ECE 0672 (CD USB2 WLAN 2MICIN OABR1 HW_NAV RAM-2GB BT USB1)
00005D18 Nav ECE 07F8 (MOST USB2 WLAN 2MICIN CVBS1 ETH OABR1 HW_NAV RAM-2GB BT USB1)
00005D19 Nav ECE 07F8 (MOST USB2 WLAN 2MICIN CVBS1 ETH OABR1 HW_NAV RAM-2GB BT USB1)
00005D1A Nav ECE 07DA (CD MOST USB2 2MICIN CVBS1 ETH OABR1 HW_NAV RAM-2GB BT USB1)
00005D1C Nav ECE 07F5 (DAB NAV_GPS USB2 WLAN 2MICIN CVBS1 ETH OABR1 HW_NAV RAM-2GB BT USB1)
00005D1E Nav ECE 07DB (DAB CD MOST USB2 2MICIN CVBS1 ETH OABR1 HW_NAV RAM-2GB BT USB1)
00005D27 Med US 13F0 (SDARS IBOC USB2 WLAN 2MICIN CVBS1 ETH OABR1 RAM-2GB BT USB1)
00005D20 Med CHI 2250 (USB2 2MICIN OABR1 BT USB1)
00005D21 Med CHI 23D0 (USB2 2MICIN CVBS1 ETH OABR1 BT USB1)
00005D22 Med CHI 23F0 (USB2 WLAN 2MICIN CVBS1 ETH OABR1 RAM-2GB BT USB1)
00005D23 Nav CHI 27F0 (USB2 WLAN 2MICIN CVBS1 ETH OABR1 HW_NAV RAM-2GB BT USB1)
00005D25 Nav CHI 2632 (CD USB2 WLAN OABR1 HW_NAV RAM-2GB BT USB1)

[nvidia-smi]

Hi, I'm going through the same process and I just updated the VO to include 6CP using bimmerutility (should it be necessary I can also do it on Esys) and then VO coded the headunit option.

I'm now going to wait for a few days to see if anything shows up on my connected drive. Do you have any of the following options in your FA: 6NW and/or 6WD?

How long did it take for you to see the changes online? ty

[mrpingu]

I don’t know but can be up to 2 weeks. I coded, and then only checked 2 weeks later. Should be enough with BimmerUtility.

I don’t have 6WD or 6NW.
But I have: 6AC, 6AE, 6AK, 6AM, 6AN, 6AP, 6NS, 6UP

[nvidia-smi]

I see! Did you also have a Connected Drive Services (CDS) subscription active at the time? In Canada they charge 120/year to have CDS that includes RTTI, Alexa, Map updates, and BMW apps. So I am now wondering if I need to also have an ongoing subscription for the VO to get updated on the BMW servers.

[mrpingu]

No active paid services but I did pay for USB-map update once. I think black friday 2023, don’t remember if it was active at the time of coding.

What you can try is to send a command to your car via the app and press update BMW services in the headunit. This might trigger a sync with BMW servers.
Otherwise Connect the car to an paid / online official ISTA. But that’s meaning, take it for service to the dealer or BMW specialist.