Hi,

Firstly, get a vagcom-log to see what codes are thrown.

Secondly, i suspect there are some essential bytes not correctly setted.

Can you ask your mechanic to give you the read-out of your ecu's eepromchip?
Before he did anything to it ? And please post it up, right here, as a zip or rar-file.

I'll have a look to it.

PvL

Hah, Deal !

First get me the real dump

The file you've posted contains no useable or processable info.

Please doubleclick the screenshot i've made for you, to have a look..  I was expecting something different

Please ask your mechanic to give you the correct readed-out file,
and post it over here.

Thanks,

PvL

Hello giantmidget,

I get the feeling your 'mechanic' isn't on-par with the stuff he is trying to do.

Let's recap : the 95040-dump you've sended, looks like a config-file of his programmer,
                   and has nothing to do with the real data which is normally stored in this
                   eeprom.

It's nice that he has 'a' MEC-programmer, but can you also tell me, if it supports the 95040 chip (http://datasheets.pl/S/ST/ST95020.pdf) ? a programmer-type or a check in the software
he received with the actual programmer would be a good thing to start with. Don't get me wrong, i'm ruling-out the possibility that the programmer did not read it correctly, and for
some kind or reason dumped a config-file of the programmer itselfe into the file it created on his pc...  Otherwise i cannot tell you why the content is totally wrong.

You also sayed, that he sended off this file to a guy, and they modified it, and sended back the modified file. Can you ask your mechanic to also give your that file, and please post that also over here ? As i'm very interested to see what the content of that file is.
In other words : they had to tell your mechanic, that he was doing something wrong with his programmer, or did something wrong while saveing the content to disk of your eprom.

Is your original 95040-chip OVERWRITTEN by your mechanic ? or did you used a new chip ?

All these questions are quite critical. I'll explain later. This to prevent further errors, and get you a proper file to write-back.

Don't worry, i'll get you the dump you need, but first i want some answers, as i'm getting the feeling a terrible mistake was made by your 'mechanic'.....   But that depends on the answer and the 'modified' dump he got from his email-friend.

I get the feeling he wrongly saved your original dump of the 95040, and therefore you are in some problems now. All chips which are then send to you, will fail, if specific procedures are not followed. Please post the dump that he writed back to your chip and soldered back, that ran for 4 seconds.

Thanks,

PvL.

Sorry rest of files here:

These are tall the available files


Regards

Hi Pvl,

Dumped your immo file , fan on car came on instantly then every couple of seconds.
Car only swings does not fire up at all.
Vcds does not want to read the car at all.

Just a question if the immo is defeated ,then it would not be neccessary to reprogram cluster or would it , the cam bus t the cluster is giving problems.

Regards

Gmidget

Hi,

Abouth the rest of the eeprom-content i cannot judge, because there are no tools which i am aware, that do the complete checksum-checking of the immo-eeprom. Therefore i think
this is a bit trickey with your current (perhaps wrongly) read-out dump.

Before commenceing starting, i would stress to firstly hook-up vcds, and see if communication is possible. Ifso, then you may try to start the engine. Ifnot, no reason to start, cause the ecu ain't working/responding.

I always check my ecu's on the workbench if they are able to communicate (before i stick them into any car). Untill now, no dead ones encountered here, so i guess my tools work correctly. I have the blue vagcom KKL-dongle to check them out with. And made myselfe a benchflash cable (also useable to do vagcom-communications with). This benchflashcable would be very handy for your mechanic or yourselfe to check-out your ecu before you put it back into your car..

Is your ecu in any other way 'modified' (chipped/not standard) ?

Next file i'm including is a virgin immo-off chip. Please write that to the chip, and VERIFY
with the programmer, the written content matches the buffered content on the pc.

Then solder it back, and if you can, do a bench-test on the ecu. It shall respond with vagcom 100%. Or your ecu is damaged. It's hard to diagnose like this, what is all happening over there, and putting the finger onto the wrong item. I hope you understand.

Vagcom cannot communicate with channel 1, your log says. Good one, you've posted this. It tells you, that the immo-chip is not correct, or that something is wrong with it.

Have a try with the added eeprom, and let me know.

Before you even think of starting the engine, hook up vcds, and see if you can communicate with the ecu and this dump programmed into the eeprom. I think the immobiliser will still kick-in, but now you can PAIR your ecu with the NEW clock again

But really we want channel 01 responding again in vagcom (vcds)..  no matter what codes it throws..  it's a beginning.

PvL

   
Hi,
 
No i watched him and the chip was soldered on correctly , we checked the data three times to make sure the data was programmed correctly.
 
I will try the virgin dump on Monday hopefully i will succeed.
 
i can not thank you enough for the info that you have provided me with thus far ,it has been a great help.
 
Just  a question does the cluster matter in the immo defeated mode? , i have the correct cluster a BoschRB4 900N ,but will a 900H also work under the defeated mode.

Regards