codes
#1
04-07-2005, 05:00 AM
codes
<HR style="COLOR: #666666" SIZE=1> <!-- / icon and title --><!-- message -->
this is my first time using the codes the codes that came up were 332 did not open /respond during test oe if memory code did not open intermittantly and 335 egr feedback signal is / was way out of range this is why i came to the conclusion a faulty egr valve [ am i right] thanks for your input i will check with ford on the parts ### help me to fix the right problem
<!-- / message -->
this is my first time using the codes the codes that came up were 332 did not open /respond during test oe if memory code did not open intermittantly and 335 egr feedback signal is / was way out of range this is why i came to the conclusion a faulty egr valve [ am i right] thanks for your input i will check with ford on the parts ### help me to fix the right problem
<!-- / message -->
#2
04-07-2005, 07:56 AM
Check the EGR system hoses and connections for looseness,pinching,leaks,splits,blockages etc.Check the EGR valve mounting bolts are not loose,or that the flange gasket is not damaged.If all is ok do a vacuum test on the EGR. The vacuum reading should be less than 1"of mercury[3. 54kPa] of vacuum.If the vacuum is greater than this your problem may be with your EVR solenoid[EGR vacuum regulator] .
#3
04-07-2005, 10:59 AM
You didn't say which type of code each was, so I'm going to have to make a couple of assumptions:
My code list suggests that a 335 can only be a KOEO code, and that a 332 can be either a KOER or memory code. I'm going to assume you only performed the KOEO test, and didn't perform the KOER test, so that makes your 332 a memory code.
SOP is to resolve KOEO codes first, because KOEO codes have to be electrical in nature. This means that we start by checking the wiring between the PFE (DPFE, EGR position sensor, EGR pressure sensor, or whatever you want to call it. Just remember, this is a family site
) Make sure the PFE sensor has 5 volts from Vref and that the computer has a good ground.
If all the wiring checks out, then you can check the output of the PFE sensor, but it's also a common part to fail on these.
My code list suggests that a 335 can only be a KOEO code, and that a 332 can be either a KOER or memory code. I'm going to assume you only performed the KOEO test, and didn't perform the KOER test, so that makes your 332 a memory code.
SOP is to resolve KOEO codes first, because KOEO codes have to be electrical in nature. This means that we start by checking the wiring between the PFE (DPFE, EGR position sensor, EGR pressure sensor, or whatever you want to call it. Just remember, this is a family site
) Make sure the PFE sensor has 5 volts from Vref and that the computer has a good ground.If all the wiring checks out, then you can check the output of the PFE sensor, but it's also a common part to fail on these.
#4
04-07-2005, 01:12 PM
Code 332 may be a consequence of Code 335. If the DPFE sensor is bad, the computer does not get feedback from the EGR system, and may post Code 332 because it commanded the EGR valve to open, and did not see a response. Not because the EGR doesn't work, but because the sensor is fried and doesn't respond.
Like Mr. Shorty said, deal with Code 335 (KOEO) first. Once fixed, clear the memory codes, drive around for a while, and see of 332 comes back.
Like Mr. Shorty said, deal with Code 335 (KOEO) first. Once fixed, clear the memory codes, drive around for a while, and see of 332 comes back.
Thread
Thread Starter
Forum
Replies
Last Post
