[01:20:34.443] EcuFlash Version 1.42.2595
[01:20:34.443] OS Version Windows Vista
[01:20:34.443] Qt Version 4.5.0
[01:20:34.457] 56 memory models read.
[01:20:34.457] scanning for metadata models in C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata
[01:20:34.797] 343 ROM metadata models scanned.
[01:20:34.797] checksum module "subarudbw" loaded.
[01:20:34.797] checksum module "mitsucan" loaded.
[01:20:34.797] flashing tool "wrx02" loaded.
[01:20:34.798] flashing tool "wrx04" loaded.
[01:20:34.798] flashing tool "sti04" loaded.
[01:20:34.798] flashing tool "sti05" loaded.
[01:20:34.798] flashing tool "mitsukernel" loaded.
[01:20:34.798] flashing tool "mitsukernelocp" loaded.
[01:20:34.798] flashing tool "mitsubootloader" loaded.
[01:20:34.799] flashing tool "shbootmode" loaded.
[01:20:34.801] flashing tool "shaudmode" loaded.
[01:20:34.801] flashing tool "subarucan" loaded.
[01:20:34.801] flashing tool "mitsucan" loaded.
[01:20:58.866] J2534 API Version: 04.04
[01:20:58.866] J2534 DLL Version: 0.50.2598 Jun 26 2009 15:02:29
[01:20:58.866] Device Firmware Version: 1.10.3020
[01:21:02.846] sending init sequence 1 (0001)
[01:21:03.037] J2534 error [ERR_TIMEOUT].
[01:21:03.568] J2534 error [ERR_TIMEOUT].
[01:21:03.568] interface close


These are the lines that pop up every time I try to read my ecu. About to have a total makeover on my setup so i need to see where I stand now, in need of a baseline. But every time i try to read I get these errors.. Anyone have any idea's I'm fairly new to the game so please school me.. Class is in session..

Thanks in advance...


JRP

 

Nobody?

 

[15:19:15.275] EcuFlash Version 1.42.2595
[15:19:15.275] OS Version Windows Vista
[15:19:15.275] Qt Version 4.5.0
[15:19:15.289] 56 memory models read.
[15:19:15.289] scanning for metadata models in C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata
[15:19:15.624] 343 ROM metadata models scanned.
[15:19:15.624] checksum module "subarudbw" loaded.
[15:19:15.624] checksum module "mitsucan" loaded.
[15:19:15.624] flashing tool "wrx02" loaded.
[15:19:15.625] flashing tool "wrx04" loaded.
[15:19:15.625] flashing tool "sti04" loaded.
[15:19:15.625] flashing tool "sti05" loaded.
[15:19:15.625] flashing tool "mitsukernel" loaded.
[15:19:15.625] flashing tool "mitsukernelocp" loaded.
[15:19:15.625] flashing tool "mitsubootloader" loaded.
[15:19:15.626] flashing tool "shbootmode" loaded.
[15:19:15.627] flashing tool "shaudmode" loaded.
[15:19:15.628] flashing tool "subarucan" loaded.
[15:19:15.628] flashing tool "mitsucan" loaded.
[15:20:00.681] J2534 API Version: 04.04
[15:20:00.681] J2534 DLL Version: 0.50.2598 Jun 26 2009 15:02:29
[15:20:00.681] Device Firmware Version: 1.10.3020
[15:20:06.680] sending init sequence 1 (0001)
[15:20:09.906] sending init sequence 1 (0003)
[15:20:13.132] sending init sequence 1 (FFFF)
[15:20:16.365] sending init sequence 1 (F0F0)
[15:20:19.082] no response to any known code
[15:20:19.083] interface close

 

There are quit a few threads on this regarding ECU connection problems:

Inspect the wire that goes to the white connector...it is probably open/bad. I have had to repair mine a couple times.

Or......

Try starting the car and then connecting. Low battery voltage may be the cause.

 

i had the same problem at first. Check our tactrix cable and make sure both connectors are plugged in under the dash. Then do a read rom.
When I only had the main one plugged in I got the same errors.
Good luck.

 

i think it's best if you asked it in ecuflash section, i don't think everybody in this section knows or uses it.

 

O snap, good point. Can a mod please move this. Thanks for the info already guys.

 

the cable i got was bad, had to pay $80 to reship it back and i've been waiting months for my replacement. wish someone else made them, guy is a joke.

 

where on earth did you ship it to that it cost you 80 bucks is the first question?

who did you buy it from?

I had a bad cable and tactrix had a new cable in my hands in 7 business days

 

it had to be sent to Zew Zealand i believe got it from evoscan

 

Tried using evoscan when car was started but no luck. ran ecu unlock-er with no luck also.. cable is in good shape. Anything else it could be?

 

i had the same errors and my cable looked fine but it ended up being faulty.

 

So can you just Ohm the cable out to find out if its bad or not?

 

your using 1.42 uninstall it and find 1.28 or 1.29 and install it.thats what i had to do 1.42 wouldnt even read my ecu then used a earlier version and it worked perfect. 1.28 or 29 is a more raw version it dosnt have all the new add ons but try it out it might work

 

Ok, I will try that tomorrow.