Content moved to separate threads
Fxx, Ixx, & Gxx Series Coding:
Fxx, Ixx, & Gxx Series Coding:
Yes, entirely. HU_CIC is for cars with 609 Nav Pro. HU_ENTRY is basic Head Unit for cars with no Nav. You will not be able to do much with ENTRY Head Unit. Sport Displays will not work, so forget them.By the way, are HU_ENTRY and HU_CIC two different things? Because I have HU_ENTRY as the module but when I get into the CAFD of HU_ENTRY, I see the module's name as HU_CICHB. What hardware do I have?
For F15 it is:Shawn,
A really dumb question as I get ready to help someone with his X5, but can't seem to find the answer.
I know that for an F30, you use F20 in E-Sys, but would you be kind enough to provide some kind of table that "translates" BMW model for E-Sys coding, particularly X5?
Also, does one use the E-Sys listing without _DIRECT?
Thank you very much
Yes, but Diagnostic Address (hex) = 63 (99 in Decimal).That is my car vin, so I have to Expert Mode => FSC Extended module => WriteDataByIdentifierVIN,
Diagnostis Address (Hex) > 0x30??
So write VIN 0F25819 back to NBT, and FSC Codes should be fixed.I don't know...
The NBT vin must be WBAWY310900F25819, I have updated NEXT maps with this vin (even I have the archives I used to update) so I don't understand what have I got to do to active FCS.
I wrote if it was possible a wrong vin to look for an explication, but I'm pretty sure this is the correct donor vin, and it has navigation, voice control... even apps.
So, maybe Am I doing something wrong? :dunno:
But It's write, I follow these steps: Expert Mode => FSC Extended module => WriteDataByIdentifierVIN,So write VIN 0F25819 back to NBT, and FSC Codes should be fixed.