How long has your Tactrix 2.0 lasted you before it started acting erratic?
Here's my story:
I've been successfully using and flashing my JDM EJ207 swapped engine/ECU with my Tactrix 2.0 cable for a couple years now. But about 6 months ago, it started to give me flashing errors. It was saying flashing voltage to low. So i started only flashing my car when I was home with a battery charger on my battery, and it was fine. But then It started giving me that error more frequently, so I searched and found some threads where people were talking about voltage errors. What fixed it for them was downloading the new version of ECUFlash. So I did that.
Now, when I plug in the cable, it doesn't acknowledge that the cable is plugged in. Obviously, I thought it was the driver, so I removed and reinstalled it, along with ECUFlash, but that didn't seem to help.
What was weird was that I tried Learning View, and it also gave me the error like there wasn't a cable plugged in. Then I wiggled the part that plugs into the OBD2 port the same way they wiggle the connector in the emissions testing stations, and it worked! So I tried flashing with ECUFlash, and it gave out in the middle of a flash! It gave me the error that said not to shut off the ignition, just retry the flash. So I did that a couple times and it didn't work. Then I wiggled it, and ultimately, held it pressed in, and it worked!
So at this point, I'm trying to figure out if it's the Tactrix cable going bad, or the hardware driver, or my car's OBD2 port. I don't want to keep trying it because I don't want to risk bricking my ECU.
Here are the details on my setup:
2002 WRX with V8 EJ207 engine/ECU
ECUFlash 1.44.3721 (OpenECU Drivers are bundled with this version of the ECUFlash download)
Windows XP SP.3
Probably something like, 80 reflashes on the ECU/Cable.
Thanks for reading, any thoughts?