i was trying to hook my computer up to my 2 boys evos and neither one will connect to the vehicle interface... i am NOT a newbie to ecuflash, and have never ran into this problem before... when i try to connect nothing happens except it gives this message:

[21:31:57.445] Version 1.34.1435
[21:31:57.452] 11 memory models read.
[21:31:57.453] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata
[21:31:57.678] 222 ROM metadata models scanned.
[21:31:57.678] checksum module "subarudbw" loaded.
[21:31:57.678] flashing tool "wrx02" loaded.
[21:31:57.679] flashing tool "wrx04" loaded.
[21:31:57.679] flashing tool "sti04" loaded.
[21:31:57.679] flashing tool "sti05" loaded.
[21:31:57.679] flashing tool "mitsukernel" loaded.
[21:31:57.679] flashing tool "mitsukernelocp" loaded.
[21:31:57.679] flashing tool "shbootmode" loaded.
[21:32:05.529] Using interface OpenPort 1.3 Mitsubishi TX14sjXMcf8ff6c900000000000000000000000000000000
[21:32:05.529] interface close
[21:32:05.538] unable to connect to vehicle interface.
[21:32:05.538] interface close
[21:33:48.890] Using interface OpenPort 1.3 Mitsubishi TX14sjXMcf8ff6c900000000000000000000000000000000
[21:33:48.890] interface close
[21:33:48.899] unable to connect to vehicle interface.
[21:33:48.899] interface close


i downloaded the new ecuflash and still nothing... help is greatly appreciated... they are having problems with their cars and are in dieing need of flash...

 

ensure that you have removed any old FTDI drivers ... (add/remove programs and delete all the old version)

 

Several other people are having the same issue with newer versions of ECUFlash. The TX14 cable seems to be the culprit. I don't know of anyone using that cable who has been able to get newer versions of ECUFlash to work properly.

 

well i know that the cable itself isnt defective i did some data logging on evoscan earlier... anyone have some solid evidence its the cable?


thanks guys

 

Didn't say the cable was defective. It just doesn't work with newer versions of ECUFlash. Do a search in this forum on TX14, and you'll find more references to this issue.

 

Don't forget, some ecus are locked and you need to run MalibuJack's unlocker program. It took me a week to figure that one out.

 

i kno that i might need this later... but its a stock map... so unlocking it should be unecessary...

 

Try using evoscan or some other logging software to connect first. As they said, it may be the cable, not the software. Hope that works. If it does, just install the older version of ECUFlash.

 

done logs with evoscan... thats why i dont understand why the software both old and new arent working...

 

EvoScan uses the OBD II connector, while ECUFlash uses the white connector. Its possible the white connector is just not working. Simple test is to find someone else who has ECUFlash that is working and a cable that is working. Try your cable with their laptop if it works, then its your ECUFlash, if it doesn't then its your cable.

 

^
|
|
|
+ 1 What he said

 

tried different laptops, different ecuflash, different versions, but not different cable............ might be the problem.... thanks