e90 Halogen To Xenon Retrofit Issues With NCSExpert

NCSUPack24 · 08-16-2020, 02:15 PM

Hey everyone.

So I went and made my own wiring harness for the official (non-spliced) halogen to xenon conversion, and found an FRM that's AHL enabled (E9x-E8xCA-AHL). Now I'm just trying to code the FRM to my car. The car is a 2007 328i Sedan (w/manual). Previously I had halogens and an E9x-E8xCA-NSW FRM.

I have already:
Changed the VIN on the FRM in WinKFP
Updated the FRM with WinKFP to the latest daten (downloaded from Bimmergeeks)
Wrote my VO from the CAS to the new FRM with FA_WRITE

However...

If I go into NCSExpert, the VIN on the xenon FRM is not mine, despite me coding the VIN with WinKFP. It shows the right VIN in INPA, but not in NCSExpert. Why?

Also, I can't run CODIERDATEN_LESEN on the FRM, it pops up error message:

"Error in CABD! Look at CABLERR and ERROR.LOG!

COAPI-2041: Falscher SG-Codierindex A_PL2FRX: CODIERINDEX =
12h FRM2_E89.C08: CODIERINDEX = 08
COAPI-2041: Falscher SG-Coderindex CODIERDATEN_LESEN"

Spent a few hours digging and people recommended reinstalling Standard Tools. Did that, no dice. Read it was due to NCS not being updated with the latest Daten. Did that again with the Coding Tool, and then did it manually on top of things, still nothing.

I also tried changing the build date from #0307 to something later, but NCS kicks it back saying its an invalid date.

Wtf is going on with this? Thanks in advance.

EDIT: Another post says the new FRM, which says "PL2 FRMFA" is FRM1 and isn't compatible as my car came with a halogen FRM2.

ultimate-tester · 08-17-2020, 06:09 AM

Hi there, here's some additional points that might get you closer to success:

Did BMW standard tools ever work? Were you successful in communicating to other modules?
The INPA and NCSExpert (might) get their information from different modules when showing the VIN. There's no caching of information, so I'd say the VIN was not changed properly in the module (as I understand you want your own VIN across all modules).
You indeed seem to have an FRM1 module, which is not compatible. Based on information from makkan00 (https://www.e90post.com/forums/showp...&postcount=223) you can find which module is required.

NCSUPack24 · 08-17-2020, 06:34 PM

Thanks for the reply. Yeah, standard tools worked, i was able to code the CAS without any issue. I’m working to pick up a FRM3 to fix this.

I read in a previous post that a user had to change the VIN in both WinKFP and with NCSExpert for it to be fully changed. Which NCS job codes the VIN?

dj_aivan · 09-01-2020, 03:29 PM

Hi, In my opinion the problem is in the DATEN files. Update them. The donor module cannot be incompatible.My car is 2005. I was with FRMFA, and now I'm with FRM3 Led-AHL with dynamic headlights, and I didn't have any problems. You need to flash the new module with current date files. Good luck and keep us posted.

NCSUPack24 · 09-05-2020, 04:16 AM

Just an update. Managed to pick up a FRM3 MAX Brose, and it didn't have the same issue updating the module, everything is hooked up and working fine.

dj_aivan · 09-05-2020, 02:26 PM

If your headlights are dynamic, I can help with a working file for FRM 3. My AHL 2 work corectly

08-16-2020, 02:15 PM	#1
NCSUPack24 Private First Class 13 Rep 109 Posts Drives: BMW 328i (E90) Join Date: Apr 2014 Location: USA iTrader: (1)	e90 Halogen To Xenon Retrofit Issues With NCSExpert Hey everyone. So I went and made my own wiring harness for the official (non-spliced) halogen to xenon conversion, and found an FRM that's AHL enabled (E9x-E8xCA-AHL). Now I'm just trying to code the FRM to my car. The car is a 2007 328i Sedan (w/manual). Previously I had halogens and an E9x-E8xCA-NSW FRM. I have already: Changed the VIN on the FRM in WinKFP Updated the FRM with WinKFP to the latest daten (downloaded from Bimmergeeks) Wrote my VO from the CAS to the new FRM with FA_WRITE However... If I go into NCSExpert, the VIN on the xenon FRM is not mine, despite me coding the VIN with WinKFP. It shows the right VIN in INPA, but not in NCSExpert. Why? Also, I can't run CODIERDATEN_LESEN on the FRM, it pops up error message: "Error in CABD! Look at CABLERR and ERROR.LOG! COAPI-2041: Falscher SG-Codierindex A_PL2FRX: CODIERINDEX = 12h FRM2_E89.C08: CODIERINDEX = 08 COAPI-2041: Falscher SG-Coderindex CODIERDATEN_LESEN" Spent a few hours digging and people recommended reinstalling Standard Tools. Did that, no dice. Read it was due to NCS not being updated with the latest Daten. Did that again with the Coding Tool, and then did it manually on top of things, still nothing. I also tried changing the build date from #0307 to something later, but NCS kicks it back saying its an invalid date. Wtf is going on with this? Thanks in advance. EDIT: Another post says the new FRM, which says "PL2 FRMFA" is FRM1 and isn't compatible as my car came with a halogen FRM2. Last edited by NCSUPack24; 08-16-2020 at 02:28 PM..
	Appreciate 0 Tweet Quote

08-17-2020, 06:09 AM	#2
ultimate-tester Enlisted Member 13 Rep 33 Posts Drives: BMW F25 xDrive28i Join Date: May 2019 Location: The Netherlands iTrader: (0)	Hi there, here's some additional points that might get you closer to success: Did BMW standard tools ever work? Were you successful in communicating to other modules? The INPA and NCSExpert (might) get their information from different modules when showing the VIN. There's no caching of information, so I'd say the VIN was not changed properly in the module (as I understand you want your own VIN across all modules). You indeed seem to have an FRM1 module, which is not compatible. Based on information from makkan00 (https://www.e90post.com/forums/showp...&postcount=223) you can find which module is required.
	Appreciate 0 Quote

08-17-2020, 06:34 PM	#3
NCSUPack24 Private First Class 13 Rep 109 Posts Drives: BMW 328i (E90) Join Date: Apr 2014 Location: USA iTrader: (1)	Thanks for the reply. Yeah, standard tools worked, i was able to code the CAS without any issue. I’m working to pick up a FRM3 to fix this. I read in a previous post that a user had to change the VIN in both WinKFP and with NCSExpert for it to be fully changed. Which NCS job codes the VIN?
	Appreciate 0 Quote

09-01-2020, 03:29 PM	#4
dj_aivan Private 0 Rep 60 Posts Drives: e90 320D Join Date: Jan 2020 Location: Bulgaria iTrader: (0)	Hi, In my opinion the problem is in the DATEN files. Update them. The donor module cannot be incompatible.My car is 2005. I was with FRMFA, and now I'm with FRM3 Led-AHL with dynamic headlights, and I didn't have any problems. You need to flash the new module with current date files. Good luck and keep us posted.
	Appreciate 0 Quote

09-05-2020, 04:16 AM	#5
NCSUPack24 Private First Class 13 Rep 109 Posts Drives: BMW 328i (E90) Join Date: Apr 2014 Location: USA iTrader: (1)	Just an update. Managed to pick up a FRM3 MAX Brose, and it didn't have the same issue updating the module, everything is hooked up and working fine.
	Appreciate 0 Quote

09-05-2020, 02:26 PM	#6
dj_aivan Private 0 Rep 60 Posts Drives: e90 320D Join Date: Jan 2020 Location: Bulgaria iTrader: (0)	If your headlights are dynamic, I can help with a working file for FRM 3. My AHL 2 work corectly
	Appreciate 0 Quote