Help us help you. By posting the year, make, model and engine near the beginning of your help request, followed by the symptoms (no start, high idle, misfire etc.) Along with any prevalent Diagnostic Trouble Codes, aka DTCs, other forum members will be able to help you get to a solution more quickly and easily!
Hi big fan! I have a question. I am the original owner of a 2005 Acura TSX with 60,000 miles on it. A few days ago I took it to my mechanic for an oil change and I knew my car had no codes. I own a simple scanner that you recommended for car owners to have (ANCEL AD310), but my mechanic voluntarily checked my car with his OBD2 Scanner and he played with his scanner for 20 minutes but he could not find any codes. However, when I came home for the first time I have a yellow triangle light that comes up on the dash. Moreover, when I drive over 30 miles per hour the VSA light turns on. I know my mechanic triggered that light when I left, but my question is the following. That the same way mechanics with their OBD2 can erase codes can mechanics on purpose create a VSA code so I have a problem with my car? That they would do this so I would go to my mechanic to solve the issue so they can make money and erase the codes. I want to see if my mechanic is honest or if he is trying to scam me.
I am reluctant to tell you that a(ny) scan tool is not designed to introduce fault codes. But I have to speak out the truth although it may demolish the idea some people cherish that mechanics are that evil people they even will flag codes into your controllers.
An expert is someone who knows each time more on each time less, until he finally knows absolutely everything about absolutely nothing.
20 minutes the guy had probably just got a new toy and was testing it.
Juergen is correct in saying scan tools aren't designed to introduce false DTCs. However they can sometimes set DTCs inadvertently. The linked thread includes several instances of your symptoms being triggered by scan tools.
With the VSA light on depending on what he was doing (checking out his new toy or what not) if he inadvertently did a steering angle reset and wheels were not straight can potentially cause a VSA issue. What codes were set? Also it's possible that it just happened to develop a problem after being at the shop. I have had this happen a few times and it happens.
Sometimes a scanner can cause a communication code to set. I like to run a health report with a good scanner and pull all codes from all modules, not just generic codes from the engine module.
Topic Author
