[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.