[scanboy]

Not so much of how to code a new FRM3 to work with the car, this part has been done by the dealer. I need help on what needs to be change on my laptop to start coding the new FRM3.

The part no. of the new FRM is 61-35--9-390-491, which I believe is FRM3. My computer was setup to code my original NFRM, worked fine. After the upgrade to FRM3, I still only see NFRM after choosing E89->CAS, and when I pick NFRM to read ECU, error popped up. I'm guessing there's something I need to change on my laptop, but don't know what. Would the software recognize that there's a new FRM3 and show FRM/FRM3 instead of NFRM in the module list? Please help.
Thanks.

[cryptomit]

only FRM1 is recognized as FRM
all others FRM2 and FRM3 are shown as NFRM in NCSEXPERT.

Your software is fine.

[scanboy]

But y can't I read the NFRM ecu? How do I make sure that the NFRM I see in the list is the new FRM3? does the software automatically recognize the new hardware and knows how to read it?

[Sensible_]

Originally Posted by scanboy

But y can't I read the NFRM ecu? How do I make sure that the NFRM I see in the list is the new FRM3? does the software automatically recognize the new hardware and knows how to read it?

So, you want to be sure dealer has installed FRM3?

Just physically inspect the footwell module and read label...it will take 30 seconds....

If still not sure read UIF with INPA and compare...but better to visually inspect the module and read label on it.

[Levanime]

change prod. date in FA before reading/coding

[KJMotorsport]

What version daten files do you have?

[scanboy]

Originally Posted by Levanime

change prod. date in FA before reading/coding

I would think that this has been done by the dealer. You are talking about change the prod. date of the FRM3 right? Dealer programmed it before getting the car back, everything works, I just can't code all the features I want to the new FRM3, so was thinking must be software on my computer.

Originally Posted by KJMotorsport

What version daten files do you have?

I think it should be pretty old, do I just replace the all the directories if I get new version?

[Sensible_]

Production date does not need to be changed for FRM3.

Only FRM2. And that is only so that NCSExpert can see there is NFRM and not FRM.

With FRM3 this is done automatically. Anyway, dealer would just have ISTA and run a retrofit program.

It definitely sounds like you need latest Daten files of dealer updated your I level.

[scanboy]

Originally Posted by Sensible_

Production date does not need to be changed for FRM3.

Only FRM2. And that is only so that NCSExpert can see there is NFRM and not FRM.

With FRM3 this is done automatically. Anyway, dealer would just have ISTA and run a retrofit program.

It definitely sounds like you need latest Daten files of dealer updated your I level.

Ok, I'll update the daten and see what happens. Does it matter which version or the latest would work? If I request for the model year (2007) wouldn't the daten files be the one that works with FRM2 (my stock FRM)? I don't understand how these daten files work.

[KJMotorsport]

Originally Posted by scanboy

Ok, I'll update the daten and see what happens. Does it matter which version or the latest would work? If I request for the model year (2007) wouldn't the daten files be the one that works with FRM2 (my stock FRM)? I don't understand how these daten files work.

I had an issue where V49.1 datens I had with my standard tools did not interact with the FRM3 module on my E82 (Build date 07/10). Kept appearing with an CABD error but cannot remember the exact error code atm.

I updated to V55 datens and that still had the same issue. Only when I updated to V59 thanks to wildcatcrazy's request file on here did I finally gain access to the FRM3.

[scanboy]

Originally Posted by KJMotorsport

I had an issue where V49.1 datens I had with my standard tools did not interact with the FRM3 module on my E82 (Build date 07/10). Kept appearing with an CABD error but cannot remember the exact error code atm.

I updated to V55 datens and that still had the same issue. Only when I updated to V59 thanks to wildcatcrazy's request file on here did I finally gain access to the FRM3.

Thanks for the tip and the v59 daten files .
Downloading ...