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-s...storation.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.

[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/0BxQz...it?usp=sharing

StockECU
https://docs.google.com/file/d/0BxQz...it?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?