For Help with NCSExpert Errors

och · 07-20-2015, 01:03 PM

Quote:

Originally Posted by wildcatcrazy

The ignition and battery dots are the ones that matter. It sounds like a software set up issue as well since the dots are constant on.

They stay on when I turn on the computer without cable plugged in, but when i actually connect it to the car, they sometimes stay on, but sometimes correctly show battery/ignition status. Thats why I'm thinking its a cable issue.

slayosan · 07-26-2015, 05:24 PM

Hey guys. Been trying to research this error for a couple of days but I've come to the point where I can't find any answers to this error. I'm able to read my airbag in INPA but in NCS can't read my VIN. I attached the error log. Any help getting this up and running would greatly be appreciated.

Bimmer-Bob · 10-03-2015, 08:12 PM

So I'm getting the "wrong ECU coding index" error. Is this just from trying to use out-of-date datens?

I was coding fine until the dealer updated my software yesterday and returned everything back to stock settings. When I tried to access the NFRM to recode my car to my preferences, I got the above error. I'm thinking the module was written with new firmware or something, and that a newer datens file is required to read it. Is the fix as easy as updating the datens? Or is it something else?

I upgraded to V54, but am still getting the error. I think the latest version is V56, but I'm having a hard time finding it. Anyone have a link? Or know what else I should be trying?

Thanks.

cryptomit · 10-06-2015, 05:44 AM

Download 56.0 and update and should be ok.

reisf · 10-24-2015, 05:27 PM

Hey so i have a weird coding problem. I have the full coding setup (NCSExpert, inpa, wool32, winkfp) and its all working fine on my 2011 e87, but i tried to code a mates 2008 e82 yesterday and i couldn't get it to work. I get the message "VIN is faulty" when i try to read the cars VO from CAS or FRM modules.

I tried doing the airbag test in INPA, but INPA couldn't see the car as Battery: ON or Ignition: ON. I think i remember reading something about pins 7 and 8 in the OBD cable needing to be soldered together? Would this need to be done on slightly older model cars?

I double checked on my car to make sure it was working and it was. Any idea what the problem is?

I have the one stop electronics cable and am fairly good with coding things. Any help would be awesome

InfiniteGinger · 10-28-2015, 01:57 PM

Hello new here,

Been trolling the forums for the last few days, I have BMW tools 2.1.2 NCS 4.0.1, EDIABAS 7.3, and someone gave me Daten v55. I updated my Daten files using BMW coding tool v2.5 and I've tried it manually. Nothing seems to work. running the programs on win7 32bit

My car is a 2013 328i conv

Here is my last error log, may contain more than one attempt to read from CAS module.

[13:38:43.196] [2015-10-28] [SERIE] 2020 Error LFCDHDIA.CPP (A_PL2FRX.IPS/IPO) CDHapiResultText 1
[13:38:43.196] [2015-10-28] [SERIE] ECU does not answer IFH-0009: No response from controlunit FRM_87

[13:38:43.301] [2015-10-28] [SERIE] 2020 Error COAPI2.CPP coapiRunCabd 6
[13:38:43.301] [2015-10-28] [SERIE] ECU does not answer FA_READ

[13:38:43.302] [2015-10-28] [SERIE] 2020 Error COAPI4.CPP coapiReadAuftrag 4
[13:38:43.302] [2015-10-28] [SERIE] ECU does not answer FA_READ: A_PL2FRX

[13:38:46.144] [2015-10-28] [SERIE] 2020 Error LFCDHDIA.CPP (A_PL2FRX.IPS/IPO) CDHapiResultText 1
[13:38:46.144] [2015-10-28] [SERIE] ECU does not answer IFH-0009: No response from controlunit FRM_87

[13:38:46.249] [2015-10-28] [SERIE] 2020 Error COAPI2.CPP coapiRunCabd 6
[13:38:46.249] [2015-10-28] [SERIE] ECU does not answer FA_READ

[13:38:46.250] [2015-10-28] [SERIE] 2020 Error COAPI4.CPP coapiReadAuftrag 4
[13:38:46.250] [2015-10-28] [SERIE] ECU does not answer FA_READ: A_PL2FRX

[13:38:48.695] [2015-10-28] [SERIE] 2020 Error LFCDHDIA.CPP (A_E65CAS.IPS/IPO) CDHapiResultText 1
[13:38:48.695] [2015-10-28] [SERIE] ECU does not answer IFH-0009: No response from controlunit CAS

[13:38:48.799] [2015-10-28] [SERIE] 2020 Error COAPI2.CPP coapiRunCabd 6
[13:38:48.799] [2015-10-28] [SERIE] ECU does not answer FA_READ

[13:38:48.800] [2015-10-28] [SERIE] 2020 Error COAPI4.CPP coapiReadAuftrag 4
[13:38:48.800] [2015-10-28] [SERIE] ECU does not answer FA_READ: A_E65CAS

[13:38:48.800] [2015-10-28] [SERIE] 1000 Warning COAPI.CPP coapiReadFgNr 9
[13:38:48.800] [2015-10-28] [SERIE] Error CAS

================================================== ==============================(2)
[13:38:51.244] [2015-10-28] [SERIE] 2020 Error LFCDHDIA.CPP (A_E65CAS.IPS/IPO) CDHapiResultText 1
[13:38:51.244] [2015-10-28] [SERIE] ECU does not answer IFH-0009: No response from controlunit CAS

[13:38:51.348] [2015-10-28] [SERIE] 2020 Error COAPI2.CPP coapiRunCabd 6
[13:38:51.348] [2015-10-28] [SERIE] ECU does not answer FGNR_LESEN

[13:38:51.349] [2015-10-28] [SERIE] 2020 Error COAPI.CPP coapiReadFgNr 12
[13:38:51.349] [2015-10-28] [SERIE] ECU does not answer FGNR_LESEN: A_E65CAS

Oh and INPA does not work....shows the 2 black dots but tells me a file is missing

"C:\EC-APPS\INPA\sgdat\MRS5.ipo(1) : error I300: Error opening object file"

My VC file is attached

wildcatcrazy · 10-28-2015, 06:45 PM

Quote:

Originally Posted by ballinallthetime

Hello new here,

Been trolling the forums for the last few days, I have BMW tools 2.1.2 NCS 4.0.1, EDIABAS 7.3, and someone gave me Daten v55. I updated my Daten files using BMW coding tool v2.5 and I've tried it manually. Nothing seems to work. running the programs on win7 32bit

My car is a 2013 328i conv

Here is my last error log, may contain more than one attempt to read from CAS module.

[13:38:43.196] [2015-10-28] [SERIE] 2020 Error LFCDHDIA.CPP (A_PL2FRX.IPS/IPO) CDHapiResultText 1
[13:38:43.196] [2015-10-28] [SERIE] ECU does not answer IFH-0009: No response from controlunit FRM_87

[13:38:43.301] [2015-10-28] [SERIE] 2020 Error COAPI2.CPP coapiRunCabd 6
[13:38:43.301] [2015-10-28] [SERIE] ECU does not answer FA_READ

[13:38:43.302] [2015-10-28] [SERIE] 2020 Error COAPI4.CPP coapiReadAuftrag 4
[13:38:43.302] [2015-10-28] [SERIE] ECU does not answer FA_READ: A_PL2FRX

[13:38:46.144] [2015-10-28] [SERIE] 2020 Error LFCDHDIA.CPP (A_PL2FRX.IPS/IPO) CDHapiResultText 1
[13:38:46.144] [2015-10-28] [SERIE] ECU does not answer IFH-0009: No response from controlunit FRM_87

[13:38:46.249] [2015-10-28] [SERIE] 2020 Error COAPI2.CPP coapiRunCabd 6
[13:38:46.249] [2015-10-28] [SERIE] ECU does not answer FA_READ

[13:38:46.250] [2015-10-28] [SERIE] 2020 Error COAPI4.CPP coapiReadAuftrag 4
[13:38:46.250] [2015-10-28] [SERIE] ECU does not answer FA_READ: A_PL2FRX

[13:38:48.695] [2015-10-28] [SERIE] 2020 Error LFCDHDIA.CPP (A_E65CAS.IPS/IPO) CDHapiResultText 1
[13:38:48.695] [2015-10-28] [SERIE] ECU does not answer IFH-0009: No response from controlunit CAS

[13:38:48.799] [2015-10-28] [SERIE] 2020 Error COAPI2.CPP coapiRunCabd 6
[13:38:48.799] [2015-10-28] [SERIE] ECU does not answer FA_READ

[13:38:48.800] [2015-10-28] [SERIE] 2020 Error COAPI4.CPP coapiReadAuftrag 4
[13:38:48.800] [2015-10-28] [SERIE] ECU does not answer FA_READ: A_E65CAS

[13:38:48.800] [2015-10-28] [SERIE] 1000 Warning COAPI.CPP coapiReadFgNr 9
[13:38:48.800] [2015-10-28] [SERIE] Error CAS

================================================== ==============================(2)
[13:38:51.244] [2015-10-28] [SERIE] 2020 Error LFCDHDIA.CPP (A_E65CAS.IPS/IPO) CDHapiResultText 1
[13:38:51.244] [2015-10-28] [SERIE] ECU does not answer IFH-0009: No response from controlunit CAS

[13:38:51.348] [2015-10-28] [SERIE] 2020 Error COAPI2.CPP coapiRunCabd 6
[13:38:51.348] [2015-10-28] [SERIE] ECU does not answer FGNR_LESEN

[13:38:51.349] [2015-10-28] [SERIE] 2020 Error COAPI.CPP coapiReadFgNr 12
[13:38:51.349] [2015-10-28] [SERIE] ECU does not answer FGNR_LESEN: A_E65CAS

Oh and INPA does not work....shows the 2 black dots but tells me a file is missing

"C:\EC-APPS\INPA\sgdat\MRS5.ipo(1) : error I300: Error opening object file"

My VC file is attached

Did you have a working system before the Daten update? Is the comm port and latency set to 1? If the cable isn't a 1 stop electronic cable wasn't verified to work before, what color is the PC board?

InfiniteGinger · 10-28-2015, 07:47 PM

Quote:

Originally Posted by wildcatcrazy

Did you have a working system before the Daten update? Is the comm port and latency set to 1? If the cable isn't a 1 stop electronic cable wasn't verified to work before, what color is the PC board?

1. White pcb board.

2. Com is set to 1 and latency is also set to 1. obd attached... I've taken it apart and the 8 pin doesn't appear to be jumped or attached to anything?

3. I don't know if it's a "1stop" cable it's labeled "INPA compatible and K+DCAN USB interface"

I did just reproduce both errors with the cable only plugged into the computer.

Is there another test I can preform that will determine if this cable even works?

Went ahead and proactively ordered from 1stop

wildcatcrazy · 10-28-2015, 08:17 PM

Quote:

Originally Posted by ballinallthetime

Quote:

Originally Posted by wildcatcrazy

Did you have a working system before the Daten update? Is the comm port and latency set to 1? If the cable isn't a 1 stop electronic cable wasn't verified to work before, what color is the PC board?

1. White pcb board.

2. Com is set to 1 and latency is also set to 1. obd attached... I've taken it apart and the 8 pin doesn't appear to be jumped or attached to anything?

3. I don't know if it's a "1stop" cable it's labeled "INPA compatible and K+DCAN USB interface"

I did just reproduce both errors with the cable only plugged into the computer.

Is there another test I can preform that will determine if this cable even works?

White PC board versions are real unreliable. You definitely don't have a cable from 1 stop. This may be your only hope to get it working.

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

InfiniteGinger · 10-29-2015, 12:04 AM

Quote:

Originally Posted by wildcatcrazy

White PC board versions are real unreliable. You definitely don't have a cable from 1 stop. This may be your only hope to get it working.

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

Oh cool. The hardware id already matched. Never thought to check that...I followed the guide you linked and no joy. I did update the driver to the latest in the process. the seller already politely agreed to return the cable and I ordered a replacement from one stop. Go big or go home I guess.

TMacie · 12-13-2015, 05:59 PM

Hi all, I'm getting a VIN not recognized error when I run NCS Expert. INPA works fine. I've looked for a couple solutions, but am still a little confused. What info do I need to provide so you guys might be able to help me out?

Thanks,
Travis

InfiniteGinger · 12-13-2015, 06:03 PM

Quote:

Originally Posted by TMacie

Hi all, I'm getting a VIN not recognized error when I run NCS Expert. INPA works fine. I've looked for a couple solutions, but am still a little confused. What info do I need to provide so you guys might be able to help me out?

Thanks,
Travis

Where did you get your cable? What color is the pcb board? I had the very same issue

wildcatcrazy · 12-13-2015, 07:12 PM

Quote:

Originally Posted by TMacie

Hi all, I'm getting a VIN not recognized error when I run NCS Expert. INPA works fine. I've looked for a couple solutions, but am still a little confused. What info do I need to provide so you guys might be able to help me out?

Thanks,
Travis

Jb4?

TMacie · 12-16-2015, 05:29 PM

Sorry guys I didnt get an e-mail when you posted. I got the cable from the guy who had the car before me. Its a blue cable, not sure on the PCB color, I'll check in a bit. the cable doesnt have any brand on it. FTDI drivers work with it though.

Thanks,
Travis

wildcatcrazy · 12-16-2015, 06:15 PM

Quote:

Originally Posted by TMacie

Sorry guys I didnt get an e-mail when you posted. I got the cable from the guy who had the car before me. Its a blue cable, not sure on the PCB color, I'll check in a bit. the cable doesnt have any brand on it. FTDI drivers work with it though.

Thanks,
Travis

JB4 installed?

TMacie · 12-16-2015, 06:31 PM

Quote:

Originally Posted by wildcatcrazy

JB4 installed?

Well....im not sure what that is, so I'm going with no....not installed. LOL.

Travis

wildcatcrazy · 12-16-2015, 09:32 PM

Quote:

Originally Posted by TMacie

Well....im not sure what that is, so I'm going with no....not installed. LOL.

Travis

Sorry, app didn't show what you were driving or I would have known you didn't have a JB4. Check your cable driver settings to make sure latency is set to 1. Also, how much can you do with INPA (read errors, UIF, etc.). Sometimes bad cables will show ign/battery dots active but not actually let you do anything.

TMacie · 12-17-2015, 02:11 PM

Quote:

Originally Posted by wildcatcrazy

Sorry, app didn't show what you were driving or I would have known you didn't have a JB4. Check your cable driver settings to make sure latency is set to 1. Also, how much can you do with INPA (read errors, UIF, etc.). Sometimes bad cables will show ign/battery dots active but not actually let you do anything.

No problem. Latency is set at 1. Looks like I can read errors in INPA, I do get errors here and there but I'm not familiar enough with it to tell if its legit, or just for something that the car doesn't have, etc. All I really need to do is code the radio to have bluetooth and SOS. i had to replace the radio this summer, and the original radio had these functions. SOS throws an error so thats most important. i'd like to change around a few other things once I get the SOS and BT fixed too.

Also, the PCB in the cable is green.

Travis

wildcatcrazy · 12-17-2015, 08:32 PM

Quote:

Originally Posted by TMacie

No problem. Latency is set at 1. Looks like I can read errors in INPA, I do get errors here and there but I'm not familiar enough with it to tell if its legit, or just for something that the car doesn't have, etc. All I really need to do is code the radio to have bluetooth and SOS. i had to replace the radio this summer, and the original radio had these functions. SOS throws an error so thats most important. i'd like to change around a few other things once I get the SOS and BT fixed too.

Also, the PCB in the cable is green.

Travis

Double check to make sure you have the E89 folder in C:\NCSEXPER\DATEN. If you're just getting language variant mismatch in INPA, that's normal.

TMacie · 12-20-2015, 10:51 AM

The E89 folder is there. there are file in it as well.

DervJim · 07-07-2016, 08:00 PM

Hi guys - really hope someone can give me a clue with this one as I'm a real NCS novice.

I have retrofitted my CIC conversion tonight and went well with it turning on and radio/hdd music working straight away. Satnav lets me search and plot a course but still thinks its current location is wherever it stopped in the car it came from, so it doesn't know its current location somehow. I have fitted an emulator BTW.

Anyway, when trying to code the CIC kit in I have successfully changed my car from year 0606 to 0910 as suggested in the youtube video I followed, and added a code $6VA like it instructs to. These have saved just fine, but when I try to run Execute Job on selecting the CIC unit as per the video, I get an error, which when opened gives this data:

[00:40:31.843] [2016-07-08] [SERIE] 2000 Error LFCDHDIA.CPP (A_CIC.IPS/IPO) CDHapiResultText 1
[00:40:31.843] [2016-07-08] [SERIE] Fehler in EDIABAS oder in SG-Beschreibungsdatei SYS-0005: SG-Beschreibungsdatei nicht gefunden CICR

[00:40:31.953] [2016-07-08] [SERIE] 2000 Error COAPI2.CPP coapiRunCabd 6
[00:40:31.953] [2016-07-08] [SERIE] Fehler in EDIABAS oder in SG-Beschreibungsdatei CODIERINDEX_LESEN

[00:40:31.953] [2016-07-08] [SERIE] 2000 Error COAPI.CPP coapiReadCodierIndexFromSg 5
[00:40:31.953] [2016-07-08] [SERIE] Fehler in EDIABAS oder in SG-Beschreibungsdatei CODIERINDEX_LESEN: A_CIC

[00:40:32.156] [2016-07-08] [SERIE] 2000 Error LFCDHDIA.CPP (A_CIC.IPS/IPO) CDHapiResultText 1
[00:40:32.156] [2016-07-08] [SERIE] Fehler in EDIABAS oder in SG-Beschreibungsdatei SYS-0005: SG-Beschreibungsdatei nicht gefunden CICR

[00:40:32.265] [2016-07-08] [SERIE] 2000 Error COAPI2.CPP coapiRunCabd 6
[00:40:32.265] [2016-07-08] [SERIE] Fehler in EDIABAS oder in SG-Beschreibungsdatei SG_CODIEREN

If someone can suggest what I've maybe done wrong I'd be really grateful indeed, thanks!
Jim

maximus81 · 01-30-2017, 07:07 AM

Hi guys, long time viewer first time posting. I have finally taken the plunge and decided to code my beloved 2008 320D M-Sport. have used Carly adaptor in past and did some neat little tricks.

Right now, the issue is permanent "Cornering lights failure" error on dash. Very annoying as it takes over time and temp. I dont even have cornering lights as I am in Australia and also have aftermarket lights. I never had this error but it came after replacing the battery at the dealership. I have been told that if I change following attributes in NFRM module it should disable the error.
CHECK_SMC_ERROR
ALC_FAHRZEUNG
ALC_KLS_ENABLE
NCSExpert is reading the module fine, changed values to nicht_activ. changed job and executed. Coding done message however when i read the module again the values are still 'activ' and error remains on dash. is there anything I am missing or not doing properly?

10-03-2015, 08:12 PM	#201
Bimmer-Bob ! 695 Rep 3,267 Posts Drives: 2010 128i Join Date: Feb 2010 Location: Anacortes, WA iTrader: (4) Garage List 2024 Ford Bronco (U ... [0.00] 2010 BMW 128i (E82) [9.25]	So I'm getting the "wrong ECU coding index" error. Is this just from trying to use out-of-date datens? I was coding fine until the dealer updated my software yesterday and returned everything back to stock settings. When I tried to access the NFRM to recode my car to my preferences, I got the above error. I'm thinking the module was written with new firmware or something, and that a newer datens file is required to read it. Is the fix as easy as updating the datens? Or is it something else? I upgraded to V54, but am still getting the error. I think the latest version is V56, but I'm having a hard time finding it. Anyone have a link? Or know what else I should be trying? Thanks.
	Appreciate 0 Quote

10-06-2015, 05:44 AM	#202
cryptomit Captain 93 Rep 713 Posts Drives: 320d 2012 Join Date: Dec 2013 Location: AS iTrader: (0)	Download 56.0 and update and should be ok. __________________ Click "Appreciate" if I helped you.
	Appreciate 0 Quote

10-24-2015, 05:27 PM	#203
reisf Lieutenant 128 Rep 525 Posts Drives: LBB M2 Join Date: Sep 2014 Location: Sydney, Australia iTrader: (0)	Hey so i have a weird coding problem. I have the full coding setup (NCSExpert, inpa, wool32, winkfp) and its all working fine on my 2011 e87, but i tried to code a mates 2008 e82 yesterday and i couldn't get it to work. I get the message "VIN is faulty" when i try to read the cars VO from CAS or FRM modules. I tried doing the airbag test in INPA, but INPA couldn't see the car as Battery: ON or Ignition: ON. I think i remember reading something about pins 7 and 8 in the OBD cable needing to be soldered together? Would this need to be done on slightly older model cars? I double checked on my car to make sure it was working and it was. Any idea what the problem is? I have the one stop electronics cable and am fairly good with coding things. Any help would be awesome
	Appreciate 0 Quote

12-13-2015, 05:59 PM	#209
TMacie New Member 3 Rep 18 Posts Drives: 2006 325Xi Sport Alpine White Join Date: Jun 2015 Location: S.E. VT. iTrader: (0)	Hi all, I'm getting a VIN not recognized error when I run NCS Expert. INPA works fine. I've looked for a couple solutions, but am still a little confused. What info do I need to provide so you guys might be able to help me out? Thanks, Travis
	Appreciate 0 Quote

12-16-2015, 05:29 PM	#212
TMacie New Member 3 Rep 18 Posts Drives: 2006 325Xi Sport Alpine White Join Date: Jun 2015 Location: S.E. VT. iTrader: (0)	Sorry guys I didnt get an e-mail when you posted. I got the cable from the guy who had the car before me. Its a blue cable, not sure on the PCB color, I'll check in a bit. the cable doesnt have any brand on it. FTDI drivers work with it though. Thanks, Travis
	Appreciate 0 Quote

12-20-2015, 10:51 AM	#218
TMacie New Member 3 Rep 18 Posts Drives: 2006 325Xi Sport Alpine White Join Date: Jun 2015 Location: S.E. VT. iTrader: (0)	The E89 folder is there. there are file in it as well.
	Appreciate 0 Quote

07-07-2016, 08:00 PM	#219
DervJim Private First Class 25 Rep 130 Posts Drives: 2006 E91 330D Touring Join Date: Mar 2012 Location: UK iTrader: (0)	Hi guys - really hope someone can give me a clue with this one as I'm a real NCS novice. I have retrofitted my CIC conversion tonight and went well with it turning on and radio/hdd music working straight away. Satnav lets me search and plot a course but still thinks its current location is wherever it stopped in the car it came from, so it doesn't know its current location somehow. I have fitted an emulator BTW. Anyway, when trying to code the CIC kit in I have successfully changed my car from year 0606 to 0910 as suggested in the youtube video I followed, and added a code $6VA like it instructs to. These have saved just fine, but when I try to run Execute Job on selecting the CIC unit as per the video, I get an error, which when opened gives this data: [00:40:31.843] [2016-07-08] [SERIE] 2000 Error LFCDHDIA.CPP (A_CIC.IPS/IPO) CDHapiResultText 1 [00:40:31.843] [2016-07-08] [SERIE] Fehler in EDIABAS oder in SG-Beschreibungsdatei SYS-0005: SG-Beschreibungsdatei nicht gefunden CICR [00:40:31.953] [2016-07-08] [SERIE] 2000 Error COAPI2.CPP coapiRunCabd 6 [00:40:31.953] [2016-07-08] [SERIE] Fehler in EDIABAS oder in SG-Beschreibungsdatei CODIERINDEX_LESEN [00:40:31.953] [2016-07-08] [SERIE] 2000 Error COAPI.CPP coapiReadCodierIndexFromSg 5 [00:40:31.953] [2016-07-08] [SERIE] Fehler in EDIABAS oder in SG-Beschreibungsdatei CODIERINDEX_LESEN: A_CIC [00:40:32.156] [2016-07-08] [SERIE] 2000 Error LFCDHDIA.CPP (A_CIC.IPS/IPO) CDHapiResultText 1 [00:40:32.156] [2016-07-08] [SERIE] Fehler in EDIABAS oder in SG-Beschreibungsdatei SYS-0005: SG-Beschreibungsdatei nicht gefunden CICR [00:40:32.265] [2016-07-08] [SERIE] 2000 Error COAPI2.CPP coapiRunCabd 6 [00:40:32.265] [2016-07-08] [SERIE] Fehler in EDIABAS oder in SG-Beschreibungsdatei SG_CODIEREN If someone can suggest what I've maybe done wrong I'd be really grateful indeed, thanks! Jim
	Appreciate 0 Quote

01-30-2017, 07:07 AM	#220
maximus81 Private 14 Rep 51 Posts Drives: 2014 BMW 320D M-Sport (F30) Join Date: Jan 2017 Location: Melbourne iTrader: (0)	coding not working Hi guys, long time viewer first time posting. I have finally taken the plunge and decided to code my beloved 2008 320D M-Sport. have used Carly adaptor in past and did some neat little tricks. Right now, the issue is permanent "Cornering lights failure" error on dash. Very annoying as it takes over time and temp. I dont even have cornering lights as I am in Australia and also have aftermarket lights. I never had this error but it came after replacing the battery at the dealership. I have been told that if I change following attributes in NFRM module it should disable the error. CHECK_SMC_ERROR ALC_FAHRZEUNG ALC_KLS_ENABLE NCSExpert is reading the module fine, changed values to nicht_activ. changed job and executed. Coding done message however when i read the module again the values are still 'activ' and error remains on dash. is there anything I am missing or not doing properly?
	Appreciate 0 Quote