Hello, i've got a little problem with a CAS2, whether possibly a key problem or corrupt eeprom, and was hoping someone here could help me to fix it.
I'll tell the whole story from the beginning to help you understand.
A customer given me a CAS2 module to add a new remote key, as they only have the plastic valet type transponder key which is put in an adapter to slot in the dash.
I've hooked up the CAS module to VVDI2 using the CAS plug adapter, and it connects fine. I like to make backups where possible before doing any work. So I read the eeprom data several times in VVDI2 and compared the files - there were differences each time, so i reverted to using VVDI-prog to read the eeprom data and flash too while i was hooked up. Comparing several reads, the file were showing the same... all good.
Now that i had the backups, i proceeded to add a key using VVDI2 'cas key learn'.
The customer has put the CAS module back into the car, both the original key and new key start the engine fine, however the new key remote doesn't work the locks (i've had the customer check the key battery is fitted correctly). I've not got access to the car right now, but using the original eeprom backup i took before starting work i've loaded it into the VVDI2 'file make key' function and it throws up an error "CAS eeprom maybe damage. The made dealer key may can't start engine". The VIN, mileage, key frequency and key code etc all show fine on the display, however there must be something in the file corrupted (i've attached a screenshot of the error). Can anyone check the attached dumps to identify what may be corrupted, and can help repair the file?
Is it likely the corrupt eeprom is the culprit for the remote fault, or is it more likely a key problem (Bought from a big UK supplier). Are there any other things you recommend to check? I'm trying to make some plan of attack just now before organising to tackle the car again.
Thanks in advance for your support
P.S. I've posted this here instead of the VVDI2 support thread as i don't think this something exclusive to VVDI2. To me it seems either a key problem or the eeprom is corrupted as indicated from my original backup.
Bookmarks