All bulbs are in FRM.

Side marker light, I believe are abbreviated with "SL". So disable the Kaltue and Warmue with SL in them. For example:

KALTUEBERWACHUNG_SL_V
WARMUEBERWACHUNG_SL_V

Note: NSL is rear fog.

 

Other bulb check abbreviations:

KALTUEBERWACHUNG_AL : cold testing bulbs in low beam
KALTUEBERWACHUNG_BL : " " " " brake light
KALTUEBERWACHUNG_BLK_HI :" " " " turn signal rear
KALTUEBERWACHUNG_BLK_VO :" " " " turn signal front
KALTUEBERWACHUNG_BL_MI : " " " " brake light
KALTUEBERWACHUNG_FL : " " " " high beam
KALTUEBERWACHUNG_KZL : " " " " number plate
KALTUEBERWACHUNG_KZL_LI :" " " "
KALTUEBERWACHUNG_NSW : " " " " foglights
KALTUEBERWACHUNG_NSL : " " " " rear foglights
KALTUEBERWACHUNG_RL : " " " " reversing light
KALTUEBERWACHUNG_SL_LHI :" " " " parking light(left)
KALTUEBERWACHUNG_SL_RHI :" " " " parking light(right)

Actual wording for setting may vary slightly.

There is a "translations.csv" file buried in the NCS Expert file tree. Very helpful.

 

Thanks cerenkov.

I'm not sure why, but my FRM file doesn't have those lines???!?

I was able to find them in an old error FRM file (meaning an attempted FRM download that I opened in texteditor before I got "coding ended" from NCSEXPERT. So I think has all modules not just the FRM, but I could be wrong).

I guess one question is how big should the FRM file be? I think 24kb.

This is what I have in the FRM file (24kb) I just downloaded from the car


This is what I can see in the old FRM error file (119kb)

So you can see the lines you referenced are there right in between the V_S_HI_KRV & NACHL_RKW in my "error" file but not in the FRM I just downloaded.

Any thoughts? Could it be in another module?

Should I add those lines back in to my newly download FRM?

 

Anyone have any input? Can anyone share their FRM file just as a comparison?

Any help appreciated.

 

I printed out all the steps, I have two types of cables, and i still get the same error and can go no farther with the programing/reading process. does anyone know why?

error- VIN is faulty
COAPI-2020:ECU does not answer IFH-0009: No response from controlunit CASPLUS some more stuff..


I have troed to enter the vin manually and get same faulty error

2016 countryman/S ALL4 ANYONE??

 

--

 

---

 

Well I tried adding the below lines suggested by cerenkov, no luck.

It actually looked like the CRM wouldn't accept the change. I would get 'code ended' every time from NCSExpert, so I know it wrote to the car. But it always failed to disable the bulb warning. I would then read the FRM again and the 4 lines I added were not present. I tried multiple times.

Oddly they were not in my FRM file from the start.

Any other ideas on how to disable the side marker bulb checks?

I'm not sure what I'm doing wrong here. I've coded many other things on my car without issue with NCSExpert.

Can anyone share their R56 FRM file for me to compare to?

 

I can send you mine. Do I have your email?

 

What cable are you using? Does it have pins 7&8 bridged?

I had similar issues with more than one car after update.
I realized that my cable (auto-detects if it is KCAN or DCAN) don't work that way anymore. i put a switch on it to enable/disable bridge between pins 7&8.

 

Thanks cerenkov. I DM'd you.

 

hi guys,
i wanted to retrofit the sport button i been search all topic but still can't get the correct pin where is the DSC cable to switch to no 18 for sport mode anyone can help?

 

So i have purchased a new laptop for this so i have nothing else interfering. And it works much better now.. I can load the FG,NRCL,and CHASSIS

BUT: I get a FA not type #0715 error

When I try to load FA manually it asked me the attribute: Anyone know what i should enter there?

The list starte like this..

#0715
$205
$210
$249 and so on?

Hey anyone ever get this?

 

Just to be completely clear, we should use the R56 datens for this right? I downloaded the v58 datens and there is no R60 folder, so that is my assumption.

 

Yes, R56 datens.

 

I managed to get all this working yesterday and coded my Bi-Xenon retrofit in about 10 minutes using the v58 datens. I'm a 15 year veteran of IT and it was scary and intimidating, but once you figure it out, it's not all that hard.

I didn't have any trouble using the most recent tools on Windows 10 64-bit with this cable:

 

Super curious how you did this, I've been trying on a windows 7 laptop with this exact cable and can't seem to make it work. I get to the test suite and it tells me that The Battery is on but not the ignition no matter what I do. I haven't tried the latest files yet, but the ones that came with the setup instructions, do I maybe need to try the latest versions? I'm also a Software developer by trade so I know my way around a PC fairly well and am a little baffled. Searching for the errors I find only references to people who have made their own cables and have it wrong, which isn't super useful.

 

I followed the guide found via this thread for BMW Coding Tool 2.12:

http://www.e90post.com/forums/showthread.php?t=1204192

I didn't actually use the Coding Tool, I used straight NCSExpert4_x64 and NCSDummy, but I did follow his guide for setting everything up.

 

help.


ERROR! Modul: LFCDHDIA.CPP (A_E65CAS.IPS/IPO), Proc: CDHapiResultText, LineNr: 01, ErrorNr: 2020
COAPI-2020: no answer from ECU
IFH-0009: NO RESPONSE FROM CONTROLUNIT

>> ERROR! Modul: COAPI2.CPP, Proc: coapiRunCabd, LineNr: 06, ErrorNr: 2020
FGNR_LESEN

>> ERROR! Modul: COAPI.CPP, Proc: coapiReadFgNr, LineNr: 04, ErrorNr: 2020
FGNR_LESEN: A_E65CAS

 

Hi guys, new member here, great threat. Learned quite few things however I'm having a problem connecting to the ECU of MY 2012 Contryman. It's one of those $20 cables from Ebay and I'm thinking that I've got a faulty or incomparable cable. It has a white board and pins 7 and 8 are not connected as can see bellow.

I've install the drivers and the software following the steps in the guide and everything looks fine until connecting to the car. At first when I connect it the red light on the cable itself comes on and when I try INPA it says the ignition is off although it's on on the car. Then couple of minutes later the light on the cable goes off and when trying INPA again it reads battery and ignition just fine. But then NCS is giving me a faulty VIN error.

Any ideas? Is it the cable or something I'm doing wrong with the installation ?
By the way anyone one in North Atlanta area done some coding ?

 

Did you set the latency of the com port to 1?

 

Yes, I did. Also used COM1 as I've read that's less likely to cause problems.

 

It's in the same state.
2013 R61 Paceman

 

What operating system are you using?

I had similar symptoms (ignition and battery not showing correctly, light on cable not on) when I upgraded to Windows 10 and when I went back to Windows 7 everything works great.

 

Windows7 And Windows XP.
The same state both.