I have a 2000 F250, auto, box stock except for air cleaner and have just tried Torque Pro for the first time today. I'm using an OBDlink MX feeding to a Samsung Tab A 8.0 tablet with the latest Android operating system, 7.1 Nougat.

Anyway I paired the two and tried the KOEO and everything lit up except that it said it couldn't see the ECU. I went through the setup and checked the ford option and added HPOP, IPR duty, Boost(MAP), ECT, TCT,Barometer, EBP, EOT, TCSlip, ECT, and RPM. Just for fun I cranked it up and most everything worked. The ECT didn't and the Barormeter didn't which was strange because my temp gauge on the dash works fine. After a 14 mile run all the working gauges gave me good reading; ICP(HPOP) idled at ~500 and went to 2850 during ride, Tranny temp never got over 142(just put in new cooler),EOT ran up to 196, Tranny slip showed the TC locking up, IPR duty maxed at 40%, boost was up to 15 lbs, and RPM was dead on with my Tach.

When I got back I switched screens to adapter status and saw that it was showing a connection to ECU but the engine died when that screen was pulled up. I switched back to Home screen and it cranked right up and when I switched to Realtime info all the gauges were working as before.

The program failed to read my truck and establish a profile so I filled one in but once again with KOEO it couldn't see the ECU(PCM). I have a ohp ELMconfig wired adapter that I use to run Forscan on a laptop and it seems to do fine with all the sensors ( it told me the EBP sensor was wonkey and the Torque program showed an unchanging reading). I'm guessing I have a wiring problem between the diagnostic port and the PCM and was wondering if anyone had the wiring diagram for the two plugs so I could check continuity. Any other thoughts on this problem would be appreciated.
Thanks,
Lewis

 

1. The ECT is not connected to the PCM - it just goes to the gauge on the dash. Therefore, you can't get it on the OBDII port.
2. BARO is primarily used for just checking EBP and MAP sensors during a specific test, and I have seen the sensor not work on the OBDII port on some trucks.
3. An engine stall usually means an illegal command took place or an invalid PID is active. It will almost certainly stall if you scan for codes - that is best done KOEO.
4. There is no problem between the diagnostics port and the PCM, or you never would have gotten any of the PIDs. There is likely a problem between the EBP sensor and the PCM.

 

Tugly,
Thanks for the info. When I fix my oil leaks in the valley area I plan on changing out the EBP sensor and tube so hopefully that problem will go away. I'm glad I don't have to chase wires at this point, did enough of that while working in shops, still brings back bad memories.
Lewis

 

My truck stalls as well if I try to check the adapter status with the truck running. So I don't think that is unusual.

Greg