Land Rover Forums - Land Rover Enthusiast Forum

Land Rover Forums - Land Rover Enthusiast Forum (https://landroverforums.com/forum/)
-   Discovery II (https://landroverforums.com/forum/discovery-ii-18/)
-   -   Codes after oil change and coolant work. (https://landroverforums.com/forum/discovery-ii-18/codes-after-oil-change-coolant-work-36125/)

buick215 11-28-2010 06:23 PM

Codes after oil change and coolant work.
 
Yesterday I did an oil change (went from Mobil I 10w 30 to rotella 15w 40), replaced all coolant hoses, flushed the coolant system, replaced the Dex-Cool with Peak Global Lifetime, and bleed the coolant system. After I finished I drove the truck around the neighborhood and all was well. Today in the morning I checked the coolant level, topped it of a hair and took the truck for a trip. At the first stop light the engine started to idle rough and the check engine light came on. After the first couple of stops it stopped idling rough but after I left the store it idled rough for the first couple of stops and then went away. I latter went to Autozone and these are the codes that I got P0150 and p1174. I had no codes before the oil change and haven't had any codes or problems since the 60K mile service was performed 10k miles ago. The only thing that I can think of was the change in oil type and brand. Maybe I should have just stayed with Mobil I 10w 30. That is what I have used for the last 20k miles and changed it at 4000k mile intervals. I decided to switch to Rotella after hearing all of the great praises. This is the first time that the engine idles rough since I have had it. Need help, I am dumbfounded and don't know where to begin. :eek: PS The engine never overheated, the coolant never went down or leaked, the heater worked fine with no waterfall noise, their appears to be no air in the cooling system and I have always used premium gas.

GARovee 11-28-2010 06:39 PM

1174 is just a junk code due to your p0150 code. Check the electrical connector for your passenger side front oxygen sensor. If it's okay, disconnect your battery for 25 mins to reset the CEL light or clear it with a scanner. If it comes back you're likely gonna have to replace that sensor (bank 2 - sensor 1)

lipadj46 11-28-2010 06:39 PM

the oil has nothing to do with it. It is what we call a coincidence. That is a front passenger side O2 code and the lean code that goes with it.

lipadj46 11-28-2010 06:40 PM

Also you cannot clear codes by unhooking the battery you need a scanner.

buick215 11-28-2010 06:41 PM

Thanks for the quick reply. I already erased the codes and the check engine light turned off. It did not come back on, on my way home from Autozone. Hopefully it won't come back on tomorrow.

GARovee 11-28-2010 06:42 PM

Oh yeah btw I think it was just coincidental that you changed the oil and then the light came on. You may have got coolant or oil in the o2 sensor connector or disturbed the wiring/connection when the coolant work was done.

buick215 11-28-2010 06:51 PM

If the check engine light comes back on is there a way of saving the oxygen sensor by cleaning or redoing the connection or am I just being cheap and ridiculous. :D

lipadj46 11-28-2010 06:59 PM


Originally Posted by buick215 (Post 211594)
If the check engine light comes back on is there a way of saving the oxygen sensor by cleaning or redoing the connection or am I just being cheap and ridiculous. :D

This is not a slam dunk, P0150 is the O2 sensor is giving a signal outside of it's operating range. Most of the time replacing the sensor will fix the problem as long as it is not a problem with the computer. If you have a scanner that reads live data you can watch the signal. Normally cleaning the sensor won't do anything unless it is just really gunked up. The kicker is that you really should replace O2 sensors in pairs, so replace both front sensors.

GARovee 11-28-2010 06:59 PM

The p0150 code will go inactive and the CEL will not be on if you disconnect the battery for 25 mins. Try it. ;)

GARovee 11-28-2010 07:01 PM

No. Unless you got the connector dirty and caused a bad connection... All you can do is clean the connector ends. If that doesn't do it then the sensor is likely going out. I just did my same sensor a few months ago for the same thing actually.


All times are GMT -5. The time now is 03:16 AM.


© 2024 MH Sub I, LLC dba Internet Brands