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.
