Pages: [1]
Author Topic: VW Mk3 Cluster Info  (Read 10151 times)
Drehkraft
Jr. Member
**

Karma: +9/-0
Offline Offline

Posts: 46


« on: March 23, 2013, 01:31:27 PM »

The purpose of this thread is for anyone to post useful information on older Mk3 clusters. 

Mileage Correction (in KM):
Read eeprom (93C46C) in 16bit
Mileage is store in the last 2 lines, and repeats 8 times per line
Change it up and re-write the eeprom.

Format is as follows:

FFFF = 0 kms
85EE = 999,999 kms

It counts down from FFFF (65535 in dec).  The mileage has a divisor of 32.   FFFE = 32 km.  In short if you wanted to program the cluster to read 100,000 kms:

100,000 / 32 = 3125 decimal
3125 dec = C35 hex
FFFF - C35 = F3CA

Your last 2 lines would look like:

F3CA F3CA F3CA F3CA F3CA F3CA F3CA F3CA
F3CA F3CA F3CA F3CA F3CA F3CA F3CA F3CA

Please add anything useful to this thread that may be included in the rest of the dump file. 



Logged
AmIdYfReAk
Full Member
***

Karma: +9/-0
Offline Offline

Posts: 129


« Reply #1 on: May 20, 2013, 12:17:55 PM »

First I'd like to say thanks to Dreh for this posting, And I'll add my findings as well

I'm in the middle of a B3 TDI Swap ( much like Dreh was in a Mk3 TDI swap ) and wanted the cluster to match the body KM.

Following his setups got me Nothing more than -------- Across the screen of the cluster, when re-checking the EEPROM the first 5 addresses where changed to seemingly random numbers while the rest of the hex addresses i put in where correct.

so back to basics and seeing if i could find whats different between the two clusters, time to see how the math worked.

The Cluster had 139'370 KM on it, and the Hex read: 22 06.

Hex 22 06 converted to Decimal got: 8710 so clearly that was wrong.
what about 139370 to hex? 2206A!

The First attempt was to put the cluster to 83000KM or Hex 14438, So i dropped the 8 and programmed it in the EEPROM.
That got me 83007KM on the dash.

So lets try the desired number that i REALLY need, 82350KM or 141AE.
Programmed it, and it got me 82351KM

Honestly, Close enough...

I still dont know how the last hex place holder works, or how its converted to get the 100% Desired Reading, but within 1KM I'm good with.

If someone would like to play with it a little more, here is the code for the Bin file:
Code:
14 1A 14 1A 14 1A 14 1A 14 1A 14 1A 14 1A 14 1A
14 1A 14 1A 14 1A 14 1A 14 1A 14 1A 14 1A 14 1A
00 00 01 68 01 68 00 96 01 2C FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF F0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
00 96 01 68 01 68 00 F0 01 2C 00 FA FF FF FF FF
FF FF E8 20 1E 80 58 05 00 FB FF FF 08 00 FF 20
B0 00 FF 27 10 BD 10 7F 04 00 01 FA 00 00 FF 0E
2D 14 01 2D 18 04 7A 25 37 16 01 31 0E BA FF FF
48 33 FF A1 FF FF FF FF FF FF FF FF FF FF 35 15
60 61 30 66 3F 18 F3 06 C2 0A 27 02 06 01 59 03

And here is some more information for those who'd like to play with the clusters:

Quote
Lines 0000: and 0010: set the millage that is displayed

no mfa man 00D0: 14 2D 2D 01 14 18 24 7A 0E 46 34 01 AF 17 FF FF
mfa auto 00D0: 14 2D 2D 01 1C 18 0F 7A 0E 46 34 22 AF 17 FF FF
mfa man 00D0: 14 2D 2D 01 1C 18 0F 7A 0E 46 34 02 AF 17 FF FF

4 gas tach 00C0: 00 B0 32 FF BD 10 7F 10 00 04 FA 01 1C 00 20 FF
6 gas tach 00C0: 00 B0 08 FF BD 10 7F 10 00 06 FA 01 09 00 15 FF

Taken from:
http://forums.tdiclub.com/showthread.php?t=268798&page=3


Keep in mind, this information is for the B4 Clusters, I'm sure some of it works for the B3 stuff, but your results may differ.
Logged
jaspersk
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 1


« Reply #2 on: November 07, 2013, 11:00:36 AM »

I can confirm what Drehkraft found.   The mileage is stored in the last 16 bytes (two rows) of the memory.   The calculation is the same for miles as well as kilometers.   I can provide a little more information for anyone trying to get down to the exact mile and doesn't want to average to 32.   If you consider all 16  bytes, they are not all the same most often.  If they were, they would only change once every 32 miles.  Actually, what happens is each time the odometer sees two miles, it decrements one byte by one bit.   Each two miles, it decrements the next byte.   The mileage is then the average of all 16 bytes.  However, because it would need 32 bytes to actually capture the number correctly using this method, I found that it actually can't store an even number.   To rectify that, they store a bit in volatile memory.   You can prove this by  turning the cluster off when it has an even mileage on the odometer.  You will find that it will actually power up 1 mile different with an odd mileage number.   While the TDI cluster that AmIdYfReAk was programming clearly used a different scheme than Drehkraftr or I had, this same insight likely applies to why he was off by one mile from what he expected.  Probably pointless for our objective but interesting none the less.
Logged
Mechsoldier
Full Member
***

Karma: +5/-11
Offline Offline

Posts: 106


« Reply #3 on: March 17, 2016, 04:11:17 PM »

Sorry to be a N00B but what program are we supposed to use for this I dont see this particular memory type in the me7eeprom or 95040 files....is this done through the obd port or do I need to remove the cluster and use a chip burner or? I have all of the above, my real vag tacho couldn't seem to do it either.
Logged
dbreeze
Jr. Member
**

Karma: +9/-0
Offline Offline

Posts: 41



« Reply #4 on: April 29, 2016, 08:50:46 AM »

It's a 93C46 chip that need to be removed and reflashed with an edited file.

Check out my post http://nefariousmotorsports.com/forum/index.php?topic=8305.msg74518 where I link to a web-based calculator I made that shows you the edits to make to the eeprom file and can even edit an uploaded file for you.
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.017 seconds with 17 queries. (Pretty URLs adds 0s, 0q)