05 gsr
Ive searched and have yet to find my problem, my tactrix cable is plugged in correctly, i have ecu flash version 1.29 all im coming up with in my task info box is

[01:45:26.937] Version 1.29.906
[01:45:26.984] 8 memory models read.
[01:45:30.296] 140 ROM metadata models read.
[01:45:30.296] checksum module "subarudbw" loaded.
[01:45:30.296] flashing tool "wrx02" loaded.
[01:45:30.296] flashing tool "wrx04" loaded.
[01:45:30.296] flashing tool "sti04" loaded.
[01:45:30.296] flashing tool "sti05" loaded.
[01:45:30.296] flashing tool "mitsukernel" loaded.
[01:45:30.296] flashing tool "mitsukernelocp" loaded.
[01:45:30.296] flashing tool "mitsubootloader" loaded.


and in the lower right hand corner it displays no vehicle interface, all of my read, write and compare ecu options arent colored and im unable to click on them, all my options under options are directories, users, metadata and appearance, there is no option for choose a different com port. ive been trying to figure this out for hours now, any help would be much appreciated.

 

Looks like the driver didn't install properly.. if the cable is installed, and the drivers were installed properly, it will detect the interface..

If you have other USB-Serial adapters, there is a possibility that the driver it uses conflicts with the tactrix driver, (if they use the same FTDI chipset) so if thats the case, try unplugging the other devices if their plugged in..

 

Also, make sure you plugged in the cable before you started ECUFlash..

 

Wow thanks for the quick reply man, i got it to connect but now when i try to read the rom it says the vehicle interface does not support needed features, i was tuned by turbo trix which i beleive is ecutek, so i downloaded the ecu unlocker from aktive matrix, but still had the same results, i noticed on the ecu unlocker it says its for version 1.28, is it not compatible with the new ecu flash version 1.29?

 

no, it means the white molex connector isn't triggering bootstrap correctly.. Check those pins and connection..

 

Oh a bad driver install "Could" also generate this error..

 

yeah i have made sure of the white connector, what would cause a bad driver install, how do i correct it?

 

Not sure, probably uninstall the driver and reinstall it..

There were a handful of bad cables that I've heard of, its entirely possible this could be one that has a problem, you really should post on OpenECU.org and ask about it there.

 

Yeah i suspected that was a possiblility, thanks for your input and time bro.

 

I also had a problem getting EcuFlash operating with the Tactrix cable.

I had installed the FTDI drivers previously in anticipation of receiving the cable, and installed 1.29 after. I had also installed .NET 2.0 in anticipation too. Would not work.

Here's what it took to fix: I left the .NET 2 stuff in place. You must have .NET 2 to run Jacks Mitsulogger BTW ( get it from Microsoft via Google ) Install mitsulogger.

I then uninstalled all FTDI drivers after removing Ecuflash 1.28 and 1.29. Used add remove in control panel (Win xp pro SP2 ) . I then downloaded the new 1.29a version of Ecuflash. Turn off internet access at this point. Installed EcuFlash . It unpacks and installs FTDI drivers. Use the " no ...install from a specific location " choice when windows asks if it can search for the drivers and point it to the \drivers subdirectory in EcuFlash 1.29a.

The driver install will then proceed, installing a couple of drivers for the cable. When done, plug in the tactrix cable and Windows will recognize and install more drivers ( 2 IIRC ) . It will then say the hardware is installed properly. Leave the cable connected.

Go to the ECUflash directory and copy the files from the directory rommetafiles\mitsubishi\evo to the backup and parent directories. Then go open up Ecuflash and select options customize and tell it where the romfiles are by selecting the appropriate directory. \rommetafiles\mitsubishi\evo.

Open a stock EVO8 rom .hex file you download from aktivematrix.com. SAve it . Then while still open click read rom. You will get a dialog box that opens up with definition choices. Choose the Evo 8 2003 up one. click and ECuflash should open a dialog box that says to connect the cable to the car and turn on the ignition and press ok. Follow that and you should be OK

That should do it.

I installed ECUflash 1.29a and mitsulogger on 2 laptops ( 1 Win XP pro, the other Win XP media center ~ 2 months old) The media center one went absolutely fine once I blasted off the previously installed FTDI drivers and let ECUflash install the bundled drivers. I read and saved a hex file and then was able to connect to the car as described above.

The second laptop with Win XP pro was more problematical. Despite the clean re-install and proper driver install it still would not work because when the dialog box opened to select the correct definition to read the ecu, it was empty, nothin to select. I wen thru several interations of changing the file directories making sure the correct ones were seleted...but no dice. I ended up copying the definitions from the \evo directory to the parent directory and the backup directory. Finally opened up with choices and smooth sailing from there.

If the cable works with Ecuflash it will work with mitsulogger.

milburn