Problem: Unable to read or write to or from the ecu using either ECUflash or Evoscan.

As I select "read from ecu" and click "0kay" ecuflash begins to send the initialization codes, but the car doesn't cut off. Sometimes it stumbles as ecuflash sends new initialization codes and the SES light will flash on once with each new attempt sent, but eventually the error message pops up stating "interface closed, no response to any known codes".

I believe my cable is functional as I'm still able to log data using evoscan. I believe my battery is good as it is one week old, showing 12.8v with the car off and 14.2 with the car running.

I've uninstalled and reinstalled ecuflash, but the results were the same. \

Has anyone encountered this before?

My next steps are to try a different cable and laptop that are known to be functional as well as attempting to read from another evo ecu using this cable and laptop.

I'll post again if/when I find a fix, but in the mean time all suggestions and advice is appreciated.

 

Ive ran into this a few times. First time it was my cable, but it could be seen. One of the pins pushed out of the OBD-2 connector. Second time, it was the drives. I believe I went back to an older version of ECUflash. 1.29 sounds familiar. I could be wrong though. Its been a year or two since it happened.

 

I'll try an older version and double check my cable tonight. Thanks for your reply.

 

It turned out to be the cable. Changed to a different one and everything worked. Thanks lancerrally for your help.

 

Good to hear! Sometimes when they are left in the car the heat will get to them, if its an older cable that coulda happened.