The 2013 CM has a different electrical system for controlling folding mirrors. Up to 11/2012 it was controlled by separate ECU/module which was not connected with any of the car's systems. It was pure electrical control without any logic nor memory.

From 11/2012 the mirror's folding is controlled by other module (either FRM or JBE - I do not remember by heart). The communication between ECU and each mirror is via LIN protocol, so each mirror has a control module build in. That is this mirrors can be 'programmed' to fold in/out by the key fob. Moreover the passenger mirror may adjust in down position when reversing.

What Kimsc321 was refering to, was opening/closing windows with key fob (as on the video footage there are both mirrors folding and windows opening trigered by key fob).

So if you want to retrofit your 2011 CM with mirror folding by key fob you will need to get:
- new 2013+ wing mirrors
- new FRM or JBE module
- upgrade wiring
- program/code

 

Special thanks to Kevdog for this one!

Setting WELCOME_SCENARIO_ACTIVE to aktiv in FRM makes the ambient lighting color come on when you unlock the car and cycle once, then stop at the original color when the door is opened. With WELCOME_SCENARIO_ACTIVE set to nicht_aktiv, ambient lighting is off until the start button is pressed and does not cycle.

 

Here from Costa Rica, Central America, I've been looking to solve the problem on NCSExpert which says "VIN is Faulty" and after long hours searching for the issue still I have no idea if the k+dcan cable is the right one or not.

INPA software shows battery and ignition.

Here are the photos of my cable:
https://www.dropbox.com/sh/co89c53ge...65lG4y9QUQDWXa


My car is 2011 Mini Countryman ALL4, made for USA market.

I'm using the software and guide of this thread, along with datens v41.

Thanks for any help you can provide.

 

Where did you get the cable? Check with the seller this cable supports 2011 model unless you got it from one stop electronics.

 

I got mine from ebay, this is the link

http://www.ebay.com/itm/380916203299...84.m1439.l2649

I'll ask the seller for the support on 2011 models.

 

Just check the driver setting if the cable is supported.

 

I don't think you will get it working with that cable. Don't want a cable that has that mess of resistors in the center of the board.

https://www.northamericanmotoring.co...0-post568.html

The green board is the LAYOUT you want the cable to have. Don't just look for a cable with a green board because mine is white with the proper design.

https://www.northamericanmotoring.co...6-post345.html

 

No problem AlphaQuad. He's referring to this thread:

https://www.northamericanmotoring.co...door-open.html

If I could only solve my own coding problems...

 

Thanks for the info.

Do you have any idea where can I get a working cable online and with relative low price?

 

I have the one stop electronics cable and also bought the following cheap cable from ebay. It worked fine on my 2012 Countryman as well 2012 X5.

http://pages.ebay.com/motors/link/?n...d=181391108834

 

Hi
There is one more folder "cfgdat" in this datens.
Do I need to copy it somewhere?

 

NCS expert in this thread is 32bit, my computer is 64 bit
What should I do?

 

It is not a problem. I have the same case - Win7 Professional 64bit. All I did was to install WinXP as virtual machine (it was free for Win7 Professional) and using this virtual WinXP installed the whole package from this tread following the manual. All works form the first kick start. Of course you need the correct cable. If you have the wrong one (which supports Mini's and BMWs till 2008), INPA will show the connections correctly (two black dots), but NCS will not be able to communicate with any ECU.

 

Quote:
Originally Posted by Theta
Here we go!

51.2 Datens here: http://www.mediafire.com/download/6o...-Daten_R56.zip

Hi
There is one more folder "cfgdat" in this datens.
Do I need to copy it somewhere?

 

Hi
What is this exactly mean: "Disable Over-Estimated Speed Reading"

 

The speedometer reads 3-5mph faster than your actual speed - you can confirm this with GPS.

This setting will correct this, but only on the digital display. The analog speedometer will remain unchanged.

 

In the US, both the tach speed display and central stack speedometer show the speed at about +2mph over actual speed. Disabling the over-estimated speed reading changes the tach speed display to the more accurate (-2mph) speed. Note that this change only affects the tach speed display; the central stack speedometer will still show about +2mph.

HTH,

 

Oops! Sorry Theta!

 

No worries - it's different on every car it seems. My last one was 3 off, this one is 4-5 at 70mph. Kind of annoying, but you get used to the buffer.

Once you take it away... It's like setting your watch ahead so you're not late, then forgetting you set it correctly.

 

Yep! My 04 MCS JCW is +3 on OEM sized wheels/tires. My 12 CMS is +2. I didn't like the setting: my OCD kicked-in when I realized the tach and speedo didn't agree! Much easier to count on the buffer no matter where you look.

 

Speaking of changes, my CMS software was updated by the dealer. Something about brake pad sensor readings and TPMS changes???? Anyhoo, all systems were defaulted and I need to reapply my changes.

Will be updating to the latest datens before reapplying. Anything new about the update procedure? Something about an additional folder???

Cheers,

 

There is one more folder "cfgdat" in 51.2 datens.
Do I need to copy it somewhere?

 

OK. This is new.

I've been successfully coding my 2012 R60 for the past two years without any problems. Good XP environment and a good cable. Many successful coding changes.

In February, my dealer updated the control modules and wiped-out all my changes. I have recently upgraded to the new 51.2 datens to recode the car. I remembered to run LADEN.BAT in the DATEN folder after copying over the new files.

INPA shows the communication link to be fine but when I run NCSExpert, I get a "Chassis is faulty" error after selecting the R56 chassis. Remember, I am using the exact same cable I have successfully used for the past 2 years!

I'm guessing that one of two things have happened:

1) The update the dealer did in February did something to upset things (less likely);
2) I have not updated NCSExpert correctly (most likely).

In any case, we can rule out the computer, XP, the cable, and satanic spells.

Is there a way to verify that the DATENS update was done correctly? Any help whatsoever would be greatly appreciated!!

H E L P !!!

TIA,

Theo

 

If I'm not mistaken, when I had that issue, the only way I was able to fix it was by doing a clean install w/o installing the old R56 datens and going straight to installing the new datens. I also use an old coding software to only update my datens now so that I never have issues. I forget what's it's called but when I get a chance to see which one it is, I will let you know.

 

The program I use solely to update my datens is called "BMW Coding Tool." I got it from a coding package from one of the members off of a BMW coding forum. Let me know if you can find it, if not, I can try to email you zip file.