My check engine light came on a few days ago so I decided to get the codes read (usually I would tinker and then reset the computer but.....)
Anyway I went down to one of the local parts stores and asked if they would read the codes.
The fellow had an OBDII scanner on the shelf which he gave to me and I went out to the lot to read the codes.
It wouldn't scan the truck so I went back in and he came out and tried.
Same thing, the device read "ErPr".
I thanked him for his time and went to another parts store on the way out of town.
Same thing. The device does not react in any way being hooked to my truck.
So I reset the computer (and waited a couple of minutes at idle) and drove home.
The idle had settled down as it was jumping around a bit this winter and the light is off.
I have never had a diagnostic plug fail on any of my vehicles.
Is there some special trick to this 1999Ford?

 

Now that I think about this, does erpr stand for power to the test port?

I wonder if there is a fuse for the port.

 

Did you ask if their OBD-II reader was capable of reading your OBD-I truck?

 

Aren't all vehicles after 1996 OBD II?

 

Over 8500 lbs, the V10, and I assume the 5.4, do NOT do lots of things.

One thing they DO do (do do do ) right is to communicate the same way as the OBD-II.

That doesn't mean the reader isn't doing something that's not supported.

Look here:

https://www.ford-trucks.com/forums/5...t-come-on.html

 

The short answer is "no".

The so-called "heavy-duty" vehicles were exempt from that date. My '97 F250 with a 460 was pure OBD-I with the connector under the hood and everything. The early Super Duty was more like an OBD-I system with an OBD-II connector. If you look at the emissions sticker under the hood, it'll probably still say the vehicle is OBD-I... at least I think my '00 model did.

 

The sticker under the hood states my truck is compliant with all Canadian and U.s federal emissions laws for heavy duty engines.

Makes no mention about being OBD I or II.

But the info on one of the previous links says my truck should be OBD I with the same connector as the OBD II trucks so the scanner should be able to link to my truck. And this is the problem I'm having as it will not link.
I am going to borrow an OBD I scanner this weekend to see if it will link up.

 

The OBD I scanner has a different plug so this particular one will not work.
The local Canadian Tire parts store says only a dealer can read it because this truck has an OBD II diagnostic port.
Has anyone had codes read with a handheld aftermarket scanner?
Seeing as I can't buy or borrow one a dealer scan is my only option.
And at $90 an hour.....ouch!

 

Some confusion... OBD-II is a certain connector style, as you found out.

What Ford means by "OBD-I" is that these motors do not have certain monitors (tests).

The PCM reports back OBD-I

I'm wondering if that scan tool just didn't know what to do about finding "OBD-I" as the system type.

Find a good mechanic... if you ask them to scan it and see what's wrong and act like you want a quote, they might do it for nothing.

 

I have a 07 SD V10 and mine had the check engine light come on, and I used my OBDII reader and it also did not connect to the system. Truck is under warrenty so it went to the dealer. I also thought that this was an OBDII truck, I think the OM says that also. Forgot to ask the dealer what was up with that, I may need to go back to get that info.
Jeff

 

05-up is CAN - Car Area Network - there's lots lots more "stuff" in there... I don't think the hand-held off-the-shelf scanners would work with it. Much like the '99 V10, apparently...

 

My '01 X w/ V-10 read just fine using the scanner at Checker Auto. It was an AutoXray product.

My dash has an OBD-II style connector. As to the OBD level of the PCM itself I can't guess.

The scanner did report some tests or data "not supported" but it did fine reading the generic codes.

I don't know if any of the cheap/simple hand held scanners will read the manufacturer specific stuff that is outside the realm of "generic" OBD II, but they should at least connect.

 

After digging around under the dash I found a burnt out fuse for the OBDII port.

After replacing it the scanner will now link. Of course there are no codes to read as I deleted them!

So next time I will get a handle on this once and for all.

 

Thanks for reporting back!

Good luck on getting it the next time ...

Makes you wonder what blew that fuse...