DemonicFX4

can anyone vouch this?

CPT150

Ive not heard that before nor them putting out different codes. I mean whats the point of that

obusnizzle

ive been running custom programmed fords for 12 years. fubar codes mean fubar programming.

RLXXI

Everytime a customer came into the shop with a check engine light and had a programmer it would throw false codes, it was to the point where a couple people would de program them before they came in. Once the programming was returned to stock I was able to retrieve the actual code and fix the vehicle. Especially power stroke deisel.

That was 10 years ago and they all used the Hypertech programmer. ymmv

DemonicFX4

Hm im picking it up in an hour or so, ill erase the code and go back to stock and drive it around see if it comes back.

RLXXI

P0451 - EVAP System FTP Sensor Range/Performance/Intermittent


Note: Starting on some 2004 applications, DTC P0451 will be set for FTP sensor range (offset) fault. DTC P0454 will replace the original P0451 for intermittent (noisy) sensor faults. Until the phase in process is complete, noisy or offset FTP sensor faults may set a P0451.

• The fuel tank pressure changes greater than 14 inches of water in 0.10 seconds.
• FTP sensor output is offset by + /- 1.7 inches H2O

• Intermittent open or short in the FTP sensor or the FTP sensor signal.
• Contaminated or damaged sensor.
• PCM damaged

• Monitor FTP PID and does it change from above 15 inches of water to below a minus (-) 15 inches of water often in 1.0 minute.
• With the FTP sensor at atmospheric pressure, the FTP PID will normally indicate 0 inches of H2O. Look for a minimum reading of plus or minus 1.7 inches of water as an indication of an offset condition.

Apparently Ford had issues with your year model and the fuel tank pressure sensor. You may also need to have the pcm flashed to update the calibration.





.

RLXXI

A small number (less than 500) of 2004 Model Year F-150 vehicles built at the Kansas City and Norfolk Assembly Plants from July 18, 2003 through August 29, 2003. Affected vehicles are identified in OASIS.


REASON FOR THIS SAFETY RECALL

Some of the affected trucks may have a fuel tank with localized depressions in the fuel tank wall at the seam between top and bottom halves of the tank (not visible from outside the fuel tank). If a depression is large enough, fuel may permeate the fuel tank wall resulting in a fuel odor, or a MIL light illumination. If left uncorrected, a fuel leak could eventually develop. There have been no reports of this condition from any customers.

You can check your truck on this link for recall's.

http://owner.ford.com/servlet/Conten...ge/RecallsPage

DemonicFX4

Well got the truck back (convinced them not to charge me for putting it back together) and when I started it up no code, so I reset my power level 2 on my edge without a custom tune and I drove home (about 15 miles) without it coming on, so Ill drive a bit more tonight to see if it turns on after 50. If Im lucky after they disconnected the tank and hoses and reconnected it, it mightve gotten rid of the code. Ill look into the recall after work, i looked all over about this code but couldnt find that anywhere. Thanks a lot brother.

CPT150

after all that, and they didnt tell you anything?

RLXXI

I guess I should have been more specific about what I'm saying, when ever I would hook the FORD SCAN TOOL on a vehicle that had an AFTERMARKET PROGRAMMING installed, the FORD scan tool would give oddball codes because it was seeing software not recognized and would screw up any chance of a diag.

They had to reset the pcm to stock and then run the vehicle until the CEL came back on (code set) and then come in so I could repair the problem.

The custom programming wasn't causing the light to come on or setting any codes, it WAS CAUSING erroneous codes to show up when retrieving fault info with the OEM scan tool.




.