[Augster]

I finally retrofitted LCI headlights to my existing Xenon AHL 2008 and on power up, I noticed the AHL and bulb errors. I thought, "no problem, just fire up NCS Expert and disable the bulb checks and reset the LSCM/RSCM modules..."

Well, when I do my initial VIN read of either the CAS, FRM, or NFRM, NCS Expert coughs up the error "VIN is faulty" and nothing is read in. Uh oh. None of the pre-LCI to LCI headlight threads I've come across ever mentioned this type of error.

I was able to read the VIN just fine before the swap so I'm assuming it has to do with the ALC modules of the used headlights.

I've read some conflicting comments regarding new/used ALC module replacements (all components except D1S, DRL, and AE bulbs are used, BTW) using using WinKFP or Tool32 to "write the VIN" but no step-by-step procedures were ever posted, while others dispute needing to perform this procedure.

So what's my next step to correcting this? Since I've never used WinKFP nor Tool32, I don't want to muck about them blindly as I've heard these are very powerful tools that can brick modules easily if not careful.

UPDATE:

Thanks to WRichieX in confirming that this is a common error that will eventually "resolve" itself somehow...

[cryptomit]

As always my question is: what version of software do you use?

[Augster]

Cable-Shack provided NCS Expert v4.0.1, under Windows 7 x64. WinKFP is v5.3.1, Tool32 is v4.0.3, and EDIABAS is v7.3.0.

But I've had no problems loading the VIN previously on this exact same setup. I've successfully enabled AE as DRL's, alarm, and BT before.

[WRichieX]

This happens to me every so often (although I just started coding). When that happens, I just go back to device manager and make sure the settings are correct for com1. And it seems to work. Worth a try?

[Augster]

Originally Posted by WRichieX

This happens to me every so often (although I just started coding). When that happens, I just go back to device manager and make sure the settings are correct for com1. And it seems to work. Worth a try?

I will check my device settings later today, however, I was able to read the FRM error codes via INPA with no problems...

[WRichieX]

Originally Posted by Augster

I will check my device settings later today, however, I was able to read the FRM error codes via INPA with no problems...

That's weird! Good luck.

[Augster]

You're right, it appears to be an error that crops up now and then because I just tried NCS Expert again and it works to load the VIN from CAS, FRM, and NFRM. Sheesh.

Now I'm going through the troubleshooting process with Rheingold ISTA because INPA indicated a Stepper Motor Control (SMC) error on the right headlight, ARGH! Since I bought this used from a guy in LA several months ago, I think I'm out of luck if the internal motors are defective.