Try to locate a wiring diagram and check the wiring that goes from the cluster to the lcm. It’s possible that there could be a short. When you find the wire or wires remove both and check the continuity to make sure that they is not a break in the wiring. I’m pretty sure that the cluster gets the info first and passes it to the lcm.


Sent from my iPhone using Tapatalk

 

Try to locate a wiring diagram and check the wiring that goes from the cluster to the lcm. It***8217;s possible that there could be a short. When you find the wire or wires remove both and check the continuity to make sure that they is not a break in the wiring. I***8217;m pretty sure that the cluster gets the info first and passes it to the lcm.

No way. Not a wiring problem. Sounds like the non volatile storage chip in the LCM is bad. Not sure if it's internal to the microcontroller or a separate chip, but, it sounds like the LCM needs to be replaced, or just live with it. If you don't read the fault codes you wouldn't know the problem is there.

 

I wouldn't think this is a wiring issue, considering that everything else with LCM works fine - I can scan it, I can code it, etc. And also, I don't think there's any wiring directly from IKE to LCM - they communicate over the shared bus that's used by other modules too. No?

 

following. i have the same issue so once i a week i update the lcm with the correct mileage

 

Maybe try setting the last two digits of the LCM kilometers value to 00 (ie if IKE has 235917 km then set LCM to 235900). Works on my early 2002 build date car, not sure about 2004 though...

 

Tried that a number of times. Actually, I'm pretty sure that if you try to code 123456 as the LCM mileage, it writes it as 123400 anyway.

 

Curious if you ever figured this out. I***8217;m getting this code through PA Soft too, have no tamper dot and am fairly certain that nether cluster nor light module were ever replaced

 

Checked this morning and the error seems to have gone away and not come back since I reset the code. Weird

 

Replaced faulty EGS transmission module. Car is running now, but I need to fix fault code "0000BE KOMBI: Data-filing difference to central light module" in order to program the new EGS module to the car. Code Type= ABL "Read out LCM operating data" (ABL-DIT-S6300_00001 - Read out LCM operating data - V.5)

Anyone know how to correct issue to clear fault?

 

If yo have > 300k KMs, you can***8217;t. LCM can***8217;t store more than 300k, so that error will remain permanently.

 

then why if you enter 350,000 in pasoft this save ?

and he can't automatically


and by hand maybe

 

@ up

 

Gentlemen, maybe I wrote it wrong? the point is you can manually enter e.g. 350,000 in PASOFT and can be saved,but LCM but he won't be alone was updating himself

So why can you save manually mileage greater than 300,000km??

 

@up

 

I never solved the issue that I noted in the original post.

Seeing some of the subsequent replies, I've since found a handful of posts (here and in other forums) that seem to indicate that IKE->LCM fails for any value greater than 300,000km.

It's notable that when I first discovered this issue, my car already had more than that.

 

just ... why can't it update itself alone

and you can enter any mileage manually
my colleague has the latest soft in the LCM module sw 4.5 cid27
and yet it still doesn't update itself

 

@up

 

It's a bug in the LCM. There's no fix.

 

I went through my notes and confirmed that this FIRST occurred on my vehicle when the LCM was stuck at 300,000km. This was back in December 2017. I even took a screenshot from PASoft (IKE was 301,447, and LCM was 300,000). Combine that evidence with multiple people saying that 300,000km is the limit for IKE->LCM transfers, and that's pretty conclusive that this is a known problem with no fix.

 

It'll come back. The EGS has nothing to do with it (in fact, many of our cars do not have have an EGS at all).

 

Same issue
I can change LCM, can change cluster, did anyone solve it?

host image online

 

My mileage is over 300km, but I can program lcm to any mileage.
Wonder if I program it to like 100km, will this error disappear?

 

2004 E46 XI. I am the original owner. Almost 200K miles.

After experiencing what I can only describe as "strange electrical things" a year or so ago while running the car to bleed the coolant system (a bunch of codes I had never seen before, but all "not currently present", outdoor temperature was -128C, gas gauge movement on its own), it's consistent that I'm always getting a code that complains that the mileage is unable to be written to LCM. I use PASoft. When first starting PASoft, IKE indicates the correct mileage (currently, 319146km), but LCM never moves beyond what I write to it (last value I wrote was 318500km). PASoft shows this as a red discrepancy when it first starts up, and IKE throws a code when scanned for errors.

BE [190] Data-filing difference to central light module (LCM)

I've tried:

• recoding the LCM
• recoding the IKE and recalculating the checksum
• reprogram LCM using "Copy FA Coding", "IKE->LCM"

Done all of these multiple times. Still, after driving for a bit, the LCM mileage doesn't update.

IKE and LCM are original and have never been removed from the dashboard.

This in no way affects drivability of the car or anything else noticable except when scanning.

Any ideas?

BE Data-filing difference to central light module

Could be simple - I replaced interior lights with LEDs in the front, but not in the back seat (didn’t have time at the moment), and this came up on the error list. Got the two in the back seat changed a couple weeks later, cleared the code, and it remains clear now.

Apparently the LCM expects all bulbs to send equal power usage (usage filing) within a group; however, the LEDs are sending a lower signal and triggering the message regarding inconsistency.

Could be something along these lines - LED replacements in some but not all lights in a group - running lights, interior, dash, trunk, license plate, etc. You may try switching back or replacing all in the group circuit with matching LED or non-LEDs.

 

BE Data-filing difference to central light module

Could be simple - I replaced interior lights with LEDs in the front, but not in the back seat (didn’t have time at the moment), and this came up on the error list. Got the two in the back seat changed a couple weeks later, cleared the code, and it remains clear now.

Apparently the LCM expects all bulbs to send equal power usage (usage filing) within a group; however, the LEDs are sending a lower signal and triggering the message regarding inconsistency.

Could be something along these lines - LED replacements in some but not all lights in a group - running lights, interior, dash, trunk, license plate, etc. You may try switching back or replacing all in the group circuit with matching LED or non-LEDs.

did you read the thread through?
it’s because the LCM can’t accept more than 300,000km (186,411 miles).