PDA

View Full Version : CAS3 VIN Change



88diablo
12th February, 2020, 06:54 PM
Hi, could someone change the VIN in this CAS3 dump and correct checksum. I need the Vin edititing to WBAVC12010VC13543 please.

droidwayne65
12th February, 2020, 07:45 PM
There ya go.

88diablo
12th February, 2020, 08:14 PM
I already tried like that, from what I’ve read it needs checksum correcting but I don’t know how myself.

raimi.s
12th February, 2020, 08:55 PM
Here you go :cheers:

88diablo
12th February, 2020, 09:11 PM
Still no good, VIN show as YYYYYYYYYYYYYYYYYY still.

droidwayne65
12th February, 2020, 09:11 PM
I already tried like that, from what I’ve read it needs checksum correcting but I don’t know how myself.
Hmmm...I think that's the correct checksum. Sum % 256, no?

88diablo
12th February, 2020, 09:29 PM
I didn’t see any change on your file other than the vin itself?

Chriz123
12th February, 2020, 09:37 PM
for all people the vin is looking good, except you... what exactly is the problem, and wich tool shows you YYYYYYYYYYYYYYYYYY

88diablo
12th February, 2020, 09:43 PM
VVDI2 and Lonsdor both show correct VIN with original file but scrambled nonsense on any corrected vin and then once taken out of the car and bench read again the car has changed the vin to all FF

kiszka
12th February, 2020, 09:48 PM
for all people the vin is looking good, except you... what exactly is the problem, and wich tool shows you YYYYYYYYYYYYYYYYYY
extremely
-----------------------------------------------------------

Here you go http://www.digital-kaos.co.uk/forums/images/smilies/cheers.gif
VIN looks bad unfortunately
--------------------------------------------------------------

VVDI2 and Lonsdor both show correct VIN with original file but scrambled nonsense on any corrected vin and then once taken out of the car and bench read again the car has changed the vin to all FF
tell me this car is working or dead
give report whether it works

88diablo
12th February, 2020, 10:48 PM
Original file reads fine but all others show yyyyyyyyyyyyyyyy

tomvleeuwen
12th February, 2020, 11:57 PM
I didn’t see any change on your file other than the vin itself?

Checksum just happens to be 00, does not mean he did not change it. Did you try droidwayne65's file?

88diablo
13th February, 2020, 12:01 AM
Yes I’ve tried them all.

doctore
13th February, 2020, 12:04 AM
tr it.......

doctore
13th February, 2020, 12:12 AM
:eek:wi have rebus here lollol

88diablo
13th February, 2020, 12:32 AM
Ill try tommorow, thanks for your help.

droidwayne65
13th February, 2020, 01:54 AM
Still no good, VIN show as YYYYYYYYYYYYYYYYYY still.

Dunno what to tell you.... Unless the apps are treating it as a CAS3 file.

kiszka
13th February, 2020, 09:36 AM
Ill try tommorow, thanks for your help.

I don't know, you have to find it yourself
what you do wrong
BMW is a car highly technologically advanced
and I see you don't understand him at all


can not provide assistance if the other side can not do

88diablo
13th February, 2020, 05:43 PM
The reason this needed sorting was that someone had put part ecu kit on car of ECU CAS and key to get it running. The vin mismatch was causing tamper dot and ABS faults. I just wanted to edit VIN in new cas to clear errors. With all those files as soon as I put in car it changed the VIN to all FF in the dump. In the end Ive sorted this by changing VIN diagnostically and now all is good. For interest I have re read the now corrected CAS on the bench and uploaded if it helps anyone.

weld88
13th February, 2020, 06:32 PM
Interesting... a special case because the VIN CS = 00

MCU wants to see CS=0A for data with CS = 00

Check any area that is zero filled in the CAS... clearly CS = 00 but in eeprom correct CS will be 0A

88diablo
15th February, 2020, 01:38 AM
Sorted now. Thanks

droidwayne65
15th February, 2020, 02:59 AM
Sorted now. Thanks
??? You waved a wand, or maybe said a few incantations? :biggrin:

88diablo
15th February, 2020, 10:22 AM
??? You waved a wand, or maybe said a few incantations? :biggrin:

No I just did it diagnostically.

z335g
16th June, 2022, 07:28 PM
Hi just reviving an old thread here;

I had a water damaged DME so swapped a used DME and CAS into the car.

Ive pulled Eeprom from old CAS.

I have also pulled Eeprom from new CAS.

Where will I find the VIN checksum in the Original CAS eeprom dump? I can see the VIN there. I want to take the VIN from my old CAS and edit the EEprom dump of the new cas and re upload.

Can anyone help me please?

jromanc78
21st June, 2022, 09:24 AM
can anyone help. im changing the Vin in my cas3+ . MILES RESET OK, long Vin changes, but I can't get short Vin to change and winkfp won't update with these errors:


[14:59:24.657] [2022-06-16] [--] 1020 Error COAPIKF.CPP coapiKfInit 31
[14:59:24.657] [2022-06-16] [--] File could not be opened for reading info.eng


[14:59:56.295] [2022-06-16] [<WinKFP Tool 32B] 3025 Error KFCONF.CPP CKfConf::GetSgMemberFromLongName 3
[14:59:56.295] [2022-06-16] [<WinKFP Tool 32B] SgMember not found KONV.TMP02 nicht in der Datei ..\DATA\konv.tmp02\KFCONF10.DA2 gefunden


================================================== ==============================
[15:00:06.351] [2022-06-16] [<WinKFP Tool] 7006 PABD/CABD CAS260 SetEcuAdr 1215
[15:00:06.351] [2022-06-16] [<WinKFP Tool] Start - EDIABAS IFH-failure (10…59, except IFH-0003 and IFH-0009) 10FLASH, FLASH_PARAMETER_SETZEN (0x40;2;18;1;Asymetrisch): IFH-0018: Initialization error


[15:00:26.347] [2022-06-16] [<WinKFP Tool] 7006 Error COAPI2.CPP coapiRunCabd 6
[15:00:26.347] [2022-06-16] [<WinKFP Tool] Start - EDIABAS IFH-failure (10…59, except IFH-0003 and IFH-0009) SET_ECU_ADDRESS


[15:00:26.350] [2022-06-16] [<WinKFP Tool] 7006 Error COAPIKF.CPP coapiKfSetGlobalPabdSgbdEcuAddr 5
[15:00:26.350] [2022-06-16] [<WinKFP Tool] Start - EDIABAS IFH-failure (10…59, except IFH-0003 and IFH-0009) Run SET_ECU_ADDRESS Job


[15:00:56.180] [2022-06-16] [<WinKFP Tool] 3025 Error KFCONF.CPP CKfConf::GetSgMemberFromLongName 3
[15:00:56.180] [2022-06-16] [<WinKFP Tool] SgMember not found KONV.TMP02 nicht in der Datei ..\DATA\konv.tmp02\KFCONF10.DA2 gefunden


================================================== ==============================
[15:01:38.883] [2022-06-16] [<WinKFP Tool] 7006 PABD/CABD CAS260 SetEcuAdr 1215
[15:01:38.883] [2022-06-16] [<WinKFP Tool] Start - EDIABAS IFH-failure (10…59, except IFH-0003 and IFH-0009) 10FLASH, FLASH_PARAMETER_SETZEN (0x40;2;18;1;Asymetrisch): IFH-0018: Initialization error


[15:01:58.877] [2022-06-16] [<WinKFP Tool] 7006 Error COAPI2.CPP coapiRunCabd 6
[15:01:58.877] [2022-06-16] [<WinKFP Tool] Start - EDIABAS IFH-failure (10…59, except IFH-0003 and IFH-0009) SET_ECU_ADDRESS


[15:01:58.880] [2022-06-16] [<WinKFP Tool] 7006 Error COAPIKF.CPP coapiKfSetGlobalPabdSgbdEcuAddr 5
[15:01:58.880] [2022-06-16] [<WinKFP Tool] Start - EDIABAS IFH-failure (10…59, except IFH-0003 and IFH-0009) Run SET_ECU_ADDRESS Job