|
|
|
|
Thread Tools | Display Modes |
12-06-2014, 06:15 PM | #1 | |
Scooby Newbie
Member#: 405053
Join Date: Oct 2014
Chapter/Region:
TXIC
Location: Houston/ College Station, TX
Vehicle:2002 wrx wagon faded silver crap |
EcuFlash not reading...about to break stuff.
Alright guys... searched around with google around this site...wrx tuners, iwsti, etc.... found a few threads with my issue and symptoms, but no resolutions.
Car: 02 wrx wagon Computer: Dell XPS running windows 8.1 Cable: Genuine Tactrix Openport 2.0 Symptoms: Romraider logger will run nicely. ECUflash Cannot read my ecu. I do have the block installed. I do have the green connectors connected. the car does go into test mode (CEL flashes, cycling fan). History: Car did have an AP that the previous owner lost. I did meet up with a fellow member on here to marry, then uninstall his AP. Log: Quote:
Please let this be something stupid. *EDIT 12/08/2014* For those searching: Got this resolved. I forwarded this thread to tactrix. They sent me a modified ECUflash (with drivers) and updated firmware for the cable. Got the timing down on the third try. This is why you buy genuine. you get the support needed to get things to work. I'm now a happy camper. before i contacted (and posted here) I did the following: 1) Searched all relevant forums, and read relevant information. Also read faq on romraider, and other forums. 2) Checked to make sure All grounds were good. (In my case I found the transmission pitch stop mount ground broken, fixed then moved on.) 3) Checked battery voltage 4) Checked cable for bent pins. 5) Checked OBD port for loose wires, bent pins, etc. 6) Checked flash block connections and voltage. 7) Checked green connectors for good contact. 8) Uninstall ECUflash, all drivers. Also deleted all traces of it on hard drive. 9) Reboot, and reinstall (as administrator if you have the option). 10) Reboot again 11) Try to connect again. 12) If all above fail, start new thread and post all relevant logs in their entirety. 13) follow advice given (if any). none in my case. 14) Email tactrix with all information gathered from above steps. also include operating system. also send them all logs in email. 15) follow tactrix instructions and advice. *Edit 2/24/15* I have been getting emails for the beta Ecuflash I was sent. unfortunately, I'm not on here nearly enough as Engineering school is kick my butt. I was under the impression the drivers have been updated, but if they have not been, here is the link to the software I was sent. Mikey, pm when we don't need these anymore....*link removed*
* Registered users of the site do not see these ads.
Last edited by madtrini; 02-25-2015 at 04:47 PM. Reason: beta link removed |
|
12-07-2014, 03:32 AM | #2 |
Scooby Newbie
Member#: 405053
Join Date: Oct 2014
Chapter/Region:
TXIC
Location: Houston/ College Station, TX
Vehicle:2002 wrx wagon faded silver crap |
anyone? reinstalled and now it just hangs... or i'll get a checksum error.
|
12-07-2014, 04:00 AM | #3 |
Scooby Newbie
Member#: 405053
Join Date: Oct 2014
Chapter/Region:
TXIC
Location: Houston/ College Station, TX
Vehicle:2002 wrx wagon faded silver crap |
well, getting somewhere i guess. second log.
[02:33:13.995] EcuFlash Version 1.44.4361 [02:33:13.995] OS Version Windows (unknown version) [02:33:13.995] Qt Version 5.2.0 [02:33:13.999] 67 memory models read. [02:33:13.999] scanning for metadata models in C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata [02:33:14.084] 558 ROM metadata models scanned. [02:33:14.084] checksum module "subarudbw" loaded. [02:33:14.084] checksum module "subarudiesel" loaded. [02:33:14.084] checksum module "mitsucan" loaded. [02:33:14.084] checksum module "mitsuh8" loaded. [02:33:14.084] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded. [02:33:14.084] patch module "Mitsu CAN RAM Parameter Logging" loaded. [02:33:14.087] using metadata XML ID read_wrxnonusdm from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_wrxnonusdm.xml [02:33:14.090] flashing tool "wrx02" loaded. [02:33:14.092] flashing tool "wrx04" loaded. [02:33:14.094] flashing tool "sti04" loaded. [02:33:14.095] flashing tool "sti05" loaded. [02:33:14.098] flashing tool "mitsucan" loaded. [02:33:14.098] flashing tool "mitsukernel" loaded. [02:33:14.098] flashing tool "mitsukernelocp" loaded. [02:33:14.098] flashing tool "mitsubootloader" loaded. [02:33:14.098] flashing tool "shbootmode" loaded. [02:33:14.098] flashing tool "shaudmode" loaded. [02:33:14.100] flashing tool "subarucan" loaded. [02:33:14.102] flashing tool "subarucand" loaded. [02:33:14.103] flashing tool "subarubrz" loaded. [02:33:14.105] flashing tool "subaruhitachi" loaded. [02:33:14.120] J2534 API Version: 04.04 [02:33:14.120] J2534 DLL Version: 1.01.4358 Oct 10 2014 03:49:00 [02:33:14.120] Device Firmware Version: 1.15.4363 [02:33:14.120] Device Serial Number: TAVwy21* [02:33:14.120] interface close [02:33:14.132] J2534 API Version: 04.04 [02:33:14.132] J2534 DLL Version: 1.01.4358 Oct 10 2014 03:49:00 [02:33:14.132] Device Firmware Version: 1.15.4363 [02:33:14.132] Device Serial Number: TAVwy21* [02:33:14.132] interface close [02:33:14.145] J2534 API Version: 04.04 [02:33:14.145] J2534 DLL Version: 1.01.4358 Oct 10 2014 03:49:00 [02:33:14.145] Device Firmware Version: 1.15.4363 [02:33:14.145] Device Serial Number: TAVwy21* [02:33:14.146] interface close [02:33:14.159] J2534 API Version: 04.04 [02:33:14.159] J2534 DLL Version: 1.01.4358 Oct 10 2014 03:49:00 [02:33:14.159] Device Firmware Version: 1.15.4363 [02:33:14.159] Device Serial Number: TAVwy21* [02:33:14.160] interface close [02:33:14.175] J2534 API Version: 04.04 [02:33:14.175] J2534 DLL Version: 1.01.4358 Oct 10 2014 03:49:00 [02:33:14.175] Device Firmware Version: 1.15.4363 [02:33:14.175] Device Serial Number: TAVwy21* [02:33:14.176] interface close [02:33:14.189] J2534 API Version: 04.04 [02:33:14.189] J2534 DLL Version: 1.01.4358 Oct 10 2014 03:49:00 [02:33:14.189] Device Firmware Version: 1.15.4363 [02:33:14.189] Device Serial Number: TAVwy21* [02:33:14.191] interface close [02:33:40.364] using metadata XML ID read_wrx02 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_wrx02.xml [02:33:40.367] using metadata XML ID read_wrx02 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_wrx02.xml [02:33:48.403] using metadata XML ID read_wrx02 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_wrx02.xml [02:33:48.415] J2534 API Version: 04.04 [02:33:48.415] J2534 DLL Version: 1.01.4358 Oct 10 2014 03:49:00 [02:33:48.415] Device Firmware Version: 1.15.4363 [02:33:48.415] Device Serial Number: TAVwy21* [02:34:46.681] denso02_bootloader_cmd_start [02:36:37.687] readback fail [02:36:50.850] J2534 error [no data was read]. [02:36:52.871] J2534 error [no data was read]. [02:36:53.873] J2534 error [no data was read]. [02:37:57.634] J2534 error [no data was read]. [02:39:30.497] J2534 error [no data was read]. [02:40:31.838] J2534 error [no data was read]. [02:40:31.838] denso02_bootloader_cmd_start [02:41:32.144] readback fail [02:41:57.337] J2534 error [no data was read]. [02:43:27.684] J2534 error [no data was read]. [02:43:28.699] J2534 error [no data was read]. [02:43:33.456] J2534 error [no data was read]. [02:43:42.581] J2534 error [no data was read]. [02:43:44.807] J2534 error [no data was read]. [02:43:44.807] denso02_bootloader_cmd_start [02:45:06.302] readback fail [02:45:07.309] J2534 error [no data was read]. [02:45:15.404] J2534 error [no data was read]. [02:45:17.434] J2534 error [no data was read]. [02:45:18.145] J2534 error [no data was read]. [02:45:19.152] J2534 error [no data was read]. [02:45:21.882] J2534 error [no data was read]. [02:45:21.882] denso02_bootloader_cmd_start [02:49:16.550] readback fail [02:49:18.064] J2534 error [no data was read]. [02:49:18.564] J2534 error [no data was read]. [02:49:20.085] J2534 error [no data was read]. [02:49:23.323] J2534 error [no data was read]. [02:49:29.388] J2534 error [no data was read]. [02:49:34.649] J2534 error [no data was read]. [02:49:34.649] denso02_bootloader_cmd_start [02:56:05.927] readback fail [02:56:39.267] kernel get version [02:57:21.144] readback fail [02:57:59.010] interface close [02:58:01.010] interface close |
12-08-2014, 04:34 PM | #4 |
Scooby Newbie
Member#: 405053
Join Date: Oct 2014
Chapter/Region:
TXIC
Location: Houston/ College Station, TX
Vehicle:2002 wrx wagon faded silver crap |
posted resolution in OP
|
12-18-2014, 04:16 PM | #5 |
Scooby Newbie
Member#: 394646
Join Date: Jun 2014
Chapter/Region:
NWIC
Location: Oregon
Vehicle:2003 WRX Flex Fuel Pv=nRT |
Having the same issue on my 2003 WRX. (made in 6/2002) Your output logs are identical, situation the same. I've just emailed them as well.
Worked beautifully on my 2009 Legacy 2.5i though... I've just emailed them, here's to good luck. |
12-18-2014, 04:31 PM | #6 |
Scooby Newbie
Member#: 394646
Join Date: Jun 2014
Chapter/Region:
NWIC
Location: Oregon
Vehicle:2003 WRX Flex Fuel Pv=nRT |
They sent me a link to a different ecuflash installer that uses a different firmware update, just as you had experienced. *insert happy meme here*
|
12-25-2014, 11:34 AM | #7 |
Scooby Newbie
Member#: 316863
Join Date: Apr 2012
Chapter/Region:
E. Canada
Location: Southern Ontario
Vehicle:2001 2.5RS Red |
Could you post the files they sent you? I am having the same issue with my op2.0 cable. I ended up borrowing a friend's 1.3U cable to get my flashing done temporarily but I would really like to get my 2.0 cable to work.
I came to the conclusion that it was the firmware, this just confirms my findings.. |
12-26-2014, 02:31 PM | #8 | ||
Scooby Newbie
Member#: 405053
Join Date: Oct 2014
Chapter/Region:
TXIC
Location: Houston/ College Station, TX
Vehicle:2002 wrx wagon faded silver crap |
Quote:
Quote:
|
||
12-26-2014, 06:05 PM | #9 |
Scooby Newbie
Member#: 316863
Join Date: Apr 2012
Chapter/Region:
E. Canada
Location: Southern Ontario
Vehicle:2001 2.5RS Red |
Done and thank you in advance! If this works I'll be so happy. I was about to sell the OP2.0 cable and buy an old 1.3U...
|
12-26-2014, 07:47 PM | #10 |
Scooby Newbie
Member#: 405053
Join Date: Oct 2014
Chapter/Region:
TXIC
Location: Houston/ College Station, TX
Vehicle:2002 wrx wagon faded silver crap |
|
12-27-2014, 11:27 AM | #11 |
Scooby Newbie
Member#: 316863
Join Date: Apr 2012
Chapter/Region:
E. Canada
Location: Southern Ontario
Vehicle:2001 2.5RS Red |
You're the MAN! My OP2.0 cable now works
EDIT: This version really should be on the tactrix website... Last edited by hopperjon; 12-27-2014 at 04:28 PM. |
12-27-2014, 08:18 PM | #12 |
NASIOC Supporter
Member#: 236475
Join Date: Jan 2010
Chapter/Region:
BAIC
Location: San Francisco
Vehicle:2002 WRX Black |
It's a beta version so it has features not fully tested for wide release, which is why we only send it to people who need it for a particular issue or for general testing. If it should be on our site it would be. Though we're not in the office, I have been checking email almost daily while visiting family for the holiday so if you had contacted us, I would have sent it to you.
|
12-27-2014, 08:51 PM | #13 |
Scooby Newbie
Member#: 316863
Join Date: Apr 2012
Chapter/Region:
E. Canada
Location: Southern Ontario
Vehicle:2001 2.5RS Red |
Understandable.. I didn't want to bother you guys with more emails if I could just get it from madtrini I'm just happy that it works. I tried so many things over the course of 20+ hours to try and get it to work (4 different computers / each with windows XP & 7 fresh formats each time / each with 1.42 1.43 1.44 and whatever op2.0 supported versions i could get my hands on). I had given up when I stumbled upon this thread
|
12-27-2014, 08:59 PM | #14 | |
NASIOC Supporter
Member#: 236475
Join Date: Jan 2010
Chapter/Region:
BAIC
Location: San Francisco
Vehicle:2002 WRX Black |
Quote:
-Mike |
|
12-27-2014, 09:32 PM | #15 | |
Scooby Newbie
Member#: 405053
Join Date: Oct 2014
Chapter/Region:
TXIC
Location: Houston/ College Station, TX
Vehicle:2002 wrx wagon faded silver crap |
Quote:
|
|
02-23-2015, 02:07 PM | #16 |
Scooby Newbie
Member#: 414273
Join Date: Feb 2015
|
Im sorry to revive such an old thread but I didn't want to post in the FAQ guide and since im a new member I can't create new threads.
Im Dante from Argentina. I own a Forester 2.0 2006/07. As it usually happens, the girl started giving me a CEL code about Secondary Air Pump. I started investigating about it and decided to remove the pump and clear the codes. I asked a friend that was traveling to the US to bring me the Tactrix cable which I got last weekend. So I installed everything in my laptop, ecuflash, romraider, definitions, etc and I tried to connect to the ECU to read it. Had no luck. Here's the log: [14:16:51.124] J2534 API Version: 04.04 [14:16:51.124] J2534 DLL Version: 1.01.4358 Oct 10 2014 03:49:00 [14:16:51.124] Device Firmware Version: 1.15.4363 [14:16:51.124] Device Serial Number: TAdbYVLw [14:16:51.281] SSM2 init [14:16:51.524] SSM2 ECU ID is 4EA4304006 [14:16:53.540] interface close [14:16:53.541] interface close downloaded all programs and definitions, connected the green cables to enter test mode, clicked the Ok button 1 second-2 seconds-less than 1 second after key set to on but nothing is working. I couldn't find a block plug so I don't think foresters have one, only WRX do? The one thing i noticed is that when I select the type of vehicle, the program uses the WRX/STI 05 template, even when im selecting 2005–2006 Subaru DBW models FXT/OBXT/LGT/Baja I don't know if the templates should be the same or if that's a bug. Blocked ECU can't be possible since here in Argentina we don't have EcuTek or AP franchises, and the previous and only other owner of the car was a family guy with no tunning abilities or intention. Any help would be very appreciated since I bought the cable ONLY to clear those CELs and Reflash. I don't even want it for tunning, but it cost me quite a lot of money (here in Argentina dollars are quite expensive) Thanks to all |
02-23-2015, 02:20 PM | #17 |
NASIOC Supporter
Member#: 236475
Join Date: Jan 2010
Chapter/Region:
BAIC
Location: San Francisco
Vehicle:2002 WRX Black |
Hey Dante,
You're correct that there is no reflash adapter needed for your vehicle. In the USDM, it would only be the 2002 - 2005 WRX, and no other models including STi. In some non-USDM markets that requirement starts with 2001 for the WRX and the same adapter can be required for STi models in the same timeframe, but never for the Forester. After you turn the key to 'ON' with the green test connectors connected do you hear the vehicles fans cycle on and off, plus see unusual dash light activity? That would confirm you're in test mode. The template behavior you're seeing isn't a bug. Those two groups of vehicles use the same flash method and memory model. The groupings of vehicles are just mapped to particular flash methods and memory models. There are many groupings of vehicles that map to the same thing. No problem there. If you can confirm that you're able to get in test mode okay, can you send me an email to support at tactrix dot com? I'll send you a registry edit to have EcuFlash display more logging info so we can get to the bottom of the issue. -Mike Tactrix |
02-23-2015, 02:24 PM | #18 |
Scooby Newbie
Member#: 414273
Join Date: Feb 2015
|
Hello mikey.
Yes, the car enters test mode. I did send an email just when I posted this info. My address should be [email protected] Thank you a lot |
02-24-2015, 01:03 PM | #19 |
Scooby Newbie
Member#: 182953
Join Date: Jun 2008
Chapter/Region:
TXIC
Location: Fort Worth
Vehicle:2007 STi SWP |
I'm in the same boat. Old laptop has been "missing" and new laptop currently running windows 8.1 64bit and 1.3 cable
Installed drivers after ECUflash 1.44 (tried 1.42 as well) was installed. Looks to be able to read the Tactrix cable. However windows is saying driver error. Car is in test mode and definitions have been installed Sent from my iPhone using NASIOC |
02-24-2015, 05:11 PM | #20 |
NASIOC Supporter
Member#: 236475
Join Date: Jan 2010
Chapter/Region:
BAIC
Location: San Francisco
Vehicle:2002 WRX Black |
|
02-24-2015, 06:18 PM | #21 |
Scooby Newbie
Member#: 405053
Join Date: Oct 2014
Chapter/Region:
TXIC
Location: Houston/ College Station, TX
Vehicle:2002 wrx wagon faded silver crap |
Updated OP.
|
02-24-2015, 08:00 PM | #22 |
Scooby Newbie
Member#: 414273
Join Date: Feb 2015
|
Sadly, as i turned out, my ECU is a Hitachi model and can't be reflashed...
But I'd like to say that Michael here helped me a lot and did his best to find a solution for me. |
03-07-2015, 10:10 PM | #23 |
Scooby Newbie
Member#: 402358
Join Date: Sep 2014
|
Hate to hi jack this thread, but I too am about to kill myself. I have been at this for about 4 hours and I can't seem to find a solution. I have the tactrix 2.0 cable and a laptop running windows 8.1. I try and plug the cable to my car and EcuFlash does not read anything as if nothing is plugged in. I tried deleting all the EcuFlash files and re-installing several times and I keep getting this error. I have tried looking for the drivers and I have come up empty.
Can someone please help me. |
03-07-2015, 10:37 PM | #24 |
NASIOC Supporter
Member#: 236475
Join Date: Jan 2010
Chapter/Region:
BAIC
Location: San Francisco
Vehicle:2002 WRX Black |
Can you send me an email with your laptop details to support at tactrix dot com? We'll go through some Windows logs to troubleshoot the driver issues.
|
03-07-2015, 10:47 PM | #25 |
Scooby Newbie
Member#: 402358
Join Date: Sep 2014
|
|
Thread Tools | |
Display Modes | |
|
|