// Resolved

Turns out it was the cable. I figured it may come down to that since there was no continuity when I checked the white connector with the multimeter, however I wanted to try other options while the cable was on the way to eliminate any other possible causes. Cable came today. Hooked it up and it flashed with no issues at all. Thank you for the help!

// Resolved

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

Car:
2003 Mitsubishi Evo 8 (USDM)
Tephra v7- SD Map
OpenPort 1.3U Cable

What I'm trying to do:
Read/write to ECU via ECUFlash 1.42.2595

Issue:
-No Known Response Code (tries 0001, 0003, FFFF, etc).
-I can datalog with EvoScan no problem.

Steps attempted to resolve issue:
-Tried after car warms up
-Verified battery voltage
-Clean install of ECUFlash (Old version and Current version)
-Clean install of Windows XP (32-bit)
-Clean install of Windows 7 (64-bit)
-Tried ECU Unlocker
-Tried various USB ports

More Info:
The car was flashed with a Tephra v7 Map about 2 weeks ago. I wasn't there physically, but the person that flashed the car says it did flash/no issues. The guy left the 1.3U cable in the car so that I can use it for future datalogging/reflashes. Attempting to put a new ROM on the car and I can't get it to work. I can datalog in EvoScan without any problems.

I have checked for continuity with the cable, and am getting nothing when checking the white connector. This would lead me to believe it is the cable that is the issue, however, I am being told it worked just fine.

Do I try something else? Am I missing something? Do I order a new cable? Out of ideas at this point.

Thank you guys in advance for any advice/info you can give me.

Thanks,
Anthony


Just to cover all my bases, here are some pictures of the cable in question:

 

in the bottom right corner of ecuflash, does it say tactrix 1.3 ?

 

It says- "OpenPort 1.3 Universal TX2BLZhh"

 

make sure you got good voltage to batt...if you can put a chage on it while you try and read the ecu. Is it cold where you are?

 

It is cold, roughly 40 degrees. When flashing, voltage is 12v when attempting to flash. Should it be something different?

 

not enough volts.
Put the battery on charge - 1.3 cables want a battery voltage over 12.5 volts.

 

If I recall correctly, the voltage actually does sit at 12.6v (unless I go to use an accessory like the window). I said 12v just as a generalization.

I will use my other car/jump cables tomorrow to see if maybe that will make a difference.

The battery is brand new. Got it less than a week ago. However, it is a mini so maybe that could cause an issue.

Thank you Merlin, I appreciate the input.

 

Just another piece of info I'd like to add- I've attempted to read/test write to the ECU while the car was running. I read that ECUFlash will shut the car down itself if it's running. I still received the same error while the car was running though.

 

Used a charger on the battery- still nothing. Same error as before.

 

I have connected with less than 12.0 volts countless times on the Evo 8 ECU's. Only the Evo 9 ECU's are as sensitive to battery voltage allowing connection in my findings.

Evoscan only uses the large black OBD connector for connection, which you have confirmed is connecting just fine. ECUflash NEEDS to connect with the white connector first before anything will happen. The problem is solely with the white connector, either in the reflash cable or the vehicle. This is PIN #79 on the ECU harness. Check continuity from the white connector to the ECU pin.

-Jamie

 

Turns out it was the cable. I figured it may come down to that since there was no continuity when I checked the white connector with the multimeter, however I wanted to try other options while the cable was on the way to eliminate any other possible causes. Cable came today. Hooked it up and it flashed with no issues at all. Thank you for the help