economy tuning
Set it to 14.7 and see if you still get the code. You're AFR's are probably fluctuating because your ECU isn't seeing ANY front O2 signal at all and is running straight off the open loop fuel map as a precaution. Do you have evoscan? Log the front O2 sensor signal and see what it looks like. It should fluctuate from .1 to .9 volts roughly.
I will try that and I have also e-mailing Zeitronix lot of logs 1- with blue & purple wires connected 2- purple to ecu 3- purple tapped to the ecu. I think my stock O2 sensor is bad!! may be because the location I placed it in O2 housing of my new turbo and getting too hot, not sure. But even if the stock O2 sensor went bad it should not matter because the ZT2 will be connected to the ECU to feed it the signal not the stock O2 right???????????
It could be bad because you connected its output wire directly with the ZT2's simulated output wire also, which you NEVER should do! The stock NB O2 sensor can be MUCH closer to a turbo than a WB O2 sensor can. The stock sensor can literally be inches from the turbo outlet (which most stock loactions are) but a WB O2 sensor should be a MINIMUM of at least 16" away from the turbo outlet.
Like you said, even if the stock O2 sensor output signal was bad, it wouldn't matter because you're using the simulated output wire from the ZT2. That is if you didn't damage the ZT2's simulated output circuit when it was connected to the output of the stock O2 sensor. Its probably fine but with the issue you are having, it might have been damaged when you wired it incorrectly the first time.
Also, why do you have the blue wire connected to the ECU? What user input were you logging with the ZT2?
Like you said, even if the stock O2 sensor output signal was bad, it wouldn't matter because you're using the simulated output wire from the ZT2. That is if you didn't damage the ZT2's simulated output circuit when it was connected to the output of the stock O2 sensor. Its probably fine but with the issue you are having, it might have been damaged when you wired it incorrectly the first time.
Also, why do you have the blue wire connected to the ECU? What user input were you logging with the ZT2?
Oh jeeze,lol. Sorry, I was mixing up your posts with Adamantium's posts. My bad.
Can you log your front O2 sensor signal at idle for like 30 seconds (car warmed up) with the simulated output wire connected to pin 71 and post the log or email it to me?
Can you log your front O2 sensor signal at idle for like 30 seconds (car warmed up) with the simulated output wire connected to pin 71 and post the log or email it to me?
Also, why do you have the blue wire connected to the ECU? What user input were you logging with the ZT2? I did as I was asked by zeitonix as they helping me with it he said to tap the blue wire in the stock O2 sensor as he want to see my stock O2 signal on the Zt-2 user input i a log.
by default mistulogger's logs get saved it the location where the mitsulogger application is saved. you can also see the log path when you open mitsulogger. it will be on the top most part of the window. you can also change it by clicking on the browse button on the upper right.
I have a zeitronix and i made use of the narrowband simulator just like in the diagram. but i am getting P0133. slow response. for the people who are using this feature of zeitronix has anyone encountered this? I was thinking maybe the code is caused because the wideband might take a bit longer to warm up. or maybe the wideband positioning. ryt now i have my wideband on my test pipe.
help please.
thanks in advance.
help please.
thanks in advance.
Hmm, not sure. I have no codes with mine. The car runs in open loop for the first 30 seconds (at least) on most cars anyways, which is the time the WB takes to warm up so i doubt thats an issue. Maybe because of the distance from the engine perhaps???
Last edited by Jack_of_Trades; Apr 28, 2008 at 03:04 PM.




