Is it possible to use iscancar to increase the odometer in a MQB cluster where odometer adjustment is not possible?

I believe other tools simulate the car moving to increase it so it feels like the simulate function should allow it?

Thanks in advance,

This appeared to be a support forum for xhorse products but I'm not getting any response to my questions.

Am I in the wrong place?

Where can I get help and support for using Iscancar?

Any ideas @xhorse ?

Do the logs show anything helpful to adapt the cluster?

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

Watching the CAN traffic when reading the PIN/CS on a cluster running 06xx, it looks like bytes 8-12 of the CS are transferred. Not sure about byte 7 though.

Still, that suggests Iscancar has the data so just need to show it to the user.

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!

Using the read pin function on a immo4 cluster, it gives the pin and 6/7 byte CS.

How can I get the full 12 byte CS to reuse keys when only replacing the cluster using Iscancar?

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...

Sure, the serial number is VD01100639.

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: - Re...