Discovery I Talk about the Land Rover Discovery Series I within.

p0130

Thread Tools
 
Search this Thread
 
Old Jan 20, 2014 | 07:25 PM
  #1  
TOM R's Avatar
Thread Starter
|
Baja
Joined: Mar 2009
Posts: 5,736
Likes: 230
From: south n.j. and ne va.
Default p0130

I lost the evap codes and gained an O2 sensor code, cleared and came back any ideas where to start? I have replaced the upstreams previously guessing within last 20k miles with new ntk,

Could I have killed the sensor running stupid rich when I had the TPS problem? I could smell how rich it was

I tried search and seems lots of d2 threads on the P0130
 
Reply
Old Jan 20, 2014 | 09:11 PM
  #2  
ihscouts's Avatar
Camel Trophy
Joined: Jan 2010
Posts: 4,245
Likes: 402
From: Traverse City MI
Default

Oxygen Sensor Circuit Malfunction (Period) Bank 1 Sensor 1 P0130

This one is tough to diagnose without an analyzer. There are four tests the O2's are checked by and a signal check and it's hard to pinpoint which one it's failing at without a T4 or Autologic on hand.

Coolant is the number one reason for O2 failure.

You can try to smoke it clean with a propane torch. Google it. The method is pretty simple. You heat it slowly until it glows and then cool it slowly that way it doesn't shatter. Doesn't always work....... so have another ready to plunk into the pipe.
 
Reply
Old Jan 20, 2014 | 09:39 PM
  #3  
TOM R's Avatar
Thread Starter
|
Baja
Joined: Mar 2009
Posts: 5,736
Likes: 230
From: south n.j. and ne va.
Default

Been a little while since the hg job, any way over fueling caused the problem?
 
Reply
Old Jan 20, 2014 | 10:16 PM
  #4  
ihscouts's Avatar
Camel Trophy
Joined: Jan 2010
Posts: 4,245
Likes: 402
From: Traverse City MI
Default

Nothing says "too much fuel" caused this code. It says it's not passing signal check and tests within spec'd time limits after two attempts. So I leave it up to you how it became roasted, it's roasted is all I read.

Is the fueling going into closed loop on your UG?
 

Last edited by ihscouts; Jan 20, 2014 at 10:23 PM.
Reply
Old Jan 21, 2014 | 08:48 AM
  #5  
TOM R's Avatar
Thread Starter
|
Baja
Joined: Mar 2009
Posts: 5,736
Likes: 230
From: south n.j. and ne va.
Default

Yes it is going closed loop, I cleared the code again to see if it comes back, guess if it does easiest to just buy another sensor
 
Reply
Old Jan 21, 2014 | 11:08 AM
  #6  
ihscouts's Avatar
Camel Trophy
Joined: Jan 2010
Posts: 4,245
Likes: 402
From: Traverse City MI
Default

Hmmm. That rules out one test.
 
Reply
Old Jan 21, 2014 | 05:38 PM
  #7  
TOM R's Avatar
Thread Starter
|
Baja
Joined: Mar 2009
Posts: 5,736
Likes: 230
From: south n.j. and ne va.
Default

I cleared it this morning and drove around all day no code maybe it self corrected? I did also change to a factory stat today cause I could not get temp over 158* took out the 180 stat it had failed in the open position so I am now again running at proper temp
 
Reply
Old Jan 23, 2014 | 08:59 PM
  #8  
TOM R's Avatar
Thread Starter
|
Baja
Joined: Mar 2009
Posts: 5,736
Likes: 230
From: south n.j. and ne va.
Default

Well came back today so what cha think ihscouts?
 
Reply
Old Jan 24, 2014 | 11:33 AM
  #9  
WaltNYC's Avatar
TReK
Joined: Mar 2010
Posts: 2,764
Likes: 617
From: NYC
Default

could it be something as simple as a bad wiring connection? How about some dielectric grease on the connector?
 
Reply
Old Jan 24, 2014 | 02:01 PM
  #10  
ihscouts's Avatar
Camel Trophy
Joined: Jan 2010
Posts: 4,245
Likes: 402
From: Traverse City MI
Default

Originally Posted by WaltNYC
could it be something as simple as a bad wiring connection? How about some dielectric grease on the connector?
It's not an electrical connection fault per se', if it was it would signify that in the code.

Tom, I know what I'd do, hit it with a propane torch, try it for a day or two and then decide. That's me.
 
Reply



All times are GMT -5. The time now is 05:25 AM.