Electrical NCSExpert DIY(do it yourself)
#277
#280
#281
New datens link
Thanks to GeoffreyM I've updated the other thread with the "newer dates". Here is a quick link to the download server. SP - R56 - V45
You just need to update the datens folder with the one you have.
Again, use this at your own risk ...
You just need to update the datens folder with the one you have.
Again, use this at your own risk ...
#282
Bulb Settings -- Results
Software: NCS Expert.
Datens: V45 for R56
Ediabas: 7.2.
I saved my initial TRC file in a safe place.
Ran NCS and had it generate a new TRC file to work with (working copy). This file was the same size as the original (i.e. no issues).
Edit: From the following list, I only disabled the following in BLUE.
KALTUE_AL_M1_6_M2_38
KALTUE_FL_M2_6_M1_04
KALTUE_KZL_M2_49
WARMUE_AL_M1_6_M2_38
WARMUE_FL_M2_6_M1_4
WARMUE_KZL_M2_49
Trial 1: Coded the first time and set the Warm Bulb checks to nicht_aktiv and then went back to recode the Cold Bulb checks and couldn't code again (got error).
Reason?: Evidently, when NCS Expert creates a TRC file based off of a code, the file size of the TRC file is larger than the original one. I don't know why. This second TRC file, when used for recoding has issues, and you get the error as seen in this attachment.
Trial 1: Based off of the first trial, where I had a successful code on the Warm Bulb Checks, I was still getting the errors when the car started. This is when I went back to recode and got the errors.
Trial 2: I saw a pattern developing with the new TRC file that was 127kb vs the OEM 24 kb. The OEM TRC files had no issues coding.
Solution: I replaced the TRC file with the OEM TRC and ran NCS Expert. I went ahead and recoded off of this TRC (setting Warm and Cold bulb checks to nicht_aktiv) and then Executed. The code finally went through with no errors.
Result: I have no bulb out errors whatsoever, however, after a few seconds of not turning on the lights, they cannot be turned on.
Basically, I'm having the same problem as earlier, except without the annoying Bulb Out Checks.
If anyone knows of some other work around where the ECU won't disable the lights, please let me know.
The mod I did is adding HID retrofits. They currently have no added plug-ins to "trick" the ECU. Perhaps that's the route I need to take. Currently, the lights can turn on within 5-10 seconds of starting the car. In the past, if I waited greater than that, the Bulb Out Error checks would turn-on and you could not turn on the headlights (parking lights worked). Also, once the lights were turned-on (i.e. before the Bulb Out Error would kick-in), if they were turned off, they could not be turned back on.
Datens: V45 for R56
Ediabas: 7.2.
I saved my initial TRC file in a safe place.
Ran NCS and had it generate a new TRC file to work with (working copy). This file was the same size as the original (i.e. no issues).
Edit: From the following list, I only disabled the following in BLUE.
KALTUE_AL_M1_6_M2_38
KALTUE_FL_M2_6_M1_04
KALTUE_KZL_M2_49
WARMUE_AL_M1_6_M2_38
WARMUE_FL_M2_6_M1_4
WARMUE_KZL_M2_49
Trial 1: Coded the first time and set the Warm Bulb checks to nicht_aktiv and then went back to recode the Cold Bulb checks and couldn't code again (got error).
Reason?: Evidently, when NCS Expert creates a TRC file based off of a code, the file size of the TRC file is larger than the original one. I don't know why. This second TRC file, when used for recoding has issues, and you get the error as seen in this attachment.
Trial 1: Based off of the first trial, where I had a successful code on the Warm Bulb Checks, I was still getting the errors when the car started. This is when I went back to recode and got the errors.
Trial 2: I saw a pattern developing with the new TRC file that was 127kb vs the OEM 24 kb. The OEM TRC files had no issues coding.
Solution: I replaced the TRC file with the OEM TRC and ran NCS Expert. I went ahead and recoded off of this TRC (setting Warm and Cold bulb checks to nicht_aktiv) and then Executed. The code finally went through with no errors.
Result: I have no bulb out errors whatsoever, however, after a few seconds of not turning on the lights, they cannot be turned on.
Basically, I'm having the same problem as earlier, except without the annoying Bulb Out Checks.
If anyone knows of some other work around where the ECU won't disable the lights, please let me know.
The mod I did is adding HID retrofits. They currently have no added plug-ins to "trick" the ECU. Perhaps that's the route I need to take. Currently, the lights can turn on within 5-10 seconds of starting the car. In the past, if I waited greater than that, the Bulb Out Error checks would turn-on and you could not turn on the headlights (parking lights worked). Also, once the lights were turned-on (i.e. before the Bulb Out Error would kick-in), if they were turned off, they could not be turned back on.
Last edited by oreo_guy; 04-16-2012 at 09:23 PM. Reason: adding picture and codes that were changed
#283
The TRC file size thing is in the instructions. The larger one is a read of all the modules, and yes, it happens after every write. The rest sounds more like your hid kit/ballasts are bad. Regardless of bulb out warnings, they should turn on. The bulb out warning doesn't cut power to the headlight, it just senses the lack of resistence and tells you the bulb may be out.
#284
The TRC file size thing is in the instructions. The larger one is a read of all the modules, and yes, it happens after every write. The rest sounds more like your hid kit/ballasts are bad. Regardless of bulb out warnings, they should turn on. The bulb out warning doesn't cut power to the headlight, it just senses the lack of resistence and tells you the bulb may be out.
I don't want to get off-topic, but I had a retrofit done with an installer, and will never go back to him. I had a feeling it's something else (i.e. product problem) was wrong, because we tested it using load resistors and the issue kept coming up.
Black Flame Customs is doing a complete overhaul, and their sets have CANBUS cancellers, so I'm a lot more optimistic.
Does anyone know if the DWA "heartbeat" light on the tach is a changing variable on a 2012 MCS? It's listed in the SPEG module as DWA_VERBAUT.
As for NCS Expert stuff, I'd like to thank the mods and other active users for sharing info that is really helpful for others.
Thanks again!!!
#285
Thanks Juppers ! Been super busy these days and can't answer questions on time
Not sure for the 2012 model ...Iam not sure if we had someone tested it out.
There is no really worst case scenario, if its there, then its changeable, if its there and changeable however it doesn't do anything, then it should affect ur car negatively
We need ppl to test 1st, volunteers ?
Ive tried on a manual to add the command to push start only the car (without the clutch) as it would be a an automatic. Obviously it didn't work didn't do anything bad to the car, just didn't start at all (good anti thief method if I was to go away for a while)
Not sure for the 2012 model ...Iam not sure if we had someone tested it out.
There is no really worst case scenario, if its there, then its changeable, if its there and changeable however it doesn't do anything, then it should affect ur car negatively
We need ppl to test 1st, volunteers ?
Ive tried on a manual to add the command to push start only the car (without the clutch) as it would be a an automatic. Obviously it didn't work didn't do anything bad to the car, just didn't start at all (good anti thief method if I was to go away for a while)
#286
#287
HELP with automatic windows!!
Hi can someone help me?? i downloaded everything GTECKO provided for coding my 07 MCS! I tried several codes that were in the spreadsheet and worked great! but I can't get to work the auto up passenger window! when I try to write the FRM Module it shows an error! Something EDIABAS faulty best and BIP-0009! I am using the V38 datens provided by GTECKO, I read another post about updating EDIABAS to 7.2, i did it and no more error message! it says coding ended but nothing happens! it doesn't overwrite mi FRM module! any help appreciated!
Thanks
Thanks
#288
#289
#290
Mods I have made on 2009 Cooper, V38 Datens
Close Windows/Roof from Fob
Disable speed overestimation
Key Gong Reminder -door open
Sunroof Auto Open/Close
Enable one-touch windows on R56 models (driver and Co-driver)
Change Standard (Boost) Radio Filter Settings
Followed Gtecko's write up - very easy - All have worked perfectly. Thanks Gtecko!
Question - Once I am done with all mods - is there a way to back up all modules in a single file?
Close Windows/Roof from Fob
Disable speed overestimation
Key Gong Reminder -door open
Sunroof Auto Open/Close
Enable one-touch windows on R56 models (driver and Co-driver)
Change Standard (Boost) Radio Filter Settings
Followed Gtecko's write up - very easy - All have worked perfectly. Thanks Gtecko!
Question - Once I am done with all mods - is there a way to back up all modules in a single file?
Last edited by euells; 05-15-2012 at 06:32 PM.
#291
We figured it out. Works exactly like BMWs. You have to disable RDC_Alive in KOMBI. After you do that and drive 1 mile, TPMS is gone forever!
#294
Hi all,
I've been able to program close windows/roof with the FOB, but I get an error when trying to read the ABG module. The error is COAPI-2021.
I am using Datens v45.
Does anybody know what needs to be done in order to read & write to the ABG module?
My car is a R56 factory Works 2008.
I've been able to program close windows/roof with the FOB, but I get an error when trying to read the ABG module. The error is COAPI-2021.
I am using Datens v45.
Does anybody know what needs to be done in order to read & write to the ABG module?
My car is a R56 factory Works 2008.
#295
Join Date: Apr 2008
Location: Twin Cities, Minnesota
Posts: 1,303
Likes: 0
Received 11 Likes
on
10 Posts
I have had no trouble reading the ABG module, to disable the seat belt chime.
#297
Join Date: Apr 2008
Location: Twin Cities, Minnesota
Posts: 1,303
Likes: 0
Received 11 Likes
on
10 Posts
Best thing to do is to put all the module trace files in a dated zip archive to keep them together.
#298
Now NCSExpert is telling me EDIABAS has an error.
I also tried the EDIABAS.INI file of the previous version...
Question: What is the procedure to follow to upgrade EDIABAS to 7.2.0 ?
#299
#300
I would appreciate anyone who have access to the spreadsheet to limit themselves with the editing. Basically there is on the year column you should be touching (if its there already, it means it have already tried and it works)
If you have find a new mod and it works, great, feel free to add it.
Please stop deleting my work and the work ppl put in the this spreadsheet, stop edition the wording, the size of the column and all ... it is meant to be that way. I would hate to lock all the cells and have this file only read.
If you want to edit it YOUR way, download it and do what you want on it.
Respect others work.
Thanks
If you have find a new mod and it works, great, feel free to add it.
Please stop deleting my work and the work ppl put in the this spreadsheet, stop edition the wording, the size of the column and all ... it is meant to be that way. I would hate to lock all the cells and have this file only read.
If you want to edit it YOUR way, download it and do what you want on it.
Respect others work.
Thanks