I am once again exploring working with BMW FEM.
There is news!!! After the last update, the problem with creating a service eeprom BMW FEM has gone away!!! Tested on many eeprom with FEM 95128 and BDC 95256
I have a test FEM:
1) reading the key data
2) reading the backup coding
3) reading eeprom 95128 using VVDI PROG
4) copy the read data of eeprom 95128 to Lonsdor, make a new service mode eeprom (previously, an error occurred at this stage - now all ok)
5) copy new service eeprom to PC and write new service eeprom using VVDI PROG
6) programming FEM. The process consists of two parts. After completing 100% the first part, FEM is click and get an error: "Communication connection failed. Code: 02. Make sure ignition is on and the OBD connector is properly connected to car." The programming process in Lonsdor seemed very long compared to VVDI2 and CGDI. Tried to re-program, however, the device did not allow to perform. Thought FEM was already a corpse
There were no more options and I proceeded to the next point.
7) write original eeprom using VVDI PROG
8) restoring the backup coding
Reading the key data and lo and behold he gets in touch and gives all the information. Programming the new key - all OK. Reset mileage - all OK.Since this is a test unit FEM, I can't test it on a car
What is the reason for the programming error? Or Lonsdon performs 2 parts of programming and shows 100%? Then what is the error Code: 02 ?
Bookmarks