Quote:
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.
TL  R: 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.