LKM headache... Help?

I was having problems, my 97 540i was intermittantly displaying "check front foglamps", while the lights worked. Then the right fog light started to delay lighting light up for about 5 sec. when switched on. My friend (an independent BMW shop owner) decided that the light control module (LKM) was bad so he ordered a new one. After installing the new one, a few wierd things happened:

When I first turned the lights on, the same foglight didn't light. After cursing for a few minutes, I turned the lights off then back on, and it light. The light has worked correctly since, and no check warning since.

However, I then got a check brake lights warning, even though all lights were working. Additionally, a small red dot next to the odometer was lit (this indicates that the cluster was changed/tampered with) Additionally, when the parking lights were switched on, everything worked. Angel eyes lit up, fogs came on, and cluster lit. But when I switch on the headlights, the angel eyes and the cluster lights went off. Headlights and fogs worked, but the AE's (which get power from the signel running light power) and the cluster are dark!

My friend sad that I had to bring the car to a dealer to have the LKM coded to the car. Ok, so I go to the dealer who fixes the brake check (by replacing all the bulbs) but told me that there was no coding to be done to the LKM, and the tamper light came on because the cluster memory is backed up by the lkm and the light can't be reset?


So why the heck am I getting the strange behavior of the cluster and running lights? If I put back the old LKM, everything works as before, (Including the check foglamps warning) And why does the EPC say that the LKM needs to be coded, yet dealer says no?

I know it's an impossible question, I'm just frustrated and I'm just hoping that maybe someone had a similar experience...

Thanks

Originally Posted by mchad

I was having problems, my 97 540i was intermittantly displaying "check front foglamps", while the lights worked. Then the right fog light started to delay lighting light up for about 5 sec. when switched on. My friend (an independent BMW shop owner) decided that the light control module (LKM) was bad so he ordered a new one. After installing the new one, a few wierd things happened:

When I first turned the lights on, the same foglight didn't light. After cursing for a few minutes, I turned the lights off then back on, and it light. The light has worked correctly since, and no check warning since.

However, I then got a check brake lights warning, even though all lights were working. Additionally, a small red dot next to the odometer was lit (this indicates that the cluster was changed/tampered with) Additionally, when the parking lights were switched on, everything worked. Angel eyes lit up, fogs came on, and cluster lit. But when I switch on the headlights, the angel eyes and the cluster lights went off. Headlights and fogs worked, but the AE's (which get power from the signel running light power) and the cluster are dark!

My friend sad that I had to bring the car to a dealer to have the LKM coded to the car. Ok, so I go to the dealer who fixes the brake check (by replacing all the bulbs) but told me that there was no coding to be done to the LKM, and the tamper light came on because the cluster memory is backed up by the lkm and the light can't be reset?


So why the heck am I getting the strange behavior of the cluster and running lights? If I put back the old LKM, everything works as before, (Including the check foglamps warning) And why does the EPC say that the LKM needs to be coded, yet dealer says no?

I know it's an impossible question, I'm just frustrated and I'm just hoping that maybe someone had a similar experience...

Thanks

The LKM needs to be coded. It should have been coded originally when it was replaced. this explains the manipulation dot in the cluster and most likely all of the probs that you are having. You need to explain to the dealer that the unit was never coded to the car. I think they may have misunderstood you, or they just dont know what theyre talking about. One or the other. Regardless it needs to be coded.
Good Luck,

DT

Thanks Dan,

So to confirm, the dealer definitly can remove the tamper dot on the odometer? I only ask because the service writer told me that they couldn't. It's a big concern for me.


Thnks very much

Originally Posted by mchad

Thanks Dan,

So to confirm, the dealer definitly can remove the tamper dot on the odometer? I only ask because the service writer told me that they couldn't. It's a big concern for me.


Thnks very much

Yes, they should be able to adapt the data from the cluster to the new LKM. This problem happens because the LKM saves the Cluster Mileage data redundantly with the cluster and so when your friend installed the base uncoded LKM the cluster and it conflicted and the warning dot appeared. Coding the LKM to match the cluster should fix this. Just explain your situation to them clearly since they are a bit out of the loop on how this situation came to be. If the service advisor cant help you or understand you ask to talk to the shop foreman if necessary. Hopefully it wont come to that. If they cant make it work however, ask for the shop foreman to explain to you exactly why and what can be done.
Good Luck,
DT