About Diagnostic Trouble Codes

Each diagnostic trouble code is diagnosed by following a specific testing procedure. The diagnostic test procedures contain step-by-step instructions for determining the cause of trouble codes as well as no trouble code problems. It is not necessary to perform all of the tests to diagnose an individual code.

Always begin by reading the diagnostic trouble codes using the DRBIII.

HARD CODE
A diagnostic trouble code that comes back within one cycle of the ignition key is a "hard" code. This means that the defect is there every time the powertrain control module checks that circuit or function. Procedures in this manual verify if the trouble code is a hard code at a the beginning of each test. When it is not a hard code, an "intermittent" test must be performed.

Codes that are for OBDII monitors will not set with just the ignition key on. Comparing these to non-emission codes, they will seem like an intermittent. These codes require a set of parameters to be performed (The DRBIII pre-test screens will help with this for MONITOR codes), this is called a "TRIP". All OBDII DTCs will be set after one or in some cases two trip failures, and the MIL will be turned on. These codes require three successful (no failures) TRIPS to extinguish the MIL, followed by 40 warm-up cycles to erase the code.

INTERMITTENT CODE
A diagnostic trouble code that is not there every time the PCM checks the circuit is an "intermittent" code. Most intermittent codes are caused by wiring or connector problems. Defects that come and go like this are the most difficult to diagnose; they must be looked for under specific conditions that cause them. The following checks may assist you in identifying a possible intermittent problem:

- Visually inspect related wire harness connectors. Look for broken, bent, pushed out, or corroded terminals.
- Visually inspect the related harnesses. Look for chafed, pierced, or partially broken wire.
- Refer to any Hotline Newsletters or technical service bulletins that may apply.
- Use the DRBIII data recorder or co-pilot.
- Use the DRBIII PEP module lab scope.

RESET COUNTER
The reset counter counts the number of times the vehicle has been started since codes were last set, erased, or the battery was disconnected. The reset counter will count up to 255 start counts.

The number of starts helps determine when the trouble code actually happened. This is recorded by the PCM and can be viewed on the DRBIII� as STARTS since set.

When there are no trouble codes stored in memory, the DRBIII will display "NO DTC'S Detected" and the reset counter will show "STARTS since clear = XXX."

HANDLING NO TROUBLE CODE PROBLEMS
Symptom checks cannot be used properly unless the driveability problem characteristic actually happens while the vehicle is being tested.

Select the symptom that most accurately describes the vehicle's driveability problem and then perform the test routine that pertains to this symptom. Perform each routine test in sequence until the problem is found.