So my frm kicked the bucket a few months back and I replaced it with a used unit. I just plugged in the newer unit and most of my functions were restored(windows,fog lights etc.) but I need to change the VIN and VO to match what my car originally had. The problem I'm having is getting the old VIN to change to my original. I used NCSexpert to get my VIN with checksum and then went into tool32 and ran frm_70.prg and placed my full 18 digit VIN into the argument line and executed the job c_fg_schreiben. When I went back to NCSexpert the frm VIN had not changed at all. I then decided to give Winkfp a try and within comfort mode I chose frm2 and entered my VIN but the text line is only long enough for 17 digits. So i tried it without the checksum and it it said it succesfully flashed the frm. Now when I check the frm VIN in NCSexpert it still hasn't changed. I've attempted both programs several times with the same result and am pretty much stumped. Has anyone else had problems changing their VIN with tool32 and Winkfp?

 

Modules are coded to the car so getting one used will not work correctly in your car and you won't be able to change the vin to match your car.

 

That is partially correct. The modules are coded to the vehicle's VO(vehicle order) and their VIN. These can be reprogrammed via tool32 and NCSexpert. My question wasn't whether or not it could be reprogrammed but rather why I can't get tool32 or Winkfp to change the VIN accordingly.

 

I'm having similar problems.. did you figure this out?
Mine is Kombi related.. shows correct vin when queried but incorrect vin at tach

 

false! I programmed and change almost all of the module on my MINIs with the exception of the CAS and DME.

 

i use Winkfp and NCS expert to the get the coding and programming done. you need Ediabas 73 and the latest SPDatens.

Do you also have INPA"?

 

INPA v5.0.6
ISTA/P 3.56.3
WinKPF v5.3.1 (SP_Daten_V59)
NCS-Expert v4.0.1 (SP_Daten_V59)

I started a new thread..
https://www.northamericanmotoring.co...pf-update.html