Interesting. It's a good time to play around since the weather is mild.

I was able to get an x64 version of the software up and running a while back but haven't played with it in a while. There are some crazy setup instructions for it here:
http://www.e90post.com/forums/showthread.php?t=1196830

 

---

 

The DUMMY4 profile is the new revtor profile for NCS Expert 4.0. The old revtor profile is for NCS Expert 3.0.

 

---

 

If you are using Expert Mode you just have to edit the profile and turn on manipulation using .man file or else you are just writing back stock values based on vehicle order. Revtors profile just comes with the manipulation setting turned on.

That is how you default your car back to stock if you are wondering, you just turn off the manipulation setting in edit profile and recode the module.

 

I have NCS working on a W10 laptop - no VM or anything I just followed a guide that was out there on the interwebs. I do all my coding on this little HP Elitebook.

 

---

 

True - instead of doing the expensive OEM halo fogs I just put in a sylvania led 194 from can tire and the philips led fogs from can tire (they brought in the good ones) and made those my drls. I dont want to use the hids for drls, what a waste of an expensive bulb that has a life span

i think the countryman/paceman that comes with the led halo fogs have those set to drls and not the low beam.

you can fix the analog display to be corrected - i had it both done, but the cruise control i could not get it figured out so i turned back on the corrected speed as it was only a few off and made everything the same and that satisfied my ocd

 

was this on a car with LED fogs or Halogen fogs?

I have a new FRM installed by dealer with halogen fogs and now I can't control welcome lights for fogs or have them on all the time as standing lights.

 

R60 JCW 2015/2016

Error: following feature is invalid for FA: #0715

Help me?!

 

This thread is for coding features on MINI's. You would be better off posting your question in the "Fixing Problems & Issues" section.

 

Really? I saw a lot of another posts talkin about problems trying to code!

This problem happens when i try to read the ECU. The tool shows this error and doesnt able the "f4" button.

 

Hi all, I will be upgrading my 2015 to a 2017 Countryman. I have heard that there may have been a platform change with this model so I am wondering if anyone knows if the coding process outlined in this thread will work on the 2017 as it did for my 2015?

Thanks!

 

It will be 90% different because it does use the newer platform. Different cable, different software, different coding process. Some of the parameters are labelled the same and some of the ECUs are named the same, but the process is definitely different.

This is a good primer for everything you need: http://www.bmwesys.com/guides/

 

Mine is Countryman R60 2014 in HK. I recentlyreplaced my fog light to LED DRL. I checked many many homepages related to coding and tried coding with different settings but still I can't get my whole HALO light (full circle) at OFF (or AUTO) position. Only I got is a top brow of the LED DRL working. Can any expert here help? it dragged me for a long time.

Original settings
1. VO with $8LH which is for HK
2. no onboard BC function
3. no DRL option in my BC

WhatI did
1.keep $8LHin VO
2.add $550 to VO and refresh module to enable onboard BC function
3.set TAG_LICHT_AN(KOMBI) to aktiv to allow DRL function in BC
4.set TAG_LICHT_AUS(KOMBI) to aktiv to allow DRL function in BC
5.with DRL function in BC set at ON, and the lighting stick to OFF position, I code dthe below
6.set VERHALTEN_DRL_TFL_3R (FRM)from drl_tfl_off to dfl_s (actually I alsotried tfl_s but failed)
7. set DRL_TFL_MIT_KZL, DRL_TFL_MIT_SL_1, DRL_TFL_MIT_SL_2, DRL_TFL_MIT_BL, DRL_TFL_BLK_V_GED to nicht_aktiv
8. set DRL_TFL_MIT_SML_3R (FRM) to aktiv
9. I can only get top brow of LED light up while DRL function at BC is set to ON and lighting stick at OFF (or AUTO) position


LED DRL installation instruction stated the DRL function at BC has to set to OFF, but no light well lighting up then.

Did I code it wrong? Did I mess up DRL and LED DRL?

or it is just a cable connection problem at Blue and Greycable? I checked and they are in good connection. Another expert said he experienced the bad cable connection in the below link
https://www.reddit.com/r/MINI/comments/2v19id/led_drlfoglight_install_issues/
If so, I may replace the crimp connector.


Thanks in advance!!!!

 

Im a bit confused on what cable to buy. I have a 2015 Countryman S All 4. I seems all the cables on go to 2008 models.

 

If you have OBD2 port, then go for the same cable...

 

It seems the links in the beginning of the thread are not what we want to use.

I have a 2012 R60 SA4 and get errors when working through the install and usage process. I cannot even get INPA to work as I am guessing it is a quite an old version.

Does anyone know where there are updated versions of the applications to install and use? I need them both for diagnostic work as well as for coding.

I have the cable I need (green board).

Thanks in advance!

 

Did you try it with the latest Datens files published on the first post?

 

I do not believe these are the latest datens. I found v60.

I am wondering if "coding" is a done subject here.....

 

Anyone know if this problem is fixable with coding?

The windows in our car don't seem to work after the engine is shut off via Start/Stop (Comfort Access, key fob in purse).

I do have Power Windows After Ignition Off set to Active.
I have Continue Window Action When Door Is opened set to Active.


We would like to be able to close the windows after shutting off the engine and after opening the door.

I don't see any other option that mention the windows.

 

Maybe you need set the KOMFORTSCHLIESSUNG_FB to aktiv (CAS)

 

I have a 2016 Countryman and followed your guide. However, I am getting the following message when NCS Expert tries to pull the FG / FA. It pulls the VIN then blows up with the error "Following feature is invalid for FA: #0715." Any suggestions / advice?

 

You need a newer version of EDIABAS and it will fix that error.

 

I actually ended up buying the latest daten files (August 2017) from ncs-expert.com. After putting them in place everything works