2003 JEEP GRAND CHEROKEE Stored codes

HISTORICAL FAULT CODES
Input faults 33 = IR thermister circuit was open
34 = IR thermister circuit was shorted
35 = Fan pot was shorted
36 = Fan pot was open
37 = Mode pot was shorted
38 = Mode pot was open
39 = IR sensor delta was too large
40 = Reserved
41 = Reserved
42 = One of four motor drivers had drive9A9shorted to
ground
43 = Engine air intake temperature Buss message
missing
44 = Country code Buss message missing
System Faults 45 = Mode motor was not responding
46 = AI (Recirc) motor was not responding
47 = Left temperature door was not responding
48 = Right temperature door was not responding
49 = Mode door travel range too small
50 = Mode door travel range too large
51 = AI (Recirc) door travel range too small
52 = AI (Recirc) door travel range too large
53 = Left temperature door travel too small
54 = Left temperature door travel too large
55 = Right temperature door travel too small
56 = Right temperature door travel too large
57 = Calibration check sum error
58 = Engine coolant temp bus message missing
59 = Vehicle speed bus message missing
60 = Engine RPM bus message missing
61 = OAT bus message missing
62 = Display intensity bus message missing
63 = VIN number bus message missing
64 = Raw OAT bus message was missing
65 = Reserved
66 = Reserved
67 = Reserved
NOTE: A battery disconnect will erase all faults
stored in Random Access Memory (RAM) of the
AZC control module. It is recommended that all
faults be recorded before they are erased.RETRIEVING FAULT CODES
(1) To begin the fault code tests, depress the A/C
and Recirc buttons at the same time and rotate the
left temperature control knob clockwise (CW) one
detent, then release the push-button.
24 - 20 CONTROLSWJ
A/C HEATER CONTROL (Continued)

EMISSIONS CONTROL
TABLE OF CONTENTS
page page
EMISSIONS CONTROL
DESCRIPTION
DESCRIPTION - EMISSION CONTROL
SYSTEM.............................1
DESCRIPTION - STATE DISPLAY TEST
MODE...............................2
DESCRIPTION - CIRCUIT ACTUATION TEST
MODE...............................2
DESCRIPTION - DIAGNOSTIC TROUBLE
CODES..............................2DESCRIPTION - TASK MANAGER.........17
DESCRIPTION - MONITORED SYSTEMS . . . 17
DESCRIPTION - TRIP DEFINITION........19
DESCRIPTION - COMPONENT MONITORS . . 19
DESCRIPTION - NON-MONITORED
CIRCUITS...........................20
DESCRIPTION - HIGH AND LOW LIMITS . . . 20
DESCRIPTION - LOAD VALUE...........20
OPERATION - TASK MANAGER............21
EVAPORATIVE EMISSIONS................24
EMISSIONS CONTROL
DESCRIPTION
DESCRIPTION - EMISSION CONTROL SYSTEM
The Powertrain Control Module (PCM) monitors
many different circuits in the fuel injection, ignition,
emission and engine systems. If the PCM senses a prob-
lem with a monitored circuit often enough to indicate an
actual problem, it stores a Diagnostic Trouble Code
(DTC) in the PCM's memory. If the code applies to a
non-emissions related component or system, and the
problem is repaired or ceases to exist, the PCM cancels
the code after 40 warm-up cycles. Diagnostic trouble
codes that affect vehicle emissions illuminate the Mal-
function Indicator (check engine) Lamp. Refer to Mal-
function Indicator Lamp in this section.
Certain criteria must be met before the PCM
stores a DTC in memory. The criteria may be a spe-
cific range of engine RPM, engine temperature,
and/or input voltage to the PCM.
The PCM might not store a DTC for a monitored cir-
cuit even though a malfunction has occurred. This may
happen because one of the DTC criteria for the circuit
has not been met.For example
,assume the diagnostic
trouble code criteria requires the PCM to monitor the
circuit only when the engine operates between 750 and
2000 RPM. Suppose the sensor's output circuit shorts to
ground when engine operates above 2400 RPM (result-
ing in 0 volt input to the PCM). Because the condition
happens at an engine speed above the maximum thresh-
old (2000 rpm), the PCM will not store a DTC.
There are several operating conditions for which
the PCM monitors and sets DTC's. Refer to Moni-
tored Systems, Components, and Non-Monitored Cir-
cuits in this section.Technicians must retrieve stored DTC's by connect-
ing the DRB scan tool (or an equivalent scan tool) to
the 16±way data link connector (Fig. 1).
NOTE: Various diagnostic procedures may actually
cause a diagnostic monitor to set a DTC. For
instance, pulling a spark plug wire to perform a
spark test may set the misfire code. When a repair
is completed and verified, connect the DRB scan
tool to the 16±way data link connector to erase all
DTC's and extinguish the MIL (check engine lamp).Fig. 1 Data Link (Diagnostic) Connector Location
1 - INSTRUMENT PANEL LOWER/LEFT EDGE
2 - DATA LINK CONNECTOR
WJEMISSIONS CONTROL 25 - 1

OPERATION - TASK MANAGER
The Task Manager determines which tests happen
when and which functions occur when. Many of the
diagnostic steps required by OBD II must be per-
formed under specific operating conditions. The Task
Manager software organizes and prioritizes the diag-
nostic procedures. The job of the Task Manager is to
determine if conditions are appropriate for tests to be
run, monitor the parameters for a trip for each test,
and record the results of the test. Following are the
responsibilities of the Task Manager software:
²Test Sequence
²MIL Illumination
²Diagnostic Trouble Codes (DTCs)
²Trip Indicator
²Freeze Frame Data Storage
²Similar Conditions Window
Test Sequence
In many instances, emissions systems must fail
diagnostic tests more than once before the PCM illu-
minates the MIL. These tests are know as 'two trip
monitors.' Other tests that turn the MIL lamp on
after a single failure are known as 'one trip moni-
tors.' A trip is defined as 'start the vehicle and oper-
ate it to meet the criteria necessary to run the given
monitor.'
Many of the diagnostic tests must be performed
under certain operating conditions. However, there
are times when tests cannot be run because another
test is in progress (conflict), another test has failed
(pending) or the Task Manager has set a fault that
may cause a failure of the test (suspend).
²Pending
Under some situations the Task Manager will not
run a monitor if the MIL is illuminated and a fault is
stored from another monitor. In these situations, the
Task Manager postpones monitorspendingresolu-
tion of the original fault. The Task Manager does not
run the test until the problem is remedied.
For example, when the MIL is illuminated for an
Oxygen Sensor fault, the Task Manager does not run
the Catalyst Monitor until the Oxygen Sensor fault is
remedied. Since the Catalyst Monitor is based on sig-
nals from the Oxygen Sensor, running the test would
produce inaccurate results.
²Conflict
There are situations when the Task Manager does
not run a test if another monitor is in progress. In
these situations, the effects of another monitor run-
ning could result in an erroneous failure. If thiscon-
flictis present, the monitor is not run until the
conflicting condition passes. Most likely the monitor
will run later after the conflicting monitor has
passed.
For example, if the Fuel System Monitor is inprogress, the Task Manager does not run the EGR
Monitor. Since both tests monitor changes in air/fuel
ratio and adaptive fuel compensation, the monitors
will conflict with each other.
²Suspend
Occasionally the Task Manager may not allow a two
trip fault to mature. The Task Manager willsus-
pendthe maturing of a fault if a condition exists
that may induce an erroneous failure. This prevents
illuminating the MIL for the wrong fault and allows
more precis diagnosis.
For example, if the PCM is storing a one trip fault
for the Oxygen Sensor and the EGR monitor, the
Task Manager may still run the EGR Monitor but
will suspend the results until the Oxygen Sensor
Monitor either passes or fails. At that point the Task
Manager can determine if the EGR system is actu-
ally failing or if an Oxygen Sensor is failing.MIL Illumination
The PCM Task Manager carries out the illumina-
tion of the MIL. The Task Manager triggers MIL illu-
mination upon test failure, depending on monitor
failure criteria.
The Task Manager Screen shows both a Requested
MIL state and an Actual MIL state. When the MIL is
illuminated upon completion of a test for a third trip,
the Requested MIL state changes to OFF. However,
the MIL remains illuminated until the next key
cycle. (On some vehicles, the MIL will actually turn
OFF during the third key cycle) During the key cycle
for the third good trip, the Requested MIL state is
OFF, while the Actual MIL state is ON. After the
next key cycle, the MIL is not illuminated and both
MIL states read OFF.
Diagnostic Trouble Codes (DTCs)
With OBD II, different DTC faults have different
priorities according to regulations. As a result, the
priorities determine MIL illumination and DTC era-
sure. DTCs are entered according to individual prior-
ity. DTCs with a higher priority overwrite lower
priority DTCs.
Priorities
²Priority 0 ÐNon-emissions related trouble codes
²Priority 1 Ð One trip failure of a two trip fault
for non-fuel system and non-misfire.
²Priority 2 Ð One trip failure of a two trip fault
for fuel system (rich/lean) or misfire.
²Priority3ÐTwotrip failure for a non-fuel sys-
tem and non-misfire or matured one trip comprehen-
sive component fault.
²Priority4ÐTwotrip failure or matured fault
for fuel system (rich/lean) and misfire or one trip cat-
alyst damaging misfire.
WJEMISSIONS CONTROL 25 - 21
EMISSIONS CONTROL (Continued)