1999 Lexus ES300 P0171 trouble
I have here a 1999 Lexus ES300 with codes P0171, and P0420. I needed some pointers or if someone has encountered similar codes or symptoms with this vehicle. So far I was able to repair two vacuum leaks one being @ the brake booster hose, and the other at the intake/induction hose boot revealed by a smoke machine test. Got a new Denso A/F Ratio sensor, and my supervisor bought a used Catalytic converter, you know how that goes anyway still the same issue.
Got freeze frame data:
- Calculated Load Value - 42.75%
- Engine Coolant Temperature - 159.8 F
- Engine RPM - 2,512 RPM
- Fuel System 1 Status - CL
- Short Term Fuel Trim Bank 2 - 0%
- Vehicle Speed Sensor - 44.12 MPH
- Fuel System 2 Status - CL
- Intake air temperature - 77 F*
- Long Term Fuel Trim Bank 1 - 39.84%
- Long Term Fuel Trim Bank 2 - 42.97%
- Short Term Fuel Trim Bank 1 - 0%.
Any suggestions? If I come to any conclusion I will re-post my results, and findings here.
i have seen a few with injecto seals leaking but that’ll show in a smoke test which you’ve done already
What’s the upstream read when WOT? Maybe fuel pump? bad MAF?
if you have other drivability codes along with a P0420. Should always nail down the other first
I don't remember off the top of my head but I have the data saved and it was @ around 3.3V @ Idle with very little change.
I have tested the MAF but have not done a visual inspection of the MAF Sensor element itself.
Since fuel trim is an active pid, then use your scan tool to gather the needed information, and let the scan tool direct you to the problem. Select RPM, throttle blade position, load, MAF, oxygen sensor voltage for all sensors & long & short term trims, now take it for a drive going from idle through a WOT shift point, then cruise.
With that information, you will have your direction with no guessing. Capture the data and post it up for use to take a look please.
Since your Freeze Frame data showed us the LTFT is very high at cruise, as opposed to at idle, I believe you have an actual fuel delivery problem, not a vacuum leak. However, you could also have bad MAF. To help narrow it down; Check the fuel pressure under full load. Also, do a VE test by recording your scan tool and using one of the available online tools.
Add those results when you post the scan tool recording Albin asked for.
Ok will do thank you, I will post the calculations, and screenshots of the data captured.
I had an issue a couple of years back with a GS300 here in the UK, turned out there is a manufacturer issue with the fix being a pair of modified lambdas and a replacement ECU with a software update, I'm unsure why the fitted ECU couldn't have had the SW loaded but I just followed the manufacturer TSB and it sorted mine. I have the TSB but it will not let me upload them - says the file is not supported (XPS) , if you email me at sales@…motors.co.uk I will send you what I have.
I see, I have looked up some TSB's but didn't find anything in particular for this problem. I'd like to see that TSB that would be helpful I will email you, thank you.
Check the air intake tube for cracks. Ck the PCV valve. Make sure it is the correct one and not aftermarket. The karman vortex MAF on these rarely fail and are very expensive. Ck the a/c idle up and the hoses. Has anyone had the intake plenum off? If so the center bolts and nuts MUST be tightened first before the bracket bolts, otherwise you will have a vacuum leak.
Ok I see. Yes I have done a smoke test, and it did already uncover a torn intake boot.
Here is some of the data I have gathered. Mr. Moore, and Mr. Welsh I have gathered those pieces as advised, and here's what I got. To me its looking like a MAF Sensor problem, but the throttle position looks a little odd as well since i do have the pedal all the way to WOT, anyway I have yet to continue. Back at it tomorrow!
Can those graphics be zoomed in a little?
Kinda hard to see.
Also, old cars like that computer is really slow. i’d pick fewer pids for better and faster sample rates.
Wot shows very lean. Idle shows rich. Gotta check fuel pressure With a gauge At idle and wot. Make sure there are no blockages in the intake track, like someone leaving a rag in the air box. Im gonna guess maf
Alex, I have read over all the replies, and the data you have posted. Please be patient with me, since I'm old and lazy. I have spent many years with a scan tool, and have found ways to get it to tell me what the problem is. Most times I will use a Snap on scan tool for this kind of work, since it does a great job of both capturing data, and displaying it in a format that is easy to understand.
Since you are using an Autel tool, you can still do the same thing, although the tool is slow and clumsy for this kind of work. You need to get the car to talk to you and tell it where the problem is. To do this, you need to capture the correct data, and put the car in the proper place and condition. I wish the autel tool would allow you to post up the captured file, instead of just the screen shots, Oh well, we will work with what we have.
From the data you have posted, it sure looks like the MAF is not reporting properly, now, lets make it prove it. Take your vehicle to a road where you can start and stop without getting run over by others. Set up a custom pid list with these pids, no more, no less. You need, TPS, MAF flow, in Grams per second if possible. RPM. Long term from both banks, short term from both banks, oxygen sensor voltage from all sensors & engine load.
Now to make the car to the talking. pull to the side of the road and stop. Start your recording, let the engine idle for about 30 seconds or so, pull out and accelerate at WOT up through at least one shift point, up to around 60 MPH if possible, then back off the throttle and cruise for a short distance, now pull over and save your capture. Now you have put the vehicle into an idle WOT condition, Full power condition to test the VE, then a cruise condition to see how things are working at part throttle. Put all that information on one screen if possible. That is the data that you need.
Here is a post I did a while ago here on DN about this subject. diag.net/msg/m6dd30cz5z…
Ok, thank you again Mr. Moore, and no problem. The way you explained it to me the first time helped. I took your pointers, and got to working on the car, and found my clues, hints, and data pieced it altogether, and got a confirmed fix. I have a Launch scan tool but the Matco tools version. I plan to invest on a OTC Evolve Scan tool but I would first like to purchase a pico. The shop I work at does have a snap on scan tool, I have taken a Diagnostic class where they have talked about VE, and VE calculations but never really put it in to use or practice but for this particular case, and along with your suggestion I did for this one, and its helped A LOT. Thank you again, I am going to post my results shortly.
After reading your info, I would recommend doing a TPS sweep test with a scope/graphing multimeter because that pid isn’t reading right. Could have a scan tool data issue as well. Also the MAF barely hitting 40 g/s at WOT is a problem.
But here’s my question: did you record this while driving the vehicle? Or did you do this in a stall? Vehicle needs to be under max load while accelerating, an in-stall test doesn’t work
Yes, I did this while driving the vehicle. The vehicle drives fine, its does not have a stall condition.
Here are the final results for a confirmed fix for P0171 on this 1999 Lexus ES300 thank you for everyone's input. As for the P0420 it also needed the Cat at the very rear of both banks, along with the O2 sensor just to cover my butt, but anyway here is the data for both the vehicle @ Idle, and WOT with the MAF Sensor replaced, and also the results of the VE Calculation with the data entered. I wanted to go more based on a data/ analytical approach for the fix but I have pictures as well with the new MAF sensor that is going to be installed, and the old one removed. I know this is what you were speaking of Mr. Caughron I have included those snapshots here as well.