2003 JEEP GRAND CHEROKEE Code

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)

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)

INSTALLATION - FIXED ORIFICE FITTING
When installing fixed orifice fitting, be sure loca-
tions of fixed orifice fitting and air inlet fitting (Fig.
9) have not been inadvertently exchanged. The fixed
orifice fitting is light grey in color and is located at
rearof valve cover. The air inlet fitting is black in
color and is located atfrontof valve cover.
(1) Connect fitting to CCV breather tube.
(2) Return fixed orifice fitting to valve cover grom-
met.
EVAP/PURGE SOLENOID
DESCRIPTION
The duty cycle EVAP canister purge solenoid (DCP)
regulates the rate of vapor flow from the EVAP can-
ister to the intake manifold. The Powertrain Control
Module (PCM) operates the solenoid.
OPERATION
During the cold start warm-up period and the hot
start time delay, the PCM does not energize the sole-
noid. When de-energized, no vapors are purged. The
PCM de-energizes the solenoid during open loop oper-
ation.
The engine enters closed loop operation after it
reaches a specified temperature and the time delay
ends. During closed loop operation, the PCM cycles
(energizes and de-energizes) the solenoid 5 or 10
times per second, depending upon operating condi-
tions. The PCM varies the vapor flow rate by chang-
ing solenoid pulse width. Pulse width is the amount
of time that the solenoid is energized. The PCM
adjusts solenoid pulse width based on engine operat-
ing condition.
REMOVAL
The duty cycle evaporative (EVAP) canister purge
solenoid is located in the engine compartment near
the brake master cylinder (Fig. 10).
(1) Disconnect electrical connector at solenoid.
(2) Disconnect vacuum lines at solenoid.
(3) Lift solenoid slot (Fig. 10) from mounting
bracket for removal.
INSTALLATION
(1) Position solenoid slot to mounting bracket.
(2) Connect vacuum lines to solenoid. Be sure vac-
uum lines are firmly connected and not leaking or
damaged. If leaking, a Diagnostic Trouble Code
(DTC) may be set with certain emission packages.
(3) Connect electrical connector to solenoid.
FUEL FILLER CAP
DESCRIPTION
The plastic fuel tank filler tube cap is threaded
onto the end of the fuel fill tube. Certain models are
equipped with a 1/4 turn cap.
OPERATION
The loss of any fuel or vapor out of fuel filler tube
is prevented by the use of a pressure-vacuum fuel fill
cap. Relief valves inside the cap will release fuel tank
pressure at predetermined pressures. Fuel tank vac-
uum will also be released at predetermined values.
This cap must be replaced by a similar unit if
replacement is necessary. This is in order for the sys-
tem to remain effective.
CAUTION: Remove fill cap before servicing any fuel
system component to relieve tank pressure. If
equipped with a California emissions package and a
Leak Detection Pump (LDP), the cap must be tight-
ened securely. If cap is left loose, a Diagnostic
Trouble Code (DTC) may be set.
REMOVAL
If replacement of the 1/4 turn fuel tank filler tube
cap is necessary, it must be replaced with an identi-
cal cap to be sure of correct system operation.
Fig. 10 EVAP/PURGE SOLENOID LOCATION
1 - BRAKE MASTER CYLINDER
2 - EVAP SOLENOID
3 - SLOT
4 - ELEC. CONNEC.
5 - VACUUM LINE CONNEC.
6 - TEST PORT
WJEVAPORATIVE EMISSIONS 25 - 29
CCV HOSE (Continued)

Check the vapor/vacuum lines at the LDP, LDP
filter and EVAP canister purge solenoid for
damage or leaks. If a leak is present, a Diagnos-
tic Trouble Code (DTC) may be set.
(2) Connect electrical connector to LDP.
(3) While raising front section of support bracket,
connect LDP wiring clip (Fig. 20).
(4) Install 3 LDP mounting bolts (Fig. 19). Refer to
Torque Specifications.
(5) Join front and rear sections of two-piece sup-
port bracket by installing 3 bolts on bottom of sup-
port bracket (Fig. 17). Do not tighten bolts at this
time.
(6) Install support bracket brace bolt (Fig. 17). Do
not tighten bolt at this time.
(7) Tighten 2 support bracket nuts at frame rail
(Fig. 19). Refer to Torque Specifications.
(8) Tighten 3 support bracket bolts and brace bolt.
Refer to Torque Specifications.
(9) Position stone shield behind left/rear wheel
(Fig. 18). Install new plastic rivets.
ORVR
DESCRIPTION
The ORVR (On-Board Refueling Vapor Recovery)
system consists of a unique fuel tank, flow manage-
ment valve, fluid control valve, one-way check valve
and vapor canister. Certain ORVR components can be
found in (Fig. 1).
OPERATION
The ORVR (On-Board Refueling Vapor Recovery)
system is used to remove excess fuel tank vapors.
This is done while the vehicle is being refueled. Cer-
tain ORVR components can be found in (Fig. 1).
Fuel flowing into the fuel filler tube (approx. 1º
I.D.) creates an aspiration effect drawing air into the
fuel fill tube. During refueling, the fuel tank is
vented to the EVAP canister to capture escaping
vapors. With air flowing into the filler tube, there are
no fuel vapors escaping to the atmosphere. Once the
refueling vapors are captured by the EVAP canister,
the vehicle's computer controlled purge system draws
vapor out of the canister for the engine to burn. The
vapor flow is metered by the purge solenoid so that
there is no, or minimal impact on driveability or
tailpipe emissions.As fuel starts to flow through the fuel fill tube, it
opens the normally closed check valve and enters the
fuel tank. Vapor or air is expelled from the tank
through the control valve and on to the vapor canis-
ter. Vapor is absorbed in the EVAP canister until
vapor flow in the lines stops. This stoppage occurs
following fuel shut-off, or by having the fuel level in
the tank rise high enough to close the control valve.
This control valve contains a float that rises to seal
the large diameter vent path to the EVAP canister.
At this point in the refueling process, fuel tank pres-
sure increases, the check valve closes (preventing liq-
uid fuel from spiting back at the operator), and fuel
then rises up the fuel filler tube to shut off the dis-
pensing nozzle.
PCV VALVE
DIAGNOSIS AND TESTING - PCV VALVE/PCV
SYSTEM - 4.7L
(1) Disconnect PCV line/hose (Fig. 21) by discon-
necting rubber connecting hose at PCV valve fitting.
(2) Remove PCV valve at oil filler tube by rotating
PCV valve downward until locating tabs have been
freed at cam lock (Fig. 21). After tabs have cleared,
pull valve straight out from filler tube.To prevent
damage to PCV valve locating tabs, valve must
be pointed downward for removal. Do not force
valve from oil filler tube.
(3) After valve is removed, check condition of valve
o-ring (Fig. 21). Also, PCV valve should rattle when
shaken.
(4) Reconnect PCV valve to its connecting line/
hose.
(5) Start engine and bring to idle speed.
(6) If valve is not plugged, a hissing noise will be
heard as air passes through valve. Also, a strong vac-
uum should be felt with a finger placed at valve
inlet.
(7) If vacuum is not felt at valve inlet, check line/
hose for kinks or for obstruction. If necessary, clean
out intake manifold fitting at rear of manifold. Do
this by turning a 1/4 inch drill (by hand) through the
fitting to dislodge any solid particles. Blow out the
fitting with shop air. If necessary, use a smaller drill
to avoid removing any metal from the fitting.
WJEVAPORATIVE EMISSIONS 25 - 37
LEAK DETECTION PUMP (Continued)

REMOVAL
The EVAP canister is located behind the left-rear
wheel (Fig. 24). It is attached to a two-piece support
bracket (Fig. 25).
(1) Remove rear bumper facia. Refer to Rear Facia
Removal / Installation in Frame & Bumpers section.
(2) Remove 1 support bracket brace bolt (Fig. 25).
(3) Loosen, but do not remove 2 support bracket
nuts (Fig. 26).
(4) Remove upper/rear support bracket mounting
bolt (Fig. 27).
(5) Carefully lower support bracket assembly to
gain access to vapor / vacuum lines. To prevent dam-
age to lines, suspend bracket assembly with rope or
string.
(6) Disconnect necessary vacuum / vapor lines at
EVAP canister.
(7) Remove EVAP canister mounting bolt (Fig. 28).
(8) Lift canister from support bracket (2 pins are
used to align canister into support bracket)
INSTALLATION
The EVAP canister is located behind the left-rear
wheel (Fig. 24). It is attached to a two-piece support
bracket (Fig. 25).
(1) Position canister to support bracket. Guide 2
alignment pins into support bracket.
(2) Install EVAP canister mounting bolt (Fig. 28).
Refer to Torque Specifications.
(3) Carefully install vapor / vacuum lines to canis-
ter.The vapor/vacuum lines and hoses must be
firmly connected. Check the vapor/vacuum
lines at the LDP, LDP filter and EVAP canister
purge solenoid for damage or leaks. If a leak is
present, a Diagnostic Trouble Code (DTC) may
be set.
Fig. 24 LOCATION, LDP / EVAP CANISTER
1 - LEAK DETECTION PUMP
2 - EVAP CANISTER
Fig. 25 TWO-PIECE SUPPORT BRACKET
1 - TWO-PIECE SUPPORT BRACKET (FRONT)
2 - SUPPORT BRACKET BRACE
3 - TWO-PIECE SUPPORT BRACKET (REAR)
4 - SUPPORT BRACKET ATTACHING BOLTS (3)
5 - SUPPORT BRACKET BRACE BOLT
25 - 40 EVAPORATIVE EMISSIONSWJ
VAPOR CANISTER (Continued)