[kafkaesk]

Hey guys!

The speedometer of my father's Golf 5 MJ 2006 is broken, display didn't turn on anymore and the engine doesn't start. 

With VCDS, I tried to read the fault codes in 17 - Instrument Cluster, but the ECU didn't respond. 
So I disassembled the speedometer to check the circuit board but couldn't find any fault.
Then I put the meter back into the car... but without the casing, only the two circuit boards connected, because the wirings in the car's dashboard are seriously too short for testings -.-
And - I don't know why, because I didn't change anything - the display magically turned back on, but the mileage didn't show up anymore, but "Error" was flashing.
Then I tried to read 17 - Instrument cluster with VCDS again and it showed me:
00003 - Control Unit
014 - failure

While the display was working, I was able to read the EEPROM with K+CAN Commander. But anything else like "Read ROM/FLASH", "Read/Write RAM", "Read Security Access Code" and "Read/Write IMMO data" didn't work.
Since I already found out that these Visteon speedometers (Part# 1K0 920 862 A) are really sensitive when it comes to voltage peaks and are most likely to fail, I ordered a used speedmeter from VDO, Part# 1K0 920 872 J of the same production year (2006).

Today, the new speedometer arrived, and when I got to the car, I realised that the old / broken speedometer didn't turn on anymore, so it seems as if it has now died completely. With a CH384A programmer, I was able to read the ST95160 EEPROM of the Visteon as well, but they both look the same (I can provide both if necessary).
Then I put in the new speedometer and could already program the mileage back to the "original" one with K+CAN, I could also read all 4 memorys with K+CAN as well (EEPROM, Flash, RAM, IMMO Data) but at this point I am stuck...

I don't know the login code of the broken speedometer, I'm not able to read the "Security Access Code" (is this the login code, btw?) of the new speedometer, and the car doesn't turn on because either VCDS, or the speedo display says "immobiliser not learned / programmed".
VCDS now shows up errors in 1 - Immobiliser not learned, and 25 - Immobilizer is not reachable any more.

I hope you guys can help me, just tell me which BIN files / other information you need.

Attached, there are already 3 files:
Tacho_EEPROM.bin - The old EEPROM (Vistreon) read with K+CAN
Tacho_neu_EEPROM.bin - The new EEPROM (VDO) read with K+CAN
ST95160W_CH341A.bin - The old EEPROM read with my CH341A programmer

Greetings, Daniel.

[evg_eni]

Hi. First save your abs coding.
You can try to adapt new vdo cluster with vcds and both pins. If this not work, then post screenshot of vdo immo data reading with your k+can. If this tool read and write immodata correct then i can give you full details decoded from your visteon cluster.

[raffy haddad]

Hey guys!

The speedometer of my father's Golf 5 MJ 2006 is broken, display didn't turn on anymore and the engine doesn't start. 

With VCDS, I tried to read the fault codes in 17 - Instrument Cluster, but the ECU didn't respond. 
So I disassembled the speedometer to check the circuit board but couldn't find any fault.
Then I put the meter back into the car... but without the casing, only the two circuit boards connected, because the wirings in the car's dashboard are seriously too short for testings -.-
And - I don't know why, because I didn't change anything - the display magically turned back on, but the mileage didn't show up anymore, but "Error" was flashing.
Then I tried to read 17 - Instrument cluster with VCDS again and it showed me:
00003 - Control Unit
014 - failure

While the display was working, I was able to read the EEPROM with K+CAN Commander. But anything else like "Read ROM/FLASH", "Read/Write RAM", "Read Security Access Code" and "Read/Write IMMO data" didn't work.
Since I already found out that these Visteon speedometers (Part# 1K0 920 862 A) are really sensitive when it comes to voltage peaks and are most likely to fail, I ordered a used speedmeter from VDO, Part# 1K0 920 872 J of the same production year (2006).

Today, the new speedometer arrived, and when I got to the car, I realised that the old / broken speedometer didn't turn on anymore, so it seems as if it has now died completely. With a CH384A programmer, I was able to read the ST95160 EEPROM of the Visteon as well, but they both look the same (I can provide both if necessary).
Then I put in the new speedometer and could already program the mileage back to the "original" one with K+CAN, I could also read all 4 memorys with K+CAN as well (EEPROM, Flash, RAM, IMMO Data) but at this point I am stuck...

I don't know the login code of the broken speedometer, I'm not able to read the "Security Access Code" (is this the login code, btw?) of the new speedometer, and the car doesn't turn on because either VCDS, or the speedo display says "immobiliser not learned / programmed".
VCDS now shows up errors in 1 - Immobiliser not learned, and 25 - Immobilizer is not reachable any more.

I hope you guys can help me, just tell me which BIN files / other information you need.

Attached, there are already 3 files:
Tacho_EEPROM.bin - The old EEPROM (Vistreon) read with K+CAN
Tacho_neu_EEPROM.bin - The new EEPROM (VDO) read with K+CAN
ST95160W_CH341A.bin - The old EEPROM read with my CH341A programmer

Greetings, Daniel.

Here is your orig data 
On the new dash specify please what eep type in 
Any way try with k+can these data

[kafkaesk]

Thanks to you both helping me!

@evg_eni:
Okay, I will go read the ABS Coding now as well.
Unfortunately, I don't have both PINs, but Raffy now provided the PIN for the old Vistreon.
Yes, I can read the VDO immo data with my K+CAN. I attached you the Immo-Reading of the VDO.

@raffy haddad:
Thanks for the data! I'm not sure what EEP type in the new VDO is... Can I find it out without disassembling the speedometer?

Greetings, Daniel.

[evg_eni]

your key file is correct, but commander also must have dump editor...

[kafkaesk]

I just read the ABS configuration as @evg_eni told me...
Also, I took the screenshots as requested.

Please find attached the screenshots of K+CAN reading the new VDO immo data.

I also found a screenshot which I took yesterday of the old Vistreon.
Since it doesn't show any data in the "big field" and no serial number, I am not sure whether this data is valid.
Also, the PIN in the screenshot differs from the PIN @raffy haddad provided.

[evg_eni]

you have both pins, from Raffy (ori) and 03645 from vdo. try with vcds.

[elektronik13]

you have both pins, from Raffy (ori) and 03645 from vdo. try with vcds.

there is no way this would work with VCDS

---

I just read the ABS configuration as @evg_eni told me...
Also, I took the screenshots as requested.

Please find attached the screenshots of K+CAN reading the new VDO immo data.

I also found a screenshot which I took yesterday of the old Vistreon.
Since it doesn't show any data in the "big field" and no serial number, I am not sure whether this data is valid.
Also, the PIN in the screenshot differs from the PIN @raffy haddad provided.

read immo data from ecu

[kafkaesk]

you have both pins, from Raffy (ori) and 03645 from vdo. try with vcds.

Okay... Do you have a guide how to do it correctly?

read immo data from ecu

How?

[evg_eni]

@elektronik13 
Until 2006 year is possible, if not work i will post immo from visteon

Daniel

http://wiki.ross-tech.com/wiki/index.php...t_Cluster)

http://wiki.ross-tech.com/wiki/index.php...y_Matching