I have a 2001 F350 with a PCM labeled "PMT2".

The SES light is triggered every time I try and pull fault codes using Torque Pro. It has done this since I installed Torque Pro many months ago. Same thing happens in another local member's (2000) truck, although I don't know his PCM version.

I'm very comfortable with the Torque Pro settings that have been detailed in other Torque Pro threads. I have been careful to choose conservative settings, including trying debug mode. I have uninstalled and reinstalled Torque Pro to see if that solves the problem - which it does not.

Question: Has anyone else with a "PMT2" PCM been able to pull fault codes using Torque Pro without tripping the SES light?



I realize another variable may be my OBD2 Bluetooth device.

As an aside, I have removed the AIH and would expect to see a fault code but Torque Pro reports no fault codes.

Thank you.

 

Yup, mine does it too.

Actually not only does it set off the CEL, it also kills the engine sometimes.

Not sure if it's the bluetooth adapter, I have the cheap $20 one, or if it's the Torque Pro software.

Either way, I just use AE for clearing codes, and Torque Pro to quickly monitor engine data.

 

I never had a problem setting the ses. Like DL said it would kill the engine ever time. I had no problems seeing and clearing codes.
I have a cheap $8 dongle form Amazon

 

JOHN2001,

Thank you. Would you happen to know your PCM code? I know the SES light being triggered (or killing the engine) by pulling fault codes in Torque happens to many people but I'm trying to focus on the cause. I have a suspicion the problem is rooted in the PCM. I will be particularly interested in the PCM code for people that don't have this problem. (?Tugly?).

David

 

I suspect it's a bug with Torque. It sets my MIL also. Sometimes it retrieves the codes, sometimes not. With the same (cheap) Bluetooth adapter, Car Gauge Pro functions fine, and doesn't stall the engine either. XLE4 PCM . . .

 

PMT2 same as yours. I wrote it down on the wall I'm my garage a few years ago just in case

 

Well, as best I can tell from my online discussions with Tugly and my online and phone discussions with a few device manufacturers (detailed in another injector buzz thread I hijacked), the problem with Torque and other apps tripping the SES light when pulling fault codes is related to the app sending a request to the ECU/PCM (via mode $09 sensor PID 02) for the truck's VIN. I'm still not sure if the problem applies to all PCMs since I did not get much feedback in this thread. The problem is definitely not unique to cheaply manufactured OBD2 Bluetooth devices.

The ScanTool OBDLink MX device I purchased was a waste of money and produced the same results as my generic device purchased off of EBay. Given my experience with the ScanTool device, the poor customer service, and the relative high cost, I am going to go on record and say I would discourage purchasing the ScanTool device. I am attempting to return the ScanTool device but theyare also making that process difficult.

As far as correcting the problem, I have sent an email to Ian at Torque and further posted the issue and potential correction in the Torque forums. I don't know if my post or email will get any traction.

I am also working with the developer of a vehicle tracking device (that uses the OBD interface) to see if the VIN info can be obtained via another source (such as the manufacturers proprietary modes (eg, Ford's mode 22). If that proves possible, I may also suggest to Torque to consider adopting that approach.

I'll post again as appropriate but am still interested in having other Torque users post their PCM code and whether Torque trips the SES light when pulling fault codes. Again, I'm curious if the problem is unique to PCM code PMT2.

David

 

My PCM




TorquePro ALWAYS stalls the engine when pulling DTCs.

On both AE and TP, clearing DTCs puts the truck into some funky mode. I noticed it at first when starting after a clear, but recently did a clear, then ran a buzz test (AE for both), which FAILED on a few cylinders

I cycled the key, disconnected and reconnected AE, then ran a buzz test again- perfect.

So I'd say YES, there is some extra junk floating around on the bus in these programs.

When clearing DTCs with either program, my Excursion does some clicks of relays and makes an odd sound and a sigh.

 

I know that click and sigh sound well. 😀. Sounds like a puff.