View Single Post
      11-20-2012, 11:05 PM   #1256
shawnsheridan
Lieutenant General
shawnsheridan's Avatar
United_States
2843
Rep
15,602
Posts

Drives: 2016 650i GC M-Sport
Join Date: Feb 2010
Location: Houston, TX

iTrader: (0)

Garage List
Quote:
Originally Posted by Yobyot View Post
For those of us who still don't quite understand the intricacies of coding, what does "removing" and "adding" a CAFD file mean.

Does the removed file represent a control unit or option that is no longer supported? What if your car has one of the now-unsupported devices?

On the other hand, does adding new files mean that there's new hardware that isn't in an older car that is now codeable? Or, maybe that existing hardware now has newly exposed functionality?

I often see people asking here for "missing" CAFD files. Does that mean they have hardware they cannot access for coding until they acquire the file?
Once released, I have no idea why BMW ever removes a CAFD file from subsequent releases, but for some reason, not often, some drop out. The affected modules are still supported, just not at that firmware version. If you have a module that is currently using an orphaned CAFD, you need to either find the CAFD file from an older PSdZData release, or somehow get the car programmed so that module gets it's firmware updated. The latter is better, but is never the easiest.

The added CAFD's are for existing modules with newer firmware, or entirely new modules for new Chassis or Model Year changes.

If you are missing a CAFD, E-Sys [C012] error, you can not code the module.
__________________

2016 650i GC M-Sport w/ 20" 373M Wheels; Alpine White; Individual Opal White Full Merino Leather; Gray Poplar Wood Trim
Anthracite Alcantara Headliner; Ceramic Controls; Executive Package w/ B&O Sound System; Integral Active Steering, etc.

Last edited by shawnsheridan; 11-20-2012 at 11:20 PM.