Flash ECU O2 Sensor Issue

[mb3000]

I was under the impression that for a stock (MAF, injectors, etc) car could simply plug up the FECU and drive without any use of a laptop or messing with the ECU in any way, however when I did just this I got the same batch of codes as this 3si member:


Pulled the codes with the blackstealth logger. My car (Canada, FED emissions) Has only 2 heated O2 sensors, and the 99 flash looks for 4. Also, my EVAP system purge solenoid is goin nuts on/off when it never did before, so I unplugged it and im getting CEL for that too. I need to ask about 3000gt file for ECUflash, as mine is old and I think the brainy boys have more things figured out and named in ECUflash. Im also getting strange trims... the logger reads a low/mid/high, and my low trims are at 50 at idle and coasting, at 120 on acceleration. Not sure what that means, but my o2's are coding like crazy, when there were no codes at stock. Here are the codes I have read so far :

P0155 - o2 heater circuit malfunction Bank 2 sensor 1 (need to disable, not on my 94)
P0156 - o2 circuit malfunction Bank 2 sensor 2 (need to disable, not on my 94)
P0161 - o2 heater circuit malfunction Bank 2 sensor 2 (need to disable, not on my 94)
P0135 - o2 heater circuit malfunction Bank 1 sensor 1 (did not throw a code using stock ECU)
P0136 - o2 circuit malfunction Bank 1 sensor 2 (did not throw a code using stock ECU)
P0141 - o2 heater circuit malfunction Bank 1 sensor 2 (did not throw a code using stock ECU)
P0443 - EVAP purge control valve circuit (unplugged, solonoid was going nuts on/off, didnt do that with my stock ECU)
P0446 - EVAP vent control circuit malfunction (related to unplugging the solonoid also?)
P1104 - Turbo wastegate solonoid - this is removed from the car, I am using an EBS. Need to turn off in the flash if I can.

There are a few things I have yet to learn about the differences between the 99 flash file I am using and the 94 car Im using it in. Any insight would be greatly appreciated! To be continued...



IIRC you can go through and disable the CEL's for emissions and whatnot, that's not what I'm concerned with. When I logged via Evoscan 2.6, the O2 values were both 0.0xxx and not changing. The engine ran very poorly, any sudden increase in throttle lead to bucking/misfiring which would not allow the engine to increase RPM. Nomatter what, and WOT the engine would buck in the same fashion at 5k RPM's.

To troubleshoot, I installed my factory '97 ECU and the O2 value for the front O2 sensor registered, and the aforementioned driving conditions were not present. The engine ran beautifully.


Any ideas?

[Greg E]

So the o2s don't cycle with the flash ECU and only one cycles with the stock ECU. Is this what you're saying?

Could you do me a favor and log the car (using my EVOScan file) with both the stock ECU and the flash ECU installed. I need to see the following from both setups:

RPM
TPS
Load
Airflow
Battery voltage
Coolant temp
ISC counts
Front/rear o2
Front/rear low fuel trim

One other thing I need is a list if absolutely every mod and maintenance item done to your car.

[Jimvr4]

Subscribed

[Greg E]

Also whomever told you that you could just plug in the ECU without doing anything is a liar.

[mb3000]

Nobody to blame for the PnP assumption except myself. What is the best way to host the logs? Google docs? Not used to working with Evoscan.

Also, engine is pretty much refreshed back to stock at this point, all aforementioned testing was done on wastegate boost. Only pertinent mod would probably be the pair of 15G's.

More info in the build thread: http://www.3sgto.org/turbo-engines-systems/12964-mbs-generic-3-s-build-restoration.html

[mb3000]

Just about as good as I can do on the logs (as far as the values logged, can post raw data if necessary) until I have access to the car again this weekend, figured it would be easiest to see it as I saw it.

http://i928.photobucket.com/albums/ad128/mb3000gt_photos/th_ECUDAtalog_zpsb49fae9c.jpg (http://i928.photobucket.com/albums/ad128/mb3000gt_photos/ECUDAtalog_zpsb49fae9c.mp4)

[Greg E]

Oh so the car isn't stock. Just has stock MAF and injectors.

Google docs works.

[mb3000]

Here are the links:

FECU
https://docs.google.com/file/d/0BxQzRWKUZMvVRkw3WG5tZUJiNDg/edit?usp=sharing

StockECU
https://docs.google.com/file/d/0BxQzRWKUZMvVODJSQnh4OS1VdDQ/edit?usp=sharing

[Greg E]

Alright first issue: you're not using my evoscan file. Download evoscan 2.9 and set it up using the XML I provided for chrome.

Couple more questions:

Where did you get your flash ECU and adaptor harness?
What version of chrome are you running?

[mb3000]

ECU purchased "new" from Jester, no adapter harness. ;94-97 models. ECU says pre-flashed with Chrome 2.0 IIRC. Logged using the Tactrix 2.0 cable.

I will have to datalog using your file and 2.9 on the weekend. May I ask, what is the difference in respect to datalogging between your version and a regular old evoscan user?

[Greg E]

Lots of things. For one you can read all 4 o2s and the file that comes with evoscan you can only log the rear.

[mb3000]

So basically it was designed for the 3/s, and is the best version to use by far?

[Greg E]

I designed it to work in conjunction with chrome but many loggable features work with the earlier 3/S (note: not all features work).

[CoreyB]

Sorry to interrupt, Greg, but could I get your setup file for 2.9? I would love to be able to see my front O2.

[mb3000]

As far as I know you have to buy it from http://chromedecu.org for $20.

[Greg E]

Shoot me a donation and ill email it to you tonight.

PayPal: nonstopmix@gmail.com

[CoreyB]

Ok, thanks a lot!!!

[mb3000]

Also whomever told you that you could just plug in the ECU without doing anything is a liar.

Getting back to this, and getting ready for the weekend, what is necessary to do for a vehicle with stock fuel system, maf, etc.. to run the ECU?

[Greg E]

Start with setting the peripheries and we will work from there.

[mb3000]

I was looking at one of your threads, and it seems that I need to disable peripheries 15, 14, 13, 11, 10, 9, 3 and 1, as well as 3 & 11 as I am not running the secondary O2 sensors. Maybe play around with the VE table to compensate for one thing or another. Anything that I'm missing for the stock fuel/maf/ & wastegate boost?

[Greg E]

You got it.

Still need to see that log to verify something's.

[mb3000]

Sure, no problem. I'll have the comparison posted this Saturday.

[CoreyB]

Greg, I got the setup file, thank you. Now I am not sure how to use it though. I have it saved in "saved settings" and I am quite sure that is wrong. Also the setup file says its for MUTII and I use the MMC 1G 16 pin connection. I am pretty new to logging so any help would be appreciated.

Sorry for the mini hijack MB3000.

[Greg E]

First post of this thread goes thru how to set it up.

http://www.3sgto.org/tuning-engine-electronics-ecu-discussions/10775-how-tune-your-3-s-using-chrome-flash-ecu.html

[CoreyB]

Thanks buddy.

[mb3000]

Couple of questions that I have that I haven't seen answered anywhere else, the actual flashing of the ECU. I have the Tactrix 2.0 cable, as well as their "Mitsubishi Re-flash Connector" and the "Flash plug & lead wire" that was included with my Jester '94-97 ECU purchase. Obviously the Tactrix plugs into the OBD2 port, but what about the flash connector(s)?

[mb3000]

I think I answered my own question. Jack plugs into the Tactrix unit which plugs into the "Mitsubishi flash" adapter that came with it, which plugs into the Jester connector which is wired directly into the ECU via Pin 57. This sound right?

[mb3000]

Greg, would you like a datalog of the FECU before or after being flashed with the disable peripheries, VE table, etc..

[Greg E]

After.

[mb3000]

Before I go flashing the ECU, is what I posted in post #27 correct?

[kywhitelightning]

Don't forget to make sure you have good battery power before flashing. Battery charger is prefered.

Jeff

[mb3000]

Going to have the charger hooked up during flashing, however there will be no flashing until I know how to set it up.

[LeRoyDL]

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.

[mb3000]

That information conflicts with what is on this site for the '94-'97: Chromed ECU | 94-97 Plug and Play Flash Ecu Installation (http://chromedecu.org/?p=1021)

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

[Greg E]

That information conflicts with what is on this site for the '94-'97: Chromed ECU | 94-97 Plug and Play Flash Ecu Installation (http://chromedecu.org/?p=1021)

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

*sigh*

You do not NEED the mitsu reflash connector. I think the reason Adam sells that piece is so you can adapt your 94-97 car to have the convenient plug setup like the 98/99 vehicles which use the mitsu reflash connector. It's a clean setup and nothing more. All that cable does is attach pin 100 to the tactrix cable so a 16V source can get to the chip. There is nothing in that connector besides wire. Be it direct or another plug, it goes to the same place and does nothing.

If you brick your ECU, it won't be because of this.

[mb3000]

So, unnessesary or not, I can install and use the plug the way it is shown on the website? Just want to double check. Already have the Tactrix male plug.

[CoopKill]

I use it, but apparently is unnecessary. Not had any issues flashing with a charger connected at all times.

[Greg E]

I use it, but apparently is unnecessary. Not had any issues flashing with a charger connected at all times.

It's a cleaner setup vs what Brett sells with the adaptor harness (not meant to bash, both function perfectly. Adams just looks like stock).

[mb3000]

Awesome. Thanks again Greg! I'll work on it this weekend and get that log hosted.

[Jesters Deadd]

I think I answered my own question. Jack plugs into the Tactrix unit which plugs into the "Mitsubishi flash" adapter that came with it, which plugs into the Jester connector which is wired directly into the ECU via Pin 57. This sound right?

YEs this is correct.

[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 (http://chromedecu.org/?p=1021)

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/0BxQzRWKUZMvVTWllY3BTQWhseHc/edit?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/ccc?key=0AhQzRWKUZMvVdEEzWmZaMHZ0N1A5WHA1MnUwSm1Rd EE&usp=sharing

[Greg E]

That's odd. How come your Baro sensor shows 0??

Does that sensor come alive when the stock ECU is plugged in?

[mb3000]

Re-installed the factory ecu. Pulls clean, hard, and to redline. Nothing was touched under the hood except the battery. Very discouraged at this point.

Logged using Evoscan 2.9, using the standard "EFI" instead of the Chrome specific "3000GT EFI" Here's the log.

https://docs.google.com/spreadsheet/ccc?key=0AhQzRWKUZMvVdG9lRnZyVjZYSlNIZXd4TklyNFZqY UE&usp=sharing

[Greg E]

Use my EVOScan file and take another log.

There is definitely something wrong with the baro sensor in your MAF.

[mb3000]

Will do. Should have it in about 15 minutes.

[mb3000]

Here's the new log: https://docs.google.com/spreadsheet/ccc?key=0AhQzRWKUZMvVdGROYTRhUE92TG80QkdRTjVPQWJyO Hc&usp=sharing

I've got a Montero 482 MAF and adapter harness ready to go, could pop that in w/ the fECU, make necessary adjustments to the fECU and give it a shot?

[Greg E]

Seems like you might have a bum ECU man.

Let me look over your logs one more time when I get home as browsing these files on my phone is difficult.

If you could do one more thing for me. Put the flash ECU back in and do a long (warm) idle log. No need to go WOT. I just want to verify the narrowbands cycle in closed loop.

[mb3000]

Alright, no problem. Should have it posted up shortly.

[mb3000]

Here's the fECU installed, warm idle: https://docs.google.com/spreadsheet/ccc?key=0AhQzRWKUZMvVdGxxek9LSVdRQ05qZ0hRblg1VEZpb mc&usp=sharing

[Greg E]

Shoot Adam a message. :(

apape10@yahoo.com

[mb3000]

Message sent. Will update thread when/if necessary.

[mb3000]

Just wanted to thank you again Greg for all of your help.

Was so disappointed yesterday that I forgot my manners. Sending ECU back this Mon. to get serviced. Don't know when I'll be able to work on the car again, looks like around Thanksgiving time.

[Greg E]

Nah man I'm sorry you the thing didn't work out of the box for you. :(

[mb3000]

Just an update if you (or anyone else) is curious.

Adam was very professional throughout our conversation back & fourth about the ECU. He checked out the ECU and said it was an earlier model, that had overspray on the O2 pin jumpers before he could test for that condition. A new unit should be shipping out early this week.

Hopefully I don't have any problems the second time around :bigthumb:

[Greg E]

Awesome!!! I'm glad Adam was able to help you!!

[mb3000]

Greg, hate to bother you with another question.

What is the most important power source for the ECU during flashing? I would like to wire up an AEM Voltmeter Gauge to that wire so I can check the volts more easily.

[Greg E]

The flash wire is the wire you want constant/steady voltage into. I'm not sure putting a gauge inline to that wire is a good idea. That gauge will draw current.

[mb3000]

Now that you mention it, that sounds like a recipe for a bricked ECU! I guess I'll just measure battery voltage instead (need to fill the last opening in my gauge pod :lol:).

[99 vr4]

FYI, you should measure the voltage coming from IG1 to the ECU. Pin 82 on the 1G / 2G ECU plug. This is the large plug on the right, bottom row, first pin on the left (looking from the wire side of the plug). IG1 supplies power to the ECU via the ignition switch, telling the ECU to turn on the MFI relay. During flashing, the MFI relay is turned off by the flash routine. This is why when you flash a running car the car shuts off to flash.

[CoopKill]

Thinking I may have a similar problem with the o2's. Will update my flash thread.