View Single Post
  #2  
Old Wed, July 13th, 2011, 01:25 PM
Jackpine's Avatar
Jackpine Jackpine is offline
PHP Groupie
 
Join Date: Nov 2008
Location: Among Elk, Deer and Javalinas on the Mogollon Rim in Aridzona
Posts: 3,243
Jackpine is a name known to allJackpine is a name known to allJackpine is a name known to allJackpine is a name known to allJackpine is a name known to allJackpine is a name known to all
Default

Quote:
Originally Posted by Power Hungry View Post
All the programmers (Gryphon, Evolution, CS, and CTS) have the capability to read the P1000. The question is whether or not the P1000 DTC has been disabled in the calibration. In most cases, the P1000 was shut off to avoid the annoyance of the DTC and also prevent unnecessary tech calls about what the P1000 DTC was. However, this does not affect the system self tests for the OBDII monitors. Those will continue to function as normal, so if the monitors continue to come back as "Not Ready" then there is a problem with one or more emissions related systems.

I will say that performing a drive cycle to reset the monitors can be extremely difficult. There are very specific guidelines that need to be adhered to and sometimes it can take days of driving to get the monitors to clear. With specific fuel levels, temperatures, drive speeds and drive cycles that need to be met, it can be quite a pain. I do think that after 500 miles of driving, if the system hasn't cleared itself then there really is a problem with the vehicle. Unfortunately, OBDII monitors aren't something that can be forced, faked, or bypassed.

Take care.
Bill, my comment about the P1000 code was based on my NEVER seeing it when returning the truck to stock while I was still using my old Gryphon. And yes, I looked for it. But, it showed up at stock when I started using the CTS. And, as you say, it certainly did not clear quickly when the truck was at stock either.

- Jack
Reply With Quote