Dodge Dakota 2001, Service Manual

Page: 2232 / 2307

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 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
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 monitors pending resolu-
AN
EMISSIONS CONTROL 25 - 19
EMISSIONS CONTROL (Continued)