1998 DODGE RAM 1500 Emission

OPERATION
OPERATION
The Powertrain Control Module (PCM) monitors
many different circuits in the fuel injection, ignition,
emission and engine systems. If the PCM senses a
problem 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
problem is repaired or ceases to exist, the PCM can-
cels the code after 40 warm-up cycles. Diagnostic
trouble codes that affect vehicle emissions illuminate
the Malfunction Indicator Lamp (MIL). The MIL is
displayed as an engine icon (graphic) on the instru-
ment panel. Refer to Malfunction 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
circuit 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 (resulting in 0 volt input to the
PCM). Because the condition happens at an engine
speed above the maximum threshold (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. The connector is
located on the bottom edge of the instrument panel
near the steering column (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.
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 TaskManager 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.
Fig. 1 DATA LINK CONNECTOR LOCATION - TYPICAL
1 - 16-WAY DATA LINK CONNECTOR
DREMISSIONS CONTROL 25 - 5
EMISSIONS CONTROL (Continued)

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 in
progress, 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 MILL 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.
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.
25 - 6 EMISSIONS CONTROLDR
EMISSIONS CONTROL (Continued)

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 Cycles
Specific 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 misfireWarm-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
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.
DREMISSIONS CONTROL 25 - 7
EMISSIONS CONTROL (Continued)

²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 the
PCM 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.
OPERATION - 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.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 injector
is 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.
25 - 8 EMISSIONS CONTROLDR
EMISSIONS CONTROL (Continued)

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 AIR FLOW
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.
DREMISSIONS CONTROL 25 - 9
EMISSIONS CONTROL (Continued)

EVAPORATIVE EMISSIONS
TABLE OF CONTENTS
page page
EVAPORATIVE EMISSIONS
DESCRIPTION - EVAP SYSTEM............10
SPECIFICATIONS
TORQUE - EVAP SYSTEM...............11
CCV HOSE
DESCRIPTION - 8.0L V-10................12
OPERATION - 8.0L V-10..................12
EVAP/PURGE SOLENOID
DESCRIPTION.........................12
OPERATION...........................12
REMOVAL.............................12
INSTALLATION.........................12
FUEL FILLER CAP
DESCRIPTION.........................13
OPERATION...........................13
REMOVAL
REMOVAL/INSTALLATION...............13
LEAK DETECTION PUMP
DESCRIPTION.........................13
OPERATION...........................14
REMOVAL.............................16
INSTALLATION.........................16ORVR
DESCRIPTION.........................17
OPERATION...........................17
P C V VA LV E
DESCRIPTION.........................17
OPERATION...........................19
DIAGNOSIS AND TESTING - PCV VALVE -
3.7L V-6/ 4.7L V-8......................20
REMOVAL.............................21
INSTALLATION.........................21
VACUUM LINES
DESCRIPTION.........................22
VAPOR CANISTER
DESCRIPTION.........................22
OPERATION...........................22
REMOVAL.............................22
INSTALLATION.........................22
NATURAL VAC LEAK DETECTION ASSY
DESCRIPTION.........................23
OPERATION...........................23
REMOVAL.............................24
INSTALLATION.........................25
EVAPORATIVE EMISSIONS
DESCRIPTION - EVAP SYSTEM
The evaporation control system prevents the emis-
sion of fuel tank vapors into the atmosphere. When
fuel evaporates in the fuel tank, the vapors pass
through vent hoses or tubes into the two charcoal
filled evaporative canisters. The canisters tempo-
rarily hold the vapors. The Powertrain Control Mod-
ule (PCM) allows intake manifold vacuum to draw
vapors into the combustion chambers during certain
operating conditions.
All gasoline powered engines use a duty cycle
purge system. The PCM controls vapor flow by oper-
ating the duty cycle EVAP purge solenoid. Refer to
Duty Cycle EVAP Canister Purge Solenoid for addi-
tional information.When equipped with certain emissions packages, a
Leak Detection Pump (LDP) will be used as part of
the evaporative system. This pump is used as a part
of OBD II requirements. Refer to Leak Detection
Pump for additional information. Other emissions
packages will use a Natural Vacuum Leak Detection
(NVLD) system in place of the LDP. Refer to NVLD
for additional information.
NOTE: The hoses used in this system are specially
manufactured. If replacement becomes necessary, it
is important to use only fuel resistant hose.
Certain EVAP system components can be found in
(Fig. 1).
25 - 10 EVAPORATIVE EMISSIONSDR

SPECIFICATIONS
TORQUE - EVAP SYSTEM
DESCRIPTION N´m Ft. Lbs. In. Lbs.
EVAP Canister Mounting
Nuts11 -95
EVAP Canister Mounting
Bracket-to-Frame Bolts14 10125
Leak Detection Pump
Mounting Bolts11 - 9 5
Leak Detection Pump
Filter Mounting Bolt11 - 9 5
Fig. 1 FUEL DELIVERY COMPONENTS
1 - FUEL TANK 8 - LDP FRESH AIR FILTER
2 - CHECK VALVE 9 - LEAK DETECTION PUMP
3 - LIQUID EXPANSION CHAMBER 10 - EVAP CANISTERS (2)
4 - FUEL FILTER / FUEL PRESSURE REGULATOR 11 - FUEL TANK STRAPS (2)
5 - QUICK-CONNECT FITTING AND FUEL LINE (TO ENGINE) 12 - CHECK VALVE
6 - EVAP LINE CONNECTION 13 - FUEL PUMP MODULE LOCK RING
7 - LEAK DETECTION PUMP FRESH AIR LINE 14 - FUEL PUMP MODULE
DREVAPORATIVE EMISSIONS 25 - 11
EVAPORATIVE EMISSIONS (Continued)

CCV HOSE
DESCRIPTION - 8.0L V-10
The 8.0L V-10 engine is equipped with a Crankcase
Ventilation (CCV) system. The CCV system performs
the same function as a conventional PCV system, but
does not use a vacuum controlled valve (PCV valve).
A molded vacuum tube connects manifold vacuum
to the top of the right cylinder head (valve) cover.
The vacuum tube connects to a fixed orifice fitting
(Fig. 2) of a calibrated size 2.6 mm (0.10 inches).
OPERATION - 8.0L V-10
A molded vacuum tube connects manifold vacuum
to the top of the right cylinder head (valve) cover.
The vacuum tube connects to a fixed orifice fitting
(Fig. 2) of a calibrated size 2.6 mm (0.10 inches). The
fitting meters the amount of crankcase vapors drawn
out of the engine.The fixed orifice fitting is grey
in color.A similar fitting (but does not contain a
fixed orifice) is used on the left cylinder head (valve)
cover. This fitting is black in color. Do not inter-
change these two fittings.
When the engine is operating, fresh air enters the
engine and mixes with crankcase vapors. Manifold
vacuum draws the vapor/air mixture through the
fixed orifice and into the intake manifold. The vapors
are then consumed during engine combustion.
EVAP/PURGE SOLENOID
DESCRIPTION
The duty cycle EVAP canister purge solenoid is
located in the engine compartment. It is attached to
the side of the Power Distribution Center (PDC).
OPERATION
The Powertrain Control Module (PCM) operates
the solenoid.
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 ener-
gizes and de-energizes the solenoid 5 or 10 times per
second, depending upon operating conditions. The
PCM varies the vapor flow rate by changing solenoid
pulse width. Pulse width is the amount of time the
solenoid energizes. The PCM adjusts solenoid pulse
width based on engine operating condition.
REMOVAL
The duty cycle EVAP canister purge solenoid is
located in the engine compartment. It is attached to
the side of the Power Distribution Center (PDC) (Fig.
3).
(1) Disconnect electrical wiring connector at sole-
noid.
(2) Disconnect vacuum harness at solenoid (Fig. 3).
(3) Remove solenoid from mounting bracket.
INSTALLATION
(1) Install solenoid assembly to mounting bracket.
(2) Connect vacuum harness.
(3) Connect electrical connector.
Fig. 2 FIXED ORIFICE FITTING - 8.0L V-10 ENGINE -
TYPICAL
1 - VACUUM TUBE
2 - FIXED ORIFICE FITTING
3 - COIL PACKS
4 - ORIFICE FITTING HOSE CONNECTIONS
25 - 12 EVAPORATIVE EMISSIONSDR