key OPEL FRONTERA 1998 Owner's Manual

5A–58
BRAKE CONTROL SYSTEM
Chart C-1-2 FR Sensor Output Inspection Procedure
StepActionYe sNo
11. Turn the key off.
2. Disconnect EHCU connector.
3. Jack up the vehicle with all four wheels off the ground.
Measure the AC voltage between EHCU connector terminals
while turning FR wheel at a speed of 1 RPS:
Is voltage between EHCU connector terminals 4 and 5 under 200
mV?
Go to Step 2
Ok.
Go to Step 3
21. Disconnect the wheel speed sensor.
2. Measure resistance between the wheel speed sensor
connector terminals 1 and 2.
Is resistance between connector (C-41) terminals 1 and 2 within
1.3k - 1.9k ohms?Connector is
faulty, or open or
short circuit of
harness between
wheel speed
sensor connector
and EHCU.
Inspect and
correct the
connector or
harness
Go to Step 3
Wheel speed
sensor is faulty.
Replace the
wheel speed
sensor.
Go to Step 3
3Reconnect all components and ensure all components are
properly mounted.
Was this step finished?Repeat the “Basic
diagnostic flow
chart.”
Go to Step 3
Chart C-1-3 RL Sensor Output Inspection Procedure
StepActionYe sNo
11. Turn the key off.
2. Disconnect EHCU connector.
3. Jack up the vehicle with all four wheels off the ground.
Measure the AC voltage between EHCU connector terminals
while turning RL wheel at a speed of 1 RPS:
Is voltage between EHCU connector terminals 22 and 23 under
200 mV?
Go to Step 2
Ok.
Go to Step 3
21. Disconnect the wheel speed sensor.
2. Measure resistance between the wheel speed sensor
connector terminals 1 and 2.
Is resistance between connector (F-3) terminals 1 and 2 within
1.3k - 1.9k ohms?Connector is
faulty, or open or
short circuit of
harness between
wheel speed
sensor connector
and EHCU.
Inspect and
correct the
connector or
harness
Go to Step 3
Wheel speed
sensor is faulty.
Replace the
wheel speed
sensor.
Go to Step 3
3Reconnect all components and ensure all components are
properly mounted.
Was this step finished?Repeat the “Basic
diagnostic flow
chart.”
Go to Step 3

5A–59 BRAKE CONTROL SYSTEM
Chart C-1-4 RR Sensor Output Inspection Procedure
StepActionYe sNo
11. Turn the key off.
2. Disconnect EHCU connector.
3. Jack up the vehicle with all four wheels off the ground.
Measure the AC voltage between EHCU connector terminals
while turning RR wheel at a speed of 1 RPS:
Is voltage between EHCU connector terminals 2 and 3 under 200
mV?
Go to Step 2
Ok.
Go to Step 3
21. Disconnect the wheel speed sensor.
2. Measure resistance between the wheel speed sensor
connector terminals 1 and 2.
Is resistance between connector (F-2) terminals 1 and 2 within
1.3k - 1.9k ohms?Connector is
faulty, or open or
short circuit of
harness between
wheel speed
sensor connector
and EHCU.
Inspect and
correct the
connector or
harness
Go to Step 3
Wheel speed
sensor is faulty.
Replace the
wheel speed
sensor.
Go to Step 3
3Reconnect all components and ensure all components are
properly mounted.
Was this step finished?Repeat the “Basic
diagnostic flow
chart.”
Go to Step 3
Chart TC-1 Sensor Output Inspection Procedure (Use TECH 2)
StepActionYe sNo
11. Connect TECH 2.
2. While driving the vehicle, check the wheel speed of each
sensor by Data List.
Is the vehicle speed value is normal?
Go to Step 6Go to Step 2
2Check the sensor harness for suspected disconnection (Check
while shaking harness/connector).
Is the sensor harness connection normal?Replace speed
sensor.
Go to Step 3
Repair.
Go to Step 6
3While driving the vehicle, check the wheel speed of each sensor
by Data List.
Is the vehicle speed value is normal?
Go to Step 6Go to Step 4
4Check the sensor rotor.
Is the sensor rotor normal?
Go to Step 6
Replace sensor
rotor.
Go to Step 5
5While driving the vehicle, check the wheel speed of each sensor
by Data List.
Is the vehicle speed value is normal?
Go to Step 6
Repair harness or
connector
between EHCU
and speed
sensor.
Go to Step 6
6Reconnect all components, ensure all components are properly
mounted.
Was this step finished?Repeat the “Basic
diagnostic flow
chart.”
Go to Step 6

5A–60
BRAKE CONTROL SYSTEM
Chart C-2 Transmission Input Inspection Procedure
StepActionYe sNo
11. Turn the key off.
2. Disconnect EHCU connector.
Is there continuity between EHCU connector terminals 6 and 15
(Gear position-P(A/T), N(M/T))?Shorted switch
harness.
Repair switch or
harness.
Go to Step 6
Go to Step 2
2Is the vehicle an A/T model?Go to Step 3Go to Step 5
3Turn the key on and measure voltage between EHCU connector
terminals 6 and 15.
Is there less than 6V when the gear position is L, and R(Battery
voltage 12V)?
Go to Step 5
Transmission SW
trouble.
Disconnected
harness.
Repair SW and
harness.
Go to Step 6
4Turn the key on and measure the voltage between EHCU
connector terminal 6 and 15.
Is there more than 9.6V when the gear position is 1, 2, R(Battery
voltage 12V)?
Go to Step 5
Transmission SW
trouble.
Disconnected
harness.
Repair SW and
harness.
Go to Step 6
5Measure the voltage between EHCU connector terminals 6 and
15.
Is there 6.6 to 9.0V when the gear position is 3, 4, 5 and N(M/T) or
2,3,D,N and P(A/T)(Battery voltage 12V)?
Go to Step 6
Transmission SW
trouble.
Disconnected
harness.
Repair SW and
harness.
Go to Step 6
61. Reconnect all components and ensure all components are
properly mounted.
2. Clear diagnostic trouble code.
Was this step finished?
Repeat the “Basic
diagnostic flow
chart.”
Go to Step 6

6C–10
ENGINE FUEL
Reuse of Quick–Connector
(Delivery Pipe)
Replace the pipe and connector if scratch, dent or
crack is found.
Remove mud and dust from the pipe and make sure
that the end including spool is free of defects, such as
scratch, rust, and dent, which may cause poor
sealability. If defective, replace with a new pipe.
If the retainer removed according to the removal step
above is attached to the pipe, clean and insert it
straight into the quick-connector till it clicks. After it
clicks, try pulling it out to make sure that it is not drawn
and is securely locked.
NOTE: The retainer, once removed from the pipe, cannot
be reused. Just replace with a new retainer. Insert the
new retainer into the connector side until it clicks, and
connect the pipe as inserting it into the retainer until it
clicks.
141RW018
(Return Pipe)
Replace the pipe and connector if scratch, dent or
crack is found.
Remove mud or dust from the pipe and make sure
that the end including spool is free from defects, such
as scratch, rust, and dent, which may cause poor
sealability. If defective, replace with a new pipe.
After cleaning the pipe, insert it straight into the
connector until it clicks. After it clicks, try pulling it out
to make sure that it is not drawn and is securely
locked.
141RW017
Assembling Advice
Application of engine oil or light oil to the pipe facilitates
connecting work. The work should be started immediately
after lubrication, since dust may stick to the pipe surface
to cause poor sealability if a long time passes after
lubrication.
Test/Inspection After Assembling
1. Reconnect the battery negative cable.
2. Turn the ignition key to the “ON” position and check
pump startup sound. As the pump is actuated to raise
fuel pressure, check and see fuel leak from the piping
system.
3. Make sure of no fuel leakage by conducting the above
fuel leak check a few times.
4. Start the engine and make sure of stable idling speed
and normal vehicle run.The entry of dust during the
work may sometimes affect the fuel injection system.

6E–40
ENGINE DRIVEABILITY AND EMISSIONS
Common OBD Terms
Diagnostic
When used as a noun, the word diagnostic refers to any
on-board test run by the vehicle’s Diagnostic
Management System. A diagnostic is simply a test run on
a system or component to determine if the system or
component is operating according to specification. There
are many diagnostics, shown in the following list:
Oxygen sensors
Oxygen sensor heaters
EGR
Catalyst monitoring
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 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
TP
fuel trim
TCC enabled
A/C on
Tr i p
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 diagnostic are run
when the vehicle is at operating temperature, some when
the vehicle first start 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 disables. 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 enables 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
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 (future)
Operating conditions Failure Records buffer, (the
number of records will vary)
Current status information on each diagnostic
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 not 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 the it illuminate under
a strict set of guide lines.
Basically, the MIL is turned on when the PCM detects a
DTC that will impact the 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
emissionsrelated faults.
Extinguishing the MIL
When the MIL is on, the Diagnostic Executive will turn off
the MIL after
three 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.

6E–41 ENGINE DRIVEABILITY AND EMISSIONS
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 with
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.
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
driveability or emissions problem, a Powertrain
On-Board Diagnostic (OBD ll) 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:
Ty p e 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
Ty p e 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
Type C (if the vehicle is so equipped)
Non-Emissions related
Requests illumination of the Service Lamp or the
service message on the Drive Information Center
(DIC) on the
first trip with a fail
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 (Ty p e D non-emissions related are not utilized
on certain vehicle applications).
Non-Emissions related
Dose 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.
Storing and Erasing Freeze Frame Data and Failure
Records
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.
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:
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

6E–42
ENGINE DRIVEABILITY AND EMISSIONS
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 the 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). The DLC is used to
connect to Tech 2. Some common uses of Tech 2 are
listed below:
Identifying stored Diagnostic Trouble Codes (DTCs).
Clearing DTCs.
Performing output control tests.
Reading serial data.
TS24064
Verifying Vehicle Repair
Verification of vehicle repair will be more comprehensive
for vehicles with OBD 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 specific
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 systems. Failure to follow these steps
could result in unnecessary repairs.
Reading Diagnostic Trouble Codes Using
A Tech 2
The procedure for reading diagnostic trouble code(s) is to
used a diagnostic Tech 2. When reading DTC(s), follow
instructions supplied by Tech 2 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 Tech 2 “clear DTCs”. When clearing DTCs
follow instructions supplied by the tool manufacturer.
When Tech 2 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).

6E–43 ENGINE DRIVEABILITY AND EMISSIONS
Te c h 2
From 98 MY, Isuzu dealer service departments are
recommended to use Tech 2. Please refer to Tech 2 Tech
2 user guide.
901RW180
Legend
(1) PCMCIA Card
(2) RS 232 Loop Back Connector(3) SAE 16/19 Adaptor
(4) DLC Cable
(5) Tech–2
Tech 2 Features
1. Tech 2 is 12 volt system. Do not apply 24 volt.
2. After connect and/or install Tech 2 body, Vehicle
Communications Interface (VCI) module, PCMCIA
card and DLC connector, connect them to the vehicle
DLC.
3. After power off to the Tech 2, remove and reinstall the
PCMCIA card.
4. The PCMCIA card has a capacity of 10 Megabytes
which is 10 times greater than the memory of the Tech
1 Mass Storage Cartridge.5. The Tech 2 has the capability of two snapshots.
6. The PCMCIA card is sensitive to magnetism and
static electricity, so care should be taken in the
handling of the card.
7. The Tech 2 can plot a graph when replaying a
snapshot.
8. Always return to the Main Menu to press EXIT key
several times before shutting down.
9. To clear Diagnostic Trouble Codes (DTCs), open
Application Menu and press “F1: Clear DTC Info”.

6E–46
ENGINE DRIVEABILITY AND EMISSIONS
060RW223
The following is a brief description of each of the sub
menus in DTC Info and Specific DTC. The order in which
they appear here is alphabetical and not necessarily the
way they will appear on the Tech 2.
DTC Information Mode
Use the DTC info mode to search for a specific type of
stored DTC information. There are seven choices. The
service manual may instruct the technician to test for
DTCs in a certain manner. Always follow published
service procedures.
To get a complete description of any status, press the
“Enter” key before pressing the desired F-key. For
example, pressing “Enter” then an F-key will display a
definition of the abbreviated Tech 2 status.
060RW221
DTC Status
This selection will display any DTCs that have not run
during the current ignition cycle or have reported a test
failure during this ignition up to a maximum of 33 DTCs.
DTC tests which run and pass will cause that DTC
number to be removed from Tech 2 screen.Fail This Ignition
This selection will display all DTCs that have failed during
the present ignition cycle.
History
This selection will display only DTCs that are stored in the
PCM’s history memory. It will not display Type B DTCs
that have not requested the MIL (“Check Engine” lamp). It
will display all type A and B DTCs that have requested the
MIL and have failed within the last 40 warm-up cycles. In
addition, it will display all type C and type D DTCs that
have failed within the last 40 warm-up cycles.
Last Test Failed
This selection will display only DTCs that have failed the
last time the test ran. The last test may have run during a
previous ignition cycle if a type A or type B DTC is
displayed. For type C and type D DTCs, the last failure
must have occurred during the current ignition cycle to
appear as Last Test Fail.
MILSVC or Message Requested
This selection will display only DTCs that are requesting
the MIL. Type C and type D DTCs cannot be displayed
using this option. This selection will report type B DTCs
only after the MIL has been requested.
Not Run Since Code Clear
This option will display up to 33 DTCs that have not run
since the DTCs were last cleared. Since any displayed
DTCs have not run, their condition (passing or failing) is
unknown.
Test Failed Since Code Clear
This selection will display all active and history DTCs that
have reported a test failure since the last time DTCs were
cleared. DTCs that last failed more than 40 warm-up
cycles before this option is selected will not be displayed.
Injector Balance Test
This test is conducted to make it sure that appropriate
electric signals are being sent to injectors Nos. 1–6.
Tech 2 must be used for this test.
Test Procedure:
1. Connect Tech 2 to the vehicle DLC.
2. Run the Engine at idle.

6E–47 ENGINE DRIVEABILITY AND EMISSIONS
3. Select F3: Miscellaneous Test in the Application
Menu.
060RW228
4. Select F7: Injector Balance Test in the Miscellaneous
Te s t .
060RX006
5. Select injector number and push “injector off” of soft
key.
060RW230
6. Make sure of engine speed change.
7. In the engine speed whose change has been
confirmed, the injector electric circuit can be regard
as normal.
As for the engine speed whose change has not been
confirmed, the injector electric circuit or the injector
proper is faulty.
EGR Control Test
This test is conducted check EGR valve for its working.
Tech 2 must be used for this test.
Test Procedure:
1. Connect Tech 2 to the vehicle DLC.
2. Run the Engine at idle.
3. Select F3: Miscellaneous Test in the Application
Menu.
060RW228