I bought my 03 last October and installed an Edge Revolution less than two months ago. Since then (and probably before then) I've been getting the P006A, P132B, and P0401, in addition to P1000 which never goes away no matter how many times I clear codes. The only issues I've had is lack of power when the engine isn't fully warm, and mileage has been 12-13mpg mixed driving with very light loads.

A couple weeks ago, I pulled the turbo and the unison ring was totally stuck. So I cleaned it all up, machined a new slot in the UR for the cam, re-installed, and ran the turbo re-learn procedure. While I was at it, I checked the barb on the intake manifold for the MAP sensor tube, and it was in serious need of unplugging.

Since the turbo rebuild, I haven't noticed much difference in performance. The P132A hasn't come back, but the P1000 and P0401 have been consistent, and the P006A just reared it's ugly head again.

Any suggestions as to the most common cause of this combination of codes? I deleted the egr cooler when I replaced the oil cooler, and all this time I've been thinking the P0401 was because of that, but I just read in another thread that it could be tied in with the other codes. One suggestion was to clean or replace the IAT2, but other than that I don't have any diagnostic equipment to go any further.

 

Well, its about time you got one. Scan Gauge II or Torque Pro. Without one we're all just guessing, but I'll try to help. Seriously, owning these trucks require a good scanner/code reader for live data to effectively trouble shoot. Scan Gauge reads live data well, not code read well. Torque Pro for Android is a good reader and live data monitor and the cheapest of the bunch.

1) P0401 is an EGR code from the deleted cooler. Takes a tuner to clear it, but plug the sensor back into the harness, it helps control fan speed, not just EGR stuff. That won't clear it, just know its there.
2) p1000 is a drive cycle test, leave it alone, it will complete with time and clear.
3) P132a is O2 sensor generic code, we don't have an O2 sensor. I think its pointing to the EBP sensor. Clean the sensor, clean the tube feeding the sensor with string trimmer line.
4) P006a is MAP sensor, clean the nipple its attached to at the manifold, clean the tube feeding it and the sensor. You may need to buy a new sensor or tube if you can't get it cleaned up.
5) Clean the IAT2 sensor as well, your right there anyway.
6) Spend the money on a reading devise before spending another dime on parts!

Your wallet will thank you and the code for a headache (Pain In My *** 1000x) will clear your brain.
IAT2 is a temp sensor, just like IAT, just in a different location.

 

After cleaning all sensors, IAT2, EBP, MAF, MAP, clean MAP and EBP tubes, and you have done the turbo, re run the whole relearn and complete the drive cycle. You will need an EGR valve in the socket and it must be electrically connected or you need a tuner to properly delete it. Then I concur with the above, something to read the codes will save you in the long run on costs.

 

The EGR is still in place and plugged in. EBP tube has already been cleaned, not really sure how to clean the sensor, except maybe shooting some MAF cleaner in there. Replaced MAP tube with a piece of fuel line already, and as noted above, cleaned out the nipple on the intake manifold. Again, not sure how to clean the MAP sensor. I guess I'll attempt to clean all the sensors and re-run the turbo re-learn cycle.

WatsonR - I'm not so sure it's as cut and dry as you make it sound after reading this short thread:
https://www.ford-trucks.com/forums/1...and-p132b.html

But I will start shopping for a diagnostic tool per your recommendation.

Thanks for the input!

 

Is the scan gauge worth the extra money over torque pro? Does it provide more information or is it just a matter of one preferred flavor over another?

 

torque pro is a better code reader and does live data... it does require initialization every time. Scan Gauge is pre-programmed (by you or someone) and connected to the OBD port, jump in and go.

Both have advantages, its a preference. I daily drive a Scan Gauge II and trouble shoot with Torque Pro and also ForScan.

 

Sorry. Wrong thread cause fat fingers on my phone.