My message center is giving me two warnings: the amber DSC warning (suspect wheel speed sensors needing a clean) and the red intermittent low coolant from the bad sensor.

However, when I hook up my ODB2 scanner (Craftsman 87702 - should be compatible), I get 1 "pending" fault, and it shows P1000 - ODB diagnostic test isn't completed. The CC test isn't completing, so I need to go finish the drive cycle, and I have searched that and will try it when possible.

My question is: why don't the 2 faults on the message center show up on my tool? Does the general diagnostic cycle have to complete before it will show any other faults? That doesn't seem right, why wouldn't all 3 show?

2nd question: does the ODB scanner need to be plugged in while the drive cycle is performed?

Appreciate any insights! TIA.

 

most generic scanners only read P-codes, they don't read the other codes like brake/transmission/etc. Not sure if low ccolant gives a code

the diagnostic cycle does not need to complete to read codes and no the code reader does not need to be plugged in while the drive cycle is performed.

 

The P1000 is irrelevant to your two faults. You will always see either P1000 (OnBoard Monitoring tests not completed since last memory clear) or P1111 (OnBoard Monitoring tests complete). These are status and not error codes.

You have already determined the cause of the low coolant message so a scan tool is not going to give you any further information on this. To make progress with the "pending" fault, you need to know the actual code that's pending. Your code reader is clearly not capable of doing this.

A "drive cycle" is completed regardless of whether there is a reader plugged into the diagnostic port or not. Many owners would find Jaguar ownership considerably less stressful if they didn't plug in a code reader so often.

Graham

 

FWIW, using the Torque Pro app on my Android phone, and a good OBDII ELM327 bluetooth device, I was able to read the wheel sensor and ABS faults on my '97.