Discovery II Talk about the Land Rover Discovery II within.
Sponsored by:
Sponsored by:

Misfire only on drivers side

Thread Tools
 
Search this Thread
 
Old Sep 14, 2013 | 11:35 AM
  #11  
jafir's Avatar
Super Moderator
Joined: Nov 2009
Posts: 5,847
Likes: 106
From: Arkansas
Default

I've replied. My 1999 had it and it was definitely either the O2 sensors or exhaust leak. I pulled the y pipe to replace a stubborn front sensor and while it was out I noticed that the cat was split. We welded it back up, put two new front sensors in and the single bank misfire codes went away. It was more likely the o2 sensors than the exhaust leak because the sensors were before the split.
 

Last edited by jafir; Sep 14, 2013 at 12:18 PM.
Reply
Old Sep 14, 2013 | 12:14 PM
  #12  
NWROVERS's Avatar
Thread Starter
|
Drifting
Joined: May 2012
Posts: 43
Likes: 1
From: Bellingham, Wa
Default

Ive been throwing around the cat fix in my head. I wounder if it would be worth while to cut the old cats out and weld an universal fit one in place. if i go the universal route, does anyone know what size tube they are?
 
Reply
Old Sep 14, 2013 | 12:43 PM
  #13  
Disco Mike's Avatar
Administrator
Joined: Apr 2006
Posts: 25,707
Likes: 107
From: Denver, Colorado
Default

02's even if they have totally failed should not cause a misfire, you would run full rich or lean and have codes indicating that.
 
Reply
Old Sep 14, 2013 | 01:02 PM
  #14  
jafir's Avatar
Super Moderator
Joined: Nov 2009
Posts: 5,847
Likes: 106
From: Arkansas
Default

Originally Posted by Disco Mike
02's even if they have totally failed should not cause a misfire, you would run full rich or lean and have codes indicating that.
Just posting my experience with my 1999 D2.
 
Reply
Old Sep 16, 2013 | 11:04 AM
  #15  
NWROVERS's Avatar
Thread Starter
|
Drifting
Joined: May 2012
Posts: 43
Likes: 1
From: Bellingham, Wa
Default

so adding on to the list. took the truck out for a drive yesterday and it will not go over 40mph. just replaced the o2 sensors the other day, and now the truck is kicking a p0134 code. So that brings the total code ups to 8. misfire 1,3,5,7, p1300, p1590, p0300, and the p0134. I am about ready to take the truck to a shop to try to figure out what is going on with this thing. I know that is going to cost a pretty penny.
 
Reply
Old Sep 16, 2013 | 11:42 AM
  #16  
Savannah Buzz's Avatar
Super Moderator
Joined: Jan 2011
Posts: 16,322
Likes: 88
From: Savannah Georgia
Default

P0134 is no activity on the front O2 sensor. Not plugged in good? You looked at plugs, wires, and coils in the dark - for little arc overs?
 
Reply
Old Sep 17, 2013 | 12:55 PM
  #17  
NWROVERS's Avatar
Thread Starter
|
Drifting
Joined: May 2012
Posts: 43
Likes: 1
From: Bellingham, Wa
Default

so yesterday i unpluged my o2 sensor to check the connection. Cleaned it up and added some dialectic grease. plugged back in and it still kicked the same codes. going to rip into this engine this weekend. My biggest qusetion is that could an abs code be the trouble behind all this. everytime ive pulled codes it show 12 but im only able to read 8.
 
Reply
Old Sep 17, 2013 | 02:10 PM
  #18  
Disco Mike's Avatar
Administrator
Joined: Apr 2006
Posts: 25,707
Likes: 107
From: Denver, Colorado
Default

Not a chance. By ripping into the engine, what exactly do you mean?
 
Reply
Old Sep 17, 2013 | 02:48 PM
  #19  
jafir's Avatar
Super Moderator
Joined: Nov 2009
Posts: 5,847
Likes: 106
From: Arkansas
Default

I'd be checking wiring before I'd tear into the engine.
 
Reply
Old Sep 17, 2013 | 03:01 PM
  #20  
NWROVERS's Avatar
Thread Starter
|
Drifting
Joined: May 2012
Posts: 43
Likes: 1
From: Bellingham, Wa
Default

The Thorttle body heater gasket started leaking on me this last week, so Im going to pull the intake off (makes it a little easier to get to) and replace the plenum gasket and re-tighten the valve cover gaskets while i have every thing off. Im going to double check the wires going to the coils and clean them up. along wire the ground wire on the back of the block. Not really going to rip into it per say.
but i am running out of things to check for this misfire.
 
Reply



All times are GMT -5. The time now is 06:30 PM.