Ect sensor JEEP GRAND CHEROKEE 2003 WJ / 2.G Workshop Manual

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)

Freeze Frame Data Storage
Once a failure occurs, the Task Manager records
several engine operating conditions and stores it in a
Freeze Frame. The Freeze Frame is considered one
frame of information taken by an on-board data
recorder. When a fault occurs, the PCM stores the
input data from various sensors so that technicians
can determine under what vehicle operating condi-
tions the failure occurred.
The data stored in Freeze Frame is usually
recorded when a system fails the first time for two
trip faults. Freeze Frame data will only be overwrit-
ten by a different fault with a higher priority.
CAUTION: Erasing DTCs, either with the DRB III or
by disconnecting the battery, also clears all Freeze
Frame data.
Similar Conditions Window
The Similar Conditions Window displays informa-
tion about engine operation during a monitor. Abso-
lute MAP (engine load) and Engine RPM are stored
in this window when a failure occurs. There are two
different Similar conditions Windows: Fuel System
and Misfire.
FUEL SYSTEM
²Fuel System Similar Conditions WindowÐ
An indicator that 'Absolute MAP When Fuel Sys Fail'
and 'RPM When Fuel Sys Failed' are all in the same
range when the failure occurred. Indicated by switch-
ing from 'NO' to 'YES'.
²Absolute MAP When Fuel Sys FailÐ The
stored MAP reading at the time of failure. Informs
the user at what engine load the failure occurred.
²Absolute MAPÐ A live reading of engine load
to aid the user in accessing the Similar Conditions
Window.
²RPM When Fuel Sys FailÐ The stored RPM
reading at the time of failure. Informs the user at
what engine RPM the failure occurred.
²Engine RPMÐ A live reading of engine RPM
to aid the user in accessing the Similar Conditions
Window.
²Adaptive Memory FactorÐ The PCM utilizes
both Short Term Compensation and Long Term Adap-
tive to calculate the Adaptive Memory Factor for
total fuel correction.
²Upstream O2S VoltsÐ A live reading of the
Oxygen Sensor to indicate its performance. For
example, stuck lean, stuck rich, etc.
²SCW Time in Window (Similar Conditions
Window Time in Window)Ð A timer used by thePCM that indicates that, after all Similar Conditions
have been met, if there has been enough good engine
running time in the SCW without failure detected.
This timer is used to increment a Good Trip.
²Fuel System Good Trip CounterÐATrip
Counter used to turn OFF the MIL for Fuel System
DTCs. To increment a Fuel System Good Trip, the
engine must be in the Similar Conditions Window,
Adaptive Memory Factor must be less than cali-
brated threshold and the Adaptive Memory Factor
must stay below that threshold for a calibrated
amount of time.
²Test Done This TripÐ Indicates that the
monitor has already been run and completed during
the current trip.
MISFIRE
²Same Misfire Warm-Up StateÐ Indicates if
the misfire occurred when the engine was warmed up
(above 160É F).
²In Similar Misfire WindowÐ An indicator
that 'Absolute MAP When Misfire Occurred' and
'RPM When Misfire Occurred' are all in the same
range when the failure occurred. Indicated by switch-
ing from 'NO' to 'YES'.
²Absolute MAP When Misfire OccurredÐ
The stored MAP reading at the time of failure.
Informs the user at what engine load the failure
occurred.
²Absolute MAPÐ A live reading of engine load
to aid the user in accessing the Similar Conditions
Window.
²RPM When Misfire OccurredÐ The stored
RPM reading at the time of failure. Informs the user
at what engine RPM the failure occurred.
²Engine RPMÐ A live reading of engine RPM
to aid the user in accessing the Similar Conditions
Window.
²Adaptive Memory FactorÐ The PCM utilizes
both Short Term Compensation and Long Term Adap-
tive to calculate the Adaptive Memory Factor for
total fuel correction.
²200 Rev CounterÐ Counts 0±100 720 degree
cycles.
²SCW Cat 200 Rev CounterÐ Counts when in
similar conditions.
²SCW FTP 1000 Rev CounterÐ Counts 0±4
when in similar conditions.
²Misfire Good Trip CounterÐ Counts up to
three to turn OFF the MIL.
²Misfire DataÐ Data collected during test.
²Test Done This TripÐ Indicates YES when the
test is done.
WJEMISSIONS CONTROL 25 - 23
EMISSIONS CONTROL (Continued)

change from opened to closed. If the reed switch
changes too quickly, a leak may be indicated. The
longer it takes the reed switch to change state, the
tighter the evaporative system is sealed. If the sys-
tem pressurizes too quickly, a restriction somewhere
in the EVAP system may be indicated.
PUMPING ACTION
Action : During portions of this test, the PCM uses
the reed switch to monitor diaphragm movement.
The solenoid is only turned on by the PCM after the
reed switch changes from open to closed, indicating
that the diaphragm has moved down. At other times
during the test, the PCM will rapidly cycle the LDP
solenoid on and off to quickly pressurize the system.
During rapid cycling, the diaphragm will not move
enough to change the reed switch state. In the state
of rapid cycling, the PCM will use a fixed time inter-
val to cycle the solenoid. If the system does not pass
the EVAP Leak Detection Test, the following DTCs
may be set:
²P0442 - EVAP LEAK MONITOR 0.0409LEAK
DETECTED
²P0455 - EVAP LEAK MONITOR LARGE LEAK
DETECTED²P0456 - EVAP LEAK MONITOR 0.0209LEAK
DETECTED
²P1486 - EVAP LEAK MON PINCHED HOSE
FOUND
²P1494 - LEAK DETECTION PUMP SW OR
MECH FAULT
²P1495 - LEAK DETECTION PUMP SOLENOID
CIRCUIT
DIAGNOSIS AND TESTING - ENABLING
CONDITIONS TO RUN EVAP LEAK DETECTION
TEST
²Cold start: with ambient temperature (obtained
from modeling the inlet air temperature sensor on
passenger vehicles and the battery temperature sen-
sor on Jeep & Dodge Truck vehicles) between 4É C
(40É F) and 32É C (90É F) for 0.040 leak. Between 4É
C (40É F) and 29É C (85É F) for 0.020 leak.
²Engine coolant temperature within:-12É to -8É C
(10É to 18É F) of battery/ambient.
²Battery voltage between 10 and 15 volts.
²Low fuel warning light off (fuel level must be
between 15% and 85%.
²MAP sensor reading 22 in Hg or above (This is
the manifold absolute pressure, not vacuum).
Fig. 13 LDP AT REST
1 - Diaphragm
2 - Inlet Check Valve (Closed)
3 - Vent Valve (Open)
4 - From Air Filter
5 - To Canister
6 - Outlet Check Valve (Closed)
7 - Engine Vacuum (Closed)
Fig. 14 DIAPHRAGM UPWARD MOVEMENT
1 - Diaphragm
2 - Inlet Check Valve (Open)
3 - Vent Valve (Closed)
4 - From Air Filter
5 - To Canister
6 - Outlet Check Valve (Closed)
7 - Engine Vacuum (Open)
25 - 32 EVAPORATIVE EMISSIONSWJ
LEAK DETECTION PUMP (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)