2.5L EGR questions

[fireguy12117]

has anyone had EGR insufficient flow codes and had success solving the issue?

I've been fighting this sumbitch for months now and had no luck whats-so-ever.

Replaced EGR tube since it cracked and failed near a DFPE senor pickup tube.
new EGR vacuum soleniod
new DFPE sensor
new vacuum like to the EGR valve

the only thing i can think of now is replacing the vacuum line to the solenoid even though it tests good, and checking to make sure the DFPE sensor hoses are in the correct order.

this has been a weird series of failures that occurred over a very long time now. i shotgunned a vacuum solenoid with shody troubleshooting which ended up really being a bad DFPE sensor, which worked for 6-8 months. then found a cracked tube, fixed it, now i cant get anywhere with it.

im just hopeing i overlooked the obvious simple thing here since all the big stuffs been eliminated. oh, EGR valve works, put vacuum on it and it opens and closes find...and the TB port is clear as well.

 

[disciplerocks]

That code is thrown by either the dpfe or the ref port.

 

[modelageek]

I am confused about shotgunning and the 6-8 months.....................if you put a new DFPE sensor in and it worked for 8 months maybe it went bad .what brand did you use?

 

[fireguy12117]

whatever local car parts place had.

when the problem originally occurred i couldn't quite troubleshoot confidently what component failed, so i took a shot on the vacuum solenoid, to discover that it was the DFPE that went bad- originally.

over a period of time there has been a series of new failures, so yeah, DFPE could be bad again i suppose...

its just that everything's pretty much new and checked out yet i still get the code...dunno what i'm missing.

 

[disciplerocks]

DPFE have a tendency to fail quite often by nature. Caused by the hot exhaust gases.

 

[fireguy12117]

biotch is under warranty, guess i'm pulling it and exchanging it- see what happens

 

[kimcrwbr1]

Just checking are you resetting the computer and erasing the memory when you mess with the sensors. First erase the memory then disconnect the battery for 30 mins then run the engine untill fully warm to set the new values then run the codes with the engine at operating temp.

 

[fireguy12117]

i was just resetting the code...clearing the CEL with the elcheapo gadget. it would go off and stay off a while, 30-40 miles worth of driving then come back.

I'm going to get the exchange for the DFPE done tomorrow after work, toss the new one in, reset the code, pull the battery cable, then go from there.

i had the EGR tube repaired at my work, i probed the smaller tubes and seemed to have a clear passage to the main tube, but that's no 100% guarantee. if this doesn't work work i will probably have to spring for replacing the EGR tube. i didn't clarify that in the first post but thought i should mention it as it just kind of slipped my mind. i suppose if a booger of weld slipped into the hole drilled in the main tube, i could get "insufficient flow".

 

[Ranger Dave (B25)]

Just checking are you resetting the computer and erasing the memory when you mess with the sensors. First erase the memory then disconnect the battery for 30 mins then run the engine untill fully warm to set the new values then run the codes with the engine at operating temp.

Pulling the battery on an OBD-II vehicle ('96>) does NOT clear any codes. OBD-II uses non-volatile memory for storage, battery cable pull does nothing except cause you extra work resetting your radio stations.

The correct way to reset the codes is with a scan-tool, just the way he said he did.

 

[fireguy12117]

thanks for the clarification. i have one of each vehicle, so that's handy to know how the memory works.

unfortunately the DFPE was a 1 year warranty and i was a few months out. I'm heading to the junk yard to ply my luck there first. if i can get another DFPE fiddle with, it may help confirm that the tube and EGR valve itself work or are part of the problem.

I had the code prior to discovering the bad tube, and still have the code since repairing the tube, so...this is just a PIA in confirming work that's been done versus tracking a new fault...

Thanks for everyone's input. it seems like there isn't something random that I've missed.