Opel Frontera UBS. Manual - part 2256

 

  Index      Opel     Opel Frontera UBS - service repair manual 1998-2002 year

 

Search            

 

 

 

 

 

 

 

 

 

Content   ..  2254  2255  2256  2257   ..

 

 

Opel Frontera UBS. Manual - part 2256

 

 

6E–60

6VE1 3.5 ENGINE DRIVEABILITY AND EMISSIONS

D

For the 3.5L w/automatic transmission, the
pre-catalyst sensors are designated Bank 1 HO2S 1
and Bank 2 HO2S 1.  The post-catalyst sensors are
Bank 1 HO2S 2 and Bank 2 HO2S 2.

Catalyst Monitor Outputs
The catalyst monitor diagnostic is sensitive to the
following conditions:

D

Exhaust leaks

D

HO2S contamination

D

Alternate fuels

Exhaust system leaks may cause the following:

D

Preventing a degraded catalyst from failing the
diagnostic.

D

Causing a false failure for a normally functioning
catalyst.

D

Preventing the diagnostic from running.

Some of the contaminants that may be encountered are
phosphorus, lead, silica, and sulfur.  The presence of
these contaminants will prevent the TWC diagnostic from
functioning properly.

Three-Way Catalyst Oxygen Storage Capacity
The Three-Way catalyst (TWC) must be monitored for
efficiency.  To accomplish this, the control module
monitors the pre-catalyst HO2S and post-catalyst HO2S
oxygen sensors.  When the TWC is operating properly,
the post-catalyst oxygen sensor will have significantly
less activity than the pre-catalyst oxygen sensor.  The
TWC stores and releases oxygen as needed during its
normal reduction and oxidation process.  The control
module will calculate the oxygen storage capacity using
the difference between the pre-catalyst and post catalyst
oxygen sensor’s voltage levels.  If the activity of the
post-catalyst oxygen sensor approaches that of the
pre-catalyst oxygen sensor, the catalyst’s efficiency is
degraded.
Stepped or staged testing level allow the control module
to statistically filter test information.  This prevents falsely
passing or falsely failing the oxygen storage capacity test.
The calculations performed by the on-board diagnostic
system are very complex.  For this reason, post catalyst
oxygen sensor activity should not be used to determine
oxygen storage capacity unless directed by the service
manual.
Two stages are used to monitor catalyst efficiency.
Failure of the first stage will indicate that the catalyst
requires further testing to determine catalyst efficiency.
The seconds stage then looks at the inputs for the pre and
post catalyst HO2S sensors more closely before
determining if the catalyst is indeed degraded.  This
further statistical processing is done to increase the
accuracy of oxygen storage capacity type monitoring.
Failing the first (stage 1) test DOES NOT indicate a failed
catalyst.  The catalyst may be marginal or the fuel sulfur
content could be very high.

Aftermarket HO2S characteristics may be different from
the original equipment manufacturer sensor.  This may
lead to a false pass or a false fail of the catalyst monitor
diagnostic. Similarly, if an aftermarket catalyst does not
contain the same amount of cerium as the original part,
the correlation between oxygen storage and conversion
efficiency may be altered enough to set a false DTC.

Misfire Monitor Diagnostic Operation

Misfire Monitor Diagnostic Operation

Misfire is monitored as a function of the combustion
quality (CQ) signals generated from the ignition current
sense system. Combustion signals represent the degree
of combustion in each cylinder. Misfire is detected when
the combustion signal is below a predetermined value.
The misfire ratio is calculated once every 100 engine
cycles. For example, on a 6-cylinder engine, 600 ignition
plug sparks occur every 100 cycles and if a misfire occurs
12 times during that time, the misfire is 12/600 

×

 100 = 2

%.

Misfire Counters

Whenever a cylinder misfires, the misfire diagnostic
counts the misfire and notes the crankshaft position at the
time the misfire occurred.  These “misfire counters” are
basically a file on each engine cylinder.  A current and a
history misfire counter are maintained for each cylinder.
The misfire current counters (Misfire Cur #1-6) indicate
the number of firing events out of the last 100 cylinder
firing events which were misfires.  The misfire current
counter will display real time data without a misfire DTC
stored.  The misfire history counters (Misfire Hist #1-6)
indicate the total number of cylinder firing events which
were misfires.  The misfire history counters will display 0
until the misfire diagnostic has failed and a DTC P0300 is
set.  Once the misfire DTC P0300 is set, the misfire
history counters will be updated every 100 cylinder firing
events.  A misfire counter is maintained for each cylinder.
If the misfire diagnostic reports a failure, the diagnostic
executive reviews all of the misfire counters before
reporting DTC.  This way, the diagnostic executive
reports the most current information.
When crankshaft rotation is erratic, a misfire condition will
be detected. Because of this erratic condition, the data
that is collected by the diagnostic can sometimes
incorrectly identify which cylinder is misfiring.  Misfires are
counted from more than one cylinder.  Cylinder #1 has the
majority of counted misfires.  In this case, the Misfire
Counters would identify cylinder #1 as the misfiring
cylinder.  The misfires in the other counters were just
background noise caused by the erratic misfire rotation of
the crankshaft.  If the number of accumulated misfires is
sufficient for the diagnostic to identify a true misfire, the
diagnostic will set DTC P0300 – Misfire Detected.
Use diagnostic equipment to monitor misfire counter data
on OBD-compliant vehicles.  Knowing which specific
cylinder(s) misfired can lead to the root cause, even when
dealing with a multiple cylinder misfire.  Using the
information in the misfire counters, identify which
cylinders are misfiring.  If the counter indicate cylinders

6E–61

6VE1 3.5L ENGINE DRIVEABILITY AND EMISSIONS

numbers 1 and 4 misfired, look for a circuit or component
common to both cylinders number 1 and 4.
Misfire counter information is located in the “Eng”. menu,
“Misfire Data” sub-menu of the data list.
The misfire diagnostic may indicate a fault due to a
temporary fault not necessarily caused by a vehicle
emission system malfunction.  Examples include the
following items:

D

Contaminated fuel

D

Low fuel

D

Fuel-fouled spark plugs

D

Basic engine fault

Fuel Trim System Monitor Diagnostic

Operation

Fuel Trim System Monitor Diagnostic
Operation

This system monitors the averages of short-term and
long-term fuel trim values.  If these fuel trim values stay at
their limits for a calibrated period of time, a malfunction is
indicated.  The fuel trim diagnostic compares the
averages of short-term fuel trim values and long-term fuel
trim values to rich and lean thresholds.  If either value is
within the thresholds, a pass is recorded.  If both values
are outside their thresholds, a rich or lean DTC will be
recorded.
The fuel trim system diagnostic also conducts an intrusive
test.  This test determines if a rich condition is being
caused by excessive fuel vapor from the EVAP canister.
In order to meet OBD requirements, the control module
uses weighted fuel trim cells to determine the need to set
a fuel trim DTC.  A fuel trim DTC can only be set if fuel trim
counts in the weighted fuel trim cells exceed
specifications.  This means that the vehicle could have a
fuel trim problem which is causing a problem under
certain conditions (i.e., engine idle high due to a small
vacuum leak or rough idle due to a large vacuum leak)
while it operates fine at other times.  No fuel trim DTC
would set (although an engine idle speed DTC or HO2S
DTC may set).  Use the Tech 2 to observe fuel trim counts
while the problem is occurring.
A fuel trim DTC may be triggered by a number of vehicle
faults.  Make use of all information available (other DTCs
stored, rich or lean condition, etc.) when diagnosing a fuel
trim fault.

Fuel Trim Cell Diagnostic Weights

No fuel trim DTC will set regardless of the fuel trim counts
in cell 0 unless the fuel trim counts in the weighted cells
are also outside specifications.  This means that the
vehicle could have a fuel trim problem which is causing a
problem under certain conditions (i.e. engine idle high due
to a small vacuum leak or rough due to a large vacuum
leak) while it operates fine at other times.  No fuel trim
DTC would set (although an engine idle speed DTC or
HO2S DTC may set).  Use the Tech 2 to observe fuel trim
counts while the problem is occurring.

6E–62

6VE1 3.5 ENGINE DRIVEABILITY AND EMISSIONS

On-Board Diagnostic (OBD) System Check

D06RY00053

Circuit Description

The on-board diagnostic system check is the starting
point for any driveability complaint diagnosis. Before
using this procedure, perform a careful visual/physical
check of the PCM and engine grounds for cleanliness and
tightness.
The on-board diagnostic system check is an organized
approach to identifying a problem created by an
electronic engine control system malfunction.

Diagnostic Aids

An intermittent may be caused by a poor connection,
rubbed–through wire insulation or a wire broken inside the
insulation. Check for poor connections or a damaged
harness. Inspect the PCM harness and connector for
improper mating, broken locks, improperly formed or
damaged terminals, poor terminal-to-wire connection,
and damaged harness.

Test Description

Number(s) below refer to the step number(s) on the
Diagnostic Chart:
2. The MIL (“Check Engine lamp”) should be “ON”

steady with the ignition “ON ” and the engine “OFF”.
If not, the “No MIL” chart should be used to isolate
the malfunction.

3. The SVS (“Service Vehicle Soon”) lamp should be

“ON” steady with the ignition “ON ”and the engine
“OFF”. If not, the “No SVS lamp”chart should be
used to isolate the malfunction.

4. Checks the Class 2 data circuit and ensures that the

PCM is able to transmit serial data.

5. This test ensures that the PCM is capable of

controlling the MIL (“Check Engine lamp”) and the
MIL (“Check Engine lamp”) driver circuit is not
shorted to ground.

6. This test ensures that the PCM is capable of

controlling the SVS (“Service Vehicle Soon”) lamp
and the SVS (“Service Vehicle Soon”) lamp driver
circuit is not shorted to ground.

8. Check the DTCs (System ,Volts Supply circuit).

9. Check the DTCs (PCM{Software} detect Errors).

12.If the engine will not start, the Cranks But Will Not

Run chart should be used to diagnose the condition.

15.A Tech 2 parameter which is not within the typical

range may help to isolate the area which is causing
the problem.

16.This vehicle is equipped with a PCM which utilizes

an electrically erasable programmable read only
memory (EEPROM). When the PCM is replaced,
the new PCM must be programmed. Refer to 

PCM

Replacement and Programming Procedures in
Powertrain Control Module (PCM) and Sensors of
this section.

11.If the starter motor will not start, the starter control

system chart should be used to diagnose the
condition.

6E–63

6VE1 3.5L ENGINE DRIVEABILITY AND EMISSIONS

On-Board Diagnostic (OBD) System Check

 

Step

Action

Value(s)

Yes

No

1

1.  Ignition “ON”, engine “OFF”.
2. Observe the Service Vehicle Soon (SVS) lamp.

Is the SVS lamp flashing?

Refer to

Immobilizer

System

Workshop

Manual

Go to 

Step 2

2

1.  Ignition “ON”, engine “OFF”.
2.  Observe the malfunction indicator lamp (MIL or

“Check Engine lamp”).

Is the MIL (“Check Engine lamp”)“ON”?

Go to 

Step 3

Go to 

No

MIL(“Check

Engine lamp”)

3

1.  Ignition “ON”, engine “OFF”.
2.  Observe the SVS (“Service Vehicle Soon”) lamp.

Is the SVS (“Service Vehicle Soon”) lamp “ON”?

Go to 

Step 4

Go to 

No

SVS

(“Service

Vehicle

Soon”) lamp

4

1. Ignition “OFF”.
2. Install Tech 2.
3. Ignition “ON”.
4. Attempt to display PCM engine data with the

Tech 2.

Does the Tech 2 display PCM data?

Go to 

Step 5

Go to 

Step 13

5

1.  Using the Tech 2 output tests function, select MIL

(“Check Engine lamp”) control and   command the
MIL (“Check Engine Lamp”) “OFF”.

2.  Observe the MIL (“Check Engine lamp”).

Did the MIL (“Check Engine lamp”) turn “OFF”?

Go to 

Step 6

Go to

MIL(“Check

Engine lamp”)

On Steady

6

1.  Using the Tech 2 output tests function, select RPL

(“Reduced Power lamp”) control and   command the
RPL (“Reduced Power lamp”) “OFF”.

2.  Observe the SVS (“Service Vehicle Soon”) lamp.

Did the SVS (“Service Vehicle Soon”) lamp turn “OFF”?

Go to 

Step 7

Go to 

SVS

(“Service

Vehicle

Soon”) lamp

On Steady

7

Select “Display DTCs” with the Tech 2.

Are any DTCs stored?

Go to 

Step 8

Go to 

Step 12

8

Stored DTCs.
P0562, P0563, P0601, P0602, P0604, P0606, P1625,
P1635, P1639, P1640, P1650

Are the applicable DTCs stored?

Go to

applicable
DTC table

Go to 

Step 9

9

Stored DTCs.
P1514, P1515, P1516, P1523, P1125, P1290, P1295,
P1299

Are the applicable DTCs stored?

Go to

applicable
DTC table

Go to 

Step 10

10

Stored DTCs.

1.  P0425, P0106, P0107, P1107, P0401, P1404,

P0405, P1120, P1221, P1515, P1516, P1275,
P1635, P1271, P1273, P1285, P1272

2.  P0336, P0337, P1220, P1515, P1221,   P1516,

P1280, P1639, P1271, P1272

Are the applicable DTCs stored?

Go to

“Multiple

PCM

Information

sensor DTCs

Set”

Go to 

Step 11

 

 

 

 

 

 

 

Content   ..  2254  2255  2256  2257   ..