maxed out at 621358 miles, 1 gigameter limit?

[K5ING]

Just wondering how the guy on this post managed to get his '99 NB odometer to read over 900,000 miles???

Nice find, Brian!

 

[turbocharged798]

Photoshop?

NB's do have a different cluster.

 

[compu_85]

Beetle clusters are not the same make as golf / jetta ones.

-J

 

[Steve99]

Yep, made by a different company, who it seems was willing to use more bytes for the odometer.

 

[K5ING]

I knew the speedo face looked a bit different, but the odometer module looked to be the same, so I figured that it was made by the same company. Maybe Brian can figure out how to use that module with his car so it will keep counting?

 

[turbocharged798]

I knew the speedo face looked a bit different, but the odometer module looked to be the same, so I figured that it was made by the same company. Maybe Brian can figure out how to use that module with his car so it will keep counting?

The odo is run by the main board. I doubt it is even remotely possible to make a NB odo work in a A4 golf/jetta.

Would it be possible to assign more bytes to the odo so it can keep counting?

 

[manual_tranny]

I can't find the link, but I'm sure I saw a MKIV Golf that was supposed to be showing over 750,000 miles... I wonder whether that was real or fake... Maybe different countries were supplied with different parts? ...

 

[alphaseinor]

Keep the ideas coming...

 

[Steve99]

OK, this isn't going to be the prettiest chunk of data to look at but it will do.
This is part of a typical MKIV VDO cluster eeprom dump
Address in hex, hex data, ascii data
You can see the vehicle VIN and Immobilizer ID(both changed from real in this example)

In green is the immobilizer SKC/PIN, its value is stored three times, take the first pair of bytes and swap them, so 2D0E becomes 0E2D, then convert to decimal - 03629 is the SKC in this dump.

In red is the odometer mileage record. It is also two bytes in length but is stored eight times. The mileage record in this dump is 60D2. To get the mileage that would be displayed on the odometer we first swap the two bytes, so 60D2 becomes D260. We then subtract that value from FFFF.
So FFFF - D260 = 2D9F. Now convert 2D9F to decimal which is 11679, now multiply that number by 10 and we have 116790 which is what the odometer would show in miles. The last digit of the odometer is not stored in the same way and is represented by a different byte, that value I do not know. When you program mileage into a new cluster you don't enter it and generally enter 10% of the mileage you really want. If the odometer is configured to metric it simply multiplies the result by roughly 1.6.
So the stored value in a odometer with 0 miles would be FFFF and it decrements from there.
Its fun having a spare cluster to see how things all work...

00A0 | FFFF56575A375A304134343333313333 |..VWZ7Z0A4433133
00B0 | 56575A375A3041343433333133335657 |VWZ7Z0A4433133VW
00C0 | 5A375A3041343433333333322D0E2D0E |Z7Z0A4433332-.-.
00D0 | 2D0E394257444536314A323234343438 |-.9BWDE61J224448
00E0 | 303538FF585858585858585858585858 |058.XXXXXXXXXXXX
00F0 | 5858585858BCDC90FC8931D860D260D2 |XXXXX.....1.`.`.
0100 | 60D260D260D260D260D260D200000000 |`.`.`.`.`.`.....
0110 | 000000001000000000000000314A3039 |............1J09
0120 | 32303930364A20204134563037FF0C00 |20906J A4V07...
0130 | 0000364E3039303939303120192A1101 |..6N0909901 .*..

 

[jcrews]

If you can tell me the exact distance in km displayed through diag, and send the entire memory, that would be helpful.

 

[oilhammer]

G/J clusters are usually VDO, NB is usually Marelli (sp?) IIRC.

Interesting that we have folks working on a solution to how to make our odometers continue to read higher as the miles/km rack up. I have a ways to go as I just turned 386k miles this morning.

 

[K5ING]

G/J clusters are usually VDO, NB is usually Marelli (sp?) IIRC.

Interesting that we have folks working on a solution to how to make our odometers continue to read higher as the miles/km rack up. I have a ways to go as I just turned 386k miles this morning.

I think it's both funny, and a testament to these cars, that this is even considered "a problem".

 

[oilhammer]

I think it's both funny, and a testament to these cars, that this is even considered "a problem".

Haha, indeed, only the folks here would consider this. Like I always say, an odometer in a Volkswagen is just for 2 things: keeping track of PM, and bragging rights.

 

[NewTdi]

you should tell vw and maybe they'll put in in their museum one day. At least they may want to give you a better odometer that can count higher like this guys's 240D that got 4.6 million KM.

http://www.expatica.com/de/news/loc...hbr46-million-kilometres-on-clock--12033.html

This is why I am looking for a 300td for my daughter for when she'll start driving! Mileage and tank built into 1.

 

[alphaseinor]

If you can tell me the exact distance in km displayed through diag, and send the entire memory, that would be helpful.

If I just do the coding to KM it's 999,999 under the adaptation channel it's 65535.

 

[jcrews]

From what I have gathered so far, it appears the application saves the odometer value to nonvolatile memory every 10 km. The 1 km position is counted in RAM and if I am correct, the odometer will revert to a multiple of 10 km each time the battery is disconnected.

Right now my unit has 26669 in the adaptation channel and is coded for miles (165714). I haven't seen any evidence that the distance is stored in nonvolatile memory in miles, at least for IMMO2 boards. I will have to take a look at my IMMO3 board later.

 

[jetta 97]

If I just do the coding to KM it's 999,999 under the adaptation channel it's 65535.

Did you try to read ECU millage?
I was wondering is it ECU passing over 999999KM?
If it does you may want to "0" your cluster and track it millage with your ECU.
Like Steve99 said there is only 2 bytes in Cluster Eeprom for Millage and it won't go over 999999KM so the only way is to see if ECU passing 999999KM and reset cluster to 0 miles and start counting 9999999KM or 660000 miles + what ever new millage is.

 

[jetta 97]

Did you have a chance to check is it ECU passing 999999KM or is it locked like cluster?
I am really want to know this.

 

[alphaseinor]

If you want to, stop by some time, I'm in frisco or Plano most of the time...


I can't seem to get access to the cluster using vagtacho, I can log into it and it shows that I can change the mileage, but it never works right...

 

[RacerTodd]

From what I have gathered so far, it appears the application saves the odometer value to nonvolatile memory every 10 km. The 1 km position is counted in RAM and if I am correct, the odometer will revert to a multiple of 10 km each time the battery is disconnected.

Right now my unit has 26669 in the adaptation channel and is coded for miles (165714). I haven't seen any evidence that the distance is stored in nonvolatile memory in miles, at least for IMMO2 boards. I will have to take a look at my IMMO3 board later.
.

I can confirm this. I replaced my clutch today which means I had the battery disconnected overnight.

When I parked it the odo was at 255414 miles. When I hooked up the battery, it read 255408.

Using your car as an example, dividing 165714/266690 gives a conversion factor of .621373.

255414 miles is 411047 kilometers. If you drop the ones digit you get 41104 as the stored value. Haven't checked it in VCDS, though.

Multiply 41104 by 10 then by .621373 to convert to miles and you get 255409. The cluster may use slightly different methods to do the math which accounts for me being off by one.

 

[bcornish]

holy hell

 

[jetta 97]

It all sorted out.
I went yesterday to Brian and check ECU, and good news is that ECU is passing 999999KM.
So car read 1000000 + KM /660000+ miles.
I reset cluster to "0" miles .
ECU will report actual millage, and he also will count current millage + what ever show on cluster.
Brian took pictures of VCDS showing actual millage in ECU and he will post it in few days.
Also this car is in very good condition as far as how many miles has on clock.And it drives very,very good.

NOTE:
ECU millage is only possible to read on cars 2000+ . 99.5 does not have this function.

 

[Steve99]

Nice!

 

[turbocharged798]

Ah, I was hoping a simple byte change would let the odo count to 999,999 miles and reset.


Are non-immo clusters used in the 99.5 cars set up the the same limit of 999,999KM?

 

[jetta 97]

Ah, I was hoping a simple byte change would let the odo count to 999,999 miles and reset.


Are non-immo clusters used in the 99.5 cars set up the the same limit of 999,999KM?

Yes they do. They also used only 2 bites in eeprom.
That is a problem, because two bites can only record 999999KM.
Millage on 99.5 none immo cluster is stored in eeprom address 036,037,038,039,03A,03B,03C,03D,03E,03F,040,041, 042,043,044,045

 

[jcrews]

Two bytes can record only 65535km, so the old cluster should fail after just over 407215 miles.

 

[mrGutWrench]

The coolest thing about that is over 600,000 miles it likely used less than 13,800 gallons of fuel. $40,000 of diesel at today price.

__. Yes, and if he'd bought a gasser that does ~32 MPG, (assuming that gasoline has been 6% less than diesel fuel since '03), he would have spent about $54,300 on gas. So, is the going price was about $20,000 in '03, he's gotten about 3/4 of a free car.

 

[alphaseinor]

So, here's the deal on the mileage.

I had Jetta97 pop out on Friday, (very nice guy, and knowledgeable) He went into the applications then showed the mileage stored in the ECU, it showed 660,538 miles.

He also was able to reset my kombiinsrument, and now I have reset the mileage to 60,784 (the added miles I just put on over the last two days.). Since he has some other nice tools I had him do the needle lights at startup, and the window rolldown/up mod on the convenience module.

I'll post a photo when I'm nearer to a computer (on my phone now)

 

[jetta 97]

Two bytes can record only 65535km, so the old cluster should fail after just over 407215 miles.

NOPE, two bites can record 999999km.
65535 is just max that you can put in adaptation of cluster with VCDS.
Read post #39 again.
On Eeprom address line 00F0 two bites storing millage not KM.

Let say two bites in dump are 460D. When you swap the two bytes, so 460D becomes 0D46.Then subtract that value from FFFF.
So FFFF - 0D46 = 2FB9. Now convert 2FB9 to decimal which is 62137, now multiply that number by 10 and we have 621370 which you can multiply 1.609 344(1 mile =1.609 344 KM)

621370 miles x 1.609344=999 998 KM

 

[1854sailor]

Conversion?

How can I reprogram the speedo to read in furlongs per fortnight?