[dy63]

so tonight i upgraded to FRM2 in my 330d 2006 build as i wanted welcome lights. everything works...xenons work fine. welcome lights etc work

i noticed my electric mirrors dont work anymore and they dont fold etc so it needs to be coded

i have done bits of coding such as basic ncs expert digital speedo etc stuff like that.

i have seen that i need to upgrade it in winkfp . can anyone tell me in detail how to do this? i opened winkfp - tried to enter my VIN but my vin is 1 digit too long for it to allow me to enter anymore?

also . how do i change production date in NCS?

please help!

- Just tried opening WINFKP. i select comfort mode. enter vin. but it does not recognise my ZUSB number or dont show any ECU options when i click upgrade ZUSB?

[charles.soori]

Originally Posted by cupraraj

so tonight i upgraded to FRM2 in my 330d 2006 build as i wanted welcome lights. everything works...xenons work fine. welcome lights etc work

i noticed my electric mirrors dont work anymore and they dont fold etc so it needs to be coded

i have done bits of coding such as basic ncs expert digital speedo etc stuff like that.

i have seen that i need to upgrade it in winkfp . can anyone tell me in detail how to do this? i opened winkfp - tried to enter my VIN but my vin is 1 digit too long for it to allow me to enter anymore?

also . how do i change production date in NCS?

please help!

- Just tried opening WINFKP. i select comfort mode. enter vin. but it does not recognise my ZUSB number or dont show any ECU options when i click upgrade ZUSB?

use tool32 to change vin. then you need to copy vo from cas to frm and default code frm after that. change date 03/07 as well .
the extra number you see in the vin checksum enter all that into tool32 .

[charles.soori]

top of my head to how to change vin using tool32

open frm_89.prg
fg_schreiben to write vin

[Sensible_]

Yep,

+1 nice instructions @charles.soori

[dy63]

can anybody tell me how to change vin in tool 32 in step by step guide?

[Sensible_]

See here:

https://www.scribd.com/mobile/doc/237495940" rel="" target="_blank">http://<a href="https://www.scribd.c.../237495940</a>

But choose the frm prg file...


Also, when you enter your vin you must use FULL vin. Which is VIN number with a checksum at the end. You can see you full vin in NCSexpert when you do any coding.

[dy63]

Originally Posted by Sensible_

See here:

https://www.scribd.com/mobile/doc/237495940" rel="" target="_blank">http://<a href="https://www.scribd.c.../237495940</a>

But choose the frm prg file...


Also, when you enter your vin you must use FULL vin. Which is VIN number with a checksum at the end. You can see you full vin in NCSexpert when you do any coding.

the web page is not available

[Sensible_]

Ok,

Well it's very simple.

1. Open tool32
2. Plug in cable
3. Press F3 and choose the frm87.prg or whatever frm you have (see from INPA uif)
4.Select job c_fg_schrieben
5. Enter your FULL vin (including checksum) into arguments field
6. Execute job

You can check the vin using job 'c_fg_lesen'

Once done use NCSEXPERT to copy your CAS FA string to FRM / change date then code to default with expertmode.

[WaLLy350GT]

Originally Posted by cupraraj

the web page is not available

Here you go http://www.scribd.com/doc/237495940/Tool32-VIN-Write

[dy63]

thanks! i think i know how to do the tool32 bit now to write the VIN. how do i copy my CAS vo to my FRM VO? also how do i change production date? appreciate all the help!

[Sensible_]

Here, taken from another forum but it's a good explanation so I won't bother repeating in my own words

Step 2 means you won't need to use tool32 at winkfp can set vin also...

The basic steps:
1) Remove FRM, install FRM2.
2) Use WinKFP to program the module, make sure to enter your VIN-number before programming.
3) Switch to NCS-EXPERT. Get your Vehicle Order from the CAS module (as we are unsure of what the FRM2 module contains.
4) Write the Vehicle Order to module "FRM" using job "FA_WRITE"
5) Go back to the main menu (or restart ncs-expert) and get the vehicle order from the "NFRM" module. Make sure NFRM returns YOUR VIN and YOUR VO. We want the VIN (FG) and VO (FA) to be the same in both CAS and NFRM.
6) You now need to do the trick described by 4711 a couple of posts back, i.e. change the production date in the VO to at least #0307. If you don't do this, ncs-expert will not list NFRM (=FRM2) in the "Process ECU"-list and you won't be able to code it. Change the VO using the "Enter FA" option - remove your production date and enter #0307 (meaning march 2007).
7) Now click "Process ECU" and select "NFRM"

Then just code to default with expert mode.

[dy63]

Originally Posted by Sensible_

Here, taken from another forum but it's a good explanation so I won't bother repeating in my own words

Step 2 means you won't need to use tool32 at winkfp can set vin also...

The basic steps:
1) Remove FRM, install FRM2.
2) Use WinKFP to program the module, make sure to enter your VIN-number before programming.
3) Switch to NCS-EXPERT. Get your Vehicle Order from the CAS module (as we are unsure of what the FRM2 module contains.
4) Write the Vehicle Order to module "FRM" using job "FA_WRITE"
5) Go back to the main menu (or restart ncs-expert) and get the vehicle order from the "NFRM" module. Make sure NFRM returns YOUR VIN and YOUR VO. We want the VIN (FG) and VO (FA) to be the same in both CAS and NFRM.
6) You now need to do the trick described by 4711 a couple of posts back, i.e. change the production date in the VO to at least #0307. If you don't do this, ncs-expert will not list NFRM (=FRM2) in the "Process ECU"-list and you won't be able to code it. Change the VO using the "Enter FA" option - remove your production date and enter #0307 (meaning march 2007).
7) Now click "Process ECU" and select "NFRM"

Then just code to default with expert mode.

thanks man. i seen this too but need to get all the info together on step by step what to do:

so far i think i need to:

1- install FRM2
2- open winkfp. enter vin. click update ZUSB and get my ZUSB from INPA for FRM
3- then click execute job or whatever it says

has this now wrote my vin to the FRM? or do i need to flash first or after or clear the current vin on the frm?

[Teq]

You can perfectly write your vin with winkfp.
Tool32 is often used when ncsexpert displays the old vin.

[dy63]

Originally Posted by Teq

You can perfectly write your vin with winkfp.
Tool32 is often used when ncsexpert displays the old vin.

i think i will use tool32 as it seems to be easier to do on there
would you agree?

[Sensible_]

The basic steps are:

1. Install FRM2
2. Change FRM2 VIN to yours. Flash FRM2 with winkfp comfort mode with your vin. Or use tool32 to change vin as above.
2.5. Verify vin change with tool32.
3. Copy CAS VO (FA) to FRM with NCSexpert.
4. Change date with NCSexpert.
5. Code to default with NCSexpert.

Exact instructions for each step are frequently discussed and freely available from most of the codon forums

[dy63]

Originally Posted by Sensible_

The basic steps are:

1. Install FRM2
2. Change FRM2 VIN to yours. Flash FRM2 with winkfp comfort mode with your vin. Or use tool32 to change vin as above.
2.5. Verify vin change with tool32.
3. Copy CAS VO (FA) to FRM with NCSexpert.
4. Change date with NCSexpert.
5. Code to default with NCSexpert.

Exact instructions for each step are frequently discussed and freely available from most of the codon forums

dont mean to harrass you

i have looked on the net but i cannot find how to copy cas vo to frm or change the date aswell

[Sensible_]

This is the best guide I've found with step by step instructions:

http://bmwxserie.blogspot.co.uk/2014...orial.html?m=1

Hope it helps, just ignore the AHL headlight stuff.

Also, if it gets confused the NCSexpert functions FA_WRITE and FA_SCHREIBEN are the same. 2nd is German version.

The date is always first line in the VO. You need to change yours to #0307 for NFRM (FRM2). But you don't need to FA_WRITE this. It is ok just to simulate it by adding it to the VO. When the VO dialog box closes it will update the VO at that time in the NCSexpert program and then you can code it NFRM. You can FA_WRITE it of course but I've heard of this causing some problems with another module. Better still, get FRM3 and it bypasses date automatically.

[dy63]

Originally Posted by Sensible_

This is the best guide I've found with step by step instructions:

http://bmwxserie.blogspot.co.uk/2014...orial.html?m=1

Hope it helps, just ignore the AHL headlight stuff.

Also, if it gets confused the NCSexpert functions FA_WRITE and FA_SCHREIBEN are the same. 2nd is German version.

The date is always first line in the VO. You need to change yours to #0307 for NFRM (FRM2). But you don't need to FA_WRITE this. It is ok just to simulate it by adding it to the VO. When the VO dialog box closes it will update the VO at that time in the NCSexpert program and then you can code it NFRM. You can FA_WRITE it of course but I've heard of this causing some problems with another module. Better still, get FRM3 and it bypasses date automatically.

That links great thanks. in tool32 i have frm70.prg and frm87.prg. which one do i use?

[dy63]

i had a look in INPA and this is what i found. seems like my FRM has already a date of 03/07?



i could not click the Footwell Module Driver FRM_87 above but it let me go into Footwell Module Driver II (from 03/07)

this is the error i got when going into Footwell Module Driver FRM_87


After i got access into FRM2 03/07 this is the information screen. does this mean i need to select FRM_70 in tool 32?


Look at the date of manifacture showing as 2008!


read the error memory in the FRM and this came up again saying FRM_70 so can someone tell me if it is FRM_70.png in tool32 and not FRM_87?


Finally..

This is my UIF print out. guy up the top said get my number or find out from this page but doesnt seem to say? also WINKFP does not recognise my ZB number that my FRM says when i go to update it and enter it after i put my vin number in


can anyone help why WINKFP wont recognise my ZUSB number?

[Sensible_]

Ok, so...

FRM2 = FRM_70.prg

So yes, when changing vin in tool32 select that prg file.

The date you see of 03/2007 is for the FRM2 which is why we must change the Vehicle Order (VO or FA in German) to reflect this.

The VO is like the DNA of your car...

Hope that helps.

-------

Re winkfp forget manually selecting zusb numbers. The number you see in INPA is current. If your date files are newer that number won't exist in that set of datens.

Instead choose comfort mode, enter vin and just select the ECU family. In your case FRM70.

If you are interested in how it works I'll explain... Ok, well I'll explain anyway....

BMW use 3 numbers to identify correct firmware...

ZB-NR - Like your part number
HW-NR - Hardware number and winkfp *.0pa file
SW-NR - Software number and winkfp *.0da file

Winkfp uses a DAT file for each module which links the current hardware and software numbers to the current zusb number.

[dy63]

Originally Posted by Sensible_

Ok, so...

FRM2 = FRM_70.prg

So yes, when changing vin in tool32 select that prg file.

The date you see of 03/2007 is for the FRM2 which is why we must change the Vehicle Order (VO or FA in German) to reflect this.

The VO is like the DNA of your car...

Hope that helps.

-------

Re winkfp forget manually selecting zusb numbers. The number you see in INPA is current. If your date files are newer that number won't exist in that set of datens.

Instead choose comfort mode, enter vin and just select the ECU family. In your case FRM70.

If you are interested in how it works I'll explain... Ok, well I'll explain anyway....

BMW use 3 numbers to identify correct firmware...

ZB-NR - Like your part number
HW-NR - Hardware number and winkfp *.0pa file
SW-NR - Software number and winkfp *.0da file

Winkfp uses a DAT file for each module which links the current hardware and software numbers to the current zusb number.

i am getting an error when using tool32

EDIABAS Fehler 28 : IFH-0018: INITIALIZATION ERROR

i selected FRM_70 but nothing came up in jobs section and seen that error

[Sensible_]

That is an EDIABAS error. Make sure no INPA / NCSEXPERT etc window is running. It should work, if not try winkfp.