Opel Frontera UE. Manual - part 1455

6E–35

6VD1 3.2L ENGINE DRIVEABILITY AND EMISSIONS

Enable Criteria
The term “enable criteria” is engineering language for the
conditions necessary for a given diagnostic test to run.
Each diagnostic has a specific list of conditions which
must be met before the diagnostic will run. “Enable
criteria” is another way of saying “conditions required”.
The enable criteria for each diagnostic is listed on the first
page of the DTC description in Section 6E under the
heading “Conditions for Setting the DTC”. Enable criteria
varies with each diagnostic, and typically includes, but is
not limited to the following items:

engine speed

vehicle speed

ECT

MAF/MAP

barometric pressure

IAT

high canister purge

fuel trim

TCC enabled

A/C on

Trip
Technically, a trip is a key on-run-key off cycle in which all
the enable criteria for a given diagnostic are met, allowing
the diagnostic to run. Unfortunately, this concept is not
quite that simple. A trip is official when all the enable
criteria for a given diagnostic are met. But because the
enable criteria vary from one diagnostic to another, the
definition of trip varies as well. Some diagnostics are run
when the vehicle is at operating temperature, some when
the vehicle first starts up; some require that the vehicle be
cruising at a steady highway speed, some run only when
the vehicle is idle; some diagnostics function with the
TCC disabled. Some run only immediately following a
cold engine start-up.
A trip then, is defined as a key on-run-key off cycle in
which the vehicle was operated in such a way as to satisfy
the enabling criteria for a given diagnostic, and this
diagnostic will consider this cycle to be one trip. However,
another diagnostic with a different set of enable criteria
(which were not met) during this driving event, would not
consider it a trip. No trip will occur for that particular
diagnostic until the vehicle is driven in such a way as to
meet all the enable criteria.

The Diagnostic Executive

The Diagnostic Executive is a unique segment of
software which is designed to coordinate and prioritize
the diagnostic procedures as well as define the protocol
for recording and displaying their results. The main
responsibilities of the Diagnostic Executive are listed as
the following:

Commanding the MIL (“Check Engine” lamp) on and
off

DTC logging and clearing

Freeze Frame data for the first emission related DTC
recorded

Non-emission related Service Lamp

Operating conditions Failure Records buffer, (the
number of records will vary)

Current status information on each diagnostic

System Status (I/M ready)

The Diagnostic Executive records DTCs and turns on the
MIL when emission-related faults occur. It can also turn
off the MIL if the conditions cease which caused the DTC
to set.

Diagnostic Information
The diagnostic charts and functional checks are designed
to locate a faulty circuit or component through a process
of logical decisions. The charts are prepared with the
requirement that the vehicle functioned correctly at the
time of assembly and that there are no multiple faults
present.
There is a continuous self-diagnosis on certain control
functions. This diagnostic capability is complemented by
the diagnostic procedures contained in this manual. The
language of communicating the source of the malfunction
is a system of diagnostic trouble codes. When a
malfunction is detected by the control module, a
diagnostic trouble code is set and the Malfunction
Indicator Lamp (MIL) (“Check Engine” lamp) is
illuminated.

Malfunction Indicator Lamp (MIL)
The Malfunction Indicator Lamp (MIL) looks the same as
the MIL you are already familiar with (“Check Engine”
lamp). However, OBD requires that it illuminate under a
strict set of guide lines.
Basically, the MIL is turned on when the PCM detects a
DTC that will impact vehicle emissions.
The MIL is under the control of the Diagnostic Executive.
The MIL will be turned on if an emissions-related
diagnostic test indicates a malfunction has occurred. It
will stay on until the system or component passes the
same test, for three consecutive trips, with no emissions
related faults.

Extinguishing the MIL
When the MIL is on, the Diagnostic Executive will turn off
the MIL after

three(3) consecutive trips that a “test

passed” has been reported for the diagnostic test that
originally caused the MIL to illuminate.
Although the MIL has been turned off, the DTC will remain
in the PCM memory (both Freeze Frame and Failure
Records) until

forty(40) warm-up cycles after no faults

have been completed.
If the MIL was set by either a fuel trim or misfire-related
DTC, additional requirements must be met. In addition to
the requirements stated in the previous paragraph, these
requirements are as follows:

The diagnostic tests that are passed must occur
within 375 RPM of the RPM data stored at the time the
last test failed.

Plus or minus ten (10) percent of the engine load that
was stored at the time the last failed.

Similar engine temperature conditions (warmed up or
warming up ) as those stored at the time the last test
failed.

Meeting these requirements ensures that the fault which
turned on the MIL has been corrected.

SECTION

6E–36

6VD1 3.2L ENGINE DRIVEABILITY AND EMISSIONS

The MIL (“Check Engine” lamp) is on the instrument
panel and has the following function:

It informs the driver that a fault affects vehicle
emission levels has occurred and that the vehicle
should be taken for service as soon as possible.

As a bulb and system check, the MIL will come “ON”
with the key “ON” and the engine not running. When
the engine is started, the MIL will turn “OFF.”

When the MIL remains “ON” while the engine is
running, or when a malfunction is suspected due to a
derivability or emissions problem, a Powertrain
On-Board Diagnostic System Check must be
performed. The procedures for these checks are
given in On-Board Diagnostic (OBD) System Check.
These checks will expose faults which may not be
detected if other diagnostics are performed first.

DTC Types

Each DTC is directly related to a diagnostic test. The
Diagnostic Management System sets DTC based on the
failure of the tests during a trip or trips. Certain tests must
fail two (2) consecutive trips before the DTC is set. The
following are the four (4) types of DTCs and the
characteristics of those codes:

Type A

Emissions related

Requests illumination of the MIL of the first trip with a
fail

Stores a History DTC on the first trip with a fail

Stores a Freeze Frame (if empty)

Stores a Fail Record

Updates the Fail Record each time the diagnostic
test fails

Type B

Emissions related

“Armed” after one (1) trip with a fail

“Disarmed” after one (1) trip with a pass

Requests illumination of the MIL on the

second

consecutive trip with a fail

Stores a History DTC on the second consecutive trip
with a fail (The DTC will be armed after the first fail)

Stores a Freeze Frame on the second consecutive
trip with a fail (if empty)

Stores a Fail Record when the first test fails (not
dependent on

consecutive trip fails)

Updates the Fail Record each time the diagnostic
test fails

(Some special conditions apply to misfire and fuel trim
DTCs)

Type C (if the vehicle is so equipped)

Non-Emissions related

Requests illumination of the Service Lamp

Stores a History DTC on the

first trip with a fail

Does not store a Freeze Frame

Stores Fail Record when test fails

Updates the Fail Record each time the diagnostic
test fails

Type D

Non-Emissions related

Not request illumination of any lamp

Stores a History DTC on the

first trip with a fail

Does not store a Freeze Frame

Stores Fail Record when test fails

Updates the Fail Record each time the diagnostic
test fails

IMPORTANT:

Only four Fail Records can be stored.

Each Fail Record is for a different DTC. It is possible that
there will not be Fail Records for every DTC if multiple
DTCs are set.

Special Cases of Type B Diagnostic Tests
Unique to the misfire diagnostic, the Diagnostic Executive
has the capability of alerting the vehicle operator to
potentially damaging levels of misfire. If a misfire
condition exists that could potentially damage the
catalytic converter as a result of high misfire levels, the
Diagnostic Executive will command the MIL to “flash” at a
rate of once per second during those the time that the
catalyst damaging misfire condition is present.
Fuel trim and misfire are special cases of

Type B

diagnostics. Each time a fuel trim or misfire malfunction is
detected, engine load, engine speed, and engine coolant
temperature are recorded.
When the ignition is turned off, the last reported set of
conditions remain stored. During subsequent ignition
cycles, the stored conditions are used as reference for
similar conditions. If a malfunction occurs during two
consecutive trips, the Diagnostic Executive treats the
failure as a normal

Type B diagnostic, and does not use

the stored conditions. However, if a malfunction occurs
on two non-consecutive trips, the stored conditions are
compared with the current conditions. The MIL will then
illuminate under the following conditions:

When the engine load conditions are within 10% of
the previous test that failed.

Engine speed is within 375 rpm, of the previous test
that failed.

Engine coolant temperature is in the same range as
the previous test that failed.

Storing and Erasing Freeze Frame Data and Failure
Records
Government regulations require that engine operating
conditions be captured whenever the MIL is illuminated.
The data captured is called Freeze Frame data. The
Freeze Frame data is very similar to a single record of
operating conditions. Whenever the MIL is illuminated,
the corresponding record of operating conditions is
recorded to the Freeze Frame buffer.
Freeze Frame data can only be overwritten with data
associated with a misfire or fuel trim malfunction. Data
from these faults take precedence over data associated
with any other fault. The Freeze Frame data will not be
erased unless the associated history DTC is cleared.
Each time a diagnostic test reports a failure, the current
engine operating conditions are recorded in the

Failure

Records buffer. A subsequent failure will update the
recorded operating conditions. The following operating
conditions for the diagnostic test which failed

typically

include the following parameters:

SECTION

6E–37

6VD1 3.2L ENGINE DRIVEABILITY AND EMISSIONS

Air Fuel Ratio

Air Flow Rate

Fuel Trim

Engine Speed

Engine Load

Engine Coolant Temperature

Vehicle Speed

TP Angle

MAP/BARO

Injector Base Pulse Width

Loop Status

Intermittent Malfunction Indicator Lamp
In the case of an “intermittent” fault, the MIL (“Check
Engine” lamp) may illuminate and then (after three trips)
go “OFF”. However, the corresponding diagnostic trouble
code will be stored in memory. When unexpected
diagnostic trouble codes appear, check for an intermittent
malfunction.
A diagnostic trouble code may reset. Consult the
“Diagnostic Aids” associated with the diagnostic trouble
code. A physical inspection of the applicable sub-system
most often will resolve the problem.

Data Link Connector (DLC)
The provision for communication with the control module
is the Data Link Connector (DLC). It is located at the
lower left of the instrument panel behind a small square
cover. The DLC is used to connect to the Tech 2 Scan
Tool. Some common uses of the Tech 2 are listed below:

Identifying stored Diagnostic Trouble Codes (DTCs).

Clearing DTCs.

Performing output control tests.

Reading serial data.

TS24064

Decimal/Binary/Hexadecimal Conversions

Beginning in 1996, Federal Regulations require that all
auto manufacturers selling vehicles in the United States
provide Scan Tool manufacturers with software
information to display vehicle operating parameters. All

Scan Tool manufacturers will display a variety of vehicle
information which will aid in repairing the vehicle. Some
Scan Tools will display encoded messages which will aid
in determining the nature of the concern. The method of
encoding involves the use of a two additional numbering
systems: Binary and Hexadecimal.
The binary number system has a base of two numbers.
Each digit is either a 0 or a 1. A binary number is an eight
digit number and is read from right to left. Each digit has a
position number with the farthest right being the 0 position
and the farthest left being the 7 position. The 0 position,
when displayed by a 1, indicates 1 in decimal. Each
position to the left is double the previous position and
added to any other position values marked as a 1.
A hexadecimal system is composed of 16 different alpha
numeric characters. The alpha numeric characters used
are numbers 0 through 9 and letters A through F. The
hexadecimal system is the most natural and common
approach for Scan Tool manufacturers to display data
represented by binary numbers and digital code.

Verifying Vehicle Repair

Verification of vehicle repair will be more comprehensive
for vehicles with OBD II system diagnostic. Following a
repair, the technician should perform the following steps:

1. Review and record the Fail Records and/or Freeze

Frame data for the DTC which has been diagnosed
(Freeze Frame data will only be stored for an A or B
type diagnostic and only if the MIL has been
requested).

2. Clear DTC(s).
3. Operate the vehicle within conditions noted in the Fail

Records and/or Freeze Frame data.

4. Monitor the DTC status information for the DTC which

has been diagnosed until the diagnostic test
associated with that DTC runs.

Following these steps are very important in verifying
repairs on OBD ll systems. Failure to follow these steps
could result in unnecessary repairs.

Reading Diagnostic Trouble Codes Using
The Tech 2 Scan Tool

The procedure for reading diagnostic trouble code(s) is to
use a diagnostic Scan Tool. When reading DTC(s), follow
instructions supplied by tool manufacturer.

Clearing Diagnostic Trouble Codes

IMPORTANT:

Do not clear DTCs unless directed to do

so by the service information provided for each diagnostic
procedure. When DTCs are cleared, the Freeze Frame
and Failure Record data which may help diagnose an
intermittent fault will also be erased from memory.
If the fault that caused the DTC to be stored into memory
has been corrected, the Diagnostic Executive will begin to
count the “warm-up” cycles with no further faults
detected, the DTC will automatically be cleared from the
PCM memory.
To clear Diagnostic Trouble Codes (DTCs), use the
diagnostic Scan Tool “clear DTCs” or “clear information”
function. When clearing DTCs follow instructions
supplied by the tool manufacturer.

SECTION

6E–38

6VD1 3.2L ENGINE DRIVEABILITY AND EMISSIONS

When a Scan Tool is not available, DTCs can also be
cleared by disconnecting

one of the following sources for

at least thirty (30) seconds.

NOTE: To prevent system damage, the ignition key must
be “OFF” when disconnecting or reconnecting battery
power.

The power source to the control module. Examples:
fuse, pigtail at battery PCM connectors, etc.

The negative battery cable. (Disconnecting the
negative battery cable will result in the loss of other
on-board memory data, such as preset radio tuning).

SECTION

Content .. 1453 1454 1455 1456 ..