Skoda Octavia II - swap ECU, Instrument and Key [pre-FL to FL maxidot]

[Games Goblin]

Hello everyone!


My daily driver is a 2006 Skoda Octavia 1.9PD TDI. It has the following problem for the past 7 months :


http://i.imgur.com/qMZQwA6.jpg


It's nearly impossible to read mileage now - I looked around and the replacement LCD screen (maxidot) for this dashboard is ?65 + ship + service charge for screen replacement


So I decided to swap this instrument with the face lift one. I read around and found that my ECU (EDC16U1) does not support the new cluster (it appears the immobilizer in the newer FL clusters are different from the older ones --- also I read that the keys would have to be changed.


So, I have been gathering parts for a while now and have got the following


http://i.imgur.com/tVOJ2bW.jpg


1. another ECU - EDC16U34 part no. 03G 9106 021 LB - came off a car with the same engine code as mine


photo (http://i.imgur.com/d3ySTbE.jpg)


2. face lift instrument cluster --- part no. 1Z0 920 943G


photo (http://http://i.imgur.com/lTYeVM3.jpg)


3. New set of keys part # 5K0 837 202 AD


http://i.imgur.com/wrLWebW.jpg

4. Adapter cable for the cluster

http://i.imgur.com/QsddS9h.jpg


Guys, I need your help to install this to my car. What tools will I need to accomplish this job. I have been reading about this for months, and as far as I can understand, this is the route I have planned to make this work:


1. Read CS data from Instrument
2. Write CS data of instrument to ECU
3. Change VIN + KM in instrument and ECU
4. Write CS data to blank key transponder
5. Match + adapt keys


Please forgive if the above is wrong - I am a newbie to immo :)


Need your help in what tools will help me do this job 100%, and what steps to be taken


These are the tools I already have:


1. VCDS ori
2. KESSv2 reworked (never tried writing with it)
3. FGTECH v54 galletto2 (not reworked, untested)
4. VAS5054A


Another problem I have is that the cluster is in Miles per hour and my car is kilometers per hour. I could not find a FL maxidot with KPH for a reasonable price, so had to go with MPH. I got the KPH speedo dial face from another cluster:


http://i.imgur.com/xVS2aHK.jpg


Is there anyway to change the software of the cluster to KPH? I have read in some forums that it is possible. Your help is most valuable to me!


Thank You!

[amigokola]

ECU has nothing to do with it as you want to swap only dash. You must do this:
-write your ABS coding
-read immo data from old dash: PIN, CS, Powerclass, MAC.....
-transfer all data to new dash but CS in NEW dash is 12bytes and in old 7, so you have to put first 6 bytes from old dash and last one write 6 random bytes of your choice (you can leave 6 original from new dash)
-you must make new transponders (put them to your old key shells and remote should work)
-you cant use new remotes becouse you have it to other (new type) BCM module.

You will do nothing with your tools.
VVDI2, SMOK, AVDI is what you need.

[raf0468]

in my opinion your first task would be to get the cluster adapted and fully functional..
then change speedo dial card ..
with vcds im sure you can change coding in 17instruments to run in kph..
never done it on your particular model of car, but done it with many other vag groups ..

[Games Goblin]

ECU has nothing to do with it as you want to swap only dash.

Hi, I am going to change ECU as well. I searched for this a lot and I found that the ECU in my car (EDC16U1) is not compatible with the immobilizer in the face-lift maxi-dot cluster. So I got a EDC16U34 from salvage.





You must do this:
-write your ABS coding
-read immo data from old dash: PIN, CS, Powerclass, MAC.....
-transfer all data to new dash but CS in NEW dash is 12bytes and in old 7, so you have to put first 6 bytes from old dash and last one write 6 random bytes of your choice (you can leave 6 original from new dash)
-you must make new transponders (put them to your old key shells and remote should work)
-you cant use new remotes becouse you have it to other (new type) BCM module.

Since I am changing both dash and ECU (both of these are from different cars), can you please tell me the steps? From what I can understand, these are the steps I have in mind when swapping ECU and cluster together:

1. Save ABS coding from old
2. Read CS data from new face-lift instrument (12 byte)
3. Write this CS data to ECU (i am guessing the ECU will take 12 bytes?)
4. Change VIN + KM in both ECU and cluster
5. Prepare transponder
6. Adapt keys
7. write ABS coding

I have older type BCM (CECM), so I am guessing remote control will not work on the new key? I am planning to swap to BCM.




You will do nothing with your tools.
VVDI2, SMOK, AVDI is what you need.

Okay, I am planning to go for VVDI2 for this job. Can you please tell me what other tools I will need? Can the cluster eeprom be read/write by vvdi2 over OBD or will I have to get a programmer to do it on the bench?

[Weasel3]

This is what they sell on AliX.
https://www.aliexpress.com/item/Full-Size-Dashboard-LCD-Display-Cluster-Repair-For-VW-Golf-V-Touran-Skoda-Octavia/32462700605.html?spm=2114.01010208.3.290.1soAWJ&ws_ab_test=searchweb0_0,searchweb201602_2,searchwe b201603_1&btsid=70433b52-ff9b-4962-b150-74c36f138bdf

Product Descriptionfor VW Golf 5 2003-2009
for Skoda Octavia 2004-2009
for VW touran 2003-2011
for VW Passat 2005-2010
LCD screen with two flexseals and with one flexseal are randomly used in other cars. I mean you just need to connect with one of them.

What I get out of this is:
You can get one used / second hand clusters of one of those vehicles. At a decent price.
Open it and find your defective part.
Replace it, and everything should work as normal.

Full size LCD screen is on highline models etc. And maybe some other country specified models.

So my advice.
Just place all your new things on ebay.
Or save it for later issues.
Concerning the ECU, you can always tune your new ECU with some extra HP.
Make a swap, and have some fun.

[amigokola]

Why you cant try and see... In ECU you have 6 bytes. Changing ECU makes no sense, someone correct me if I am wrong... Only thing you can have problems with is ABS pump which you probably will must upgrade but I dont know for sure. To read eeprom always use good programmer and desolder to have backup. Do steps as I have written and give us feedback.

[Games Goblin]

Okay, so an update on this. With the help of my friend, we managed to take apart the cluster, de-solder the 24c32 chip and managed to read it with his programmer. :)

I have given up the idea of trying to program key, instead want to go with immo off route for now - since we do not have specialist tools for the job.

The only problem is that the cluster I got has come off a face-lift Octavia 2 estate with miles per hour. Is it possible to change the cluster to KM/H by editing the dump?

http://i.imgur.com/Bs6y1fr.jpg

[Games Goblin]

UPDATE:


I got someone to immo off the new ECU (EDC16U34) and from this forum, I found a dump of cluster eeprom with KPH - my cluster p# is 1Z0 920 943G and I found a dump of 1Z0 920 843G HERE (http://www.digital-kaos.co.uk/forums/showthread.php/402269-Skoda-Super-3T2-920-841K-wanted?p=2245172&viewfull=1#post2245172)

flashed both ECU and cluster and hooked everything up today and here is what happened:

* car started right away and there is no "immobilizer active" error on the dash

* there is no mileage showing in the cluster -- only "Error" appears

http://i.imgur.com/DXmwZn3.jpg

here is the fault code in the dash:


-------------------------------------------------------------------------------
Address 17: Instruments (J285) Labels: 5K0-920-xxx-17.clb
Part No SW: 1Z0 920 843 G HW: 1Z0 920 843 G
Component: KOMBI H05 0305
Serial number: 00000000000000
Coding: 110F00
Shop #: WSC 21030 072 200001
ASAM Dataset: EV_Kombi_UDS_VDD_RM09 A04052
ROD: EV_Kombi_UDS_VDD_RM09_004_VW25.rod
VCID: 3C7D0AABB7F167A1FF-8068


1 Fault Found:
10485825 - Internal Control Module Memory Check Sum Error
B2000 41 [137] - General checksum failure
MIL ON - Confirmed - Tested Since Memory Clear
Freeze Frame:
Fault Status: 00000001
Fault Priority: 2
Fault Frequency: 1




-------------------------------------------------------------------------------


* Apparently, there is no VIN number in the car, so I am unable to re-code the ABS. Portion of VCDS scan below, VIN shows up as 17 "X"s


Chassis Type: XX (7N0)
Scan: 01 02 03 08 09 10 15 16 17 19 25 36 37 42 44 46 47 52 55 56
62 72


VIN: XXXXXXXXXXXXXXXXX


01-Engine -- Status: OK 0000
02-Auto Trans -- Status: OK 0000
03-ABS Brakes -- Status: Malfunction 0010
04-Steering Angle -- Status: OK 0000
08-Auto HVAC -- Status: Malfunction 0010
09-Cent. Elect. -- Status: OK 0000
10-Park/Steer Assist -- Status: Malfunction 0010
15-Airbags -- Status: OK 0000
16-Steering wheel -- Status: OK 0000
17-Instruments -- Status: Malfunction 0010
19-CAN Gateway -- Status: OK 0000
25-Immobilizer -- Status: OK 0000
36-Seat Mem. Drvr -- Status: OK 0000
37-Navigation -- Status: Malfunction 0010
42-Door Elect, Driver -- Status: OK 0000
44-Steering Assist -- Status: OK 0000
46-Central Conv. -- Status: Malfunction 0010
47-Sound System -- Status: Malfunction 0010
52-Door Elect, Pass. -- Status: OK 0000
55-Headlight Range -- Status: OK 0000
56-Radio -- Status: Malfunction 0010
61-Battery Regul. -- Status: Malfunction 0010
62-Door, Rear Left -- Status: OK 0000
72-Door, Rear Right -- Status: OK 0000

* Apart from this, the cluster works well, I can browse through the menus etc.



Guys, please help me get my VIN number onto the car, as without it the ABS won't work. Any help would be appreciated.

Could the checksum error be beause of bad dump file? If you have a known good dump of 1z0920843G dash, could you please share it?


Cheers

[benfirth]

i would put the original dump back on the cluster with the immo off.

with VAS5054A download odis service3.0 or higher.

you can change the display output to km with guided diagnostics when the instrument cluster is selected. done this many times

hope this helps

[Games Goblin]

i would put the original dump back on the cluster with the immo off.

with VAS5054A download odis service3.0 or higher.

you can change the display output to km with guided diagnostics when the instrument cluster is selected. done this many times

hope this helps


Thank you mate! I will put back the original dump and try it. Will report back here

[benfirth]

no probs let us know its crap when it goes pete tong

[Games Goblin]

UPDATE:


Someone helped me by making a "repaired" eeprom file for the cluster -- i.e. Into the original eeprom dump from my cluster (1z0 920 943g) ---> merged the KM measurements from the dump of the 1z0 920 843g.


I flashed this file and now the cluster seems to be working properly. I am able to connect to the immobilizer with VCDS.


The cluster now displays the message "key not found" - the mileage now shows in KM but the place where the mileage shows now keeps intermittently switches between "Error" and then back to showing the mileage.


Now i am not able to use the functions of the maxi-dot display (unable to call up the menu with the indicator stalks). The checksum error still shows up on VCDS (in the instruments)


https://s17.postimg.org/ru3z1a54f/IMG_20170215_081945.jpg


Now, I think the only solution is to make key and adapt with AVDI / VVDI


If I take this car to someone with AVDI, what all do I need to do? Should I change ECU EEPROM (write CS data etc).


Please guide me to finish this project.


Thanks to all who have helped so far.

[pintu]

Change ecu mileage same as odometer cluster for error in cluster

[Games Goblin]

Update after a long time:

I had abandoned this project because I don't have the tools - I could live with not seeing the mileage - but a few days back, my old cluster's fuel & temp gauges stopped working - so I need to change my cluster now! I can't take my car out for long journeys.

Can someone with the right tools do this job for me, please? I can send the maxidot cluster, ECU and new transponder to you by courier - I will pay your service charge of course - please contact me by PM if you can help - I would appreciate it a lot as I am without a car now!

[Tibi1983]

ECU has nothing to do with it as you want to swap only dash. You must do this:
-write your ABS coding
-read immo data from old dash: PIN, CS, Powerclass, MAC.....
-transfer all data to new dash but CS in NEW dash is 12bytes and in old 7, so you have to put first 6 bytes from old dash and last one write 6 random bytes of your choice (you can leave 6 original from new dash)
-you must make new transponders (put them to your old key shells and remote should work)
-you cant use new remotes becouse you have it to other (new type) BCM module.

You will do nothing with your tools.
VVDI2, SMOK, AVDI is what you need.





Please help!


You need the immobilizer code from the odometer!


The clock has been replaced and needs to be adjusted.




Thanks.

[H2Deetoo]

First of all why don't you open your own topic?

Secondly you cannot do anything with only eeprom. Reading/writing immo can only be done by OBD with proper tools.


Rgs H2Deetoo