Our Community is 940,000 Strong. Join Us.


O2 Sensor - OBD code P0153


dwoolley
09-18-2004, 05:34 PM
No sooner had I bought an OBD II code reader on sale (just in case) when my 1998 Windstar engine light comes on. Turns out to be code P0153 which relates to be a driver side sensor being "slow to respond"..possible causes contamination , bad fuel mix or the sensor going bad (and others)...as an aside I did add some STP gas treatment very recently so not sure if that might upset the sensor. So I cleared the code (paying for the cost of the code reader right there I justified to my wife) and am awaiting re-occurrence.

If it happens again...I'll assume the O2 Sensor is bad and replace...any idea of the work involved and replacement parts/tools needed? Any site that has this info? Thanks.

busboy4
09-19-2004, 02:13 PM
Hi
if you need to change an O2 sensor it is a simple job. Unplug it and unscrew it,then replace it. You should have 4 on the 3.8L.Code 153 in my book shows bank 2 upstream sensor, so that should be the one you can easily see just behind the radiator. Bank 1 is the rear cylinder bank, bank 2 the front. Upstream sensors are near the cylinder head, downstream sensors are in the exhaust "y"s visible underneath the van. Finding the right one is usually the only challenge.

You will be glad you bought that OBDII scanner.

Good Luck

dwoolley
09-21-2004, 11:07 AM
Hi
if you need to change an O2 sensor it is a simple job. Unplug it and unscrew it,then replace it. You should have 4 on the 3.8L.Code 153 in my book shows bank 2 upstream sensor, so that should be the one you can easily see just behind the radiator. Bank 1 is the rear cylinder bank, bank 2 the front. Upstream sensors are near the cylinder head, downstream sensors are in the exhaust "y"s visible underneath the van. Finding the right one is usually the only challenge.

You will be glad you bought that OBDII scanner.

Good Luck

No kidding...the OBDII scanner should be standard issue...I saw the O2 sensor you mentioned...seems easy to get at (and contaminate I assume).

After resetting the code and running through the Drive Cycles to set the Monitors again (using the same scanner to ensure the monitors are "done") I havent had a re-occurence...maybe a blip..if it happens again I'll replace.

Thanks for your help.

wiswind
09-21-2004, 11:52 AM
You might want to spray a little "PB Blaster" onto the threads and let them soak for a while.....and also let it cool down to loosen things up and assist you in the removal process.

Add your comment to this topic!