When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Hi guys..
I have a BlueDriver OBD 2 reader that I've been using on different cars every time I the engine light came on.. and lately I use it on my Audi A4 2017 Progressive.
When I bought the car I have noticed those codes (this is a crop from the phone screen-shot):
The dealer that I bought the car from, told me that the car was inspected (and provide inspection report) by VW OEM Dealer and no problems were found and probably the previous owner when returned the car from lease there was some service and they forgot to clear the codes...
I didn't know what to say so I bought the car which runs nice and smooth...
My previous mechanic told me once that some of the codes come on with different errors and not necessary with a problem, so if the engine light doesn't come on the dash but you see any error codes after a OBD2 scan - by clearing the codes and drive few days, see if they come on again .. if not, probably it wasn't a real problem but just a temporary error in the system.
Based on this statement I did clear the above codes and drove over a month and they didn't come on again... which, I guess, it is ok!
Now, yesterday I did another scan and I have noticed this new error code 522:
The engine temperature seems to be measured fine on the dash - I mean, it starts cold and in few km it gets to 90*C and stays there for the rest of the ride - which makes me think that everything works well. As I know, a short circuit may cause fire, or for this sensor to not measure the temperature at all. I was also expecting an error on the dash - for such a problem.
After I noticed this, my first taught was to clear it and wait few days to see if it will come again - but then I considered to share this here - not all mechanics might be honest and not all cars are the same.
At this point the error code still shows up when scanning with the OBD2 and car runs perfectly...
Yes, there are occaisionally spurious error codes that get captured, and then wait for a confirmation with other occurrences (referred to as Pending, iirc). If it doesn't occur again within a set period of time, the code is cleared. If you are getting what seem to be accurate readings, and a dash error hasn't been thrown, it's probably a spurious error. Rather than clear it, just wait a bit and see if it goes away.
More specific definition
OBD II Pending Codes are also referred to as “continuous monitor” and “maturing codes”. An intermittent fault will cause the computer to store a pending code in memory. If the fault does not recur within 40 warm-up cycles, the code will be cleared from memory. If the fault recurs a specific number of times, the code will then mature into a diagnostic trouble code (DTC) and the MIL or “check engine” light will turn on.
Hey @PghRich thanks for your reply. I'll try your suggestion this time - I won't clear the code but drive few more days and then check again!
Is it possible for an error to remain active - simply because the system got it once and stay there until cleared (even if the problem was real and fixed by a mechanic) ?
I second what PghRich stated. You may also want to have a look at you battery and alternator. In my experience, electrical issues are a high contributor to random codes
I second what PghRich stated. You may also want to have a look at you battery and alternator. In my experience, electrical issues are a high contributor to random codes
Thanks Larry,.. Not sure exactly how should I check the Alternator or the Battery.. I have a multimeter but will that be the case?
Hey @PghRich thanks for your reply. I'll try your suggestion this time - I won't clear the code but drive few more days and then check again!
Is it possible for an error to remain active - simply because the system got it once and stay there until cleared (even if the problem was real and fixed by a mechanic) ?
I can't vouch for it, but what I pasted says Pending codes can stay Pending for up to 40 wram-up cycles, so it could be a while.
There are such a thing as Permanent DTCs (code) - they are relatively new and didn't exist when I last had to deep dive into codes/types/etc.
Here's a summary - https://www.autoserviceworld.com/car...ermanent-dtcs/ I don't know if a temp error would fall under emissions as a possible permanent code - possibly, due to rich fuel/increased emissions at cold start.. The article documents a Universal Drive Pattern that is supposed to clear "permanent" codes. It seems like something that would occur in the normal course of driving, but who knows.
(It wasn't clear, but if you had previous cleared this same code with a code reader then it's not a Permanent Code)
I never cleared those codes - they just came on after 2-3 weeks from the previous scan.
But.. WOW.. last night I did another scan and another codes pop-up:
2nd - RKA Pressure Loss, Puncture detected - which is a list that doesn't make any sense for me since this car doesn't have pressure sensors to read the exact tire pressure - but all it does is go with the ABS wheel rpm / compared with the rest of the wheels. So not sure how it can detect a tire puncture. Also the pressure in the tires didn't change at all since mid September - when I bought the car and tested the pressure:
I don't know if this BlueDriver is the issue or the Audi - which is a German quality car - so my expectations are pretty high on it, especially for that price tag I paid.
I'll clear all those codes today and see how it goes...
For the 5644: Low Fuel Pressure regulation Fuel pressure fluctuates I did a research and found some symptoms that make it clear that the Fuel Pressure is not right and none of those appear to be while I drive my car. Vehicle runs nice and smooth, no throttle lag, no hard time to start , etc. If I wouldn't have the OBD scanner I wouldn't even tell that this is an issue. I don't know what to say - why so many errors appear to be with the car when none of them I can actually experience or see anything wrong with the car. I'm confused!
Unless the dash warning light is illuminated, there actually aren't any errors that appear to be with the car.
Originally Posted by Scutu Mix
If I wouldn't have the OBD scanner I wouldn't even tell that this is an issue.
Exactly. Because it's not.
This is one of the reasons Pending codes aren't exposed to the owner/driver/user. Modern cars are very complex, highly computerized pieces of equipment. Nothing is perfect and there are layers and layers of validation, verification, etc. You can go crazy worrying about one-off signal errors that don't exist.
Until the electronics of the car, which are designed to tell you when something is actually confirmed to be wrong, tell you there's a problem, I suggest you not try chasing ghosts.
I'm pretty sure my last few scans have turned up a pending issue or three. I never thought twice about it, and the service techs never mentioned it when in for factory service.
(Interesting trivia - when my daughter's RX350 throws a "Check AWD System" error, I tell her she forgot to tighten the gas cap. It's a well know Lexus diagnostic)
Unless the dash warning light is illuminated, there actually aren't any errors that appear to be with the car.
... yeah, I have to agree.. but pretty strange!
Yesterday I just cleared the latest codes, drove 20km, scan again to find out that none of them come back... and to make it clear I also sold the BlueDriver... Hahaha...
I'm looking to get the OBDeleven instead... just a bit afraid not to brick the car!
New Audi A6 Allroad Is The Market's Coolest Wagon: 9 Things to Know
Slideshow: Audi's latest A6 Allroad gets RS-style fenders, real off-road hardware, and enough personality to stand out in a market obsessed with crossovers.
Audi Recreates Crazy-Looking Speed Record Breaker From 1935
Slideshow: Audi has recreated one of the wildest machines of the pre-war speed-record era, reviving a streamlined V16 racer that originally exceeded 200 mph in 1935.
OBD Codes!
