When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
FRM2 replaced with FRM3 - can't access with NCS Expert
Hi all, I purchased a MINI Clubman S and have been playing around with coding some modules, over the past year. In 2015 the FRM2 was replaced (by a reputable MINI service shop) with a new FRM3 module. It works great in the car (no errors) but I can not access it with NCS Expert, but I can with INPA or Rheingold to review the module and clear faults.
So I am wondering where to begin. When I look in INPA I see under the "functional jobs" option that when I read the UIF that most of the modules are missing the VIN, some have a different VIN and some just have strange Y characters, so I'm not sure what to think of that.
Never the less, I know the car originally came with FRM2 module but now INPA states the PN is for an FRM3.
I have daten files for an FRM3 in my same directory as my FRM2, so I'm wondering why NCS Expert will not allow me to access the FRM to recode a few options. "Coding 2041 : wrong ECU coding index".
I've not opened WinKFP to compare the current firmware to potential updates but would ASSUME that the module is running latest since it was installed in 2015 (well after last verson of R55/R56). Anyhow, does anyone know if this error is usually because of missing sp-daten files or do I need to change something in the VO (production date, as example, to match with date of when FRM3s began being used)?
Thanks for any support.
Tonight, I'm hoping to try to open NCS Expert, with Expert mode and Manipulation turned off, try coding the FRM3 back to factory for tha module based on my factory VO (nothing has been swapped in car, so that shouldnt screw anything elswe up), but I'm curious if that will help this issue.
wait, after some research, does the error message in NCS Expert mean my car's FRM3R module has coding index 37 (therefore .C37) and yet my daten files only go up to .C35 for an FRM3R?
So, if I use WinKFP to factory reset my FRM3R and I'll reinstall the VIN (just to be sure, as its not showing up in INPA with the module), will that factpry reset bring it back to the first version of daten files available for the FRM3R (I believe is the .C31 index)? and then I could keep playing with C33 and C35 till I'm happy with the coding I want for that FRM3R module?
09-06-2022, 10:10 AM
