openecu.org

Since you don't specifically mention it.. I"m assuming your car is an EVO IX.. Have you tried putting a battery booster/charger on the car before you attempt to read the ECU?

If you've done everything, but can sucessfully write and log using other software then try a different computer just to rule out any other possibility but the cable.

Ahhhh sorry to bump an ancient thread, but I'm having this exact problem.

I've got an Evo IX mr's with a 1.3 tactrix cable and EcuFlash.

With 1.29 i get "no response to any known code."

With 1.42 i get "unable to connect to vehicle interface"

In both cases I'm running "ECUFlash ECU Unlocker."

With 1.29, you see it attempting different inti codes until F0F0, after which it gives the error. With 1.42, it kicks the error back almost instantly.

I'm new to exploring Ecu's but not new computers/coding. The Ecu was tuned by a tuner who most likely locked and possible by Ecutech

Any ideas?

I get more success it that I get a respose to init sequence 1 and 2, then it goes to bootloader. Then I get a kernal read, then all of a sudden I get a kernal rsp end. then the interface close.
I got an evo 9 using 1.3U cable.
anyone have any idea?

I got thr same problem ... I have one EDM Colt ralliart and an Colt CZT EDM.
LOG with EVOSCAN 2.7 and read with
and when i tried to log or to read the ecu it doesn´t work on the RA
EcuFlash Version 1.43.3150
sending init sequence 1 (0001)
sending init sequence 1 (0003)
sending init sequence 1 (FFFF)
no response to any known code

but on the CZT i can only log but when i want to read i got back
sending init sequence 1 (0001)
got 0x05 response
sending init sequence 2
got 0x1a response instead 0x1b
sending init sequence 3
entering bootloader
interface closed