1999 TOYOTA AVENSIS Supplement

Important Points in the Customer Problem Analysis
 What ––––– Vehicle model, system name
 When ––––– Date, time, occurrence frequency
 Where ––––– Road conditions
 Under what conditions? ––––– Running conditions, driving conditions, weather conditions
 How did it happen? ––––– Problem symptoms
(Sample) Supplemental restraint system check sheet.
Supplemental Restraint System Check Sheet
Customer’s Name
Date Vehicle Brought In
Registration No.
Frame No.
Odometer Reading
km
miles
Date Problem First Occurred
Weather
Temperature
Vehicle OperationFine Cloudy
StartingIdling
Driving
Constant speed Acceleration
OtherInspector’s
Name
CUSTOMER PROBLEM ANALYSIS CHECK
Registration Year
RainySnowyOther / / / /
/ /
Approx.
Deceleration [
]
IN–20– INTRODUCTIONHOW TO TROUBLESHOOT ECU CONTROLLED
SYSTEMS
1. CUSTOMER PROBLEM ANALYSIS
In troubleshooting, the problem symptoms must be confirmed accurately and all preconceptions must be
cleared away in order to give an accurate judgement. To ascertain just what the problem symptoms are, it
is extremely important to ask the customer about the problem and the conditions at the time it occurred.
Important Point in the Problem Analysis:
The following 5 items are important points in the problem analysis. Past problems which are thought to be
unrelated and the repair history, etc. may also help in some cases, so as much information as possible should
be gathered and its relationship with the problem symptoms should be correctly ascertained for reference
in troubleshooting. A customer problem analysis table is provided in DI section for each system for your use.

DIAGNOSTIC TROUBLE CODE CHECK PROCEDURE
Diagnostic Trouble
Code Check (Make a
note of and then clear)Confirmation
of SymptomsDiagnostic Trouble
Code CheckProblem Condition
Diagnostic Trouble
Code DisplayProblem symptoms
existSame diagnostic
trouble code is
displayedProblem is still occurring in the diagnostic
circuit
Normal code is
displayedThe problem is still occurring in a place
other than in the diagnostic circuit
(The diagnostic trouble code displayed
first is either for a past problem or it is a
secondary problem)
No problem
symptoms existThe problem occurred in the diagnostic
circuit in the past
Normal Code DisplayProblem symptoms
existNormal code is
displayedThe problem is still occurring in a place
other than in the diagnostic circuit
No problem
symptoms existNormal code is
displayedThe problem occurred in a place other
than in the diagnostic circuit in the past
– INTRODUCTIONHOW TO TROUBLESHOOT ECU CONTROLLED
SYSTEMSIN–21
2. SYMPTOM CONFIRMATION AND DIAGNOSTIC TROUBLE CODE CHECK
The diagnostic system in the AVENSIS/ CORONA fulfills various functions. The first function is the Diagnos-
tic Trouble Code Check in which a malfunction in the signal circuits to the ECU is stored in code in the ECU
memory at the time of occurrence, to be output by the technician during troubleshooting. Another function
is the Input Signal Check which checks if the signals from various switches are sent to the ECU correctly.
By using these check functions, the problem areas can be narrowed down quickly and troubleshooting can
be performed effectively. Diagnostic functions are incorporated in the following systems in the AVENSIS/
CORONA.
SystemDiagnostic Trouble
Code CheckInput Signal Check
(Sensor Check)Other Diagnosis
Function
Supplemental Restraint System
In diagnostic trouble code check, it is very important to determine whether the problem indicated by the diag-
nostic trouble code is still occurring or occurred in the past but returned to normal at present. In addition,
it must be checked in the problem symptom check whether the malfunction indicated by the diagnostic
trouble code is directly related to the problem symptom or not. For this reason, the diagnostic trouble codes
should be checked before and after the symptom confirmation to determine the current conditions, as shown
in the table below. If this is not done, it may, depending on the case, result in unnecessary troubleshooting
for normally operating systems, thus making it more difficult to locate the problem, or in repairs not pertinent
to the problem. Therefore, always follow the procedure in correct order and perform the diagnostic trouble
code check.

Diagnostic trouble code check
Making a note of and clearing of the diagnostic trouble codes displayed
Symptom confirmation
No problem symptoms
exist Problem symptoms
exist
Simulation test using the symptom
simulation methods
 Normal code displayed
 Problem symptoms exist Normal code displayed
 No problem symptoms exist Diagnostic trouble code check
Troubleshooting of problem indicated
by diagnostic trouble code Diagnostic trouble code displayed
 Problem symptoms exist
System Normal Troubleshooting of each
problem symptom
If a diagnostic trouble code was
displayed in the initial diagnostic
trouble code check, it indicates
that the trouble may have occurred
in a wire harness or connector in
that circuit in the past. Therefore,
check the wire harness and con-
nectors (See page IN–29).
IN–22– INTRODUCTIONHOW TO TROUBLESHOOT ECU CONTROLLED
SYSTEMS
Taking into account the above points, a flow chart showing how to proceed with troubleshooting using the
diagnostic trouble code check is shown below. This flow chart shows how to utilize the diagnostic trouble
code check effectively, then by carefully checking the results, indicates how to proceed either to diagnostic
trouble code troubleshooting or to troubleshooting of problem symptoms.

V07268
VIBRATION METHOD: When vibration seems to be the major cause.
CONNECTORS
WIRE HARNESS
PARTS AND SENSOR1
Slightly shake the connector vertically and horizontally.
Slightly shake the wire harness vertically and horizontally.
The connector joint, fulcrum of the vibration, and body
through portion are the major areas to be checked thorough-
ly.
Apply slight vibration with a finger to the part of the sensor
considered to be the problem cause and check that the mal-
function occurs.Shake Slightly
Swing Slightly
Vibrate Slightly
HINT:
Applying strong vibration to relays may result in open relays.
– INTRODUCTIONHOW TO TROUBLESHOOT ECU CONTROLLED
SYSTEMSIN–23
3. SYMPTOM SIMULATION
The most difficult case in troubleshooting is when there are no problem symptoms occurring. In such cases,
a thorough customer problem analysis must be carried out, then simulate the same or similar conditions and
environment in which the problem occurred in the customer’s vehicle. No matter how much experience a
technician has, or how skilled he or she may be, if he or she proceeds to troubleshoot without confirming
the problem symptoms he or she will tend to overlook something important in the repair operation and make
a wrong guess somewhere, which will only lead to a standstill. For example, for a problem which only occurs
when the engine is cold, or for a problem which occurs due to vibration caused by the road during driving,
etc., the problem can never be determined so long as the symptoms are confirmed with the engine hot condi-
tion or the vehicle at a standstill. Since vibration, heat or water penetration (moisture) is likely cause for prob-
lem which is difficult to reproduce, the symptom simulation tests introduced here are effective measures in
that the external causes are applied to the vehicle in a stopped condition.
Important Points in the Symptom Simulation Test:
In the symptom simulation test, the problem symptoms should of course be confirmed, but the problem area
or parts must also be found out. To do this, narrow down the possible problem circuits according to the symp-
toms before starting this test and connect a tester beforehand. After that, carry out the symptom simulation
test, judging whether the circuit being tested is defective or normal and also confirming the problem symp-
toms at the same time. Refer to the problem symptoms table for each system to narrow down the possible
causes of the symptom.


B02390
HEAT METHOD: When the problem seems to occur when the suspect area is heated. 2
NOTICE:3 WATER SPRINKLING METHOD:
(1)
(2)
4 OTHER: When a malfunction seems to occur when electrical load is excessive.When the malfunction seems to occur on a rainy day or in a
high–humidity condition. Heat the component that is the likely cause of the malfunction
with a hair dryer or similar object. Check to see if the malfunction
occurs.
Sprinkle water onto the vehicle and check to see if the malfunc-
tion occurs.
Turn on all electrical loads including the heater blower, head
lights, rear window defogger, etc. and check to see if the mal-
function occurs.ON HINT:
If a vehicle is subject to water leakage, the leaked water may
contaminate the ECU. When testing a vehicle with a water leak-
age problem, special caution must be taken.
Malfunc-
tion
Do not heat to more than 60 C (140 F). (Temperature
is limited not to damage the components.)
Do not apply heat directly to parts in the ECU. (1)
(2)
Never sprinkle water directly into the engine compart-
ment, but indirectly change the temperature and hu-
midity by applying water spray onto the radiator front
surface.
Never apply water directly onto the electronic compo-
nents. NOTICE: IN–24
– INTRODUCTIONHOW TO TROUBLESHOOT ECU CONTROLLED
SYSTEMS

Detection Item DTC No.
(See page)Trouble AreaSRS
DIAGNOSTIC TROUBLE CODE CHART
If a malfunction code is displayed during the DTC check, check the circuit listed for that code in the table
below. (Proceed to the page given for that circuit).
Warming Light
ON
ON
ON
ON
ON
ON
ON
DTC No.
Indicates the diagnostic trouble code.
Page or Instructions
Indicates the page where the inspection procedure
for each circuit is to be found, or gives instructions
for checking and repairs. 

Detection Item
Indicates the system of the problem or
contents of the problem. Trouble Area
Indicates the suspect area of the
problem. 
11
(DI–165)
12
(DI–170)
13
(DI–174)
14
(DI–178)
15
(DI–178)
16
airbag sensor assembly malfunction Front airbag sensor assembly (RH)
malfunction Short in D squib circuit (to ground)
Short in D squib circuit (to B)
Short in D squib circuit
Open in D squib circuit
Front airbag sensor assembly (LH)
malfunction Steering wheel pad (squib)
 Spiral cable
 Airbag sensor assembly
 Wire harness
 Front airbag sensor assembly (RH)
 Wire harness
 Front airbag sensor assembly (LH)
 Wire harness  Steering wheel pad (squib)
 Spiral cable
 Airbag sensor assembly
 Wire harness
 Steering wheel pad (squib)
 Spiral cable
 Airbag sensor assembly
 Wire harness
 Steering wheel pad (squib)
 Spiral cable
 Airbag sensor assembly
 Wire harness
Airbag sensor assembly
 Front passenger airbag sensor assembly (squib)
 Airbag sensor assembly Short in P squib circuit (to ground)ON
– INTRODUCTIONHOW TO TROUBLESHOOT ECU CONTROLLED
SYSTEMSIN–25
4. DIAGNOSTIC TROUBLE CODE CHART
The inspection procedure is shown in the table below. This table permits efficient and accurate troubleshoot-
ing using the diagnostic trouble codes displayed in the diagnostic trouble code check. Proceed with trouble-
shooting in accordance with the inspection procedure given in the diagnostic chart corresponding to the
diagnostic trouble codes displayed. The Supplemental Restraint System diagnostic trouble code chart is
shown below as an example.

IN–26– INTRODUCTIONHOW TO TROUBLESHOOT ECU CONTROLLED
SYSTEMS
5. PROBLEM SYMPTOMS TABLE
The suspected circuits or parts for each problem symptom are shown in the table below. Use this table to
troubleshoot the problem when a ”Normal” code is displayed in the diagnostic trouble code check but the
problem is still occurring. Numbers in the table indicate the inspection order in which the circuits or parts
should be checked.
HINT:
When the problem is not detected by the diagnostic system even though the problem symptom is present,
it is considered that the problem is occurring outside the detection range of the diagnostic system, or that
the problem is occurring in a system other than the diagnostic system.
Symptom
Suspect AreaSee page
With the ignition switch in the ACC or ON position, the SRS warning
light sometimes lights up after approx. 6 seconds have elapsed.
SRS warning light is always lit up even when ignition switch is in
the LOCK position
With the ignition switch in the ACC or ON position, the SRS warning
light does not light up.
PROBLEM SYMPTOMS TABLE
DTC is not displayed.
SRS warning light is always lit up at the time of DTC check
procedure.
DTC is displayed without Tc and E1 terminal connection.DI–294 DI–290
 Problem Symptom
Proceed with troubleshooting of each circuit in the table below.
 SRS warning light circuit
(Always lights up when ignition switch is in
LOCK position.)
 SRS warning light circuit
(Dose not light up when ignition switch is turned to
ACC or ON.)
 Tc terminal circuit
DI–288
Circuit Inspection, Inspection Order
Indicates the circuit which needs to be checked for each problem
symptom. Check in the order indicated by the numbers. Page
Indicates the page where the flow chart for each circuit
is located. 
Circuit or Part Name
Indicates the circuit or part which needs to be checked. 









B02407
WIRING DIAGRAM
DTC 13 Short in D Squib Circuit
CIRCUIT DESCRIPTION
The D squib circuit consists of the airbag sensor assembly, spiral cable and steering wheel pad.
It causes the airbag to deploy when the airbag deployment conditions are satisfied.
For details of the function of each components,see OPERATION on page RS–2.
DTC 13 is recorded when a short is detected in the D squib circuit.
DTC No.DTC Detecting Condition
Trouble Area
Short circuit between D wire harness and D wire harness of squib
D squib malfunction
Spiral cable malfunction
Airbag sensor assembly malfunctionSteering wheel pad (D squib)
Spiral cable
Airbag sensor assembly
Wire harness
 Diagnostic Trouble Code No. and Detection Item
Circuit Description
The major role and operation, etc. of the circuit
and its component parts are explained. 
Indicates the diagnostic trouble code, diagnostic
trouble code set parameter and suspect area of
the problem. 
Wiring Diagram
This shows a wiring diagram of the circuit.
Use this diagram together with ELECTRICAL
WIRING DIAGRAM to thoroughly understand the
circuit.
Wire colors are indicated by an alphabetical code.
B = Black, L = Blue, R = Red, BR = Brown,
LG = Light Green, V = Violet, G = Green,
O = Orange, W = White, GR = Gray, P = Pink,
Y = Yellow
The first letter indicates the basic wire color and
the second letter indicates the color of the stripe. 
Spiral
Cable
G–R
G–Y 1
27
6D+
D–
A15
A15
D SquibAirbag Sensor
Assembly
13
– INTRODUCTIONHOW TO TROUBLESHOOT ECU CONTROLLED
SYSTEMSIN–27
6. CIRCUIT INSPECTION
How to read and use each page is shown below.