After You Get the Codes

Once you pull the code(s), follow the diagnostic procedure for that particular code on your vehicle. That information can be found in the service manual for your vehicle. Don’t assume that just because you have a code for something it means that the part you have a code for is bad. This is particularly true for O2 sensor codes. There are several O2 sensor codes, and they don’t all mean that the O2 sensor is bad. In fact, it would be bad practice to replace a part that you had a code for without verifying it was bad first. You can waste your time and money doing this. The problem could just as easily be bad wiring or some other fault that set the code. The computer doesn’t know that a given part is actually bad; all it knows are voltage readings. If the voltage readings are off, then it sets a code. It doesn’t ask why the readings are off; it just sets a code and leaves you to figure out what the issue truly is.

Another thing to note here is that you can often get your local auto parts store to pull codes for you. Keep in mind this is all they can really do. These people are not trained technicians, so any information they give you outside of what the code is should be taken with a grain of salt. It is true that some of them are former technicians or that they might have some mechanical experience, but you should only take their advice as just that, advice. Don’t assume what they tell you is a diagnosis; think of it as more of a jumping-off point. I strongly recommend you get your hands on a service manual for your vehicle and perform the troubleshooting associated with your code(s) before purchasing any parts. This video might help you find a service manual if you need one.

Video Title: After You Get the Codes – Solving Automotive Performance Issues – EricTheCarGuy Video Description: In this Article, After You Get the Codes, we look at how this can impact Engine Performance. Thumbnail: http://www.ericthecarguy.com/images/faq_buttons/Large_FAQ_Images/Performance-and-Driveability-icon-1200.jpg