Page 1 of 1
EcuFlash 1.3 doesn't prompt me to plug in cable and click ok

Posted:
Wed Apr 18, 2007 8:11 am
by coffeeslug
Previous versions always prompted me, but 1.3 does not. Anyone else have this? I don't know if it's not installing correctly or if it's an indicator of some other problem.
This is an 05 Evo btw, win xp sp2

Posted:
Wed Apr 18, 2007 3:36 pm
by cboles
That sounds like a problem. What does the log say? What model cable are you using?
Colby

Posted:
Thu Apr 19, 2007 5:01 am
by coffeeslug
I have the 1.3 cable, and for ecuflash 1.3 the log says "unable to connect to vehicle interface"
When I use 1.29a, I do get prompted and then I get the three inits and then "no response to any known code".
A friend has 1.3 cable and ecuflash 1.3 and a different laptop. When he tried to flash me, he got the prompts, but then the same "unable to connect to vehicle interface"
I can log with mitsulogger no problem. People have me focusing on the white connector, but I checked for continuity and it was fine. I checked the female end in the car, and it was fine. I've tried the battery charger also, warming up the car. Seems like it has to be software, cable, or connector in the car. Anything else I can check for? Thanks for reading!

Posted:
Sat Apr 21, 2007 8:57 am
by abd
Seems like I have the same problem as you too. 1.3 gives "can't connect to vehicle interface" and 1.28 gives three inits and then an error..
Did you solve it?

Posted:
Sat Apr 21, 2007 8:57 am
by abd
Seems like I have the same problem as you too. 1.3 gives "can't connect to vehicle interface" and 1.28 gives three inits and then an error..
Did you solve it?

Posted:
Thu Apr 26, 2007 12:11 pm
by danl
I was searching because I am no able to read or write to my ecu after installing ecuflash 1.3. I also can not log my car via evoscan. However I can use the cable to read OBDII data via the scantech logger software. If anybody has figured out a solution please let me know.
To clarify I do get the Mitsubishi open port 1.3 in the lower right hand corner. When I click write to ecu it does not prompt me to turn the ignition on or anything and just scrolls through until I see "unable to establish connection" at the bottom of the data.

Posted:
Thu Apr 26, 2007 12:32 pm
by C6ect.ect
Did you go to devise manager and check your drivers?
Looks like you might have to uninstall/reinstall like I have over a dozen times

Posted:
Tue May 01, 2007 2:26 pm
by danl
1.29 works so I haven't really found interest in making 1.30.

Posted:
Sat May 05, 2007 2:40 pm
by Jorge T
I have a similar problem with 1.30 I can write to the ECU but cannot read read rom image from ECU. When I hit the read from ECU the dialog box t button is greyed out and not clickable, also there is no data inside the box. IIRC there was something in there to select? There is tatrix cable verification in the lower right corner.
I've used 1.28 and 1.29 to read from ecu before.