How to swap 2012+ vw caddy dashboard

[Dayo]

What is the best tool to swap vwcaddy 2012 dashboard to high cluster? Iv read up that vcds wont do it, what about vag can pro? As immobiliser is in these. Thanks

[H2Deetoo]

You need proper tools to read immo from orig cluster, and write to target cluster.
You cannot use VCDS or VCP.

[talk2idris]

VCDS, ODIS with online access

[H2Deetoo]

ODIS online yes, but VCDS not.

[bersch8688]

FVDI can do it too ;-)

[sendreq]

What is the best tool to swap vwcaddy 2012 dashboard to high cluster? Iv read up that vcds wont do it, what about vag can pro? As immobiliser is in these. Thanks

VCDS and VCP -> no way to do it
In your signature you have x-tool and smok - both of the tools are able to copy the immo data.

[Dayo]

VCDS and VCP -> no way to do it
In your signature you have x-tool and smok - both of the tools are able to copy the immo data.

iv never done any immo work on vw mate. Iv read that smok can do if you ourchase the license. I see xtool can read skey? Is that how its done? Read original skey, then write skey to new cluster?

[amigokola]

All is inside SMOK MANUAL.
Download soft and read, read, read.
Rgs.

[sendreq]

iv never done any immo work on vw mate. Iv read that smok can do if you ourchase the license. I see xtool can read skey? Is that how its done? Read original skey, then write skey to new cluster?

For SMOK you need the X-can option.

To copy the immo data you have to read the security block (Sec.Block) from the original cluster and copy it into new one.
Before you do anything, save the ABS coding!
ABS coding will be lost if you connect dash with different VIN number.

To access new cluster, read the 24c64 eeprom by programmer, save the backup and then FF the immo area (0x13A0 - 0x1450).
Write this eeprom (with FF) to new cluster, connect via OBD and write the backup. Do not turn the ignition off.
Immediately after writing the original eeprom, write the security block.
Do the ABS coding, adaptation of sensors, erase errors and that's all.

Eeprom is located under the display, no need to pull off the needles.

You can connect also on bench, you'll save then the effort with ABS coding etc.

[Manuelgb]

[QUOTE = sendreq; 3306187] Para SMOK necesita la opción X-can.

Para copiar los datos de immo, debe leer el bloque de seguridad (Sec.Block) del grupo original y copiarlo en uno nuevo.
Antes de hacer nada, guarde la codificación ABS !
La codificación del ABS se perderá si conecta el tablero con un número VIN diferente.

Para acceder al nuevo clúster, lea el eeprom 24c64 por el programador, guarde la copia de seguridad y luego presione FF en el área immo (0x13A0 - 0x1450).
Escriba este eeprom (con FF) en el nuevo clúster, conéctese a través de OBD y escriba la copia de seguridad. No apague la ignición.
Inmediatamente después de escribir el eeprom original, escriba el bloque de seguridad.
Haga la codificación del ABS, la adaptación de los sensores, borre los errores y eso es todo.

Eeprom se encuentra debajo de la pantalla, sin necesidad de sacar las agujas.

Puede conectarse también en el banco, ahorrará entonces el esfuerzo con la codificación ABS, etc. [/ QUOTE]


Hi friend
Work is done as you explain but it does not start, I work with smok and vvdi. Odis failure in immobilizer (lack of information). Can you help me

vw golf 1600 tdi, dash 24c64 year 2011

[H2Deetoo]

If you read immo block from old cluster, then write this immo block to target cluster then car starts.
What are you doing differently?

[sendreq]

Hi Manuelgb,
probably you did not write the ori eeprom back and just put security block into patched eeprom.

Here is detailed manual:

1. read the sec block of original cluster via obd with your tool and save it (read and save also the eeprom - just in case)
2. save abs coding using vcds (it is important to save it, because there is VIN number crypted in the coding. Hard to restore if it get lost)
3. Disconnect the ABS pump (safe option - coding will be not erased)

Now remove the old cluster from the car, you no longer need it.
New cluster is blocked as you don't have the working key. You have to do the FF-trick to patch immo and access dash via OBD.

4. open new cluster and read eeprom via programmer, save backup (make sure you have a good read)
5. edit backup and FF the immo area 0x13a0 - 0x1450
6. write the FFed file via programmer and then connect the cluster to car (error can appear on dash, don't worry) - access via obd is possible now
7. write the original eeprom file of new cluster back via obd - it will show "no key found" but access via obd will still work. DO NOT TURN OFF THE IGNITION!!!
8. write security block (point 1) via obd - job almost done
9. turn ign off and connect ABS pump
10.erase errors and that's it

ABS coding should be not lost. In case it will be set to zero, just take VCDS, put your backup of coding, go to basic setting and do the adaptations of G85 and all other sensors (3 sensors in total - easy job)

[sendreq]

If you read immo block from old cluster, then write this immo block to target cluster then car starts.
What are you doing differently?

I think he put the sec block on patched eeprom, hence the problem.

[H2Deetoo]

I think he put the sec block on patched eeprom, hence the problem.

Nah that's not true. If you write immo data (sec block) then what you will have patched out will be restored.
Depending on what area was patched there might still be a checksum error but with a valid immo block present car will start.

Anyway he did something wrong obviously ...