Which version of Tactrix Cable USDM 05 STI

[JoeT]

Hi All,

I currently have a 2005 USDM STi and a 05 USDM Legacy GT. Just a couple of questions around this and a question about ECUFlash 1.32.

I purchased a Tactrix Cable about 8 monts ago, I'm just wondering if this cable will work for the 2005 STI as well.

http://www.tactrix.com/product_info.php?products_id=35

Also, another couple of questions with regards to ECUFlash 1.32

When trying to read the ECU data using version 1.32, we get an error saying that it's incomplete, and then it aborts. It reads kind of ok on 1.29a, basically aborts and when re-run, it continues ok.

ECU Box: 22611
ECU Type: AJ931

Here's the bad part, when flasing with version 1.29a, it wrote the rom fine, but when I upgraded to 1.32 and tried to reflash, it basically destroyed the ROM information, net result is I ordered a new ECU.

Can anyone shed some light on what I did wrong? On the 2005 STI, there's only the diagnostic connectors that needed to be hooked together, so it was pretty straight forward.

HELP..

Thank You in advance.

[Freon]

http://www.openecu.org/index.php?title= ... cleSupport
If your cable works on a US LGT, it will work on any US 2.5L turbo car.

I couldn't tell you what went wrong while flashing your car. If there is a problem with flashing, ECUflash should warn you. You need to pay attention to what it tells you. I doubt it flashed normally & said everything was ok, but actually damaged your ECU.

You really haven't provided any useful information for finding out what happened with your possibly broken ECU. Even if it is too late to get a log from an ECUflash session you just closed before you saved the log or took a screencap, you can at least post if the car turns over, or what happens when you try to reflash it again. You gotta give us something...

For future reference, ECUflash should bark up an error at the end of flashing if it cannot successfully write and get a good checksum on every block it writes to the ECU. If it does that, you need to KEEP THE KEY IN THE IGNITION AND DO NOT TURN IT OFF. The error also says this. This has also been written in the forums countless times. At this point you can just click write again and it should retry the write. As normal, it will only write the blocks that contain differences between the actual ECU and the ROM you are trying to write. If necessary, you can reboot your laptop as well, again, just don't touch the key!

It may be possible to save an ECU that had bad data written to it. You can read here:
http://www.openecu.org/index.php?title=SHBootMode

[JoeT]

Thanks for the information, it helps greatly. We're suspecting that the battery voltage dropped that's why it didn't complete the flash. User error, as usual.

Anyways, is there anywhere we can purchase a pre-made flashboot mode adapter?

The one referenced in the schematic: http://openecu.org/downloads/shbootmode.pdf

Thanks for the assistance.

[radsdau]

It is also possible you edited the ROM with 1.3x using XML defs from a pre-1.3 (slightly different format, I think); this could corrupt the data in the ROM, and who knows, perhaps stop the car starting. Even if the reflash was good, it may still make the ECU unresponsive.
Can anyone confirm the accuracy of this please?