Ford ABS PID won't work

[OxJaw]

Vehicle is a 99 Ford F150 4.6L 4x4

From the email I sent to PPE support

I am trying to read the ABS wheel speed sensors on a 1999 Ford F150 4.6L 4X4. When I located the PID's for these in the menu they show as not supported. I have read them on various other scan tools but cannot seem to read them with your software. I have the ScanXL Pro and Ford Enhanced Add-on. Am I doing something wrong or are they not supported in your software, and if that is the case why not? They were listed on the supported PID's table I found on your website.

This is the response I got

Our software supports this. First make sure you vehicle is configured in the Vehicle Manager. Connect to your vehicle,  then go to Settings > PID Config and click on Validate PIDs. If this  doesn't help you could try deleting and re-creating your vehicle, and validate your PIDs again. Let me know if this helps.

Let me know if you have additional questions.
Regards,
PPE Support

I did exactly what they said to do and it still will not work. I sent them several more email and got nothing in return.

Any help would be greatly appreciated.

Thanks in advance.

[OxJaw]

Well I finally got a response and I can say I am very very pissed off. How can they advertise something and then tell me that "Unfortunately, we can't know what PIDs a vehicle will support without actually connecting to it and checking" This is bullshit, I have checked these sensors on numerous other scanners so I know the vehicle supports it. What a cop-out.

Here's the email I got
No vehicle supports every PID. If you still aren't getting wheel speed
data after an aggressive validation, chances are your vehicle just doesn't
support those PIDs. Unfortunately, we can't know what PIDs a vehicle will
support without actually connecting to it and checking.

Regards,
Weston

They don't bother to tell you that before you drop $300 on their software.

[BrianP]

I'm sorry you feel that way, but it is true - we cannot know beforehand exactly what set of PIDs is supported by your vehicle. This is stated on our website. For instance, on this page:

http://www.palmerperformance.com/support/supported_vehicles/ford_enhanced.php

right at the top it says "Some parameters may not be supported by all vehicles." But this is hardly unexpected. Suppose we have support for, I don't know, cruise control PIDs, and you use it on one vehicle and the PIDs work, but then you try it on another vehicle (could even be of the exact same make and model) they still may not work, especially if the second car didn't include a cruise control option.

But that's just an example. There are many reasons why this could happen. Perhaps you didn't connect to the correct diagnostic system? It is also possible that there is a bug in our software. In any case, you would have to work with us to figure out what is going wrong. I would be interested to hear what other scanner you were able to get these PIDs on, and what vehicle ECU they came from. That could help us determine if we have a bug in our system.

[OxJaw]

The other scanners I used in the past were a Snap-on Solus scanner that was borrowed from a friend and also a Cornwell tools scanner that was also borrowed. I read them on the exact same truck that I am trying to use your software on. When I read them I could see the MPH for the front two ABS sensors and the one rear sensor, each sensor was read individually.

[Bullitt54]

I  have had the same issue on a Ford Explorer, I was attempting to troubleshoot a problem with Select Trac RSC system. The wheel sensors would not validate . I tried using both Palmer ELM and Drewtech Mongoose cables. Bummer