2002 JEEP GRAND CHEROKEE key

(M)Malfunction Indicator Lamp (MIL) illuminated during engine operation if this DTC was recorded
(depending if required by CARB and/or EPA). MIL is displayed as an engine icon on instrument panel.
(G)Generator lamp illuminated
Generic Scan
Tool P-CodeDRB Scan Tool Display Brief Description of DTC
P1498 High Speed Rad Fan Ground CTRL
Rly CircuitAn open or shorted condition detected in the control
circuit of the #3 high speed radiator fan control relay.
P1499 Hydraulic cooling fan solenoid circuit An open or shorted condition detected in the cooling fan
control solenoid circuit.
P1594 (G) Charging System Voltage Too High Battery voltage sense input above target charging voltage
during engine operation.
P1594 Charging System Voltage Too High Battery voltage sense input above target charging voltage
during engine operation.
P1595 Speed Control Solenoid Circuits An open or shorted condition detected in either of the
speed control vacuum or vent solenoid control circuits.
P1595 Speed Control Solenoid Circuits An open or shorted condition detected in the speed
control vacuum or vent solenoid circuits.
P1596 Speed Control Switch Always High Speed control switch input above maximum acceptable
voltage.
P1597 Speed Control Switch Always Low Speed control switch input below minimum acceptable
voltage.
P1597 Speed Control Switch Always Low Speed control switch input below the minimum acceptable
voltage.
P1598 A/C Pressure Sensor Volts Too High A/C pressure sensor input above maximum acceptable
voltage.
P1598 A/C Sensor Input Hi Problem detected in air conditioning electrical circuit.
P1599 A/C Pressure Sensor Volts Too Low A/C pressure sensor input below minimum acceptable
voltage.
P1599 A/C Sensor Input Lo Problem detected in air conditioning electrical circuit.
P1602 PCM not programmed
P1680 Clutch Released Switch Circuit Problem detected in clutch switch electrical circuit.
P1681 No I/P Cluster CCD/J1850
Messages ReceivedNo CCD/J1850 messages received from the cluster
control module.
P1682 (G) Charging System Voltage Too Low Battery voltage sense input below target charging voltage
during engine operation and no significant change in
voltage detected during active test of generator output
circuit.
P1682 Charging System Voltage Too Low Charging system output voltage low.
P1683 SPD CTRL PWR Relay; or S/C 12v
Driver CKTAn open or shorted condition detected in the speed
control servo power control circuit.
P1683 Spd ctrl pwr rly, or s/c 12v driver
circuitAn open or shorted condition detected in the speed
control servo power control circuit.
P1684 Batt Loss (disconnected) in last 50
StartsThe battery has been disconnected within the last 50
starts
P1685 SKIM Invalid Key - (Wrong or Invalid
Key MSG Received From SKIM)The engine controler has received an invalid key from the
SKIM.
P1686 No SKIM BUS Messages Received No CCD/J1850 messages received from the Smart Key
Immobilizer Module (SKIM).
25 - 14 EMISSIONS CONTROLWJ
EMISSIONS CONTROL (Continued)

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)

Non-emissions related failures have no priority.
One trip failures of two trip faults have low priority.
Two trip failures or matured faults have higher pri-
ority. One and two trip failures of fuel system and
misfire monitor take precedence over non-fuel system
and non-misfire failures.
DTC Self Erasure
With one trip components or systems, the MIL is
illuminated upon test failure and DTCs are stored.
Two trip monitors are components requiring failure
in two consecutive trips for MIL illumination. Upon
failure of the first test, the Task Manager enters a
maturing code. If the component fails the test for a
second time the code matures and a DTC is set.
After three good trips the MIL is extinguished and
the Task Manager automatically switches the trip
counter to a warm-up cycle counter. DTCs are auto-
matically erased following 40 warm-up cycles if the
component does not fail again.
For misfire and fuel system monitors, the compo-
nent must pass the test under a Similar Conditions
Window in order to record a good trip. A Similar Con-
ditions Window is when engine RPM is within  375
RPM and load is within  10% of when the fault
occurred.
NOTE: It is important to understand that a compo-
nent does not have to fail under a similar window of
operation to mature. It must pass the test under a
Similar Conditions Window when it failed to record
a Good Trip for DTC erasure for misfire and fuel
system monitors.
DTCs can be erased anytime with a DRB III. Eras-
ing the DTC with the DRB III erases all OBD II
information. The DRB III automatically displays a
warning that erasing the DTC will also erase all
OBD II monitor data. This includes all counter infor-
mation for warm-up cycles, trips and Freeze Frame.
Trip Indicator
TheTripis essential for running monitors and
extinguishing the MIL. In OBD II terms, a trip is a
set of vehicle operating conditions that must be met
for a specific monitor to run. All trips begin with a
key cycle.
Good Trip
The Good Trip counters are as follows:
²Specific Good Trip
²Fuel System Good Trip
²Misfire Good Trip
²Alternate Good Trip (appears as a Global Good
Trip on DRB III)
²Comprehensive Components
²Major Monitor
²Warm-Up CyclesSpecific Good Trip
The term Good Trip has different meanings
depending on the circumstances:
²If the MIL is OFF, a trip is defined as when the
Oxygen Sensor Monitor and the Catalyst Monitor
have been completed in the same drive cycle.
²If the MIL is ON and a DTC was set by the Fuel
Monitor or Misfire Monitor (both continuous moni-
tors), the vehicle must be operated in the Similar
Condition Window for a specified amount of time.
²If the MIL is ON and a DTC was set by a Task
Manager commanded once-per-trip monitor (such as
the Oxygen Sensor Monitor, Catalyst Monitor, Purge
Flow Monitor, Leak Detection Pump Monitor, EGR
Monitor or Oxygen Sensor Heater Monitor), a good
trip is when the monitor is passed on the next start-
up.
²If the MIL is ON and any other emissions DTC
was set (not an OBD II monitor), a good trip occurs
when the Oxygen Sensor Monitor and Catalyst Mon-
itor have been completed, or two minutes of engine
run time if the Oxygen Sensor Monitor and Catalyst
Monitor have been stopped from running.
Fuel System Good Trip
To count a good trip (three required) and turn off
the MIL, the following conditions must occur:
²Engine in closed loop
²Operating in Similar Conditions Window
²Short Term multiplied by Long Term less than
threshold
²Less than threshold for a predetermined time
If all of the previous criteria are met, the PCM will
count a good trip (three required) and turn off the
MIL.
Misfire Good Trip
If the following conditions are met the PCM will
count one good trip (three required) in order to turn
off the MIL:
²Operating in Similar Condition Window
²1000 engine revolutions with no misfire
Warm-Up Cycles
Once the MIL has been extinguished by the Good
Trip Counter, the PCM automatically switches to a
Warm-Up Cycle Counter that can be viewed on the
DRB III. Warm-Up Cycles are used to erase DTCs
and Freeze Frames. Forty Warm-Up cycles must
occur in order for the PCM to self-erase a DTC and
Freeze Frame. A Warm-Up Cycle is defined as fol-
lows:
²Engine coolant temperature must start below
and rise above 160É F
²Engine coolant temperature must rise by 40É F
²No further faults occur
25 - 22 EMISSIONS CONTROLWJ
EMISSIONS CONTROL (Continued)

²No engine stall during test.
NOTE: IF BATTERY VOLTAGE DROPS BELOW 10
VOLTS FOR MORE THAN 5 SECONDS DURING
ENGINE CRANKING, THE EVAP LEAK DETECTION
TEST WILL NOT RUN.
NOTE: THE FOLLOWING VALUES ARE APPROXI-
MATE AND VEHICLE SPECIFIC. USE THE VALUES
SEEN IN PRE TEST/MONITOR TEST SCREEN ON
THE DRB IIIT. SEE TSB 25-02-98 FOR MORE
DETAIL.
A DTC will not be set if a one-trip fault is set or if
the MIL is illuminated for any of the following:
²Purge Solenoid Electrical Fault
²All TPS Faults
²All Engine Controller Self Test Faults
²LDP Pressure Switch Fault
²All Cam and/or Crank Sensor Fault
²EGR Solenoid Electrical Fault
²All MAP Sensor Faults
²All Injector Faults
²Ambient/Battery Temperature Sensor Electrical
Faults²Baro Out of Range
²Vehicle Speed Faults
²All Coolant Sensor Faults
²LDP Solenoid Circuit
NOTE: IF BATTERY TEMPERATURE IS NOT WITHIN
RANGE, OR IF THE ENGINE COOLANT TEMPERA-
TURE IS NOT WITHIN A SPECIFIED RANGE OF THE
BATTERY TEMPERATURE, THE PCM WILL NOT
RUN TESTS FOR DTC P1494, P1486, P0442, P0455
AND P0441. THESE TEMPERATURE CALIBRATIONS
MAY BE DIFFERENT BETWEEN MODELS.
SECTION 1 - P1495 Leak Detection Pump
Solenoid Circuit-When the ignition key is turned
to9ON9, the LDP diaphragm should be in the down
position and the LDP reed switch should be closed. If
the EVAP system has residual pressure, the LDP dia-
phragm may be up. This could result in the LDP reed
switch being open when the key is turned to9ON9
and a P1494 fault could be set because the PCM is
expecting the reed switch to be closed.
After the key is turned9ON9, the PCM immedi-
ately tests the LDP solenoid circuit for electrical
faults. If a fault is detected, DTC P1495 will set, the
Fig. 15 DIAPHRAGM DOWNWARD MOVEMENT
1 - Diaphragm
2 - Inlet Check Valve (Closed)
3 - Vent Valve (Closed)
4 - From Air Filter
5 - To Canister
6 - Outlet Check Valve (Open)
7 - Engine Vacuum (Closed)EVAP LDP TEST SEQUENCE
1 - IGNITION SWITCH
2 - LDP DIAPHRAM
3 - LDP SWITCH
4 - LDP SOLENOID
5 - SECTION 1
6 - SECTION 2
7 - SECTION 3
8 - SECTION 4
9 - SECTION 5
10 - 3 TEST CYCLES TO TEST FOR BLOCKAGE
11- RAPID PUMP CYCLING FOR 70 CYCLES
WJEVAPORATIVE EMISSIONS 25 - 33
LEAK DETECTION PUMP (Continued)

MIL will illuminate, and the remaining EVAP Leak
Detection Test is canceled.
SECTION 2 - P1494 Leak Detection Pump
Switch or Mechanical Fault-If DTC P1495 is not
set, the PCM will check for DTC P1494. If the LDP
reed switch was closed when the key was turned to
9ON9, the PCM energizes the LDP solenoid for up to
8 seconds and monitors the LDP switch. As the LDP
diaphragm is pulled up by engine vacuum, the LDP
reed switch should change from closed to open. If it
does not, the PCM sets a temporary fault (P1494) in
memory, and waits until the next time the Enabling
Conditions are met to run the test again. If this is
again detected, P1494 is stored and the MIL is illu-
minated. If the problem is not detected during the
next enabling cycle, the temporary fault will be
cleared.
However, if the PCM detects the reed switch open
when the key is turned to9ON9, the PCM must deter-
mine if this condition is due to residual pressure in
the EVAP system, or an actual fault. The PCM stores
information in memory on EVAP system purging
from previous engine run or drive cycles.
If little or no purging took place, residual pressure
could be holding the LDP diaphragm up, causing the
LDP switch to be open. Since this is not a malfunc-
tion, the PCM cancels the EVAP Leak Detection Test
without setting the temporary fault.
If there was sufficient purging during the previous
cycle to eliminate EVAP system pressure, the PCM
judges that this is a malfunction and sets a tempo-
rary fault in memory. The next time that the
Enabling Conditions are met, the test will run again.
If the fault is again detected, the MIL will illuminate
and DTC P1494 will be stored. If the fault is not
detected, the temporary fault will be cleared.
SECTION 3 - P1486 EVAP Leak Monitor
Pinched Hose Found-If no fault has been detected
so far, the PCM begins testing for possible blockage
in the EVAP system between the LDP and the fuel
tank. This is done by monitoring the time required
for the LDP to pump air into the EVAP system dur-
ing two to three pump cycles. If no blockage is
present, the LDP diaphragm is able to quickly pump
air out of the LDP each time the PCM turns off the
LDP solenoid. If a blockage is present, the PCM
detects that the LDP takes longer to complete each
pump cycle. If the pump cycles take longer than
expected (approximately 6 to 10 seconds) the PCM
will suspect a blockage. On the next drive when
Enabling Conditions are met, the test will run again.
If blockage is again detected, P1486 is stored, and
the MIL is illuminated.
SECTION4-NoDTCCanBeSetDuring This
Time-After the LDP blockage tests are completed,
the PCM then tests for EVAP system leakage. First,the PCM commands the LDP to rapidly pump for 20
to 50 seconds (depending on fuel level) to build pres-
sure in the EVAP system. This evaluates the system
J18-24-0 to see if it can be sufficiently pressurized.
This evaluation (rapid pump cycling) may occur sev-
eral times prior to leak checking. The LDP reed
switch does not close and open during rapid pumping
because the diaphragm does not travel through its
full range during this part of the test.
SECTION 5 - P0456, P0442, P0455 EVAP Leak
Monitor and Leak Detected-Next, the PCM per-
forms one or more test cycles by monitoring the time
required for the LDP reed switch to close (diaphragm
to drop) after the LDP solenoid is turned off.
If the switch does not close, or closes after a long
delay, it means that the system does not have any
significant leakage and the EVAP Leak Detection
Test is complete.
However, if the LDP reed switch closes quickly,
there may be a leak or the fuel level may be low
enough that the LDP must pump more to finish pres-
surizing the EVAP system. In this case, the PCM will
rapidly pump the LDP again to build pressure in the
EVAP system, and follow that by monitoring the time
needed for several LDP test cycles. This process of
rapid pumping followed by several LDP test cycles
may repeat several times before the PCM judges that
a leak is present.
When leaks are present, the LDP test cycle time
will be inversely proportional to the size of the leak.
The larger the leak, the shorter the test cycle time.
The smaller the leak, the longer the test cycle time.
DTC's may be set when a leak as small as 0.5 mm
(0.0209) diameter is present.
If the system detects a leak, a temporary fault will
be stored in PCM memory. The time it takes to detect
a .020, .040, or Large leak is based on calibrations
that vary from model to model. The important point
to remember is if a leak is again detected on the next
EVAP Leak Detection Test, the MIL will illuminate
and a DTC will be stored based on the size of leak
detected. If no leak is detected during the next test,
the temporary fault will be cleared.
DIAGNOSTIC TIPS During diagnosis, you can
compare the LDP solenoid activity with the monitor
sequence in Figure 6. If the PCM detects a problem
that could set a DTC, the testing is halted and LDP
solenoid activity will stop. As each section of the test
begins, it indicates that the previous section passed
successfully. By watching to see which tests complete,
you can see if any conditions are present that the
PCM considers abnormal.
For example, if the LDP solenoid is energized for
the test cycles to test for blockage (P1486), it means
that the LDP has already passed its test for P1494.
Then, if the PCM detects a possible blockage, it will
25 - 34 EVAPORATIVE EMISSIONSWJ
LEAK DETECTION PUMP (Continued)