BMW Forum - BimmerFest BMW Forums banner

How does an E39 determine miles (specific question based on red tamper dot avoidance)

20K views 25 replies 13 participants last post by  mattmar1  
#1 ·
This thread is opened to determine exactly how the E39 determines miles driven, and specifically related to avoidance of the red tamper dot under unusual (but legal) circumstances.

In another thread, an inoperative ABS was found where the vehicle had the SES/ABS/BRAKE/DSC LEDs removed by the OP so that nobody would know.
- Can our cars be driven without ABS module in place?

The new owner sent out both his instrument cluster & ABS control module to ATE for repairs ... and was cautioned to drive no more than 200 miles.

QUESTION:
- Where are the # of miles stored?
- How does the E39 determine the number of miles driven?
- If the red-tamper-dot appears when the cluster is re-inserted after repair; how do you remove the tamper dot?
- What does a red tamper dot look like anyway (see verbal descriptions that it's a dot to the LEFT of the mileage, but no images yet for the E39)

Notes:
- This thread says PA Soft can remove the tamper dot.
 
#2 · (Edited)
Mileage is stored in the IKE & LCM...and if you have the new style "diamond shaped" key...it also stores mileage. The caution to NOT drive over 120 miles (or 200 km) can be seen in data point #5 in the Redundant Data Storage info below. Also, the tamper dot only appears if the VIN coded into the LCM & IKE do NOT match.

Image

The odometer tamper dot can be seen in these images below...it is directly to the left of the trip odometer...and just below the miles or to the right of km:

Image


Image
 
#3 ·
So if the speedometer/odometer are both inop when the ABS module is out of the car, is the car recording mileage? If so, how? It's my understanding that the Rear Left wheel speed sensor is responsible for this data. If that sensor talks to the car through the ABS module, then what other part/system/method is being used to record mileage?

Has anyone driven their car more than 120 miles with the ABS module removed and NOT had the manipulation dot appear?

Has anyone successfully removed the manipulation dot using GT1, DIS or some other software?
 
#4 · (Edited)
The odometer manipulation dot only appears when the IKE & LCM have a different VIN numbers encoded to them. If you've only removed the ABS module...and one of the wheel sensors is responsible for capturing mileage...then the tamper dot WON'T illuminate since the IKE & LCM still have the same VIN. If there's a difference of 120 miles/200km between them...then a "data transfer fault" is registered (it says nothing about the tamper DOT illuminating). See the SIX data points in the Redundant Data Storage info in my post above. :)

FWIW...I think odometer mileage is captured by one of the sensors on the transmission...but since I don't have the empirical data right now to prove that...I will only offer it up as speculation. :)
 
#5 ·
I think odometer mileage is captured by one of the sensors on the transmission...
It's all very confusing to me, but, when I removed just my ABS module, for a week, no odometer miles were recorded on the cluster.

Of course, that doesn't mean the transmission sensor wasn't comparing the difference, but it intimates (without proving) that the ABS is required for odometer mileage to accrue.
 
#6 ·
Thanks for the info QSilver7. I still believe odometer data comes from the Left Rear speed sensor; odometer/speedometer data does indeed originate at the diff on my E30.

Bluebee, or anyone, did you drive your car more than 120 miles while your ABS module was removed?
 
#9 · (Edited)
Bluebee, or anyone, did you drive your car more than 120 miles while your ABS module was removed?
Nope. I removed the ABS control module, covered the remainder with aluminum foil, drove from San Jose to San Francisco, flew out on a trip, came back about a week later, drove back to San Jose from San Francisco, and put the module back (which was waiting for me back at home). It was all very efficient. I'm sure there's someone out there who drove more than 120 miles with the ABS module out though.
 
#8 ·
Some people seem to have different behaviour when removing the module; I don't have any specific links but it may be possible that different cars/transmissions/years get their data from different points on the car. My grandfather's 540 does not have reliable cruise control (it tends to floor the accelerator for a few seconds occasionally) but the speedometer works very reliably. All four sensors are new; the module is fried. I do find it surprising that the wheel speed sensor provides the only speed information on many cars as reported here.
 
#10 · (Edited)
Left rear wheel speed sensor it is (see DISTANCE SIGNAL in info below taken from BMW info about the BUS system). Apparently the signal goes from the wheel sensor to the ABS/ASC+T/DSC control module, which then relays distance info to the IKE...so removing the ABS/ASC+T/DSC control module interrupts that info from reaching the IKE if it is removed.


Image
 
#12 ·
I've driven well over 250 while my module is at module masters. No red tamper dot. The only time I got it was when I put in an LCM from a 99 540i because I thought I had an LCM issue. Once I plugged my original LCM back, the tamper dot went away. I didn't drive the car at all with the other LCM installed, just started it and tested all the lights.
 
#16 ·
It can be driven more than 120 miles without the risk of a temper dot. I know an E39 that had been driven close to 500 miles without the ABS control module (which was being rebuilt), and upon arrival of a rebuilt unit, no temper mark. No mileage information is transmitted to IKE, nor to LCM. The executive functions of the vehicle do not receive the speed signal, and as far as mileage tracking, your vehicle does not have a clue on how many miles it had been driven, be it 120 or 1200.

For mileage storage, it is similar to removing your rear left wheel sensor. No speed signal. Obviously, ABS module does a lot more than a speed sensor and driving without it is not recommended.
 
#13 ·
On my 540i the cluster had 100% dead pixels. I got my hands on the M5 cluster for cheap. I used PA soft to put my VIN in the IKE module, and used INPA (thru carsoft cables) to code the module properly. This removed the tamper dot as well as got the temperature correct. The oil temp still doesn't work nor does the active tach. The red line is correct however. I recoded the EEProm (with EPROM programmer) on the tach to match correct mileage from the LCM. The tamper dot is just VIN related as this went away as soon as I put my VIN in the IKE, even though the mileage was wrong at first.
 
#14 ·
While my car was not driven more than 200 km with the controller removed, it was driven what I’d estimate to be 1,000-2,000 miles with a bad controller. This caused the speedometer and odometer to be non-operational for 80% of the time. Since I wasn’t concerned about traction control or the lack of ABS (I live in So. Cal. and don’t drive in congestion much.), I put off the significant cash outlay for the new controller. Plus, I hardly ever drove the car.
The bottom line is that I’m sure that the odometer is showing mileage that is short by 1,000-2,000 miles. :eeps: The controller has been bad for that number of miles but failed 6 years ago. (Some guy at the smog check place remarked at how clean my 528i is. I guess that’s, again, because I hardly ever drive it.) There is no tamper dot showing on my odometer. I suppose in a perfect world, there would be. Perhaps that would have been different if I had put the controller from another car in instead of a new one? That said, if anyone tampered with the odometer it will have been, indirectly at least, BMW. They're the ones who designed the car and placed that sensitive ABS controller so close to the exhaust manifold, and made it responsible for too many things. To think that I used to hate the idea of a multi-function SWITCH.....:rolleyes:
 
#15 ·
Sort of related question.....
So if I stick a DME from another 540 that has a VIN of 20 numbers higher than my car will it start?
I'm guessing no because the VIN won't match the VIN stored in the EWS.
Will anything else happen that I won't like?
The reason I ask it because many years ago I bought one for $20, figured it was worth having for some of the parts inside, fuel injector driver transistors, etc.
 
#17 ·
For the record, this was posted today:

This is on my E38, but I figure the setup is similar enough and this is where the action is...

I've had the car for over 6,000 miles and the tamper dot has never been illuminated in that entire period. This morning, I started the car and the tamper dot was ON!

It's daily driven, has absolutely no history of cluster issues, lighting issues, or drivability issues that would make me think there was any communication issue between the cluster and LCM or DME.

What the hell caused this and how can I fix it? Any help is appreciated!

Any errors in this post are purely Swype's fault, not mine.
I don't have a clue but typing /tamper dot F3 in the bestlinks netted these two threads:

  1. Redundant data storage for mileage tamper dot
  2. Tamper dot for mileage explained
In addition, I remember talk of the tamper dot in this coding thread:
- What happens if you don't code the VIN into a new ABS module

Perhaps most appropriate is the result from a title-only E39-only search for "tamper dot", which reveals this thread:
- How does an E39 determine miles (specific question based on red tamper dot avoidance)

BTW: Would you kindly post a picture of the tamper dot to this thread so we can better see what it looks like?
Image
 
#18 ·
This was posted today, which I cross reference here, so that others find it more easily:
Quick question: Is it possible to drive an e39 without a cluster installed? Just wondering...
It is possible to drive an E39 without the cluster as long as you do not exceed 120 miles while it is out. Doing so will illuminate the tamper dot and require a trip to the dealership.
 
#19 ·
For the crosslinked record, this was posted today:
Hi all,

I've recently decided to fox completely my car (change gearbox, renovating front and rear axles, ...). And therefore, i have to fix my old lcm (which has the current front right light problem). But i changed the lcm, waiting the old one to be changed. That´s why i've got a red dot for the mileage mistake.
When i'll put the old lcm back in the car, how can i delete that red dot? I had the idead to change the mileage once down, and once again to reach the original amount. But maybe there's an easyer way?
Can someone explain me, or does anyone has a diy for changing mileage or delete that red dot?

Thank you!
Buy BMW scanner 1.4 and you can input the correct mileage.
 
#20 · (Edited)
For a crosslink, here's a tamper dot thread today ...
> E39 (1997 - 2003) > Tamper dot with replacement (used) LCM. Should I code the dot out PRIOR to driving?

The original 4/99 build LCM III in my car recently decided to go bananas after an unusually frigid cold spell here. I replaced it today with a used (10/99 build) LCM III that I purchased on ebay.

Now, everything seems to be back to normal, all lights work again as they should; the turn signal stalk operates the lights as designed. Only thing I knew I'd have to deal with is the tamper dot.

I have not driven the car out of the drive-way yet. What I would like to know is, should I learn how to code the replacement LCM and remove that dot PRIOR to driving the car, or whether it will matter?
First, if the VIN doesn't match in the IKE & LCM...the tamper dot illuminates and they DON'T exchange any info between each other (see data point #1).

Second, the LCM can only be overwritten with a HIGHER mileage...(see data point #4).

Third, if the mileage differs by MORE THAN 120 miles (this is when the VINs match)...then a data transfer fault will be stored in the IKE (see data point #5).

Everything you need to know or get done requires that the SIX data points in the info below are taken care of...and a BMW dealerships equipment CAN NOT overwrite a used cluster or LCM (see the 1st paragraph AFTER data point #6). They can only work with new or remanufactured components that have officially been "zeroed":

Image
A new cluster/IKE (or a used cluster zeroed by aftermarket software/hardware) will be at zero miles, which then allows the VIN (ID) to be coded to it (see #3)...when the VINs match, then the LCM will share its data with the IKE (mileage & Serv Interval data) as mentioned in #2. :)
 
#23 ·
The analog speedo is "advanced" over the actual speed. Compare the digital speed readout (test 8, high cluster, in km/hr) in the cluster to your GPS.

The spec allows a reading as high as 10% of actual, plus 2.4 MPH.

The odometer is accurate.
 
#24 ·
An interesting mileage-reporting related discrepancy showed up today...
> E39 (1997 - 2003) > Huge mileage discrepancy in EWS when viewed with INPA or PA Soft
Using INPA, I read some of the data recorded in various modules. The odometer mileage readings in all are the same .... except the EWS, where it's over three times as much: about 850,000 km.

But ... checking the EWS for errors, it claims it's error-free .... not even any shadow errors.

Plus, I don't have any symptoms of immobilizer functions acting up, or keys not working ... no nothing to complain about.

I'm just wondering why the EWS-recorded mileage is so huge? The unit's manufacture date is pretty close to the dates for other original modules in the car, so I think it's original, too.

1. Why the discrepancy? How does it happen?
2. Can it be "fixed" by re-synching with the DME? [Probably not ... I don't see an odometer reading in the DME.]
3. Will it cause any communication problems with other modules?
4. When I sell the car, will the buyer likely deem it suspicious or indicative of tampering?

I also recently purchased and installed BMW Scanner 1.4.0 (aka PA Soft). When I click the EWS page in that, it shows me a selection of coding options in there somewhere with one button to "clear and unlock" the EWS. That button is "live," not grayed-out. Below that choice, it states that the EWS is currently Locked. I thought the EWS was not codeable but still would like to sync the mileage with other modules, namely, read it in from the IKE or LCM. But ... think I'll leave it alone as I don't know if I'm burning bridges messing with this.

Any one else have crazy mileage in their EWS? Thoughts?