I just got it in the mail. I am trying to read my ecu (03 evo 8) IT will not connect.

My computer recognizes the cable, the tactrix adapter is plugged into the obd 2 port and the lights are flashing. Is this all i need?

It keeps saying no response to any known code.

Help !!i want to get this to connect so i can get a tune coming.

here is the log

[19:59:18.457] EcuFlash Version 1.42.2595
[19:59:18.457] OS Version Windows Vista
[19:59:18.457] Qt Version 4.5.0
[19:59:18.467] 56 memory models read.
[19:59:18.467] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata
[19:59:18.694] 343 ROM metadata models scanned.
[19:59:18.694] checksum module "subarudbw" loaded.
[19:59:18.694] checksum module "mitsucan" loaded.
[19:59:18.694] flashing tool "wrx02" loaded.
[19:59:18.695] flashing tool "wrx04" loaded.
[19:59:18.695] flashing tool "sti04" loaded.
[19:59:18.695] flashing tool "sti05" loaded.
[19:59:18.695] flashing tool "mitsukernel" loaded.
[19:59:18.695] flashing tool "mitsukernelocp" loaded.
[19:59:18.695] flashing tool "mitsubootloader" loaded.
[19:59:18.696] flashing tool "shbootmode" loaded.
[19:59:18.697] flashing tool "shaudmode" loaded.
[19:59:18.697] flashing tool "subarucan" loaded.
[19:59:18.697] flashing tool "mitsucan" loaded.
[19:59:50.244] J2534 API Version: 04.04
[19:59:50.244] J2534 DLL Version: 0.50.2598 Jun 26 2009 15:02:29
[19:59:50.244] Device Firmware Version: 1.10.3020
[19:59:58.966] sending init sequence 1 (0001)
[20:00:02.200] sending init sequence 1 (0003)
[20:00:05.431] sending init sequence 1 (FFFF)
[20:00:08.148] no response to any known code
[20:00:08.150] interface close
[20:01:09.471] J2534 API Version: 04.04
[20:01:09.472] J2534 DLL Version: 0.50.2598 Jun 26 2009 15:02:29
[20:01:09.472] Device Firmware Version: 1.10.3020
[20:01:11.693] sending init sequence 1 (0001)
[20:01:14.923] sending init sequence 1 (0003)
[20:01:18.160] sending init sequence 1 (FFFF)
[20:01:20.876] no response to any known code
[20:01:20.878] interface close

 

Did you upload the device driver?

 

I think this is a common mistake many make, did you look at the Cable selector on the EVOScan site?
I know Evoscan is not ECUflash but it seams the 2.0 cable works best with later model Evos. Unless there is a work around the 1.3U cable works best.

EvoScan cable selection guide.

http://www.evoscan.com/mitsubishi-su...bd2-can-cables

Also form the web site:

IMPORTANT NOTE: OpenPort 1.3D/1.3R/1.3U is twice as fast at datalogging than OpenPort 2.0

IMPORTANT NOTE: OpenPort 2.0 is required for Reflashing 1998-2000 H8 Mitsubishi Evo5/6/6.5 TME/DSM ECUs.

For Mitsubishi DSM/3000GT use EvoScan v2.5, and here are some additional instructions

1.3R and 1.3U are the exact physical same cable.. there is 100% no differences... ok there is one difference.. a special serial number is loaded into each 1.3U cable that allows it to work with ecuflash reprogramming, but this is a software check thing, not a physical cable thing.. you will find that for all features of EvoScan such as actuators and datalogging, they are 100% identical cables.

Athanasios

 

I think the driver is working ok. Im going to check if evoscan works.

 

evo scan works fine, still cant connect with ecu flash HElp anyone!?

 

hmm. It may be the usb cable. Have you tried different usb ports?

You can try different miniUSB to USB cables, they are (were) very common in cell phones


my openport 2.0 works perfectly. Check to make sure you have the peripheral attached. Evo 8's and 9's need it, it plugs into the other plug next to the main one (term?) and then plugs into the openport 2.0 via the 2.5mm jack.

Im pretty sure you dont have that peripheral attached

 

That peripheral piece which you speak of I believe is only required for reflashing. You still should be able to atleast connect and scan the ecu.

 

Try starting the car, then while running click read from ecu.

 

if you have the tactrix plug connected and have the little white flash block connected and it wont read try running ecu unlocker before you open ecuflash then try reading it.

 

Im going to run home and try this. I had it pluged in but not the 2.5mm jack to the OBDII adapter that it comes with. I thaught that was for logging a lc1 or somthing.
If this does not wrok I will get ahold of the ecu unlock program.

 

I got it to work. THANKS FOR THE HELP. !!Also what is the best way to hook up my aem uego so i can log on evo scan? Do i go through a ecu imput with the 5v signal?

 

good to hear

Easiest way is to run that 5v signal into the #8 pin on the openport plug. Its the "adc" pin that logs 5v peripherals.

I modified my logcfg.txt file on the root of my 2.0's sd card so it looked like this:


the only downside is, I think this only allows you to log WITHOUT evoscan by logging to the sd card at all times insead. I havent really researched how to make it work with evoscan, but im thinking there should be a way to do it.

if you want to log this way, I can go into the specifics about how to make a proper formula and stuff. If you see my scalingrpn code, it calculates for the error my LC-1 reads for every voltage.

you may want to just do the rear 02 sensor input mod to log with evoscan. Im probably going to to this as well, but my current setup is the easiest.

 

Thanks for the help, I was going to fallow this and see ware this gets me.https://www.evolutionm.net/forums/la...o-evoscan.html