TUNERS, help me out! 2002 wrx wagon With everything connected tonight the way I believe it should be, the "read rom" icon lit up, I was able to click on it, and then I stared at the small pop up window. It was blank and never did anything, no prompt to start ignition, etc. I haven't tried to use this software or system yet, I am in the process of learning. Having said that, I did my research and so here are the steps I took tonight. I will walk you through in chronological order as it might be crucial. 1. Get to car, put laptop in passenger seat, turn on. 2. climb under to where I can see the column, connect green harness 3. Take the "short" block (blue accessory that comes with tactrix) and place it on the open female harness tied into the spine of wires next to the green harnesses. 4. Connect tactrix cable to OBDII port, connect to laptop. Tactrix cable is lit up and making its rainbow colors, computer recognizes its plugged in. 5. Run through tactrix table set up with laptop, first clicking the no button, then clicking install what is recommended by windows. Done. Everything's good. 6. Open Ecuflash, hit "read rom" 7. watch pop up window open, and stay blank. Wait 2 minutes, still nothing. Click cancel. Reboot ecuflash, run again. Nothing. I have the 12 pin additional harness block that came with the kit (plugs into the headset output on the tactrix) as well as the other "short" block that comes in the set. Is the 12 pin (2 blank pin locations) the 16 pin they continually talk about? I never was prompted to turn on the ignition, so I didn't. I have all the recent definitions and have followed all instructions, or so I think. Is there some other connection to make on the '02s?
The next step in the proccess should be for the software to prompt you to pick ECU definitions for the ROM you are reading. It doesn't even get to that point?
nope, did I make the right connections? I have the newest ecuflash downloaded from osecuroms.com with the same definitions. I believe I loaded the definitions correctly, but I was a little hazy on the directions. The Tactrix cable I have is the 2.0 version, just got it.
Well, you're doing this out of ECUFlash, so it's using whatever def's come packaged with the version of ECUFlash you have. You definitely need the newest version of ECUFlash for it to work. Try checking your version and downloading/installing the newest version. http://openecu.org/index.php?title=EcuFlash
Did you click 'No' to installing unsigned drivers? Tactrix is a relatively small operation will probably never bother getting their drivers signed.
I do have the newest version of ecuflash. When reading the open source site, it said to download the newest definitions and go to: Options, then open metadata directory, delete the file in there that starts with R (forgetting the name) and then replace it with the "subaru" file in the definitions. Does that sound correct, or did I not do it correctly? In my research it said that ecuflash does not come with definitions loaded anymore, forcing people to actually download and install the newest versions as a fail safe. I clicked 'no' initially, and then when it asked if I wanted to install the recommended driver recommended by microsoft I selected yes, and it loaded flawlessly. Ecuflash recognizes the tactrix cable, so the drivers installed okay I would think.
1) Goto device manager 2) Find the device that you think is the Tactrix cable 3) Right-Click -> Properties Should look something like this:
Just bugged my buddy daniel, (thormix on most forums.) He's one of the top guys over at XPT. Ive been to a few install meets at his house in LA, and had his number so I gave him a call. He said that the '02s can be tricky with the new software, and to hit the read rom button, and turn the ignition on before it prompts. He said try this several different ways, hit read rom, wait a second, turn key, or try them simultaneously. I guess I'll give it a whirl, I dont see what it would hurt.
That is normal for the 02/03 WRX's, they are picky at what time you hit each button. However, normally when you hit read, it should go something like this: -You press the read button -ECUFlash prompts you to pick the correct definition file for the ROM being read -ECUFlash prompts you to connect the test connectors and turn the cars ignition on and hit "ok" when done -You turn on the ignition and hit "ok" right away I guess I should also mention that I'm still using an older version of ECUFlash and haven't bothered to upgrade in a few versions.
maybe I should just get the old version to run on my car. exactly nate, Im not getting any of those prompts. Straight to a blank window that sits like that indefinitely. Two things, if I loaded the definitions the wrong way, that would cause this issue, correct? Is there a way you can walk me through how you would load them, step by step? If I were to load the older ecuflash, would the new definitions give me any sort of trouble? All that was going on while trying to do the "turn key while hitting read" stuff like I believed daniel was saying, is that my CEL would flash, my radiator fans would run at an interval, and it sounded like my fuel pump was cycling, or the relays on my flashers were ticking.
Hrm, sounds like you have a bad application install, I haven't seen that before. Try reinstalling the application and the defs. Unsure. It's possible, as the application is looking at your definitions during that step, as it populates a list from you to choose from. As I said, I haven't yet bothered to upgrade to the newer versions of ECUFlash. The last one I installed had the def's packaged with it. Yeah, that's what it should do. That means you correctly plugged the green connectors.
I don't think you can use too old of a version since the cable support is only for the newer releases. What version ecuflash do you have?
Bullwinkle, is there a way I could bug you to email me your current version of Ecuflash? Its under 10mb, right? I just wouldnt load the definitions, and see if it works. The tactrix cable might not work, but I'd blame software before I'd blame hardware.
I think I'm still using a really old version (like 1.29 or so). That won't work with your OP v2.0 at all. You need the newest version of ECUFlash (1.41, iirc). Have you tried just reinstalling the application and reimporting the defs? EDIT: I just checked, and I must've upgraded at some point, because I am using version 1.40. I don't remember specifically importing any drivers, they must've just came with my original install and stayed as I upgraded. EDIT2: It looks like ECUFlash does still come packaged with a metric version of the current definitions. My advice is just to try a clean reinstall and see if the application behaves any nicer.
nate- Huge thanks for the help. I will try a reinstall, without adding any definitions that do not come with the program. Metric is better than nothing at this point, I'm curious to see if it will read. I'll give it a shot over the next hour and report back with what I find.
Alright!!!! It worked out. I deleted everything including the definitions from my computer, downloaded 1.40 (not 1.41) and went to my car. Using only the definitions that came with ecuflash 1.40, I was able to read, and flash, the new map onto my car. I am not running a stg. 1 tune from osecurom.com I did a few logs, and everything is gravy from what I can see. Pulls wayyyyy harder. Will definitely tide me over to stg two, but I need to wait for a clutch.
