What is your question?
·
·
What is your question?
All systems work correctly, all measures and voltage within specs. No clogs, no vacuum leaks, EGR opens and engines shuts off at idle, no cracked hard lines. Dealer cannot find problem and now wants to remove lower intake to find what they cannot understand. Car runs excellent, fuel mileage great, no stalling, missing, no problems. Check engine light will not stay off after resetting. I believe the dealer is fishing for funds without a clue. Should I allow removal? What are they missing? All information appreciated.
·
1 Reply
i would get it away from the dealer.you more than likely have a carbon blockage.i know a guy that had the same code for 8 months,replaced everything to do with the egr system,like most do and it don't fix it.he said he researched the problem and decided to remove the throttle body,and he was shocked! it was completely clogged up,hard as steel,had to dig it out with a PICK and a screwdriver,no flow period!just a thought.if the dealer is guessing at it,why not guess at yourself,and save who knows how much $$$$$..........
Thanks for the info. There are no clogs on the upper side. All lines hard and soft checked or placed. TB clean, new egr hard line to intake, dealer check all passages, no blockage. All mechanics and shops old guy 3800 himself said huh! I will remove intake lower and see what is down there. Still do not believe that is the problem. Street guy said O2 sensor was his problem. Diag said no bad sensors. They had it all day and could find a problem? All that is left is replace map, maf, and O2 until something gives. Sounds like the wrong road to go down. Will see if anyone else has a thought. Grump out.
ok.well i have seen that code(egr insuff.flow detected) more than you can imagine.and it always turned out to be a vacuum leak,pressure sensor, egr valve,and most of all carbon build up.i'm sure one of or both shops and the dealer hooked up a REAL SCANNER with live data and should have found it.but,maybe going to start guess until it's found.i did read somewhere that a map sensor was someones problem throwing that code,and it was the last thing they tried,and it fixed it.good luck with it,and post findings.