Electrical Countryman-Specific Coding - R60 Guide
1st Gear
Joined: Mar 2011
Posts: 14
Likes: 0
VIM Coding
VIM Coding
I have read the PDF in the first link about coding the VIM. I have tried to find info here but still can't figure out how to make it work. It seems the tutorial is for a BMW while our R60's are a bit different.
I have found the "Video_Nuir_Mit_Handbremse" in two modules, the Media and CHAMP. I believe this is because I have the display without Navigation. Neither file creates a NETTODAT file with the "00,00,03,03" values mentioned in the tutorial. I'm not sure what values to change and/or what module to use.
Would anyone that has done this mind posting a guide for me?
I have read the PDF in the first link about coding the VIM. I have tried to find info here but still can't figure out how to make it work. It seems the tutorial is for a BMW while our R60's are a bit different.
I have found the "Video_Nuir_Mit_Handbremse" in two modules, the Media and CHAMP. I believe this is because I have the display without Navigation. Neither file creates a NETTODAT file with the "00,00,03,03" values mentioned in the tutorial. I'm not sure what values to change and/or what module to use.
Would anyone that has done this mind posting a guide for me?
Add this to the list
After spending a number of hours playing with FRM module settings, I finally got the DRLs to light only the city lights! This process was aided by a post by strobey-probey in a thread about city lights as DRLs on Canadian R60s. Please note the specifics below:
Enviromental:
MINI: USA 2012 CMS (Canadian R60s will need to have their VO changed to reflect a USA version - thanks strobey-probey!)
Build Date: Nov 7, 2011
Headlamps: Xenon
Datens: V46. Those with newer datens should be ok as the settings listed below should be present in your FRM module's FSW_PSW.TRC file. I'm not sure whether these settings will be the same in pre-V46 datens, but most likely so.
Misc: Must have working cable and (preferably) NCSExpert programming experience. These instructions assume that you know how to successfully code your R60 with NCSExpert.
Requirements/suggestions before beginning:
1. The DRL option should be activated in the BC;
2. The headlamp setting should be set to "off" for programming, but then you can set it to "Auto" afterwards;
3. Fully read this post before beginning;
4. Plan and document your work (OCD Club Members Unite!).
5. Post if this works for you!
FRM Settings:
VERHALTEN_DRL_TFL_3R drl_s // This setting turns-off the low beam headlamps.
Note: after this setting was made, wheel arch lights, rear taillights and license plate light were still on.
DRL_TFL_MIT_KZL nicht_aktiv // This setting turns-off the license plate lights.
Note: after this setting was made, license plate lights were turned-off but taillights were still on. In fact, the lower taillight in each lens glowed brightly at brake light intensity, the upper taillights were at normal intensity, however. Odd.
DRL_TFL_MIT_SL_1 nicht_aktiv // These settings turned-off the left and right wheel arch lights and
DRL_TFL_MIT_SL_2 nicht_aktiv // lower taillights.
Note: After this setting was made, the upper taillights were still on. According to NCSDummy, the "SL" means "standing lights", so the bright lower taillights may be in standing light mode.
DRL_TFL_MIT_BL nicht_aktiv // This setting turned-off the the upper taillights.
And, finally…
DRL_TFL_MIT_SML_3R aktiv // This setting turned-on the city lights!
Other stuff:
- I made these changes one-by-one. After each change, I exited NCSExpert and turned-off the R60. Then I turned the R60 back on and checked the status of the lights to make sure that the desired effect had been achieved. I suspect that all these edits could be made and programmed in one step, but I thought that I'd just let you know the way in which I did them.
- I never had to touch the companion settings in the CAS module.
- Today I tested the function of the lights in "Auto" mode as they switched between DRL illumination and night illumination. Perfect!
Have fun...
Enviromental:
MINI: USA 2012 CMS (Canadian R60s will need to have their VO changed to reflect a USA version - thanks strobey-probey!)
Build Date: Nov 7, 2011
Headlamps: Xenon
Datens: V46. Those with newer datens should be ok as the settings listed below should be present in your FRM module's FSW_PSW.TRC file. I'm not sure whether these settings will be the same in pre-V46 datens, but most likely so.
Misc: Must have working cable and (preferably) NCSExpert programming experience. These instructions assume that you know how to successfully code your R60 with NCSExpert.
Requirements/suggestions before beginning:
1. The DRL option should be activated in the BC;
2. The headlamp setting should be set to "off" for programming, but then you can set it to "Auto" afterwards;
3. Fully read this post before beginning;
4. Plan and document your work (OCD Club Members Unite!).
5. Post if this works for you!
FRM Settings:
VERHALTEN_DRL_TFL_3R drl_s // This setting turns-off the low beam headlamps.
Note: after this setting was made, wheel arch lights, rear taillights and license plate light were still on.
DRL_TFL_MIT_KZL nicht_aktiv // This setting turns-off the license plate lights.
Note: after this setting was made, license plate lights were turned-off but taillights were still on. In fact, the lower taillight in each lens glowed brightly at brake light intensity, the upper taillights were at normal intensity, however. Odd.
DRL_TFL_MIT_SL_1 nicht_aktiv // These settings turned-off the left and right wheel arch lights and
DRL_TFL_MIT_SL_2 nicht_aktiv // lower taillights.
Note: After this setting was made, the upper taillights were still on. According to NCSDummy, the "SL" means "standing lights", so the bright lower taillights may be in standing light mode.
DRL_TFL_MIT_BL nicht_aktiv // This setting turned-off the the upper taillights.
And, finally…
DRL_TFL_MIT_SML_3R aktiv // This setting turned-on the city lights!
Other stuff:
- I made these changes one-by-one. After each change, I exited NCSExpert and turned-off the R60. Then I turned the R60 back on and checked the status of the lights to make sure that the desired effect had been achieved. I suspect that all these edits could be made and programmed in one step, but I thought that I'd just let you know the way in which I did them.
- I never had to touch the companion settings in the CAS module.
- Today I tested the function of the lights in "Auto" mode as they switched between DRL illumination and night illumination. Perfect!
Have fun...
Is there anyway you can make a note of this option or add this to the list in the beginning of the thread so more enthusiasts may know of it?
Neutral
Joined: May 2013
Posts: 7
Likes: 0
Anyone knows what this error message might mean? Error message is the same when using V49 and V49.4 datens?
Message from error.log:
ERROR! Modul: LFCDHDIA.CPP (A_E65R.IPS/IPO), Proc: CDHapiResultText, LineNr: 01, ErrorNr: 2020
COAPI-2020: no answer from ECU
IFH-0009: ECU not connected or doesn't answer
>> ERROR! Modul: COAPI2.CPP, Proc: coapiRunCabd, LineNr: 06, ErrorNr: 2020
SG_CODIEREN
Message from error.log:
ERROR! Modul: LFCDHDIA.CPP (A_E65R.IPS/IPO), Proc: CDHapiResultText, LineNr: 01, ErrorNr: 2020
COAPI-2020: no answer from ECU
IFH-0009: ECU not connected or doesn't answer
>> ERROR! Modul: COAPI2.CPP, Proc: coapiRunCabd, LineNr: 06, ErrorNr: 2020
SG_CODIEREN
Last edited by k33z; Aug 5, 2013 at 07:29 AM.
Neutral
Joined: Aug 2013
Posts: 2
Likes: 0
I got problems with the installation.
if i make everything like the your documentation and copy the V41 datens the program works but V41 datens are too old for my car.
so if i then copy the v45 datens i get the error window "Baureihe fehlerhaft" at opening the R56.
same if i copy the v45 or v49 datens to a clean installation.
What i´m making wrong ??
thx for help
if i make everything like the your documentation and copy the V41 datens the program works but V41 datens are too old for my car.
so if i then copy the v45 datens i get the error window "Baureihe fehlerhaft" at opening the R56.
same if i copy the v45 or v49 datens to a clean installation.
What i´m making wrong ??
thx for help
Neutral
Joined: Apr 2013
Posts: 6
Likes: 0
From: Columbus, OH
Anyone knows what this error message might mean? Error message is the same when using V49 and V49.4 datens?
Message from error.log:
ERROR! Modul: LFCDHDIA.CPP (A_E65R.IPS/IPO), Proc: CDHapiResultText, LineNr: 01, ErrorNr: 2020
COAPI-2020: no answer from ECU
IFH-0009: ECU not connected or doesn't answer
>> ERROR! Modul: COAPI2.CPP, Proc: coapiRunCabd, LineNr: 06, ErrorNr: 2020
SG_CODIEREN
Message from error.log:
ERROR! Modul: LFCDHDIA.CPP (A_E65R.IPS/IPO), Proc: CDHapiResultText, LineNr: 01, ErrorNr: 2020
COAPI-2020: no answer from ECU
IFH-0009: ECU not connected or doesn't answer
>> ERROR! Modul: COAPI2.CPP, Proc: coapiRunCabd, LineNr: 06, ErrorNr: 2020
SG_CODIEREN
Any ideas? Does this indicate an issue with the cable?
6th Gear
Joined: Aug 2003
Posts: 1,474
Likes: 3
From: Over there -->
Hope this works for you...
Neutral
Joined: Aug 2013
Posts: 3
Likes: 0
Hi, Dear
I'm in trouble.
Although I could re-write the CAS module, the FRM module could not be done.
The next error message has come on.
"COAPI 1043:error during processing CBD-file FRM3_R56.C35"
If someone has any solution let me know please.
I'm in trouble.
Although I could re-write the CAS module, the FRM module could not be done.
The next error message has come on.
"COAPI 1043:error during processing CBD-file FRM3_R56.C35"
If someone has any solution let me know please.
Neutral
Joined: Apr 2013
Posts: 6
Likes: 0
From: Columbus, OH
I have a manual, and hitting the Start button without the clutch and brake pressed seems to turn on all the electrical and the center tach display shows a big "!" to let me know it didn't start. INPA reads Battery: ON and Ignition: ON as instructed, so I'm not really sure where I'm going wrong here.
2nd Gear
Joined: Jul 2013
Posts: 76
Likes: 0
From: San Diego
What is the difference between these two?
Opening Door Does Not Stop Window Roll-Up (60 Seconds) in CAS
FH_ABSCHALTKRITERIUM
nicht_aktiv
Windows DO NOT Stop Rolling Up When Door Opened in FRM
FH_TUERAUF_STOP_MAUT_3R
nicht_aktiv
-----
What I'm really trying to do is allow 1-touch up when the door is opened and key is taken out. The first setting works. It allows windows to go up when door is open, WHILE holding switch. Yes, I do have 1-touch enabled, and it works while the car is running and the doors are closed.
I haven't noticed any changes when changing the second setting. While car is running, I have started 1-touch up, opened the door, and window stops. Does this setting really do anything? BTW I have an R58, but these settings and modules are the same as an R60. My 1-touch-up IS a different setting and module than yours.
FH_ABSCHALTKRITERIUM
nicht_aktiv
Windows DO NOT Stop Rolling Up When Door Opened in FRM
FH_TUERAUF_STOP_MAUT_3R
nicht_aktiv
-----
What I'm really trying to do is allow 1-touch up when the door is opened and key is taken out. The first setting works. It allows windows to go up when door is open, WHILE holding switch. Yes, I do have 1-touch enabled, and it works while the car is running and the doors are closed.
I haven't noticed any changes when changing the second setting. While car is running, I have started 1-touch up, opened the door, and window stops. Does this setting really do anything? BTW I have an R58, but these settings and modules are the same as an R60. My 1-touch-up IS a different setting and module than yours.
