Codes JEEP GRAND CHEROKEE 2003 WJ / 2.G Owner's Guide

DESCRIPTION - TASK MANAGER
The PCM is responsible for efficiently coordinating
the operation of all the emissions-related compo-
nents. The PCM is also responsible for determining if
the diagnostic systems are operating properly. The
software designed to carry out these responsibilities
is referred to as the 'Task Manager'.
DESCRIPTION - MONITORED SYSTEMS
There are new electronic circuit monitors that
check fuel, emission, engine and ignition perfor-
mance. These monitors use information from various
sensor circuits to indicate the overall operation of the
fuel, engine, ignition and emission systems and thus
the emissions performance of the vehicle.
The fuel, engine, ignition and emission systems
monitors do not indicate a specific component prob-
lem. They do indicate that there is an implied prob-
lem within one of the systems and that a specific
problem must be diagnosed.
If any of these monitors detect a problem affecting
vehicle emissions, the Malfunction Indicator Lamp
(MIL) will be illuminated. These monitors generate
Diagnostic Trouble Codes that can be displayed with
the MIL or a scan tool.
The following is a list of the system monitors:
²Misfire Monitor
²Fuel System Monitor
²Oxygen Sensor Monitor
²Oxygen Sensor Heater Monitor
²Catalyst Monitor
²Leak Detection Pump Monitor (if equipped)
All these system monitors require two consecutive
trips with the malfunction present to set a fault.
Refer to the appropriate Powertrain Diagnos-
tics Procedures manual for diagnostic proce-
dures.
The following is an operation and description of
each system monitor:
OXYGEN SENSOR (O2S) MONITOR
Effective control of exhaust emissions is achieved
by an oxygen feedback system. The most important
element of the feedback system is the O2S. The O2S
is located in the exhaust path. Once it reaches oper-
ating temperature 300É to 350ÉC (572É to 662ÉF), the
sensor generates a voltage that is inversely propor-
tional to the amount of oxygen in the exhaust. The
information obtained by the sensor is used to calcu-
late the fuel injector pulse width. This maintains a
14.7 to 1 Air Fuel (A/F) ratio. At this mixture ratio,
the catalyst works best to remove hydrocarbons (HC),
carbon monoxide (CO) and nitrogen oxide (NOx) from
the exhaust.
The O2S is also the main sensing element for the
Catalyst and Fuel Monitors.The O2S can fail in any or all of the following
manners:
²slow response rate
²reduced output voltage
²dynamic shift
²shorted or open circuits
Response rate is the time required for the sensor to
switch from lean to rich once it is exposed to a richer
than optimum A/F mixture or vice versa. As the sen-
sor starts malfunctioning, it could take longer to
detect the changes in the oxygen content of the
exhaust gas.
The output voltage of the O2S ranges from 0 to 1
volt. A good sensor can easily generate any output
voltage in this range as it is exposed to different con-
centrations of oxygen. To detect a shift in the A/F
mixture (lean or rich), the output voltage has to
change beyond a threshold value. A malfunctioning
sensor could have difficulty changing beyond the
threshold value.
OXYGEN SENSOR HEATER MONITOR
If there is an oxygen sensor (O2S) shorted to volt-
age DTC, as well as a O2S heater DTC, the O2S
fault MUST be repaired first. Before checking the
O2S fault, verify that the heater circuit is operating
correctly.
Effective control of exhaust emissions is achieved
by an oxygen feedback system. The most important
element of the feedback system is the O2S. The O2S
is located in the exhaust path. Once it reaches oper-
ating temperature 300É to 350ÉC (572 É to 662ÉF), the
sensor generates a voltage that is inversely propor-
tional to the amount of oxygen in the exhaust. The
information obtained by the sensor is used to calcu-
late the fuel injector pulse width. This maintains a
14.7 to 1 Air Fuel (A/F) ratio. At this mixture ratio,
the catalyst works best to remove hydrocarbons (HC),
carbon monoxide (CO) and nitrogen oxide (NOx) from
the exhaust.
The voltage readings taken from the O2S sensor
are very temperature sensitive. The readings are not
accurate below 300ÉC. Heating of the O2S sensor is
done to allow the engine controller to shift to closed
loop control as soon as possible. The heating element
used to heat the O2S sensor must be tested to ensure
that it is heating the sensor properly.
The O2S sensor circuit is monitored for a drop in
voltage. The sensor output is used to test the heater
by isolating the effect of the heater element on the
O2S sensor output voltage from the other effects.
LEAK DETECTION PUMP MONITOR (IF EQUIPPED)
The leak detection assembly incorporates two pri-
mary functions: it must detect a leak in the evapora-
WJEMISSIONS CONTROL 25 - 17
EMISSIONS CONTROL (Continued)

an associated limp in will take two trips to illumi-
nate the MIL.
Refer to the Diagnostic Trouble Codes Description
Charts in this section and the appropriate Power-
train Diagnostic Procedure Manual for diagnostic
procedures.
DESCRIPTION - NON-MONITORED CIRCUITS
The PCM does not monitor the following circuits,
systems and conditions that could have malfunctions
causing driveability problems. The PCM might not
store diagnostic trouble codes for these conditions.
However, problems with these systems may cause the
PCM to store diagnostic trouble codes for other sys-
tems or components. For example, a fuel pressure
problem will not register a fault directly, but could
cause a rich/lean condition or misfire. This could
cause the PCM to store an oxygen sensor or misfire
diagnostic trouble code
FUEL PRESSURE
The fuel pressure regulator controls fuel system
pressure. The PCM cannot detect a clogged fuel
pump inlet filter, clogged in-line fuel filter, or a
pinched fuel supply or return line. However, these
could result in a rich or lean condition causing the
PCM to store an oxygen sensor or fuel system diag-
nostic trouble code.
SECONDARY IGNITION CIRCUIT
The PCM cannot detect an inoperative ignition coil,
fouled or worn spark plugs, ignition cross firing, or
open spark plug cables.
CYLINDER COMPRESSION
The PCM cannot detect uneven, low, or high engine
cylinder compression.
EXHAUST SYSTEM
The PCM cannot detect a plugged, restricted or
leaking exhaust system, although it may set a fuel
system fault.
FUEL INJECTOR MECHANICAL MALFUNCTIONS
The PCM cannot determine if a fuel injector is
clogged, the needle is sticking or if the wrong injectoris installed. However, these could result in a rich or
lean condition causing the PCM to store a diagnostic
trouble code for either misfire, an oxygen sensor, or
the fuel system.
EXCESSIVE OIL CONSUMPTION
Although the PCM monitors engine exhaust oxygen
content when the system is in closed loop, it cannot
determine excessive oil consumption.
THROTTLE BODY AIRFLOW
The PCM cannot detect a clogged or restricted air
cleaner inlet or filter element.
VACUUM ASSIST
The PCM cannot detect leaks or restrictions in the
vacuum circuits of vacuum assisted engine control
system devices. However, these could cause the PCM
to store a MAP sensor diagnostic trouble code and
cause a high idle condition.
PCM SYSTEM GROUND
The PCM cannot determine a poor system ground.
However, one or more diagnostic trouble codes may
be generated as a result of this condition. The mod-
ule should be mounted to the body at all times, also
during diagnostic.
PCM CONNECTOR ENGAGEMENT
The PCM may not be able to determine spread or
damaged connector pins. However, it might store
diagnostic trouble codes as a result of spread connec-
tor pins.
DESCRIPTION - HIGH AND LOW LIMITS
The PCM compares input signal voltages from each
input device with established high and low limits for
the device. If the input voltage is not within limits
and other criteria are met, the PCM stores a diagnos-
tic trouble code in memory. Other diagnostic trouble
code criteria might include engine RPM limits or
input voltages from other sensors or switches that
must be present before verifying a diagnostic trouble
code condition.
DESCRIPTION - LOAD VALUE
ENGINE IDLE/NEUTRAL 2500 RPM/NEUTRAL
All Engines 2% to 8% of Maximum Load 9% to 17% of Maximum Load
25 - 20 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)