[wildcatcrazy]

I have ran across a problem that I'm pulling my hair out trying to solve...

Replaced a FRM1 (w/out adaptive lights) with a FRM2 (w/ adaptive lights). I changed the VO from #0906 to #0307, flashed the new software/VIN with WinKFP, but when I try to default code the NFRM using expert mode, it gives me the coding index error. So I switch the VO back to #0906, and NCS reads/codes it just fine using the FRMFA DATENs.

Anyone have any ideas on how I can write the proper TRC file to the module and subsequently code it using NCS?

[808AWD325xi]

Originally Posted by wildcatcrazy

I have ran across a problem that I'm pulling my hair out trying to solve...

Replaced a FRM1 (w/out adaptive lights) with a FRM2 (w/ adaptive lights). I changed the VO from #0906 to #0307, flashed the new software/VIN with WinKFP, but when I try to default code the NFRM using expert mode, it gives me the coding index error. So I switch the VO back to #0906, and NCS reads/codes it just fine using the FRMFA DATENs.

Anyone have any ideas on how I can write the proper TRC file to the module and subsequently code it using NCS?

Hmmm...aren't you Joe@TopGearSolutions?:
E & F Series Coding Services << | DVD In Motion & More

It appears so to me:


I find your lack of transparency disturbing. That being said, I am not about to help someone who is just going to turn around and profit from it...

[Sensible_]

Try using CODERIUNGINDEX_LESSEN after you select NFRM before SG_CODIEREN.

Coding Index errors are common with retrofits if there is something amiss with the ZCS / VO.