| and that the harnesses are not damaged or burnt. You might even want to bend the female pins in the connector a little to ensure a good connection. An O2 code can indicate a problem in the circuit, not necessarily that the sensor itself has failed. Fuel pressure test like Draker mentioned would be good to know, and to rule out the possibility of the fuel smell coming from a leak. A bad Coolant Temp sensor or low coolant can cause a rich condition as well, so check that. MAS was mentioned, too. Be sure that the sensor wire is clean (MAF cleaner spray) and the connection is good. Run a cylinder balance, and be sure to check the plugs and coils. Are you using the right NGK's? Are you getting a strong spark from each coil? No spark will cause a rich condition as well. If all seems okay at that point, clear the codes via the ECU screw, and go for a drive. If the code 33 comes back, then before shelling out to replace them, you might try swapping your 02 sensors. Move the left to the right side and the right to the left side. The harnesses are different lengths, but the sensors themselves are the same. clear the ECU and go for a long drive. The ECU may need to relearn the fuel trims a bit. I'm not sure how long that takes. If the problem now moves to the right side or the ECU now throws a code 53 instead of a code 33, then what is now the right side sensor is probably bad. As in the problem followed the sensor. As a double check, run the O2 diagnostic again (in neutral, 2000-2500RPM, blinking CEL) if the light remains lit while checking the right side sensor, then that sensor is probably bad. If the problem remains on the left side, or the ECU throws another code 33, and the O2 diag reports the same results (light stays lit while checking left side O2 at 2000-2500RPM) then you probably have a problem in the left bank of the engine. If you're going to replace one, you're probably better off replacing them both at the same time, unless the good O2 is relatively new.
|
20:27:13 05/18/11
