I have had the truck a few months now but the engine light does not light up with ignition on or if I unplug a coil pack when it is running. If there a bulb in dash?

 

Yes, there is a check engine light that should come on momentarily when you turn the ignition on. I wonder if the seller pulled the bulb so you wouldn't know there was a problem?

 

It's in this photo between the red lights.

 

I recon he might have, it seems to run ok but it feels restricted when you boot in, and as well as the exhaust noise there is a rushing sound from the exhaust.
it has a roush supercharger fitted

 

I wonder if the rushing sound is the supercharger bypass?

 

I think the rushing sound is coming out of the exhaust which makes me think blocked cats

 

The OBDII system has information in addition to Trouble Codes that might help you with this. If you have, or have access to, an OBDII scanner that can read specific codes.


MIL, Malfunction Indicator Lamp. PID # 1103, One byte in which BIT 5 represents state of MIL. 1 = ON, 0 = OFF.


MIL_DIS, Distance Traveled with MIL ON. PID # 0021, two bytes binary, formula = (A*256)+B, gives you kilometers driven with MIL ON (from 0 to 65,535 Km). This might tell you if the MIL was on when it was sold to you.


If that proved true - don't 'clear' the MIL/DTCs. I'd invest in some forensics on the Instrument Cluster and if it was tampered with, guarantee you the guy that sold it to me would fix everything on that vehicle from bumper to bumper.

 

Thanks F150 i will get codes red. I have a scanner from my 2003 f150 but it comes up with no faults. I will take it to the garage and get them to read it with there snap-on reader

 

Most ANY ole reader will read all codes, so guess that sorta' debunks my suspicion.
The PCM will clear codes itself (after varying number of drive cycles) if the problem is corrected or corrects itself - and MIL would 'go out'. But the parameters I mentioned are instructive to look at, and can be a comforting indication of overall health.


And then there is:
CLRDIST, Distance Traveled since codes cleared, PID # 0031, two bytes binary - formula (A*256)+B = Kilometers travel. This could give some indication if there has been a code since you purchased, and even if the PCM cleared the code.

TRIPCNT, OBD2 Trips Completed, PID # 0100, one byte binary - Count of completed trips where all (about 8) internal OBD diagnostics routines have been successfully completed.


DRIVECNT, OBD2 Drive Cycles, PID # 0101, two bytes binary - formula (A*256)+B = number of engine warmup drive cycles. two bytes formula (A*256)+B


My old truck with 230k miles on her has some impressive (comforting) numbers:
CLRDIST - 18,410 miles
TRIPCNT - 40
DRIVECNT - 1704




EDIT-----------
As I had mentioned - the OBDII system on our trucks has a wealth of information in it, if we can just find it.


I just noticed there is actually a "FAULT" indication for the MIL control circuit. I guess the engineers at FORD considered some wise guy might try to remove the indicator lamp or cut a trace. It seems that circuit's electrical integrity is monitored for opens and shorts. A fault in that circuit will set a DTC P0650. It MAY be a federally mandated indicator as it seems the CODE number is the same for ALL vehicle manufacturers.


Our FORD Truck's OBD has a FLAG BIT assigned in PID # 162E, one byte response, Bit 4, On = MIL Fault. Obviously I have never tested this one! But I note that EVERY bit in that byte represents a 'FAULT' of some kind, so basically it should always be zero.


This should answer your Thread question.