Notices
Scion tC 1G Forced Induction Turbo and supercharger applications...

O2 sensor problem after going turbo

Thread Tools
 
Search this Thread
 
Old 09-28-2013, 10:24 PM
  #1  
Senior Member
10 Year Member
5 Year Member
SL Member
Thread Starter
iTrader: (1)
 
vi3tb0i09's Avatar
 
Join Date: Sep 2010
Location: https://t.me/pump_upp
Posts: 164
Default O2 sensor problem after going turbo

So finally got the chance to install my turbo kit for from ptuning but unfortunately I am running into some problems. I am getting a p0138, code O2 Oxygen Sensor Circuit High Voltage (Bank1, Sensor2). I already tested my o2 sensor which is located on my spipe by measuring the resistance and it was around 15ohms which is within spec. There is a antifouler on it because of the cat delete but I don't think thats the reason why this code is on. Does anyone have any idea? This was all after a professional tune at Church Automotive located in SoCal. I called them they said its either the o2 sensor or my aem fic going bad... and not the tune. I don't know about that but I'm still going to stop by to have them check it out. Any help would be greatly appreciated.

BTW, I did replace my wideband o2 sensor (sensor 1) because it died during the install of the turbo so i don't know if that is effecting anything. I remember reading somewhere that you should replace o2 sensors in pairs? since the new o2 would have better readings. But I didn't find it necessary since the secondary o2 only sees if the cat is working properly.
vi3tb0i09 is offline  
Old 09-30-2013, 06:05 PM
  #2  
Senior Member
10 Year Member
5 Year Member
SL Member
iTrader: (4)
 
Drey's Avatar
 
Join Date: Sep 2007
Location: Baytown, TX
Posts: 442
Default

Yeah I have exact same problem with my kit, ptuning as well. I replaced secondary o2 sensor and it didn't do a thing. That got something to do with fic I think.
Drey is offline  
Old 09-30-2013, 06:49 PM
  #3  
Senior Member
10 Year Member
5 Year Member
SL Member
Thread Starter
iTrader: (1)
 
vi3tb0i09's Avatar
 
Join Date: Sep 2010
Location: https://t.me/pump_upp
Posts: 164
Default

Are you running an antifouler? I checked my o2 resistance and its within spec. But my obd2 scanner read that there was no voltage coming from the second o2. I just abought a replacement o2. About it install it and hope it fixes it.
vi3tb0i09 is offline  
Old 10-01-2013, 02:38 AM
  #4  
Senior Member
10 Year Member
5 Year Member
SL Member
iTrader: (4)
 
Drey's Avatar
 
Join Date: Sep 2007
Location: Baytown, TX
Posts: 442
Default

Yeah I have antifouler and still. I've been just reseting codes every 2 days since I got boosted since June. I didn't get oem toyota replacement sensor tho and it actually caused even more codes, like sensor slow response, crank position and something else. LMK if it works for you, I might try new oem sensor.
Drey is offline  
Old 10-01-2013, 12:58 PM
  #5  
Senior Member
10 Year Member
5 Year Member
SL Member
iTrader: (4)
 
Drey's Avatar
 
Join Date: Sep 2007
Location: Baytown, TX
Posts: 442
Default

Or it could be resistors in fic harness? https://www.scionlife.com/forums/sho...d.php?t=177011
Drey is offline  
Old 10-03-2013, 05:42 PM
  #6  
Senior Member
10 Year Member
5 Year Member
SL Member
Thread Starter
iTrader: (1)
 
vi3tb0i09's Avatar
 
Join Date: Sep 2010
Location: https://t.me/pump_upp
Posts: 164
Default

So I installed a new Bosch secondary sensor and the code went away! I drove it for about 500miles now and everything is running smooth. I am finally enjoying my car now. I am running both Bosch o2 sensors for my wideband and my narrow. With a antifouler on the narrow. My FIC does have the resistor mod but that only helps you with stuttering and sputtering problems while WOT. Don't think it fix any cel. I definitely suggest you to get oem or some nice Bosch sensors. They work really well.
vi3tb0i09 is offline  
Old 10-03-2013, 05:44 PM
  #7  
Senior Member
10 Year Member
5 Year Member
SL Member
Thread Starter
iTrader: (1)
 
vi3tb0i09's Avatar
 
Join Date: Sep 2010
Location: https://t.me/pump_upp
Posts: 164
Default

Btw, I don't think my old secondary o2 went bad. I think its because I swapped in a new o2 for the primary and kept the old which probably caused the code. I think you should always switch out both o2 at the same time since the second o2 goes off the primary for readings.
vi3tb0i09 is offline  
Old 10-04-2013, 05:02 PM
  #8  
Senior Member
10 Year Member
5 Year Member
SL Member
iTrader: (4)
 
Drey's Avatar
 
Join Date: Sep 2007
Location: Baytown, TX
Posts: 442
Default

Well that's good to hear that it worked for you. I just returned ebay sensor back and I guess Ill try replacing with both Bosch sensors then. My oxygen sensors are still original with 93k miles, ran with out cat for last 2-3 years, I know its a matter of a time before they go out.
Drey is offline  
Old 10-09-2013, 02:22 AM
  #9  
Senior Member
5 Year Member
SL Member
 
That_Kid_Ju's Avatar
 
Join Date: May 2011
Location: Northern NJ
Posts: 353
Default

I have the same problem after my tune @ ptuning. Running the Dezod kit with the FIC. I think it's tune related because when switching to my old map, CEL never comes on. When I run the ptuning map, CEL after 30-40 miles. The ptuning map (11 psi) is a bit richer than the other custom map, maybe that's why. Probably somewhere in the fuel and/or o2 maps that triggers it.
That_Kid_Ju is offline  
Old 10-09-2013, 05:50 AM
  #10  
Senior Member
10 Year Member
5 Year Member
SL Member
Thread Starter
iTrader: (1)
 
vi3tb0i09's Avatar
 
Join Date: Sep 2010
Location: https://t.me/pump_upp
Posts: 164
Default

What kind of code are you getting? I don't think its the tune. For my situation, it was just that point in time where my o2 sensors just needed replacing. It might also be your FIC since those are also known to go bad.
vi3tb0i09 is offline  
Old 10-09-2013, 04:05 PM
  #11  
Banned
10 Year Member
5 Year Member
Scionetics
KAD
SL Member
 
paul_dezod's Avatar
 
Join Date: Oct 2005
Location: Western NY
Posts: 11,936
Default

Feel free to send me a copy of the calibration and I can take a quick look to see if anything jumps out at me.
paul_dezod is offline  
Old 10-09-2013, 04:10 PM
  #12  
Senior Member
5 Year Member
SL Member
 
That_Kid_Ju's Avatar
 
Join Date: May 2011
Location: Northern NJ
Posts: 353
Default

P0138. Pretty convinced its tune related cuz it doesn't happen when I run my old tune. Car runs fine, its just annoying. Already passed inspection (with turbo and catted dp) so it doesn't matter till 2015, if I even still have the car.
That_Kid_Ju is offline  
Old 10-09-2013, 04:39 PM
  #13  
Banned
10 Year Member
5 Year Member
Scionetics
KAD
SL Member
 
paul_dezod's Avatar
 
Join Date: Oct 2005
Location: Western NY
Posts: 11,936
Default

Originally Posted by That_Kid_Ju
P0138. Pretty convinced its tune related cuz it doesn't happen when I run my old tune. Car runs fine, its just annoying. Already passed inspection (with turbo and catted dp) so it doesn't matter till 2015, if I even still have the car.



Like I said, fire over the cals. Let me compare and mod. I have an idea as to what is wrong already
paul_dezod is offline  
Old 10-09-2013, 07:28 PM
  #14  
Senior Member
10 Year Member
5 Year Member
SL Member
Thread Starter
iTrader: (1)
 
vi3tb0i09's Avatar
 
Join Date: Sep 2010
Location: https://t.me/pump_upp
Posts: 164
Default

I got a quick question for you Paul. The reason why I thought it was my o2 sensor in the first place was because i was getting no voltage reading using a scanner. Thats why I went ahead to replace it but the odd thing is, after replacing it, there is still no voltage reading from the second o2. However the code did go away. Well at least for now that is. So my question is could it be the tune? Before my tune, running base map I didn't get any codes. But after the tune, i started to get the same code.
vi3tb0i09 is offline  
Old 10-09-2013, 07:43 PM
  #15  
Banned
10 Year Member
5 Year Member
Scionetics
KAD
SL Member
 
paul_dezod's Avatar
 
Join Date: Oct 2005
Location: Western NY
Posts: 11,936
Default

Originally Posted by vi3tb0i09
I got a quick question for you Paul. The reason why I thought it was my o2 sensor in the first place was because i was getting no voltage reading using a scanner. Thats why I went ahead to replace it but the odd thing is, after replacing it, there is still no voltage reading from the second o2. However the code did go away. Well at least for now that is. So my question is could it be the tune? Before my tune, running base map I didn't get any codes. But after the tune, i started to get the same code.
Sounds tune related. If the O2 map is off, it can cause a multitude of issues like this.
paul_dezod is offline  
Old 10-09-2013, 07:53 PM
  #16  
Senior Member
10 Year Member
5 Year Member
SL Member
Thread Starter
iTrader: (1)
 
vi3tb0i09's Avatar
 
Join Date: Sep 2010
Location: https://t.me/pump_upp
Posts: 164
Default

Would it be ok for me to send you my cal for you to take a look at as well?
vi3tb0i09 is offline  
Old 10-09-2013, 08:08 PM
  #17  
Banned
10 Year Member
5 Year Member
Scionetics
KAD
SL Member
 
paul_dezod's Avatar
 
Join Date: Oct 2005
Location: Western NY
Posts: 11,936
Default

Originally Posted by vi3tb0i09
Would it be ok for me to send you my cal for you to take a look at as well?
Sure. Send before and after.
paul_dezod is offline  
Old 10-11-2013, 01:50 AM
  #18  
Senior Member
10 Year Member
5 Year Member
SL Member
Thread Starter
iTrader: (1)
 
vi3tb0i09's Avatar
 
Join Date: Sep 2010
Location: https://t.me/pump_upp
Posts: 164
Default

@Paul I sent you an email of the before and after cal. Please let me know what you think! Thanks again!
vi3tb0i09 is offline  
Old 10-12-2013, 09:03 PM
  #19  
Senior Member
10 Year Member
5 Year Member
SL Member
iTrader: (4)
 
Drey's Avatar
 
Join Date: Sep 2007
Location: Baytown, TX
Posts: 442
Default

I replaced both of old sensors with brand new Bosch sensors last week, paid $280 and it did fix my P0138 and P0136 codes. I guess it wasnt tune related in my case. Still got that P0335 crank position sensor code popping sometimes.
Drey is offline  
Old 10-13-2013, 06:24 AM
  #20  
Senior Member
10 Year Member
5 Year Member
SL Member
Thread Starter
iTrader: (1)
 
vi3tb0i09's Avatar
 
Join Date: Sep 2010
Location: https://t.me/pump_upp
Posts: 164
Default

Good to hear that! Well that P0335 code isn't o2 related. I think your crack position sensor is just going bad. Shouldn't be too hard of a fix as well.
vi3tb0i09 is offline  


Quick Reply: O2 sensor problem after going turbo



All times are GMT. The time now is 04:11 AM.