I originally posted this in the "yes you can" sticky thread, but never got any responses. I'm reposting in a new thread hoping that the lack of response is because maybe the experienced coders no longer look at the sticky thread.

I followed the directions to update EDIABAS to avoid the faulty BEST version error, and was able to read FRM. Now I have some questions. I want to set the options to 1) not interrupt window roll up when the door is opened and 2) allow the fogs and high beams to be on simultaneously. In the spreadsheet, these are listed as:

1. FRM2: TUERAUF_STOP_MAUT (activ -> nicht_activ)
2. FRM2: FL_UND_NSW_NICHTGLEICHZ (activ -> nicht_activ)

So, when I press F4 to select the module to read, there is a FRM listed not a FRM2. When I select that module, the dialog box says:

ECU short FRM
CBD name: FRM2_R56.C08
CABD name: A_PL2FRX.IPO
SGBD name: FRM_70.PRG

So, is this FRM or FRM2 or what?

I read that module and it looks like it has the right stuff in it. I changed FL_UND_NSW_NICHTGLEICHZ to nicht_activ. However, there is not a TUERAUF_STOP_MAUT, but there is a FH_TUERAUF_STOP_MAUT_3R.

I decided to give those changes a try, so I coded both of these values and wrote the module back to the car. Neither change seems to have any affect. The auto-up for the windows still stops if I open the door, and the fog lights still turn off when I switch on the high beams.

I tried reading the module again to make sure the update was written. The values were in fact written, and the newly read data has some additional values that were not in the data when I read it the first time, these values are:

CBD_ZEICHN_INDEX - wert_01
INNENLICHT_ABSENKEN - wert_05
TIME_COLOR_CIRCLE - 5sec

Google Translate says:
ZEICHN = Draw
INNENLICHT ABSENKEN = Lower Inner Light
wert = worth

So coding experts, here are my questions:

1. Am I working with the right module?
2. Why does the name for that parameter not match?
3. Why don't the changes have any affect?
4. Where did the new values come from?

In case it matters, I followed the directions in the thread referenced above to update EDIABAS including updating the datens to V41. Any help or suggestions would be appreciated. I didn't have any problems doing coding changes in CAS, IHKA or SHD.

Thanks in advance.

 

What is the month/year build of your car?

 

It is a 2011. I'll have to look up the build month. I bought it off the lot. I think the dealer got it in the last quarter of 2010. What's the most reliable way to find out the build month? I assume there is a sticker or plate somewhere on the car.

 

The build month/year is in the door sill. FRM should be the correct module.

When you get the trace file output, make sure it is a small file that is JUST the output of that particular module (a couple of kilobytes), and not the "Big" list (that is like a 100+KB).

I have the FL_UND_NSW_NICHTGLEICHZ working fine on my car, and it should work fine on your LCI model. After writing the tracefile to the module, the module will do a quick reset to activate the changes. Maybe that didn't occur. Maybe a disconnect of the battery will help?

Have you done other changes to other modules successfully?

 

You should have an FRM3 for a 2011 model. FRM1 and FRM2 were discontinued some time ago.

 

I have successfully coded CAS so I can close the windows and sunroof from the fob, SHD so I have two-touch operation of the sunroof, and IHKA to disable automatic engagement of a/c when pressing auto button. I am quite confused why I am having problems with FRM. I'm pretty sure that the trace file is the smaller one for the specific module. Any comments about the additional data that shows up when I read the module after trying to code just the two changes, as described in my first post?

 

I wouldn't worry about the extra settings, your coding index may have changed arbitrarily (as I have seen mine report a different version a few times).

My vehicle started as the FRM2_R56.C08 but sometimes it shows up as C09 and C0A.

Did you try to set the double-flash hazard lights? That's another FRM setting I can think of off-hand that's easy to try out.

 

No, I didn't try that option because I really don't care about that one. I suppose I could give it a try when I get a chance just to see if it works and then undo it.

 

I checked my cable, and it does have pins 7 and 8 soldered together. I only sporadically see the error about not being able to read the VIN, so I don't think that's what is causing my problems with coding the FRM module. Does anybody think I need to try removing the connection between pins 7 and 8 for use with my 2011 MINI?

Also, in case it matters, my 2011 was was manufactured 09/10.

 

Bridging pins 7+8 together isn't required for any of the newer Mini's, and BMW has been repurposing Pin 8 for ethernet on newer cars. So just to be safe, I would remove the bridge between pins.

 

Sorry for the double post!!

 

Maybe you are just using too old datens! It happened to me when I flashed my FRM with WinKFP to the latest version (v40). If memory serves right, the module is identified as FRM3 after the flash. Now NCSEXPERT must also have the latest corresponding indexes for the modules, otherwise the changes you make in the trace files may be ineffective even if the names used are the same and even if the changes are stored. Basicly you may be changing the values at the wrong address because NCSExpert interprets the value with wrong coding index.

From the info you posted, your latest index is 8 from "FRM2_R56.C08"... I"ll check my configuration later and let you know if that is the latest index version

 

I have tried with V41 datens. Previously I tried with either V38 or V40, can't remember which. I've never seen anything written about indexes much less how to check them or update them.

 

Tigger,

Have you made any progress? I have a 2011 MCS and am having the same problem. The spreadsheet says that those FRM2 options have been done on a 2011, but I can't see the right module to get it done.

Side notes, I have successfully coded the CAS module to allow closing the windows from the fob. I am using the 7.2.0 version of EDIABAS with v41 datens, and I have already unsoldered pins 7 and 8 on my cable.

 

Try to update your module with WinFKP and then try to do this again...and try to do this with v.43 or newer.

 

Thanks for the reply, but I'm not sure what you mean. I have WinKFP 5.1.0 installed as part of the BMW standard tools install per the coding how-to guide.

I'm clueless as to how I'd go about updating the module. Which module, update it from what to what, and with what files?

 

Instead of upgrading the module, you can try to use an older FRM ECU file. If you followed the instructions for NCS, you know you copy the ECU files in the EDIABAS\ECU folder. What you need is a sufficiently old version of the ECU file (like v32).

 

I just tried v32 FRM datens yesterday. They didn't work for me. I guess I'm stuck with not being able to modify the FRM2

 

Just make sure of one thing - make sure you are using the right profile in NCS Expert. Maybe "FSW PSW MAN" or something else - if you are making changes and they are kind of "not taking", you might be in the wrong profile.

 

Using v32 is a horrible idea. Use v45 so you don't mess anything up.

 

The only v45 I can find is in the countryman section, but it's labeled as r56 Were can we find the v45 datens we need? I've google search on bmwcoding.com but could not find anything relevant. Thanks for your help Juppers!

 

Did you look in this forum?

https://www.northamericanmotoring.co...ert-diy-3.html

 

R56 chassis datens cover the R55, R56, R57, R58, R59 and R60 models (just like the E60 datens cover, the E60, E61, E63, E64).

 

lol, not since 2-3-12
Thanks strobey, I had a feeling they did, but you can't be too sure!

 

My BMW is a 2010 and uses the FRM3 module. It had to have v45 daten to even read it much less code changes. Chances are yur setup is too old for your car. Update to v45 or v46 and try again. FRM/FRM2/FRM3 are different versions of the same module. They control and define a lot of lighting characteristics, but offer additional features such as welcome lights, pathway lights, etc in the later versions.