[l1stigerlurch]

Hi,

so I basically have two clusters which I coded for my car. Both got virginized VIN and Odo.

For a while I used the M cluster and now I changed to a different one with F-Style Dials.

My issue is that after switching to the F-Style Dial Cluster my Odometer didn't adjust to the new higher Odometer.

Initially both were as following:
M3 - 80.000 km
F-Style 80.000 km

Now the M3 shows the correct Mileage and the F-Style still shows the mileage from the intial coding and also adds normally to that value without tampering dots or anything:
M3 - 81.000 km
F-Style - 80.200 km

I was under the impression that as soon as i switch to the stored cluster that it will adjust automatically to the now higher mileage of the car? Or do i have to again Zero Out the F-Style Cluster and let it grab the mileage?

I tried coding the F-Style and also disconnecting it but it still doesn't grab the correct higher odo from the cas. Or do i need to disconnect battery? Or write an empty .MAN file? or use a tool32 job?

i drove a couple of km hoping it would at some point just automatically adapt to the correct km and also did an ignition cycle but nothing worked. Or is the difference just too low for it to take the correct one from the cas?

if noone has an idea i guess i will open it up again and reset the odo to 0 again...

[LMB335IS]

Originally Posted by l1stigerlurch

Hi,

so I basically have two clusters which I coded for my car. Both got virginized VIN and Odo.

For a while I used the M cluster and now I changed to a different one with F-Style Dials.

My issue is that after switching to the F-Style Dial Cluster my Odometer didn't adjust to the new higher Odometer.

Initially both were as following:
M3 - 80.000 km
F-Style 80.000 km

Now the M3 shows the correct Mileage and the F-Style still shows the mileage from the intial coding and also adds normally to that value without tampering dots or anything:
M3 - 81.000 km
F-Style - 80.200 km

I was under the impression that as soon as i switch to the stored cluster that it will adjust automatically to the now higher mileage of the car? Or do i have to again Zero Out the F-Style Cluster and let it grab the mileage?

I tried coding the F-Style and also disconnecting it but it still doesn't grab the correct higher odo from the cas. Or do i need to disconnect battery? Or write an empty .MAN file? or use a tool32 job?

i drove a couple of km hoping it would at some point just automatically adapt to the correct km and also did an ignition cycle but nothing worked. Or is the difference just too low for it to take the correct one from the cas?

if noone has an idea i guess i will open it up again and reset the odo to 0 again...

It will catch up if you use it long enough.

[l1stigerlurch]

ok i see thank you! but in the meantime i already resetted it again to 0 at least for next time i will just drive for a longer period.

but i noticed another problem: while resetting the m3 style it worked without problem..just connect it and then use the erase eeprom function to 0 out the first two lines. as expected it show for the first two lines 00 and when i connected pin 9 and 18 on startup it show the expected 999990km

since i was already zeroing out the clusters i did the same for the f-style one since i might not use it anymore. strangely when i connected it via pin 9 and 18 it show somehting around 90000km but when i connect it to the eeprom read it show 00 on the first two lines? so i FF'd the 2E0 09-0F and also tried to erase the eeprom which both always says success and the first two lines show 00 but when i connect it via 9 and 18 it starts up again with that 90k km without tamper dot?

Is it that i have to change the 2D0 07 to "00"? or is there another place on the eeprom where the mileage is stored?

[LMB335IS]

Originally Posted by l1stigerlurch

ok i see thank you! but in the meantime i already resetted it again to 0 at least for next time i will just drive for a longer period.

but i noticed another problem: while resetting the m3 style it worked without problem..just connect it and then use the erase eeprom function to 0 out the first two lines. as expected it show for the first two lines 00 and when i connected pin 9 and 18 on startup it show the expected 999990km

since i was already zeroing out the clusters i did the same for the f-style one since i might not use it anymore. strangely when i connected it via pin 9 and 18 it show somehting around 90000km but when i connect it to the eeprom read it show 00 on the first two lines? so i FF'd the 2E0 09-0F and also tried to erase the eeprom which both always says success and the first two lines show 00 but when i connect it via 9 and 18 it starts up again with that 90k km without tamper dot?

Is it that i have to change the 2D0 07 to "00"? or is there another place on the eeprom where the mileage is stored?

A totally zeroed out cluster will actually read 999xxx kms or 621xxx miles. I usually reset mileage to 50 km in a customers cluster just save myself from having to explain it over and over again.

[Sensible_]

Set 2D7 to 00 after you erase the miles in the first 2 lines.

[LMB335IS]

Originally Posted by Sensible_

Set 2D7 to 00 after you erase the miles in the first 2 lines.

Your inbox is full. I have someone that needs a little assistance in London if you can possibly help.

[Sensible_]

Originally Posted by LMB335IS

Your inbox is full. I have someone that needs a little assistance in London if you can possibly help.

Sorry, I've been away. Inbox now open...

[LMB335IS]

Originally Posted by Sensible_

Sorry, I've been away. Inbox now open...

A couple of guys looking for help in London again if you're around.