qew
Newbie
Karma: +0/-0
 Offline
Posts: 6
|
 |
« on: May 07, 2018, 11:53:36 AM »
|
|
|
I'm in the process of doing a cluster swap on my 2003 A6.
Got the low-line display from factory and picked up a used high line 2003 cluster for cheap at the scrapyard, it came with a 1 year warranty so seemed like a good deal...
For the past week I have been trying to get the pins without much success...
I have a VCDS, a vag-tacho and a "dumb" kkl cable.
So far I've tried vag-tacho, vag commander and vag eeprom programmer, none seem to be able to pull any useful information from either of the clusters.
I managed to get a pin from my ECU using the me795040 tool and from what I understand it should be the same pin for my original cluster, and VCDS does not report anything when I try it so should be fine.
Any advice on how to get the pin, or even a eeprom dump from my new (used) cluster?
Thanks in advance
|
|
|
|
|
Logged
|
|
|
|
|
macxxx
|
|
« Reply #1 on: May 07, 2018, 11:26:57 PM »
|
|
|
Use kkl+ vag eeprom programeer - works best for vdo cluster
|
|
|
|
|
Logged
|
|
|
|
qew
Newbie
Karma: +0/-0
Offline
Posts: 6
|
|
« Reply #2 on: May 07, 2018, 11:53:52 PM »
|
|
|
I have tried, but mostly it's not working at all, just gives a generic "ECU not found" message.
When it does connect and reads the EEPROM none of the fields get filled in (pin/km and so on) and the hex dump is just repeating characters, so obviously somethings not right...
What am I missing here guys?
|
|
|
|
|
Logged
|
|
|
|
|
macxxx
|
|
« Reply #3 on: May 07, 2018, 11:58:36 PM »
|
|
|
Does the cluster work normally?
|
|
|
|
|
Logged
|
|
|
|
qew
Newbie
Karma: +0/-0
Offline
Posts: 6
|
|
« Reply #4 on: May 08, 2018, 12:03:54 AM »
|
|
|
From what I can tell, yes. I have had it hooked up with only the ignition on and everything seems fine, all lights and dials light up as they should, mileage and everything. I connected to it with VCDS and only got two fault codes, one for the Immo (obviously) and another one for the CAN entertainment so I'd say the cluster is working. This is the dump I got when kkl+ vag eeprom programer connected and reported a succesful reading. https://imghost.io/image/1kGjK |
|
|
|
« Last Edit: May 08, 2018, 12:11:40 AM by qew »
|
Logged
|
|
|
|
|
macxxx
|
|
« Reply #5 on: May 08, 2018, 12:15:39 AM »
|
|
|
Try vag k+can comannder 1.4 it works with kkl cable
|
|
|
|
|
Logged
|
|
|
|
qew
Newbie
Karma: +0/-0
Offline
Posts: 6
|
|
« Reply #6 on: May 08, 2018, 12:27:14 AM »
|
|
|
I managed to locate v 1.4, will give it ago soon.
On another note, I've been reading some and it says to use EEPROM programmer with the cable in USB mode, so far I've been using the KKL cable and COM1, should I switch to using my VCDS cable with generic drivers?
|
|
|
|
« Last Edit: May 08, 2018, 12:34:26 AM by qew »
|
Logged
|
|
|
|
qew
Newbie
Karma: +0/-0
Offline
Posts: 6
|
|
« Reply #7 on: May 08, 2018, 02:28:02 AM »
|
|
|
All right, downloaded a new copy of EEPROM programmer 119, same files but different source than the one I had used and tried that before vag k+can comannder 1.4, suddenly it connected properly and it all worked fine. All the fields were filled out with correct data and the EEPROM dump looks solid, so far so good. Connected to the new cluster with VCDS, tried loging in -"incorrect pin"  Is there a reason why the SKC reported by vag_eeprom_programmer is wrong? Could someone please take a look at the dump and see if they come up with another pin than the one reported automatically? https://nofile.io/f/reE1j5yNd3g/4B0920933P++KOMBI+WEGFAHRS.+VDO+D09.BIN |
|
|
|
« Last Edit: May 08, 2018, 02:37:44 AM by qew »
|
Logged
|
|
|
|
qew
Newbie
Karma: +0/-0
Offline
Posts: 6
|
|
« Reply #8 on: May 15, 2018, 01:22:43 AM »
|
|
|
Don't mind me, I'm just being an idiot... For some reason there was a lock time on the cluster, maybe from the scrapyard, and I never bothered to check before I attempted to login. Once I let that run out my pin was accepted without question and the cluster is now happily adapted  |
|
|
|
|
Logged
|
|
|
|
elektronik13
Full Member
Karma: +10/-36
Offline
Posts: 204
|
|
« Reply #9 on: May 20, 2018, 07:11:20 AM »
|
|
|
All right, downloaded a new copy of EEPROM programmer 119, same files but different source than the one I had used and tried that before vag k+can comannder 1.4, suddenly it connected properly and it all worked fine. All the fields were filled out with correct data and the EEPROM dump looks solid, so far so good. Connected to the new cluster with VCDS, tried loging in -"incorrect pin" Is there a reason why the SKC reported by vag_eeprom_programmer is wrong? Could someone please take a look at the dump and see if they come up with another pin than the one reported automatically? https://nofile.io/f/reE1j5yNd3g/4B0920933P++KOMBI+WEGFAHRS.+VDO+D09.BINpin is ..01539.. 244013 km share the eeprom of the original counter |
|
|
|
« Last Edit: May 20, 2018, 07:22:32 AM by elektronik13 »
|
Logged
|
|
|
|
|
