pcmhacking.net

I was wondering if anyone has expirence with the tactrix & EcuFlash/OpenECU kit?

I've tried it on a few different Subi's & mitsubishi's & alway had troubles...

The current car I'm trying to find if it has been tuned already is a 2005 WRX with EJ205 turbo, it has STi stickers & badges but been told it's just WRX!

I've made sure I have the green plug connected together under dash when trying to read,I even have the 4 pin plug with bridging connector but been told thats only really needed when trying to write to it.
I've seen they can have trouble catching ignition cycle & tried clicking ok just before ignition a few time & then the other way a few times & tried every possible subaru format selection available but no luck.

Here's the log from the attempts...

[10:21:24.490] Logging to file C:/Users/Win7-T42/AppData/Roaming/OpenECU/EcuFlash/logs/ecuflash_log_20161122t102124.txt
[10:21:24.490] EcuFlash Version 1.44.4799
[10:21:24.490] OS Version Windows 7
[10:21:24.490] Kernel Type winnt
[10:21:24.490] Kernel Version 6.1.7601
[10:21:24.490] CPU i386
[10:21:24.490] Product Name Windows 7
[10:21:24.490] Product Type windows
[10:21:24.490] Product Version 7
[10:21:24.490] Qt Version 5.6.0
[10:21:24.490] Qwt Version 6.1.2
[10:21:24.490] QwtPlot3D Version 0.2.6
[10:21:24.490] Boost Version 1.60
[10:21:24.490] FTDI Library Version 3.02.11
[10:21:24.490] Openport J2534 Library Version 1.02.4798
[10:21:24.510] 67 memory models read.
[10:21:24.510] scanning for metadata models in C:/OpenECU/EcuFlash/rommetadata
[10:21:24.760] 745 ROM metadata models scanned.
[10:21:24.760] checksum module "subarudbw" loaded.
[10:21:24.760] checksum module "subarudiesel" loaded.
[10:21:24.760] checksum module "subaruhitachi" loaded.
[10:21:24.760] checksum module "mitsucan" loaded.
[10:21:24.760] checksum module "mitsuh8" loaded.
[10:21:24.760] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[10:21:24.760] patch module "Mitsu CAN RAM Parameter Logging" loaded.
[10:21:24.770] using metadata XML ID read_sti05 from file C:/OpenECU/EcuFlash/rommetadata/read templates/read_sti05.xml
[10:21:24.780] flashing tool "wrx02" loaded.
[10:21:24.780] flashing tool "wrx04" loaded.
[10:21:24.791] flashing tool "sti04" loaded.
[10:21:24.791] flashing tool "sti05" loaded.
[10:21:24.801] flashing tool "mitsucan" loaded.
[10:21:24.801] flashing tool "mitsukernel" loaded.
[10:21:24.801] flashing tool "mitsukernelocp" loaded.
[10:21:24.801] flashing tool "mitsubootloader" loaded.
[10:21:24.801] flashing tool "shbootmode" loaded.
[10:21:24.801] flashing tool "shaudmode" loaded.
[10:21:24.801] flashing tool "subarucan" loaded.
[10:21:24.811] flashing tool "subarucand" loaded.
[10:21:24.811] flashing tool "subarubrz" loaded.
[10:21:24.821] flashing tool "subaruhitachi" loaded.
[10:21:24.871] J2534 API Version: 04.04
[10:21:24.871] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[10:21:24.871] Device Firmware Version: 1.16.4769
[10:21:24.871] Device Serial Number: TARpXi0T
[10:21:24.871] interface close
[10:21:24.881] J2534 API Version: 04.04
[10:21:24.881] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[10:21:24.881] Device Firmware Version: 1.16.4769
[10:21:24.881] Device Serial Number: TARpXi0T
[10:21:24.881] interface close
[10:21:24.921] J2534 API Version: 04.04
[10:21:24.921] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[10:21:24.921] Device Firmware Version: 1.16.4769
[10:21:24.921] Device Serial Number: TARpXi0T
[10:21:24.921] interface close
[10:21:24.931] J2534 API Version: 04.04
[10:21:24.931] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[10:21:24.931] Device Firmware Version: 1.16.4769
[10:21:24.931] Device Serial Number: TARpXi0T
[10:21:24.931] interface close
[10:21:24.971] J2534 API Version: 04.04
[10:21:24.971] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[10:21:24.971] Device Firmware Version: 1.16.4769
[10:21:24.971] Device Serial Number: TARpXi0T
[10:21:24.971] interface close
[10:21:24.981] J2534 API Version: 04.04
[10:21:24.981] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[10:21:24.981] Device Firmware Version: 1.16.4769
[10:21:24.981] Device Serial Number: TARpXi0T
[10:21:24.981] interface close
[10:21:39.412] using metadata XML ID read_sti04 from file C:/OpenECU/EcuFlash/rommetadata/read templates/read_sti04.xml
[10:21:39.422] using metadata XML ID read_sti04 from file C:/OpenECU/EcuFlash/rommetadata/read templates/read_sti04.xml
[10:21:41.605] using metadata XML ID read_sti04 from file C:/OpenECU/EcuFlash/rommetadata/read templates/read_sti04.xml
[10:21:41.615] J2534 API Version: 04.04
[10:21:41.615] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[10:21:41.615] Device Firmware Version: 1.16.4769
[10:21:41.615] Device Serial Number: TARpXi0T
[10:21:49.347] kernel get version
[10:21:49.567] interface close
[10:21:49.577] J2534 API Version: 04.04
[10:21:49.577] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[10:21:49.587] Device Firmware Version: 1.16.4769
[10:21:49.587] Device Serial Number: TARpXi0T
[10:21:49.777] interface close
[10:21:49.817] J2534 API Version: 04.04
[10:21:49.817] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[10:21:49.827] Device Firmware Version: 1.16.4769
[10:21:49.827] Device Serial Number: TARpXi0T
[10:21:49.998] SSM2 init
[10:21:50.158] SSM2 ECU ID is 3D54583005
[10:21:52.221] interface close
[10:21:52.221] interface close
[10:21:59.596] using metadata XML ID read_sti04 from file C:/OpenECU/EcuFlash/rommetadata/read templates/read_sti04.xml
[10:21:59.616] J2534 API Version: 04.04
[10:21:59.616] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[10:21:59.616] Device Firmware Version: 1.16.4769
[10:21:59.616] Device Serial Number: TARpXi0T
[10:22:06.446] kernel get version
[10:22:06.666] interface close
[10:22:06.676] J2534 API Version: 04.04
[10:22:06.676] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[10:22:06.676] Device Firmware Version: 1.16.4769
[10:22:06.676] Device Serial Number: TARpXi0T
[10:22:06.876] interface close
[10:22:06.916] J2534 API Version: 04.04
[10:22:06.916] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[10:22:06.926] Device Firmware Version: 1.16.4769
[10:22:06.926] Device Serial Number: TARpXi0T
[10:22:07.096] SSM2 init
[10:22:07.257] SSM2 ECU ID is 3D54583005
[10:22:09.320] interface close
[10:22:09.320] interface close
[10:22:21.192] using metadata XML ID read_sti05 from file C:/OpenECU/EcuFlash/rommetadata/read templates/read_sti05.xml
[10:22:21.202] using metadata XML ID read_sti05 from file C:/OpenECU/EcuFlash/rommetadata/read templates/read_sti05.xml
[10:22:25.428] using metadata XML ID read_sti05 from file C:/OpenECU/EcuFlash/rommetadata/read templates/read_sti05.xml
[10:22:25.468] J2534 API Version: 04.04
[10:22:25.468] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[10:22:25.468] Device Firmware Version: 1.16.4769
[10:22:25.468] Device Serial Number: TARpXi0T
[10:22:29.371] kernel get version
[10:22:29.581] interface close
[10:22:29.621] J2534 API Version: 04.04
[10:22:29.621] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[10:22:29.631] Device Firmware Version: 1.16.4769
[10:22:29.631] Device Serial Number: TARpXi0T
[10:22:29.801] interface close
[10:22:29.821] J2534 API Version: 04.04
[10:22:29.821] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[10:22:29.821] Device Firmware Version: 1.16.4769
[10:22:29.821] Device Serial Number: TARpXi0T
[10:22:29.982] SSM2 init
[10:22:30.142] SSM2 ECU ID is 3D54583005
[10:22:32.215] interface close
[10:22:32.215] interface close
[10:22:56.280] using metadata XML ID read_wrx02 from file C:/OpenECU/EcuFlash/rommetadata/read templates/read_wrx02.xml
[10:22:56.290] using metadata XML ID read_wrx02 from file C:/OpenECU/EcuFlash/rommetadata/read templates/read_wrx02.xml
[10:23:00.616] using metadata XML ID read_wrx02 from file C:/OpenECU/EcuFlash/rommetadata/read templates/read_wrx02.xml
[10:23:00.666] J2534 API Version: 04.04
[10:23:00.666] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[10:23:00.666] Device Firmware Version: 1.16.4769
[10:23:00.666] Device Serial Number: TARpXi0T
[10:23:08.256] denso02_bootloader_cmd_start
[10:23:09.488] denso02_bootloader_cmd_start
[10:23:10.730] denso02_bootloader_cmd_start
[10:23:11.951] denso02_bootloader_cmd_start
[10:23:13.183] denso02_bootloader_cmd_start
[10:23:13.614] kernel get version
[10:23:13.934] interface close
[10:23:13.934] interface close

Without trying to understand all what you posted I use an OP2 on my EVO regularly and never have a problem. It may be the version for EcuFlash is an old one and there isn't a definition file for that car. The only issue I know of with Subi's is flashing back can sometimes brick the ECU.

Ahh I finally got the file off the ECU & once the EcuFlash program catches the ecu it stops the fans & other things switching on & off!

All I did to get it to work was completely uninstall everything & then re-installed to the location the program prefers it to be & then it worked.

Strange thing is the rom is a H4TH100H & there isn't 1 defined for it but there is for A4TH100H & is very similar so I think it may be edited.

Can you post the bin file. I wouldn't mind have a look at it just for curiosity.

No worries, I also attached the file I think it may be created from....

But I don't know enough about it yet to automatically copy maps structure from the possible original file to the 1 I think may be edited.

The second bin file made sense. Boy a big flat 14.7 plateau even well into boost and 9.5 for engine preservation. The EVO's have a lot of 9.5 and a little leaning makes the world of difference (caution). Timing maps look pretty good. They seem to tolerate quiet a bit of advance.

Thats the thing. I don't reckon they do tolerate well. You just have to look at stock wrx piston ring land failures. Everyone blames the pistons but I always suspected the tune might have to do with it.

Yea I agree if they detonate they will break but I think even the later ones still have cast pistons. I am not keen on pistons laying on their sides with oil control. Burning oil causes very severe detonation. I have the bin file from Mines EVO tune and buy are they asking for some serious engine damage with the amount of timing they put in.

If you watch hill climb videos on youtube, the cars that only ever grenade all seem to be evos

vlad01 wrote:If you watch hill climb videos on youtube, the cars that only ever grenade all seem to be evos

So haven't they evolved to be stronger?