Flash ECU O2 Sensor Issue

[Jesters Deadd]

You don't use the mits adapter from tactrix, just plug the module into the obd port and the stereo connector from pin 100 into the module.

He is running one of my 94-97 PNP ecus.
The information you gave him is for a 98/99 pin out only.

[Jesters Deadd]

That information conflicts with what is on this site for the '94-'97: Chromed ECU | 94-97 Plug and Play Flash Ecu Installation

Which is why I have not done anything as far as flashing is concerned, because of fear of bricking the ECU.

FYi the fastest way to get answers on my ecus is to email me .

[mb3000]

Awesome, I'll be installing it here in the next couple minutes. I appreciate the support!

[mb3000]

Alright, got the yellow flash wire installed, wired in my wideband, but the interior back together and did a "test flash" and it failed. Here is what I am seeing:

[22:27:21.968] EcuFlash Version 1.44.3721
[22:27:21.968] OS Version Windows XP
[22:27:21.968] Qt Version 4.8.0
[22:27:21.968] 63 memory models read.
[22:27:21.968] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata
[22:27:22.187] 612 ROM metadata models scanned.
[22:27:22.187] checksum module "subarudbw" loaded.
[22:27:22.187] checksum module "mitsucan" loaded.
[22:27:22.187] checksum module "mitsuh8" loaded.
[22:27:22.187] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[22:27:22.187] patch module "Mitsu CAN RAM Parameter Logging" loaded.
[22:27:22.187] flashing tool "wrx02" loaded.
[22:27:22.187] flashing tool "wrx04" loaded.
[22:27:22.187] flashing tool "sti04" loaded.
[22:27:22.187] flashing tool "sti05" loaded.
[22:27:22.187] flashing tool "mitsukernel" loaded.
[22:27:22.187] flashing tool "mitsukernelocp" loaded.
[22:27:22.187] flashing tool "mitsubootloader" loaded.
[22:27:22.187] flashing tool "shbootmode" loaded.
[22:27:22.187] flashing tool "shaudmode" loaded.
[22:27:22.187] flashing tool "subarucan" loaded.
[22:27:22.187] flashing tool "subarucand" loaded.
[22:27:22.203] flashing tool "mitsucan" loaded.
[22:27:22.203] error loading FTD2XX.DLL
[22:27:22.218] J2534 API Version: 04.04
[22:27:22.218] J2534 DLL Version: 1.00.3721 Jan 9 2013 17:24:59
[22:27:22.218] Device Firmware Version: 1.12.3688
[22:27:22.218] Device Serial Number: TAYR8pPr
[22:27:22.218] interface close
[22:27:22.250] J2534 API Version: 04.04
[22:27:22.250] J2534 DLL Version: 1.00.3721 Jan 9 2013 17:24:59
[22:27:22.250] Device Firmware Version: 1.12.3688
[22:27:22.250] Device Serial Number: TAYR8pPr
[22:27:22.250] interface close
[22:27:22.281] J2534 API Version: 04.04
[22:27:22.281] J2534 DLL Version: 1.00.3721 Jan 9 2013 17:24:59
[22:27:22.281] Device Firmware Version: 1.12.3688
[22:27:22.281] Device Serial Number: TAYR8pPr
[22:27:22.281] interface close
[22:29:27.578] 131072 byte image read.
[22:29:27.578] using metadata XML ID 23862006 from file C:/Program Files/OpenECU/EcuFlash/rommetadata/mitsubishi/23862006.xml
[22:29:32.093] J2534 API Version: 04.04
[22:29:32.093] J2534 DLL Version: 1.00.3721 Jan 9 2013 17:24:59
[22:29:32.093] Device Firmware Version: 1.12.3688
[22:29:32.093] Device Serial Number: TAYR8pPr
[22:29:40.734] sending init sequence 2
[22:29:42.750] interface close


Connects to Evoscan 2.9 just fine.

Guessing it has something to do with

error loading FTD2XX.DLL



Any ideas?

[mb3000]

Edit: FTD2XX.DLL fixed. Downloaded the dll and put it into System32. Still not working.

[mb3000]

Got the issue sorted out. Future reference, the flash wire was pulled out of the ECU pin slightly when I was putting back the interior trim.

Disabled the peripheries, added a little bit to the VE table. Took it out for a drive and did the same 5k rpm bucking. O2 values do not seem to be registering. Here is the datalog, from initial start to the single 2nd gear pull:

https://docs.google.com/file/d/0BxQz...it?usp=sharing

One CEL displayed via Evoscan 2.9, P0105 Barometer Pressure circuit.

[mb3000]

After reviewing the logs it seems that the O2 sensors "catch on" somewhere throughout the log, however the first O2 drops down to 0.0V when the TPS is 99.xx, RPM is 5187. To make this easy to find, it is row "890". Wideband also goes way lean around the same area.

Note that the factory ecu did not have any of these problems. No mechanical changes were made aside from swapping in the FECU, setting the peripheries, and modifying the VE table.

[Greg E]

Disable/raise fuel cut
Verify your fuel pump goes into "hi speed mode" (you REALLY SHOULD just Hotwire it)
Turn the boost down.
Change your fuel filter and clean your injectors.

[mb3000]

Underhood fuel pump relay is bypassed.
Running wastegate boost
Fuel filter was changed 30 miles ago. I have freshly cleaned Evo 560cc's sitting on the shelf with new seals ready to go in, after this issue is fixed. Also have a Walbro 255 and hotwire kit sitting on the shelf, waiting for the issue to be resolved.


Will disable fuel cut and report back.

[mb3000]

Set all values in "Fuel Cut (double mod)" to 638. No change.

https://docs.google.com/spreadsheet/...EE&usp=sharing