The real story will be told when you go back in a week and read the codes again. If the 49 is there it is the likely cause of your fuel codes. 81 is not what you think it is usually low fuel pressure, it is a bad translation that makes it sound the way it does.
Santi had a good idea. Louis needs to buy a Peake reader and keep it in the car. The next time he gets a CEL he needs to immediately pull over and check the codes. That way, he is more likely to find the code that is the culprit, rather than a bunch of latent legacy codes.
The CATs on the car are BMW. They have been replaced. Santi checked the welds and didn't see any signs of exhaust leaks. One of the O2 sensors did tighten a little, but wasn't loose.
Repacing the O2 sensors is the first order of business. I'd like the give the Indie the benefit of the doubt and believe the original CATs needed replacement, but it's hard to do that when they didn't replace the O2 sensors with the CATs. Makes you wonder, although Louis still thinks highly of them.
Louis also mentioned that he ran the tank empty, so that may explain some of the codes. We also reiterated the importance of making sure the fuel tank cap is tight, as that will also throw a CEL.
Santi had a good idea. Louis needs to buy a Peake reader and keep it in the car. .
Duh. for $150 having the ability to pull codes when you need and not wait, or drive over to someone's house, or pay a shop....or just not to have to wonder for the remainder of the 100 mile drive...everyone should have one, even if you never work on your own car.
Quote:
Originally Posted by Georgia M5
The next time he gets a CEL he needs to immediately pull over and check the codes. That way, he is more likely to find the code that is the culprit, rather than a bunch of latent legacy codes.
Not sure what kind of advice this is.... you may be creating false concerns about what he needs to do.
If you reset and cleared all his codes today, there shouldn't be a 'bunch of latent legacy codes'... the next time he reads codes it will be all codes since the last reset. I'd submit that any codes between today and next time are germane to his issues.
As Sailor posted the low fuel tank thing is often a red herring- and I'm not sure I'd wind him up about gas caps when there is no evidence any of his codes were related to the evap system... not even a latent legacy loose cap.
Duh. for $150 having the ability to pull codes when you need and not wait, or drive over to someone's house, or pay a shop....or just not to have to wonder for the remainder of the 100 mile drive...everyone should have one, even if you never work on your own car.
Not sure what kind of advice this is.... you may be creating false concerns about what he needs to do.
If you reset and cleared all his codes today, there shouldn't be a 'bunch of latent legacy codes'... the next time he reads codes it will be all codes since the last reset. I'd submit that any codes between today and next time are germane to his issues.
As Sailor posted the low fuel tank thing is often a red herring- and I'm not sure I'd wind him up about gas caps when there is no evidence any of his codes were related to the evap system... not even a latent legacy loose cap.
The point is, he needs to read the codes after he gets the CEL, not weeks or months later (like we did yesterday) when the car is full of a bunch of other codes that may not be related to the issue at hand. This was actually Santi's comment and I agree with it. That may be "Duh" and obvious to an expert like you, but not to someone who is new to the car, has never seen a Peake code reader, and doesn't regularly use the codes to trouble shoot problems. That means getting a code reader and not waiting until he has the time to take it back to his favorite Indie to read the codes after the next CEL. Sorry to have to state the obvious, but it wasn't directed at you.
Everyone should have a reader of atleast the quality that will also read pending codes. I think that should be the first thing you get even before you buy the car.
Hate the thought of reading at the light for diagnostics. Obviously you read as soon as you get the light but.... When you know you have codes you need to read without clearing after almost every drive, then write it down. Every test has different "requirements" for it's test, so the question of when they happen is not always clear. What I mean is a car that had fuel codes and cat codes but only when you took it to the highway and ran 2000 rpm in 6th.
Don't forget it takes two can kicks to trigger the light. Once you have cleared the codes all the codes are relevant because often two codes together send you in a different direction. On a ford van which I have 12 of, there is a code for a stuck throttle plate but if it comes with a fuel code the problem is a wiring one elsewhere. We have the same with these cars but.... well, not enough info to make all the connections.
The point is, he needs to read the codes after he gets the CEL, not weeks or months later (like we did yesterday) when the car is full of a bunch of other codes that may not be related to the issue at hand. This was actually Santi's comment and I agree with it. That may be "Duh" and obvious to an expert like you, but not to someone who is new to the car, has never seen a Peake code reader, and doesn't regularly use the codes to trouble shoot problems. That means getting a code reader and not waiting until he has the time to take it back to his favorite Indie to read the codes after the next CEL. Sorry to have to state the obvious, but it wasn't directed at you.
Yeah, I agree. He doesnt need to swerve to the side of the road and read codes immediately.... Light comes on, read the codes ASAP. Like that night in the garage, or when you fill it up, etc. Clearly not waiting days or weeks or months. WRITE them down. And RESET. Even if the light turns off.
Even people that aren't 'car guys', that don't plan on fixing it themselves...a code reader will give them a HUGE advantage when it comes to telling their indy what is wrong, and evaluating what needs to be done.
Yes, if I some how implied he should read the codes while driving the car or at the light, that is not what I meant. Get the car home or stopped. Read the codes and write them down.