can someone check cas3 eeprom/flash

[cniksor]

here is eeprom and flash i read on a cas3 module i picked up from the local yard. just curious to check if VVDI prog is reading correctly. i did make a key via bench and works, but i checked eeprom on cas3+ editor and shows errors, but is this because that program only for cas3+ and this cas is just cas3? thank you for any help.

[3inferno3]

here is fixed.. but write vin ,keys manualy . try read by xprog to campare both eeproms

[RG550]

Hello,
Are you sure that module is cas3?
Maybe cas2?
What is the mask on motorola you read, 2K79X ?
VIN: WBANE53527CY04690
KM: 237215 km


Key cutting code:HA00016741
CAS remote control frequency:315Mhz

[3inferno3]

Sorry DG550 u have right! in cas edit i have info - cas2 - vin -WBANE53527CY04690 isn - B9 F0 . It isn't cas3+ eeprom

[cniksor]

yes cas3 taken from a 2006 e60 , OL01Y. not customers vehicle. but when i see a cas modules at the local yards i like to grab and read to keep files handy/share as im learning more and like to on spare parts. this one i read like i normally do, but since this is cas3 and not + i was curious is cas3+ editor is accurate or is only for cas3+ specifically.

i made key with cgdi bench, and tested it on my bench setup with cluster and it turns on fine like i normally check my keys. so just wanted a 2nd opinion is it is correct, just curious if reading correctly on vvdi

[droidwayne65]

yes cas3 taken from a 2006 e60 , OL01Y. not customers vehicle. but when i see a cas modules at the local yards i like to grab and read to keep files handy/share as im learning more and like to on spare parts. this one i read like i normally do, but since this is cas3 and not + i was curious is cas3+ editor is accurate or is only for cas3+ specifically.

i made key with cgdi bench, and tested it on my bench setup with cluster and it turns on fine like i normally check my keys. so just wanted a 2nd opinion is it is correct, just curious if reading correctly on vvdi

If you come across a 0L01Y, chances are it's more CAS2/CAS3 and definitely not CAS3+. Your file, with it's two-byte ISN, B9F0, and key data located in the 0200h~ area is closer to CAS2 than CAS3.