Adaptive Headlight Error Help

[M3Enthusiast]

Does anyone have an easy download link (i.e. not MEGA) they can provide for the latest V71 SP-DATEN E89 files?

Thanks in advance.

[RocketyMan]

Is v71 the best SP-DATEN files for e89?

Here. I searched this for you and is the best I can find.

https://drive.google.com/drive/mobil...HGh0ZwwU1U2cdV

[M3Enthusiast]

Originally Posted by RocketyMan

Is v71 the best SP-DATEN files for e89?

Here. I searched this for you and is the best I can find.

https://drive.google.com/drive/mobil...HGh0ZwwU1U2cdV

Thanks for providing the link for v69. From my brief research, v71 is supposed to be the latest and greatest. I didn't know there was a best version of the daten files specific for the e89...

[tdott]

you dont need the latest and greatest.

No updates to E89 since like 2014 i think...

[M3Enthusiast]

Updated the daten files to v69 with the daten files provided above.

To give you guys the full story, I sent out my original 2011 LCI headlights to BayOptiks for their retrofit service since the originals were in bad shape from a cosmetic standpoint. They finally finish the service and send back the headlights which cosmetically look a lot better now, but I've got this adaptive headlight warning on the idrive which I can't seem to resolve. I've scanned and cleared the error memory with INPA several times and it comes back with the same two error codes (i.e. "9CC1" and "E596") which decode to the AHL module under the headlight. I've checked out the board and visually it looks good with no corrosion or damage. I've tried re-writing the LSMC module with a blank .MAN trace file and no luck, the error won't go away. Another odd thing is that NCSExpert comes back with reading the FRM as FRM_87 and not FRM_70 but shouldn't it be FRM_70 since the car is an LCI? Any help would be greatly appreciated.

[RocketyMan]

"9CC1"
"E596"

FRM3 is the NFRM. That looks normal to me. Your particular version of the NFRM is the ".C32" version. Don't get hung up on the ".PRG" routines that are run when executing certain commands [read].

Do you have NCS Dummy?
Do you know how to use Tool32?

[RocketyMan]

Do make sure that when you are coding and otherwise "KO-EO" the car, that you have an appropriate battery charger connected to the vehicle that maintains a voltage of 13.0 volts minimum or greater--no more than 14.2 volts.

Review this.
https://www.e90post.com/forums/showthread.php?t=2004716

[M3Enthusiast]

Originally Posted by RocketyMan

"9CC1"
"E596"

FRM3 is the NFRM. That looks normal to me. Your particular version of the NFRM is the ".C32" version. Don't get hung up on the ".PRG" routines that are run when executing certain commands [read].

Do you have NCS Dummy?
Do you know how to use Tool32?

Yes to having NCS Dummy but No to knowing how to use Tool32.

[M3Enthusiast]

Originally Posted by RocketyMan

Do make sure that when you are coding and otherwise "KO-EO" the car, that you have an appropriate battery charger connected to the vehicle that maintains a voltage of 13.0 volts minimum or greater--no more than 14.2 volts.

Review this.
https://www.e90post.com/forums/showthread.php?t=2004716

So you're saying even if writing the blank .MAN file looks to be successful because no error messages come up that the write could not execute correctly if the voltage is not maintained using a battery charger?

[RocketyMan]

Originally Posted by M3Enthusiast

So you're saying even if writing the blank .MAN file looks to be successful because no error messages come up that the write could not execute correctly if the voltage is not maintained using a battery charger?

It's possible--these are finicky architectures, and low voltage is something to always avoid as it can cause more issues.

Writing a blank .man was probably not something I would've done. I question now if you should re-write your default VO to the modules. This would be the best option IMO.

In Tool32, there are routines to run for when the modules in the headlights fail so many times, they need to be reset in order for the codes to clear.

[M3Enthusiast]

Originally Posted by RocketyMan

It's possible--these are finicky architectures, and low voltage is something to always avoid as it can cause more issues.

Writing a blank .man was probably not something I would've done. I question now if you should re-write your default VO to the modules. This would be the best option IMO.

In Tool32, there are routines to run for when the modules in the headlights fail so many times, they need to be reset in order for the codes to clear.

You're right about the low voltage because I recall getting errors when trying to execute "SG Codieren" in NCSExpert which I didn't get this last time when I had the battery charger hooked up but the adaptive headlight error still exists.

I was under the impression that re-writing a blank .MAN file is the same as re-writing the default VO module.

What exact steps do I need to follow to re-write the default VO to the modules as I don't thing I've ever done that? I've only manipulated the trace files using NCSExpert and NCSDummy translator using the "Lesen" and "Codieren" executes.

[RocketyMan]

Originally Posted by M3Enthusiast

You're right about the low voltage because I recall getting errors when trying to execute "SG Codieren" in NCSExpert which I didn't get this last time when I had the battery charger hooked up but the adaptive headlight error still exists.

I was under the impression that re-writing a blank .MAN file is the same as re-writing the default VO module.

What exact steps do I need to follow to re-write the default VO to the modules as I don't thing I've ever done that? I've only manipulated the trace files using NCSExpert and NCSDummy translator using the "Lesen" and "Codieren" executes.

You need to read your VO from the CAS and then change module to the one in question and perform a FA_Codieren (or FA_WRITE) in NCS.

There is a "short counter" for the LCM I believe that can only be reset using Tool32.

Try this instruction using Tool32.
https://www.bimmerforums.com/forum/s...8#post21497878

[M3Enthusiast]

Quick update, I swapped in another supposedly good, used OEM adaptive headlight module into the left side headlight, cleared codes and read codes again, same two errors (i.e. "9CC1" and "E596") came back and the adaptive headlight warning on the iDrive came back.

I then swapped the same replacement module from the left side headlight to the right-side headlight and vice versa. I clear codes and check error memory again and the "9CC1" is now gone and the adaptive headlight warning from the iDrive is gone as well but I still get the "E596" error code when reading the FRM module, also the headlights no longer auto-level move or dither, so I reverted back to the original modules for both sides with the two errors.

[M3Enthusiast]

I tried coding the missing VIN to my FRM module using WinKFP and selecting "FRM3R" for the ECU family but I received the following error message...

[M3Enthusiast]

I checked the FRM module using Tool32 and it doesn't look like there are any short circuit locks anywhere. I believe the problem is the AHL module itself.

Can a known good used AHL module be programmed to work with a different car or is a new one needed?

What are the specific steps needed to code either a used or new AHL module?

[M3Enthusiast]

Is it okay that the FRM module doesn't have a VIN associated with it?

[TboneS54]

when I download the e89 zip (from google link in op), winrar says the file is corrupted. Anyone else? Any other download url?

[M3Enthusiast]

Originally Posted by TboneS54

when I download the e89 zip (from google link in op), winrar says the file is corrupted. Anyone else? Any other download url?

I was able to download, unzip and update using the files without issue.

[TboneS54]

Oh well. I was able to find v71 daten torrent elsewhere so I'm good now!

[M3Enthusiast]

Originally Posted by TboneS54

Oh well. I was able to find v71 daten torrent elsewhere so I'm good now!

Can you provide a link to the torrent site or provide a Google drive download link? I found v71 on Mega but the download is unbearable as it limits your download unless you have a paid subscription.

[TboneS54]

I should be able to post the magnet string which won't be a link perse, and may buffer us from censorship/removal?

The magnet can be copied and pasted into the URL field of a browser and it should trigger utorrent or whatever client to open.

[M3Enthusiast]

Originally Posted by TboneS54

I should be able to post the magnet string which won't be a link perse, and may buffer us from censorship/removal?

The magnet can be copied and pasted into the URL field of a browser and it should trigger utorrent or whatever client to open.

Why not just upload it to a Google drive and I can download then you just remove the link after I'm done, should be brief so don't have to worry about removal.

That's what worked for the above v69 files download.