Hi, I have an Audi A2 1.4 Petrol 2003
Engine: BBY
ECU: MARELLI 4MV / 036 906 034 CA
VIN: WAUZZZ8Z73N006323
The car has been a nightmare since I bought it, after a lot of changes to the car we are left with the ECU. The ECU in the car has been replaced by the past owner, it’s a second-hand ECU with no guaranty that the replacement was in good conditions, neither that the job was done correctly. What has been done with this ECU is also unsecure, therefore I decided to buy a second-hand ECU. I have no SKC/PIN code for the car, neither do I have the SKC/PIN for the new donor ECU. Since I need the SKC/PIN for the adaption/replacement of ECU, we have been trying to retrieve PIN using Vagtacho, no luck with this tool. Then we tried this tool: Vag Eeprom Programmer 1.19, no luck.
After reading several threads in this forum we found the tool ME7 Eeprom programmer (Argdub's tool) which seemed very promising. We have tried an eeprom dump using OBD and Galletto 1260 (cheap Chinese cable), but no luck getting any eeprom read. We decided to build this harness like described in this tread and connect it directly to the donor ECU:
http://nefariousmotorsports.com/forum/index.php?topic=417.msg2922#msg2922The reads have been tried in OBD mode, and not boot-mode, these are the error codes we got:
C:\eeprom>me7_95040 --OBD -r -p 1 95040.bin
Ver: 1.31
Com Port: 1
Baud Rate: 10400
Opening COM1 ... OK
Initiating communication ... FAIL. (error=0x01)
Closing COM1
C:\eeprom>me7_95040 --OBD -r -p 1 95040.bin
Ver: 1.31
Com Port: 1
Baud Rate: 10400
Opening COM1 ... OK
Initiating communication ... FAIL. (error=0x07)
Closing COM1
C:\eeprom>me7eeprom --OBD -r -p 1 95040.bin
ME7_EEPROM v1.40
COM: 1, Baud Rate: 10400
Opening COM1 ... OK
Initiating communication ... FAIL. (error=0x21007)
Closing COM1
C:\eeprom>me7eeprom --OBD -r -p 1 95040.bin
ME7_EEPROM v1.40
COM: 1, Baud Rate: 10400
Opening COM1 ... OK
Initiating communication ... FAIL. (error=0x50101)
Closing COM1
We have also tried different baud Rates and software version 1.31 and 1.40. Maybe we should try boot-mode instead, but from what I understand this is usually not needed for eeprom dumps/reads, only for writes. I have ordered a KKL cable with FTDI FT232RL chip which is on is way.
Thanks for reading my post, hopefully you guys are able to help us out, thanks!