There is a possibility that your truck has never been updated to wake up the OBD II port and capabilities. 94.5's were originally OBD I but if they received a update from the dealer then they switched over to OBD II.

I don't know if a dealer would do this anymore for you or if you are going to have to go to a vendor and have them update the computer. You might check with a dealer and have them run your Vin and see if they can tell if it has been updated and go from there.

 

Yes, this could be the issue and we can flash your PCM to make it OBDII compliant if needed. You would just order a Stock tune flash from here and send us your PCM... https://www.dp-tuner.com/ford-power.../pcm-flash/customer-supplied-pcm-flash-stock-or-optional-performance-flash.html

It could also be due to the bluetooth adapter and/or torque app. I have heard of this stumbling and dying problem many times on the OBS trucks when using those products.

 

Bugman, I will call the dealer in town and see what they say.
Justin, so do I understand right that I would have my truck down for however long it takes to get the pcm to you and then back?
Thanks!

 

Yes, that is correct. That is the downside. However, we normally ship the PCM back out the day after we receive it. We can ship using any method you wish.

 

Actually, your PCM probably IS flashed. If it weren't, your code reader wouldn't communicate at all via the interior diagnostic port. From everything I've read, Torque Pro cannot read codes, it can only read live data. You need CarGauge Pro to read codes. The engine stumbling / stalling when attempting to read codes is a typical sign of attempting to communicate using a generic OBD-II protocol.

 

This^^^^^. I can't read codes with torque.

 

This is interesting to me as I run into this often with Rangers and Explorers. Some 1995 Rangers are EEC IV and some are EEC V = PITA

So can he use the old OBDI code reader method? (count the flashes?)

 

No. "EEC-(whatever)" refers to GASSERS. Our trucks are a modified OBD-II that standard OBD-II devices can't read.

 

I've had good results using the FORScan app. Have you tried reading the codes without the truck running and the key in the start position?


Sent from my iPhone using Tapatalk

 

You want to try it with the key in the RUN position (aka KOEO). In the START position, the starter will crank.

 

You sir are correct, my bad.


Sent from my iPhone using Tapatalk

 

Had the same issue with my 96, not sure what caused it but the two local ford dealers couldnt read it nor could any code puller from any auto parts store. Took it to my father-in-law(mechanic by trade), he had some old a$$ code reader that picked it up. Its probably still running an OBD I system.

 

If that old a$$ reader produced codes that were five characters beginning with a P, it was NOT OBD-I. OBD-I and its cousins all produce only numeric codes, usu. two or three digits, and of course no zeros.

 

Never stated that is was a 5 character code starting with a P. I never asked what it was, just knew that all of the 7 or so OBD II readers I personally tried did not read any codes, which in turn led me to believe it was OBD I.