One of the most common falsehoods you'll hear concerning car repair is that trouble codes will tell you what is bad on your car. Just read the code and know what the problem is. There is no truth in that statement and, for some reason many people believe it anyway. I imagine it gets tossed out there most often by misleading ads from makers of code readers. I can tell you this, if a code reader would diagnose a car problem I wouldn't spend any time learning how systems work, how to test operation or definitely wouldn't spend so much money on testing equipment.
If you were driving a car and noticed a problem that you felt should be checked out, you would bring the car in and describe what you are noticing. Coming in and saying something is looking like a problem on my car, with no more information, then I'd have a really hard time determining what you are seeing that you are worried about. A warning light coming on in your car is the equivalent of that. The light is just saying hey I noticed something. If it stopped there I would have an extremely hard time determining the problem. If you said I noticed a problem with the engine sometimes being hard to start, idling rough and black smoke, then I would know what sort of things to start checking to determine the problem. Trouble codes are the way the car tells you more about what it is seeing that looks like a problem. It is giving you a place to start testing to determine the problem.
If I need more information from you about the problem, I ask for it. If I need more from the car computer, I use a scan tool to look a bit further. So, I ask for it.
Let's walk through one. 2012 Ford Edge Limited 3.5 Because the Malfunction Indicator Light is on and because that just means there is a problem, I need codes. I don't need codes to tell me what is wrong, because they don't. But I do need codes to know what sort of concerns the computer has noticed.
No comments:
Post a Comment