Sorry here is the file

I just wanted to know (at the time) if the EEPROM dump would work...But I found that it changed a lot more than the immo due to it being a 1024 size. I ended up just taking the immo, and checksum values from the generated dump and manually edited the original file.

Thanks

Hello All,

can I use this program to change VIN, SKC, Cluster code and Immo ID in ECU bin file ? I have similar problem as user "stranger_in_distress". I want to use AUQ ECU with AUM engine with Immo ON. I read that stranger_in_distress solved it, but its almost 6 years ago.

I succesfully changed VIN in eeprom file via this program but change of SKC, Cluster code and Immo ID is not possible  

Do I something wrong ? Because command line shows "Not Yet Supported for ECU Bins".


C:\>e2t.exe
usage: e2t.exe [-h] --in INFILE [--out OUTFILE] [--status] [--immo IMMO]
               [--vin VIN] [--skc SKC] [--cc CC] [--ii II] [--pair PAIR]
               [--fixcs] [--nofixcs] [--cluster] [--force]
e2t.exe: error: argument --in is required

C:\>e2t.exe --in HN.bin --vin TMBBL21U838684718 --out HN_VIN.bin
Read in 512bytes
Setting VIN to TMBBL21U838684718
- Setting backup pages
- Correcting checksums

- Write Successful

C:\>e2t.exe --in HN_VIN.bin --skc 00679 --out HN_VIN_SKC.bin
Read in 512bytes
Not Yet Supported for ECU Bins
Traceback (most recent call last):
  File "eepromtool_04.py", line 794, in <module>
  File "eepromtool_04.py", line 769, in main
AttributeError: ecueeprom instance has no attribute 'setSKC'
[4452] Failed to execute script eepromtool_04






Thanks.

Thank you for offer, but fortunately it has been fixed. I found program "VisualME7Logger" and this cool software did what i needed to do.

After that ECU works fine in car without any problem and I hope so.

Immo is ON and works.

Here is what I did:

1) Downloaded E2prom from HJ ECU (AUM) and from HN ECU (AUQ)

2) Opened HJ E2prom in VisualME7Logger and copy VIN, SKZ, Immo PIN and Cluster code to notepad

3) Opened HN E2prom in VisualME7Logger and replace VIN, SKZ, Immo PIN and Cluster code by data from HJ (notepad)

4) Saved updated E2prom with checksum routine

5) Flashed to ECU and installed ECU to car


I dont know if this is correct procedure, but it works without any DTCs and I have tried more than 20 starts of engine, I drove more than 50 km and its still OK.




 
 

During testing I found small bug. When I tried to pair Skoda's cluster and ECU bin I found that this SW only accept Immo ID with 13 characters. Skoda uses IMMO ID with 14 characters.

Can anyone confirm this ?

C:\>e2.exe --in cluster.bin --out cluster_paired.bin --pair ecu.bin
Read in 2048bytes
Detected 2kb bin, parsing as a cluster eeprom (prevent this guessing by using --force)
Read in 512bytes
Setting VIN to TMBUR41U038686255
Setting Immo ID to SKZ7Z0B1704024
Setting SKC to 00648

Cluster updated to:
EEPROM Status:
- Type: Cluster
- VIN: TMBUR41U038686255 (Skoda 2003 - Octavia 96-03, Dresden; Vrchlabi)
- SKC: 0648
- Cluster Code: EC 88 B1 E4 9A F4 CE
- Immo ID: SKZ7Z0B170402

Writing 2048kb cluster eeprom bin to: cluster_paired.bin
- Write Successful

This tool cannot set checksum for cluster bins, so you must force the cluster to reset the checksum by using VCDS to update the cluster softcoding (setting it to the same value will force the update)

C:\>e2.exe --in cluster_paired.bin
Read in 2048bytes
Detected 2kb bin, parsing as a cluster eeprom (prevent this guessing by using --force)
EEPROM Status:
- Type: Cluster
- VIN: TMBUR41U038686255 (Skoda 2003 - Octavia 96-03, Dresden; Vrchlabi)
- SKC: 0648
- Cluster Code: EC 88 B1 E4 9A F4 CE
- Immo ID: SKZ7Z0B170402

On the first page of this topic are some examples with Audi and there is only 13 characters in Immo ID. However I have tried to open updated bin of cluster in another SW and it seems that Immo ID has 14 characters.

It looks like its only display bug.