sensor DODGE RAM SRT-10 2006 Service Repair Manual

COMPONENT MONITORS
There are several components that will affect vehicle emissions if they malfunction. If one of these components
malfunctions the Malfunction Indicator Lamp (MIL) will illuminate.
Some of the component monitors are checking for proper operation of the part. Electrically operated components
now have input (rationality) and output (functionality) checks. Previously, a component like the Throttle Position sen-
sor (TPS) was checked by the PCM for an open or shorted circuit. If one of these conditions occurred, a DTC was
set. Now there is a check to ensure that the component is working. This is donebywatchingforaTPSindication
of a greater or lesser throttle opening than MAP and engine rpm indicate. Inthe case of the TPS, if engine vacuum
is high and engine rpm is 1600 or greater, and the TPS indicates a large throttle opening, a DTC will be set. The
same applies to low vacuum if the TPS indicates a small throttle opening.
All open/short circuit checks, or any component that has an associated limp-in, will set a fault after 1 trip with the
malfunction present. Components without an associated limp-in will taketwo trips to illuminate the MIL.
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
withamonitoredcircuitoftenenoughtoindicatean
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 cancels the code after 40
warm-up cycles. Diagnostic trouble codes that affect
vehicle emissions illuminatethe Malfunction Indicator
Lamp (MIL). The MIL is displayed as an engine icon
(graphic) on the instrument 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 specific range
of engine RPM, engine temperature, and/or input volt-
age to the PCM.
The PCM might not store a DTC for a monitored cir-
cuit 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 thesensor’s output circuit shorts to
ground when engine operates above 2400 RPM (resulting in 0 volt input to thePCM). Because the condition hap-
pens at an engine speed above the maximum threshold (2000 rpm), the PCM willnot store a DTC.
There are several operating conditions for which the PCM monitors and setsDTC’s. Refer to Monitored Systems,
Components, and Non-Monitored Circuits in this section.
Technicians must retrieve stored DTC’s by connecting the DRB scan tool (oran 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.
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 (1) toerase all DTC’s and extinguish
the MIL.

TA S K M A N A G E R
The Task Manager determines which tests happen when and which functions occur when. Many of the diagnostic
steps required by OBD II must be performed under specific operating conditions. The Task Manager software orga-
nizes and prioritizes the diagnostic procedures. The job of the Task Manager is to determine if conditions are appro-
priate for tests to be run, monitor theparameters 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
Te s t S e q u e n c e
In many instances, emissions systems must fail diagnostic tests more thanonce before the PCM illuminates 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 monitors.’ A trip is defined as ’start the vehicle and operate 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 monitorspendingresolution 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 signals
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 running could result in an erroneous failure. If thisconflictis present,
themonitorisnotrununtiltheconflicting condition passes. Most likelythe monitor will run later after the con-
flicting 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 willsuspendthe
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 theOxygen Sensor Monitor either
passes or fails. At that point the Task Manager can determine if the EGR system is actually failing or if an
Oxygen Sensor is failing.
MIL Illumination
The PCM Task Manager carries out the illumination of the MIL. The Task Manager triggers MIL illumination 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 deter-
mine MIL illumination and DTC erasure. DTCs are entered according to individual priority. DTCs with a higher pri-
ority 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.
Priority 3 — Two trip failure for a non-fuel system and non-misfire or matured one trip comprehensive com-
ponent fault.
Priority 4 — Two trip failure or matured fault for fuel system (rich/lean) and misfire or one trip catalyst dam-
aging misfire.
Non-emissions related failures have no priority. One trip failures of twotrip faults have low priority. Two trip failures
or matured faults have higher priority. 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 failsthe 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 automatically erased following 40 warm-up cycles if the component does not fail
again.
For misfire and fuel system monitors, the component must pass the test under a Similar Conditions Window in order
to record a good trip. A Similar Conditions 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 component does not have to fail under a similar window of oper-
ation to mature. It must pass the test under a Similar Conditions Window whenitfailedtorecordaGood
Trip for DTC erasure for misfire and fuel system monitors.
DTCs can be erased anytime with a DRB III. Erasing 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 information for warm-up cycles, trips and Freeze Frame.
Trip Indicator
TheTri pis essential for running monitors and extinguishing the MIL. In OBD II terms,atripisasetofvehicle
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 monitors), 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 Oxy-
gen Sensor Monitor, Catalyst Monitor, Purge Flow Monitor, Leak DetectionPump 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 Monitor 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 (threerequired) 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
CycleCounterthatcanbeviewedontheDRBIII.Warm-UpCyclesareusedtoerase 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 follows:
Engine coolant temperature must start below and rise above 160° F (71.1°C).
Engine coolant temperature must rise by 40° F (4.4°C)
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 conditions 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 overwritten 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 information about engine operation during a monitor. Absolute 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 switching 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 Adaptive 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)—Atimer 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—ATripCounterusedtoturnOFFtheMILforFuelSystemDTCs.To
increment a Fuel System Good Trip, the engine must be in the Similar Conditions Window, Adaptive Memory
Factor must be less than calibrated 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 (71.1°C).
In Similar Misfire Window— An indicator that ’Absolute MAP When Misfire Occurred’ and ’RPM When Mis-
fire Occurred’ are all in the same range when the failure occurred. Indicated by switching 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 Adaptive 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.
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 systems or components.EXAM-
PLE:a fuel pressure problem will not register a fault directly, but could causea rich/lean condition or misfire. This
could cause the PCM to store an oxygen sensor or misfire diagnostic troublecode
FUEL PRESSURE
The fuel pressure regulator controls fuel system pressure. The PCM cannotdetect 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 con-
dition causing the PCM to store an oxygen sensor or fuel system diagnostic 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.
EXCESSIVE OIL CONSUMPTION
Although the PCM monitors engine exhaust oxygen content when the system isin 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 gener-
ated as a result of this condition. The module 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 connector pins.

VALVE-EGR
DESCRIPTION
4.7L Engine
The electronic EGR valve and solenoid assembly (3)
is attached to the rear of the left cylinder head. An
exhaust gas routing tube (1) connects the EGR valve
to the intake manifold.
5.7L Engine
The electronic EGR valve and solenoid assembly (2)
is attached to the front of the right cylinder head. An
exhaust gas routing tube (4) connects the EGR valve
to the intake manifold.
OPERATION
Exhaust gas recirculation flow is determined by the Powertrain Control Module (PCM) and is controlled by an elec-
tronic EGR valve assembly. For a given set of conditions, the PCM knows the ideal exhaust gas recirculation flow
to optimize NOx and fuel economy as a function of the pintle position. Pintle position is obtained from the position
sensor. The PCM adjusts the duty cycle of 128 Hz power supplied to the solenoid coil to obtain the correct position.
The electronic EGR valve assembly consists of a pintle, valve seat, and housing which contains and regulates
exhaust gas flow. An armature, return spring, and solenoid coil provide the operating force to regulate exhaust gas