OBD II on 2000 Tioga with 1999 Ford V10?

[sam-rv]

Has anyone had any problems hooking up a scan tool to get the trouble codes on a 1999 Ford V10 Class C chassiss? I have a Service Engine Soon light that came on and stayed on and I tried to connect a OBDII scan tool as well as Autel MaxiTrip TP100 4-In-1 Auto Computer to it and both would not communicate or get info from the truck. I know I plugged it in the right port which had a cover that says Data Link on it.
Just wondering if there's something wrong with my data port of if I need any special connector or tool to read it.

Thanks for any info.
Sam.

[Talons]

There can be two different connections for the odb io.
One is under the dash, the other can be under the hood.

You could be connecting to a terminal that is not really active.

Other than that, verify that power is coming out the connection from the vehicle, if not then you have the wrong connector.

If you find that to be the only connector and power to be coming out of it, and the reader still does not work, then have an autoshop read it and show you what they do so you can do it next time.

Talons
Good Luck and keep us posted.

[sam-rv]

I just took a look under the hood and I don't see any other connector. The label in the engine compartment says that it is OBD I compliant. I'm gessing that means it does not have OBD II and I would have to use an OBD I scan method and tool?
Is there a sequence we can do with the key to get the codes?

Thanks.
Sam

[TXiceman]

The scan tool is powered from the OBD II port which is generally on the same circuit as the cigarette lighter. Check for a blown fuse or bad connection.

ken

[Talons]

Obd I is not that standardized.

Is there power in the connector?

Talons

[Lt46]

To my knowledge an OBD 2 scan tool will not work on an OBD 1 system. You'll need a OBD 1 compliant scanner.

[sam-rv]

Well I checked and yes there's power on the connector.
I was able to borrow a scan tool from a friend that can read OBD I & II and it came back with the code P0705 (Transmission Range Sensor Circuit (PRNDL Input)) and some threads I have been reading suggests trying to replace the TRS switch and that it should fix the problem.
Will let you know if it turns out to be that switch or sensor.

Kind of a bummer though about the Ford being only OBD I as I was hoping to get on of those ScanGuageII tools to install and be able to monitor gas milage and other things

Thanks for all the replies.

Sam

[angelino1]

Quote:

Originally Posted by sam-rv Has anyone had any problems hooking up a scan tool to get the trouble codes on a 1999 Ford V10 Class C chassiss? I have a Service Engine Soon light that came on and stayed on and I tried to connect a OBDII scan tool as well as Autel MaxiTrip TP100 4-In-1 Auto Computer to it and both would not communicate or get info from the truck. I know I plugged it in the right port which had a cover that says Data Link on it. Just wondering if there's something wrong with my data port of if I need any special connector or tool to read it. Thanks for any info. Sam.

According to auto tap starting in 1996 all vehicles were supposed to be OBDll compliant.
Auto tap is an electronics firm that sells all diagnostic tools and can be viewed on the web. They have a free tech library on thhe web and it's worth looking at.
Tony

[angelino1]

Quote:

Originally Posted by sam-rv Has anyone had any problems hooking up a scan tool to get the trouble codes on a 1999 Ford V10 Class C chassiss? I have a Service Engine Soon light that came on and stayed on and I tried to connect a OBDII scan tool as well as Autel MaxiTrip TP100 4-In-1 Auto Computer to it and both would not communicate or get info from the truck. I know I plugged it in the right port which had a cover that says Data Link on it. Just wondering if there's something wrong with my data port of if I need any special connector or tool to read it. Thanks for any info. Sam.

www.autotap.com is the link that will answer most diagnostic questions.
Tony