jase1979
Newbie
Karma: +0/-0
 Offline
Posts: 17
|
 |
« on: July 28, 2014, 01:33:36 PM »
|
|
|
Hi, it's my first post of the forum, so hello.
I've messed up my cluster on my 2002 Audi TT. I messed it up using VAGTACHO. The cluster is a Magneti Marelli brand. I also tried to read the cluster eeprom using vag k commander. This saved a file, but it doesn't look right. I've attached the file to this post.
Can anyone give me advice on how to fix this please? The actual mileage is 132000m.
Thanks in advance for any help offered.
|
|
|
|
|
Logged
|
|
|
|
jase1979
Newbie
Karma: +0/-0
Offline
Posts: 17
|
|
« Reply #1 on: July 29, 2014, 11:37:54 AM »
|
|
|
I've managed to dump the full eeprom I think. Please find attached.
|
|
|
|
|
Logged
|
|
|
|
Allabout
Full Member
Karma: +0/-2
Offline
Posts: 54
|
|
« Reply #2 on: July 29, 2014, 09:12:38 PM »
|
|
|
Hi, it's my first post of the forum, so hello.
I've messed up my cluster on my 2002 Audi TT. I messed it up using VAGTACHO. The cluster is a Magneti Marelli brand. I also tried to read the cluster eeprom using vag k commander. This saved a file, but it doesn't look right. I've attached the file to this post.
Can anyone give me advice on how to fix this please? The actual mileage is 132000m.
Thanks in advance for any help offered.
With the Magneti Marelli brand clusters, they can sometimes take 1-4 hours to crack the SKC. Once you have the SKC, go and login then adjust your mileage reading accordingly. Otherwise, find another cluster, pull SKC then perform a cluster swap and adaption. |
|
|
|
|
Logged
|
|
|
|
jase1979
Newbie
Karma: +0/-0
Offline
Posts: 17
|
|
« Reply #3 on: July 30, 2014, 04:08:17 AM »
|
|
|
Hi, I have the SKC for the cluster, just don't know how to change the odometer. It's stuck on 999999 at the moment. I've tried changing it with VAG tacho, (This is what messed it up in the first place)
Are you referring to a different method to changes the odo?
Thanks the the reply.
Jase
|
|
|
|
|
Logged
|
|
|
|
|
eliotroyano
|
|
« Reply #4 on: July 30, 2014, 07:23:03 PM »
|
|
|
Hi, I have the SKC for the cluster, just don't know how to change the odometer. It's stuck on 999999 at the moment. I've tried changing it with VAG tacho, (This is what messed it up in the first place)
Are you referring to a different method to changes the odo?
Thanks the the reply.
Jase
Try to write cluster odometer to 000000. I have read that any cluster with less than 100kms can be changed using VCDS/VagCom to the mileage you want without messing it up with other software. I tested it when I change my cluster to a newer one and works quite good. Also cluster needs to be adapted before for sure. |
|
|
|
|
Logged
|
|
|
|
jase1979
Newbie
Karma: +0/-0
Offline
Posts: 17
|
|
« Reply #5 on: July 31, 2014, 02:35:57 AM »
|
|
|
I've tried that, it still shows 999999. These marelli clusters are tricky. I read that the odometer is stored 0xAA to 0xC8 and has two blocks that are 0x90 bytes long, one storing the an inverse odo and the other storing the real odo. I don't know how to decipher the reading I have in my dump to try and make changes offline and re-flash the eeprom.
Any ideas?
|
|
|
|
|
Logged
|
|
|
|
Allabout
Full Member
Karma: +0/-2
Offline
Posts: 54
|
|
« Reply #6 on: July 31, 2014, 05:08:13 AM »
|
|
|
I've tried that, it still shows 999999. These marelli clusters are tricky. I read that the odometer is stored 0xAA to 0xC8 and has two blocks that are 0x90 bytes long, one storing the an inverse odo and the other storing the real odo. I don't know how to decipher the reading I have in my dump to try and make changes offline and re-flash the eeprom.
Any ideas?
vagtacho, just be able to assist you with this. |
|
|
|
|
Logged
|
|
|
|
jase1979
Newbie
Karma: +0/-0
Offline
Posts: 17
|
|
« Reply #7 on: July 31, 2014, 07:54:40 AM »
|
|
|
VAGtacho messed it up in the first place. I have tried again, however, any value I put in, always shows up as 999999.
|
|
|
|
|
Logged
|
|
|
|
|
littco
|
|
« Reply #8 on: August 01, 2014, 12:38:37 AM »
|
|
|
VAGtacho messed it up in the first place. I have tried again, however, any value I put in, always shows up as 999999.
I think the first cluster dump you posted is the correct one, I say this as I have read the Dump off my clusters with carprog directly off the board and it's the same as your ttcluster1.bin file in terms of size and layout. This was the way Kompressed said I needed to read it. I have the same problem , as mine went 99999 with vagtacho and I'm hoping to fix it in a hex editor and reflash, Not much luck at the moment though as Kompressed very kindly had a look at the file for me and corrected it back to 00000 but even with the changes it is still reading 99999 on the cluster! I have bought 3 cheap clusters off ebay all working bar the dials which is an easy fix so will get the dumps off thoughs and see what I can find out. |
|
|
|
|
Logged
|
|
|
|
jase1979
Newbie
Karma: +0/-0
Offline
Posts: 17
|
|
« Reply #9 on: August 01, 2014, 02:42:37 AM »
|
|
|
Nice one, I hope you find a solution. I've worked out how the mileage is stored but, I think there must be some other info or a checksum somewhere in the eeprom.
When I dump the cluster using the "direct" setting, I get an file that is 0x10000 bytes long, the part of interest to us starts at 0x3800 and is 0x800 bytes long.
The odo seems to be recored 36 times in inverse hex and 36 times normal hex below are some examples from a dump of this forum, I worked out the mileage for easy reading, the reading seems to go up in twos but the lowest reading isn't at the start or end, it's in the middle and there are two orders in each column. When I have tried reseting using vagtacho, each of the readings in the columns is set to the same number and doesn't go up in twos:
FFFE5444 0001ABBB 109499
FFFE5442 0001ABBD 109501
FFFE5440 0001ABBF 109503
FFFE543E 0001ABC1 109505
FFFE543C 0001ABC3 109507
FFFE543A 0001ABC5 109509
FFFE5438 0001ABC7 109511
FFFE5436 0001ABC9 109513
FFFE5434 0001ABCB 109515
FFFE5432 0001ABCD 109517
FFFE5478 0001AB87 109447
FFFE5476 0001AB89 109449
FFFE5474 0001AB8B 109451
FFFE5472 0001AB8D 109453
FFFE5470 0001AB8F 109455
FFFE546E 0001AB91 109457
FFFE546C 0001AB93 109459
FFFE546A 0001AB95 109461
FFFE5468 0001AB97 109463
FFFE5466 0001AB99 109465
FFFE5464 0001AB9B 109467
FFFE5462 0001AB9D 109469
FFFE5460 0001AB9F 109471
FFFE545E 0001ABA1 109473
FFFE545C 0001ABA3 109475
FFFE545A 0001ABA5 109477
FFFE5458 0001ABA7 109479
FFFE5456 0001ABA9 109481
FFFE5454 0001ABAB 109483
FFFE5452 0001ABAD 109485
FFFE5450 0001ABAF 109487
FFFE544E 0001ABB1 109489
FFFE544C 0001ABB3 109491
FFFE544A 0001ABB5 109493
FFFE5448 0001ABB7 109495
FFFE5446 0001ABB9 109497
|
|
|
|
|
Logged
|
|
|
|
ddillenger
Moderator
Hero Member
Karma: +641/-21
Offline
Posts: 5640
|
|
« Reply #10 on: August 01, 2014, 11:14:08 AM »
|
|
|
I think the problem is the MCU has been corrupted. To fix it is a solder job. I think carprog will fix it.
|
|
|
|
|
Logged
|
Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!
Email/Google chat:
DDillenger84(at)gmail(dot)com
Email>PM
|
|
|
jase1979
Newbie
Karma: +0/-0
Offline
Posts: 17
|
|
« Reply #11 on: August 01, 2014, 02:09:04 PM »
|
|
|
Thanks for the reply ddillenger. Excuse my ignorance but what is the MCU?
Using Vag Commander, I can read two different size dumps. The biggest is 10000 bytes long the smaller one which is part of the 0x1000 byte dump and contains the immo and odo data is 0x800 bytes long. The smaller file is made up of data from address 0x3800 and 0x800 bytes long.
Is the data from 0x3800 and 0x800 bytes long the eeprom data? If so, I goes the rest of the data is software. Is that the MCU software?
I hope the above makes sense, as I'm pretty new to this kind stuff.
Thanks again
|
|
|
|
|
Logged
|
|
|
|
|
littco
|
|
« Reply #12 on: August 02, 2014, 05:02:06 AM »
|
|
|
Thanks for the reply ddillenger. Excuse my ignorance but what is the MCU?
Using Vag Commander, I can read two different size dumps. The biggest is 10000 bytes long the smaller one which is part of the 0x1000 byte dump and contains the immo and odo data is 0x800 bytes long. The smaller file is made up of data from address 0x3800 and 0x800 bytes long.
Is the data from 0x3800 and 0x800 bytes long the eeprom data? If so, I goes the rest of the data is software. Is that the MCU software?
I hope the above makes sense, as I'm pretty new to this kind stuff.
Thanks again
Microcontroller. It's a Motorola mcu and needs 4 wires soldered on to the board and use carprog to read the flash. It's actually pretty simple and just needs the rear case removing, once the wires are soldered on you can either run it whilst plugged into the dash harness or use a bench harness.. The flash you down load is as I uploaded in the original sections... |
|
|
|
|
Logged
|
|
|
|
BDK
Jr. Member
Karma: +2/-0
Offline
Posts: 28
|
|
« Reply #13 on: August 02, 2014, 12:53:14 PM »
|
|
|
try these 2 files, report back
I had some trouble a while back and setting the cluster to 0km wouldn't work but setting it to 1km did.
|
|
|
|
|
Logged
|
|
|
|
jase1979
Newbie
Karma: +0/-0
Offline
Posts: 17
|
|
« Reply #14 on: August 03, 2014, 04:32:00 AM »
|
|
|
I'm away from home for two weeks, soon as I'm back, I'll try the files and report back. Thanks for all the replies
|
|
|
|
|
Logged
|
|
|
|
|
