ECUflash ECUflash won't read Ecu

[Christoph]

Hello, I have been trying to read my ecu with ECUflash but I get a pop up error while doing so.
I have a 1999 Eclipse GSX with a verified flashable 99 black box ecu.
I have installed ECUflash and Ceddymods correctly.
I have the HEX and XML files in the correct folder.
My vehicle selected is the 99/evo5-6; which I believe is correct.
The key is in the correct position.
The reflash connector is in and has continuity with pin 79.
ECUflash acknowledges that I am connected to the ECU.

I have read all the threads on this website regarding failure to read ECU's. They do not pertain to my situation and non of them describe a log anything like mine.

Here is the log:

[16:55:10.381] using metadata XML ID read_evo65 from file C:/Program Files/OpenECU/EcuFlash/rommetadata/read templates/read_evo65.xml
[16:55:10.396] J2534 API Version: 04.04
[16:55:10.396] J2534 DLL Version: 1.01.4671 Mar 11 2016 19:11:49
[16:55:10.396] Device Firmware Version: 1.16.4647
[16:55:10.396] Device Serial Number: TAQVz8Yq
[16:55:12.068] sending init sequence 2
[16:55:14.130] interface close

I would really appreciate some help here.

 

[onefast2gdsm]

uninstall ecuflash and reinstall it. Sounds like a driver error

 

[onefast2gdsm]

This is what my ecu is set to under ecu settings

 

[Christoph]

I have reinstalled ECUFlash and the Tactrix drivers 3 times. I have also tried all possible H8 ecu options while attempting to read the ECU

 

[onefast2gdsm]

Can you log with evoscan at all

 

[Christoph]

My car is not running yet, my ECU is not prepared to run the current setup on my engine, I have bigger injectors, turbo, etc. Thus my need to modify my tune.

 

[onefast2gdsm]

yeah but you should still be able to connect to evoscan with the key on and log with the engine off. if it connects with evoscan ecuflash is the problem.

 

[Christoph]

Ok great I will try tomorrow, thank you

 

[Christoph]

Hello, I have had a very busy couple of weeks, finally got around to hooking up EVOScan and attempting to log, no dice, I got an error similar to the EcuFlash one:


Info: OpenPort 2.0 Found.
Info: OpenPort Firmware v1.16.464
Info: Battery 5.032V
Info: Initialize Vehicle ECU...
Info: DSM Initialize...
Info: Initializing At 5 baud...
Error: J2534 init error ERR_INVALID_CHANNEL_ID
Info: Datalogger Ended.

 

[Christoph]

I realized I had not uploaded the entire log from my ECUFlash log window, here is the complete one:

[13:49:16.290] EcuFlash Version 1.44.4671
[13:49:16.290] OS Version Windows 7
[13:49:16.290] Kernel Type winnt
[13:49:16.290] Kernel Version 6.1.7601
[13:49:16.290] CPU x86_64
[13:49:16.290] Product Name Windows 7
[13:49:16.290] Product Type windows
[13:49:16.290] Product Version 7
[13:49:16.290] Qt Version 5.5.1
[13:49:16.290] Qwt Version 6.1.2
[13:49:16.290] QwtPlot3D Version 0.2.6
[13:49:16.290] Boost Version 1.60
[13:49:16.290] FTDI Library Version 3.02.11
[13:49:16.290] Openport J2534 Library Version 1.01.4671
[13:49:16.290] 67 memory models read.
[13:49:16.290] scanning for metadata models in C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata
[13:49:16.384] 750 ROM metadata models scanned.
[13:49:16.384] checksum module "subarudbw" loaded.
[13:49:16.384] checksum module "subarudiesel" loaded.
[13:49:16.384] checksum module "mitsucan" loaded.
[13:49:16.384] checksum module "mitsuh8" loaded.
[13:49:16.384] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[13:49:16.384] patch module "Mitsu CAN RAM Parameter Logging" loaded.
[13:49:16.399] using metadata XML ID read_evo65 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo65.xml
[13:49:16.399] flashing tool "wrx02" loaded.
[13:49:16.399] flashing tool "wrx04" loaded.
[13:49:16.399] flashing tool "sti04" loaded.
[13:49:16.399] flashing tool "sti05" loaded.
[13:49:16.415] flashing tool "mitsucan" loaded.
[13:49:16.415] flashing tool "mitsukernel" loaded.
[13:49:16.415] flashing tool "mitsukernelocp" loaded.
[13:49:16.415] flashing tool "mitsubootloader" loaded.
[13:49:16.415] flashing tool "shbootmode" loaded.
[13:49:16.415] flashing tool "shaudmode" loaded.
[13:49:16.415] flashing tool "subarucan" loaded.
[13:49:16.415] flashing tool "subarucand" loaded.
[13:49:16.415] flashing tool "subarubrz" loaded.
[13:49:16.415] flashing tool "subaruhitachi" loaded.
[13:49:16.462] J2534 API Version: 04.04
[13:49:16.462] J2534 DLL Version: 1.01.4671 Mar 11 2016 19:11:49
[13:49:16.462] Device Firmware Version: 1.16.4647
[13:49:16.462] Device Serial Number: TAQVz8Yq
[13:49:16.462] interface close
[13:49:16.508] J2534 API Version: 04.04
[13:49:16.508] J2534 DLL Version: 1.01.4671 Mar 11 2016 19:11:49
[13:49:16.508] Device Firmware Version: 1.16.4647
[13:49:16.508] Device Serial Number: TAQVz8Yq
[13:49:16.508] interface close
[13:49:16.524] J2534 API Version: 04.04
[13:49:16.524] J2534 DLL Version: 1.01.4671 Mar 11 2016 19:11:49
[13:49:16.524] Device Firmware Version: 1.16.4647
[13:49:16.524] Device Serial Number: TAQVz8Yq
[13:49:16.524] interface close
[13:49:16.555] J2534 API Version: 04.04
[13:49:16.555] J2534 DLL Version: 1.01.4671 Mar 11 2016 19:11:49
[13:49:16.555] Device Firmware Version: 1.16.4647
[13:49:16.555] Device Serial Number: TAQVz8Yq
[13:49:16.555] interface close
[13:49:16.571] J2534 API Version: 04.04
[13:49:16.571] J2534 DLL Version: 1.01.4671 Mar 11 2016 19:11:49
[13:49:16.571] Device Firmware Version: 1.16.4647
[13:49:16.571] Device Serial Number: TAQVz8Yq
[13:49:16.571] interface close
[13:49:16.618] J2534 API Version: 04.04
[13:49:16.618] J2534 DLL Version: 1.01.4671 Mar 11 2016 19:11:49
[13:49:16.618] Device Firmware Version: 1.16.4647
[13:49:16.618] Device Serial Number: TAQVz8Yq
[13:49:16.618] interface close
[13:49:24.277] using metadata XML ID read_evo5 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo5.xml
[13:49:24.293] using metadata XML ID read_evo5 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo5.xml
[13:49:43.150] using metadata XML ID read_evo5 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo5.xml
[13:49:43.181] J2534 API Version: 04.04
[13:49:43.181] J2534 DLL Version: 1.01.4671 Mar 11 2016 19:11:49
[13:49:43.181] Device Firmware Version: 1.16.4647
[13:49:43.181] Device Serial Number: TAQVz8Yq
[13:49:46.286] sending init sequence 2
[13:49:48.329] interface close

Obviously I am still having issues with this, I have gotten a new laptop with windows 7 and done an entire fresh installation. This leads me to believe that it may not be software related, and maybe having to do with the Tactrix unit or maybe it has something to do with the firmware, not entirely sure what exactly that is. Any help is very much appreciated.

 

[tunernewb92]

Every an update on this?

 

[Tiki2777]

Sounds like he had an issue with connectivity (common) or a dud op 2.0 cable/module (most likely).

 

[Christoph]

No update, the problem still persists just have had no time to work on the car. Although I did change the engine harness to a new unmolested stock one. It didnt change anything. I emailed Tactrix for help, he told me that there is a problem with my OBD. thats what the whole problem is, EcuFlash tries to read but it doesnt get passed conencting to the OBD. Im baffled on what to do or how/where to pin point whats wrong.

 

[tunernewb92]

I actually figured my issue out on this right after I wrote this. My single wire never went to the ECU Pin 79 so it wasn't receiving signal to allow the flash to happen. Ran a wire and pinned it and viola worked.

 

[Christoph]

The single wire from the tactrix unit?