[kuno24]

"There is difference in 2013-7 and upper with modules than 2013-7 lower like kafas etc.."

ETK shows for KAFAS part nr 66 51 6822684 (old part nr 66 51 9281718) and production from 07/2012. I think, this must be KAFAS2.
Windshield picture with KAFAS2 https://cimg5.ibsrv.net/gimg/5series.net...257691.jpg
How handle KAFAS FSC-s, are described here https://www.bimmerfest.com/threads/undo-...407/page-3
Also read post #35
May be KAFAS FSC-s are located in KAFAS ECU, i dont know, where exactly.
https://www.realoem.com/bmw/enUS/showpar...Id=66_0315

[aleksandrw]

I level (factory) F001-12-11-502
I level (current) F001-17-03-505
Go to Esys, VCM, read I Level from Master, edit it (if needed, very important, that factory I Level was right), write back
Also write to backup
After this flash all modules (and off course code) or better, use ISTA for flashing.
If ESYS is not Your friend, then find who knows what to do. Simply play with this program is strongly prohibited.
Production date:28.11.2012

If Yo still have problem with KAFAS FSC, may be order FCS repair pack and solve problem with this. Without KAFAS collision detection ACC claims.
Also double check, that FA have all listed parameters, also paint and upholstery code.

hi! i-level factory that I used in esys was always F001-12-11-2012. Solved the KAFAS FSC issues.

---

hi did you also checked de date of manufacture/zeitkreterium when you was coding or flashing

I see that your car is from 28-nov-2012. but ISTA Says Juli-2013. Maybe there is difference in modules in date and the coding

There is difference in 2013-7 and upper with modules than 2013-7 lower like kafas etc..

Its a Guess.

Production date in ISTA is indeed 01/11/2012, but ISTA Construction date is 2013/07. Don't know what the difference between them is.

[aleksandrw]

Guys, thanks for the help. Your idea with the model year was the right one, it was just not about the firmware, but the coding. So everytime I flashed a module in the car the istep shipment I used was the correct one: 12-11-502 and everything was error free. So apparently that FA date was not affecting the firmware, but it was affecting the coding. So last night, I edited the FA and replaced 0713 (which was the date in the existing initial FA i discovered to have the wrong type key) with 1112, wrote it to the car then coded all the modules in the car and I was done with all the signal errors. 
Everything is working fine now, but I have a different issue, somehow related.

Although the car came with all 3 FSCs for kafas2 - 7e, be, bf, apparently there were some fake FSCs on it. I got a repair pack, but when I try to upgrade sc fwith stock fsc it tells me that I am trying to add older fsc than kafas, or something like that. 

Is there any way to "reset" the kafas so that it will accept my stock fsc? The fake fsc i am currently running are from a 2015 VIN. I already tried flashing kafas, but i get the same results.

thanks!

[Siki78]

I can give you fsc from 2016 and you can upgrade exist one. Or you will need to buy new one

[aleksandrw]

I can give you fsc from 2016 and you can upgrade exist one. Or you will need to buy new one

Are the 2016 FSC going to be for my vin and stay there even after using ISTA? Or are they the same as the fake 2015 fsc I have? I am asking because I am trying to get my 2012 FSCs back on the car, or FSCs that will not be removed by using ISTA. Ty!

[Siki78]

Like I write you put fake fsc or buy new one it is not possible to clean kafas2 like I know