Daewoo Matiz (2003 year). Manual - part 26

1F – 14 ENGINE CONTROLS

termittent 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 de-
tected, the DTC will automatically be cleared from the
Engine Control Module (ECM) memory.

To clear DTCs, use the diagnostic scan tool.

It can’t cleared DTCs without the diagnostic scan tool.
So you must use the diagnostic scan tool.

Notice: To prevent system damage, the ignition key
must be OFF when disconnecting or reconnecting bat-
tery power.

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

The negative battery cable. (Disconnecting the nega-
tive battery cable will result in the loss of other Euro
On-Board memory data, such as preset radio tuning.)

DTC Modes

On Euro On-Board Diagnostic (EOBD) passenger cars
there are five options available in the scan tool DTC
mode to display the enhanced information available. A
description of the new modes, DTC Info and Specific
DTC, follows. After selecting DTC, the following menu
appears:

DTC Info.

Specific DTC.

Freeze Frame.

Fail Records (not all applications).

Clear Info.

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 neces-
sarily the way they will appear on the scan tool.

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 ser-
vice procedures.

To get a complete description of any status, press the
‘‘Enter” key before pressing the desired F-key. For ex-
ample, pressing ‘‘Enter” then an F-key will display a defi-
nition of the abbreviated scan tool status.

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 num-
ber to be removed from the scan tool screen.

Fail This Ign. (Fail This Ignition)

This selection will display all DTCs that have failed dur-
ing the present ignition cycle.

History

This selection will display only DTCs that are stored in
the ECM’s history memory. It will not display Type B
DTCs that have not requested the Malfunction Indicator
Lamp (MIL). It will display all type A, B and E 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 Fail

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 dis-
played. For type C and type D DTCs, the last failure
must have occurred during the current ignition cycle to
appear as Last Test Fail.

MIL Request

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 and E
DTCs only after the MIL has been requested.

Not Run SCC (Not Run Since Code Clear)

This option will display up to 33 DTCs that have not run
since the DTCs were last cleared. Since the displayed
DTCs have not run, their condition (passing or failing) is
unknown.

Test Fail SCC (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 dis-
played.

Specific DTC Mode

This mode is used to check the status of individual diag-
nostic tests by DTC number. This selection can be ac-
cessed if a DTC has passed, failed or both. Many EOBD
DTC mode descriptions are possible because of the ex-
tensive amount of information that the diagnostic execu-
tive monitors regarding each test. Some of the many
possible descriptions follow with a brief explanation.

The “F2” key is used, in this mode, to display a descrip-
tion of the DTC. The “Yes” and “No” keys may also be
used to display more DTC status information. This
selection will only allow entry of DTC numbers that are
supported by the vehicle being tested. If an attempt is,

ENGINE CONTROLS 1F – 15

made to enter DTC numbers for tests which the diag-
nostic executive does not recognize, the requested in-
formation will not be displayed correctly and the scan
tool may display an error message. The same applies to
using the DTC trigger option in the Snapshot mode. If an
invalid DTC is entered, the scan tool will not trigger.

Failed Last Test

This message display indicates that the last diagnostic
test failed for the selected DTC. For type A, B and E
DTCs, this message will be displayed during subse-
quent ignition cycles until the test passes or DTCs are
cleared. For type C and type D DTCs, this message will
clear when the ignition is cycled.

Failed Since Clear

This message display indicates that the DTC has failed
at least once within the last 40 warm-up cycles since the
last time DTCs were cleared.

Failed This Ig. (Failed This Ignition)

This message display indicates that the diagnostic test
has failed at least once during the current ignition cycle.
This message will clear when DTCs are cleared or the
ignition is cycled.

History DTC

This message display indicates that the DTC has been
stored in memory as a valid fault. A DTC displayed as a
History fault may not mean that the fault is no longer
present. The history description means that all the con-
ditions necessary for reporting a fault have been met
(maybe even currently), and the information was stored
in the control module memory.

MIL Requested

This message display indicates that the DTC is currently
causing the MIL to be turned ON. Remember that only
type A B and E DTCs can request the MIL. The MIL re-
quest cannot be used to determine if the DTC fault con-
ditions are currently being experienced. This is because
the diagnostic executive will require up to three trips dur-
ing which the diagnostic test passes to turn OFF the
MIL.

Not Run Since CI (Not Run Since Cleared)

This message display indicates that the selected diag-
nostic test has not run since the last time DTCs were
cleared. Therefore, the diagnostic test status (passing
or failing) is unknown. After DTCs are cleared, this mes-
sage will continue to be displayed until the diagnostic
test runs.

Not Run This Ig. (Not Run This Ignition)

This message display indicates that the selected diag-
nostic test has not run during this ignition cycle.

Test Ran and Passed

This message display indicates that the selected diag-
nostic test has done the following:

Passed the last test.

Run and passed during this ignition cycle.

Run and passed since DTCs were last cleared.

If the indicated status of the vehicle is “Test Ran and
Passed” after a repair verification, the vehicle is ready to
be released to the customer.

If the indicated status of the vehicle is “Failed This Igni-
tion” after a repair verification, then the repair is incom-
plete and further diagnosis is required.

Prior to repairing a vehicle, status information can be
used to evaluate the state of the diagnostic test, and to
help identify an intermittent problem. The technician can
conclude that although the MIL is illuminated, the fault
condition that caused the code to set is not present. An
intermittent condition must be the cause.

PRIMARY SYSTEM-BASED
DIAGNOSTICS

There are primary system-based diagnostics which
evaluate the system operation and its effect on vehicle
emissions. The primary system-based diagnostics are
listed below with a brief description of the diagnostic
function:

Oxygen Sensor Diagnosis

The fuel control oxygen sensor (O2S) is diagnosed for
the following conditions:

Few switch count (rich to lean or lean to rich).

Slow response (average transient time lean to rich or
rich to lean).

Response time ratio (ratio of average transient time
rich(lean) to lean(rich)).

Inactive signal (output steady at bias voltage approxi-
mately 450 mV).

Signal fixed high.

Signal fixed low.

The catalyst monitor heated oxygen sensor (HO2S) is
diagnosed for the following conditions:

Heater performance (current during IGN on).

Signal fixed low during steady state conditions or
power enrichment (hard acceleration when a rich mix-
ture should be indicated).

Signal fixed high during steady state conditions or de-
celeration mode (deceleration when a lean mixture
should be indicated).

Inactive sensor (output steady at approx. 438 mV).

If the O2S pigtail wiring, connector or terminal are dam-
aged, the entire O2S assembly must be replaced. Do
not attempt to repair the wiring, connector or terminals.
In order for the sensor to function properly, it must have
clean reference air provided to it. This clean air refer-
ence is obtained by way of the O2S wire(s). Any attempt
to repair the wires, connector or terminals could result in

1F – 16 ENGINE CONTROLS

the obstruction of the reference air and degrade the O2S
performance.

Misfire Monitor Diagnostic Operation

The misfire monitor diagnostic is based on crankshaft
rotational velocity (reference period) variations. The En-
gine Control Module (ECM) determines crankshaft rota-
tional velocity using the Crankshaft Position (CKP)
sensor and the Camshaft Position (CMP) sensor. When
a cylinder misfires, the crankshaft slows down momen-
tarily. By monitoring the CKP and CMP sensor signals,
the ECM can calculate when a misfire occurs.

For a non-catalyst damaging misfire, the diagnostic will
be required to monitor a misfire present for between
1000–3200 engine revolutions.

For catalyst-damaging misfire, the diagnostic will re-
spond to misfire within 200 engine revolutions.

Rough roads may cause false misfire detection. A rough
road will cause torque to be applied to the drive wheels
and drive train. This torque can intermittently decrease
the crankshaft rotational velocity. This may be falsely
detected as a misfire.

A rough road sensor, or “G sensor,” works together with
the misfire detection system. The rough road sensor
produces a voltage that varies along with the intensity of
road vibrations. When the ECM detects a rough road,
the misfire detection system is temporarily disabled.

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 Current
#1–4) indicate the number of firing events out of the last
200 cylinder firing events which were misfires. The mis-
fire current counter will display real time data without a
misfire DTC stored. The misfire history counters (Misfire
Histtory #1–4) 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 200
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 re-
porting a DTC. This way, the diagnostic executive re-
ports 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.

Use diagnostic equipment to monitor misfire counter
data on EOBD compliant vehicles. Knowing which spe-
cific 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 cylin-
ders are misfiring. If the counters indicate cylinders
numbers 1 and 4 misfired, look for a circuit or compo-
nent common to both cylinders number 1 and 4.

The misfire diagnostic may indicate a fault due to a tem-
porary fault not necessarily caused by a vehicle emis-
sion system malfunction. Examples include the following
items:

Contaminated fuel.

Low fuel.

Fuel-fouled spark plugs.

Basic engine fault.

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 malfunc-
tion 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 val-
ue 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 intru-
sive test. This test determines if a rich condition is being
caused by excessive fuel vapor from the controlled char-
coal canister. In order to meet EOBD requirements, the
control module uses weighted fuel trim cells to deter-
mine 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 ve-
hicle 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 a scan tool 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 oth-
er times. No fuel trim DTC would set (although an en-
gine idle speed DTC or HO2S DTC may set). Use a
scan tool to observe fuel trim counts while the problem is
occurring.

ENGINE CONTROLS 1F – 17

DIAGNOSTIC INFORMATION AND PROCEDURES

SYSTEM DIAGNOSIS

DIAGNOSTIC AIDS

If an intermittent problem is evident, follow the guide-
lines below.

Preliminary Checks

Before using this section you should have already per-
formed the “Euro On-Board Diagnostic (EOBD) System
Check.”

Perform a thorough visual inspection. This inspection
can often lead to correcting a problem without further
checks and can save valuable time. Inspect for the fol-
lowing conditions:

Engine Control Module (ECM) grounds for being
clean, tight, and in their proper location.

Vacuum hoses for splits, kinks, collapsing and proper
connections as shown on the Vehicle Emission Con-
trol Information label. Inspect thoroughly for any type
of leak or restriction.

Air leaks at the throttle body mounting area and the
intake manifold sealing surfaces.

Ignition wires for cracks, hardness, proper routing,
and carbon tracking.

Wiring for proper connections.

Wiring for pinches or cuts.

Diagnostic Trouble Code Tables

Do not use the Diagnostic Trouble Code (DTC) tables to
try and correct an intermittent fault. The fault must be
present to locate the problem.

Incorrect use of the DTC tables may result in the unnec-
essary replacement of parts.

Faulty Electrical Connections or Wiring

Most intermittent problems are caused by faulty electri-
cal connections or wiring. Perform a careful inspection
of suspect circuits for the following:

Poor mating of the connector halves.

Terminals not fully seated in the connector body.

Improperly formed or damaged terminals. All connec-
tor terminals in a problem circuit should be carefully

inspected, reformed, or replaced to insure contact
tension.

Poor terminal-to-wire connection. This requires re-
moving the terminal from the connector body.

Road Test

If a visual inspection does not find the cause of the prob-
lem, the vehicle can be driven with a voltmeter or a scan
tool connected to a suspected circuit. An abnormal volt-
age or scan tool reading will indicate that the problem is
in that circuit.

If there are no wiring or connector problems found and a
DTC was stored for a circuit having a sensor, except for
DTC P0171 and DTC P0172, replace the sensor.

Intermittent Malfunction Indicator Lamp
(MIL)

An intermittent Malfunction Indicator Lamp(MIL) with no
DTC present may be caused by the following:

Improper installation of electrical options such as
lights, two way radios, sound, or security systems.

MIL driver wire intermittently shorted to ground.

Fuel System

Some intermittent driveability problems can be attrib-
uted to poor fuel quality. If a vehicle is occasionally run-
ning rough, stalling, or otherwise performing badly, ask
the customer about the following fuel buying habits:

Do they always buy from the same source? If so, fuel
quality problems can usually be discounted.

Do they buy their fuel from whichever fuel station that
is advertising the lowest price? If so, check the fuel
tank for signs of debris, water, or other contamina-
tion.

IDLE LEARN PROCEDURE

Whenever the battery cables, the Engine Control Mod-
ule (ECM), or the fuse is disconnected or replaced, the
following idle learn procedure must be performed:

Turn the ignition ON for 10 seconds.

Turn the ignition OFF for 10 seconds.

Content .. 24 25 26 27 ..