Notices
1999 - 2016 Super Duty 1999 to 2016 Ford F250, F350, F450 and F550 Super Duty with diesel V8 and gas V8 and V10 engines
Sponsored by:
Sponsored by: Real Truck

OBD2 Questions

Thread Tools
 
Search this Thread
 
Old Apr 12, 2010 | 05:30 PM
  #1  
5.4L to Freedom's Avatar
5.4L to Freedom
Thread Starter
|
Posting Guru
Joined: Jul 2007
Posts: 1,433
Likes: 2
From: Spring Lake
OBD2 Questions

So I've been having lots of issues with the truck lately, and it hasn't thrown a code. So naturally, I verified the check engine lightbulb is not burned out. On the OBD2 port there is voltage,

But get this, because I dont trust that stupid light... I started unplugging and playing. Here's what I have found:

Disconnected cam sensor: runs and drives exactly the same, no check engine light
Disconnected MAF: barely runs, still no code

Disconnected various coils: barely runs, still no code

Is there anything I can do to make it throw a code? How do I go about troubleshooting something like this? All the repair material I've read is dependant upon codes, and well, without them I can't do too much
 
Reply
Old Apr 13, 2010 | 02:20 AM
  #2  
5.4L to Freedom's Avatar
5.4L to Freedom
Thread Starter
|
Posting Guru
Joined: Jul 2007
Posts: 1,433
Likes: 2
From: Spring Lake
So after doing some research, it turns out on GM vehicles the CEL can be deactivated and certain categories of codes/ all codes can be ignored if that is how the tuner set them up.

Does anyone know if this can be done on a Ford, or if anyone has had experience doing it?

I checked the pinout of my OBD2 (with the Fluke) port and everything is live and working, but for some reason the PCM isn't acknowledging anything that should throw a code~ I'm wondering if perhaps the dealer that sold me the truck deactivated the CEL... it turns out everything else they told me about the truck was a lie.

On the plus side, in the search for my PCM I found receipts behind the glovebox, turns out the truck spent at least a year or two in Miami Gardens.
 
Reply
Old Apr 13, 2010 | 10:42 AM
  #3  
GlamisDude's Avatar
GlamisDude
New User
Joined: Mar 2008
Posts: 8
Likes: 0
I have found that it takes two faults of the same problem in two different run cycles. So to get your code to show, make the problem then shut it off and restart. code should come up.
 
Reply
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
89BlackBeauty
1999 - 2003 7.3L Power Stroke Diesel
41
Apr 4, 2009 01:07 PM
Tomget
1983 - 2012 Ranger & B-Series
10
Sep 18, 2008 11:26 AM
Xdrive
1983 - 2012 Ranger & B-Series
5
Feb 10, 2007 05:58 PM
justbabs
1987 - 1996 F150 & Larger F-Series Trucks
2
Nov 21, 2004 11:06 AM
69crewcab
1999 - 2003 7.3L Power Stroke Diesel
25
Sep 9, 2004 10:31 AM




All times are GMT -5. The time now is 07:54 AM.