forum Xhorse

I want to replace the cluster in a 2011 Skoda Octavia.

I've bought iscancar as it's advertised as being able to replace PQ35 immo4 instrument clusters and I've updated it to the latest v2.3.1 software.

I've extracted the PIN and CS from the original/old cluster.
I've also extracted the PIN and CS from the replacement/new cluster after filling a section of EEPROM with FF's.
The "read PIN" functions fails on my EDC17 ECU, any suggestions?

I then use: Special function -> Adapt unit module -> Replace PQ35 dasboard (UDS)

It asks for a PIN and CS, I assume this is for the replacement/new cluster?
It then asks for a PIN, CS1 (ECU), CS2, power level etc.

Where can I get PIN, CS1 (ECU) and CS2? I assume PIN and one CS are from the old cluster. What about the other CS?

The original cluster has two keys and works normally with the car/immo.
The new cluster has no keys and obvious isn't paired to the car.

With the original cluster connected:
- Read the pin/CS from the original cluster (with key)

With the new cluster out of the car, using an external programmer:
- Read the EEPROM from the new cluster
- Filled 13A0-144F with FF and wrote it back to the new cluster

With the new cluster connected:
- Read the pin/CS from the new cluster (without key)
- Restored the original EEPROM to the new cluster
- Started the "Replace PQ35 dasboard (UDS)" function
- Entered the pin/CS from the new cluster, hit "OK"
- Entered the VIN, pin, CS1 (ECU), power level from the old cluster
- Entered junk for CS2 (001122334455), hit "OK"

It gave me two options at this point, I tried both but they failed with some error about writing the pin/CS.

Any suggestions where I've gone wrong and how to get the new cluster matched without it's key would be much appreciated.

Few links that I've used:

I've been following this guide which seems to be an older firmware version:
http://blog.obdii365.com/2017/09/20/rep ... er-mm-007/

This page shows that immo4 has a 12 byte CS which can be split into CS1 and CS2. Iscancar only shows the first 6 bytes.
http://blog.xhorsetool.com/vvdi2-vag-4t ... er-system/

This post suggests only the first 6 bytes are important and the last 6 bytes and be anything/random:
http://www.digital-kaos.co.uk/forums/sh ... ost2882367

Please post device s/n first

Sure, the serial number is VD01100639.

I tried the same procedure on a different dash and it was successful.

Dash that worked - NEC+24C64 (2014-VW/Skoda/Seat)
Part: 5L0 920 970 S
SW: 1018
HW: H03

Dash that's failing - NEC+24C64 (2009-)
Part: 1Z0 920 943 K
SW: 0420
HW: H20

In both cases, I used the same 'keyless' method to extract the PIN/CS and restored the EEPROM afterwards. I also used the same 'new' details in each case. Is this a bug? Is there any information I can provide to help solve this?

More detail on the error:

Connecting controller...
VAG Number:5K0953234 SW:0420 Type:IMMO
Writing data...
Try to set PIN/CS, please wait... Failed!
Procedure failed!

I've attached the original EEPROM dump plus logs from extracting the PIN/CS and attempting to adapt the cluster:

Any ideas @xhorse ?

Do the logs show anything helpful to adapt the cluster?