Page 65 of 1807

IN04G-02
Vehicle Brought Workshop
Customer Problem
Analysis
Symptom Confirmation
and Diagnostic Trouble
Code Check
Symptom Simulation
Diagnostic Trouble
Code Chart
Matrix Chart of Problem
Symptoms
Circuit Inspection or Parts
Inspection
Repair
Confirmation Test
End 1
2
43
5
6
7
8Ask the customer about the conditions and the
environment when the problem occurred.1
Confirm the symptoms and the problem conditions,
and check the diagnostic trouble codes.
(When the problem symptoms do not appear
during confirmation, use the symptom simulation
method described later on.)2, 3
Check the results obtained in Step 2, then confirm
the inspection procedure for the system or the part
which should be checked using the diagnostic
trouble code chart or the matrix chart of problem
symptoms.4, 5, 6
Check and repair the affected system or part in
accordance with the instructions in Step 6. 7
After completing repairs, confirm that the problem
has been eliminated.
(If the problem is not reproduced, perform the
confirmation test under the same conditions and
in the same environment as when it occurred for
the first time.)8
IN-18- INTRODUCTIONHOW TO TROUBLESHOOT ECU CONTROLLED
SYSTEMS
18 Author: Date:
1997 SUPRA (RM502U)
HOW TO PROCEED WITH TROUBLESHOOTING
Carry out troubleshooting in accordance with the procedure on the following page. Here, only the basic pro-
cedure is shown. Details are provided in the DI section, showing the most effective methods for each circuit.
Confirm the troubleshooting procedures first for the relevant circuit before beginning troubleshooting of that
circuit.
Page 66 of 1807

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) Engine control system check sheet.
ENGINE CONTROL SYSTEM Check Sheet
Customer's Name
Driver's Name
Data Vehicle
Brought in
License No.
Model and Model
Year
Frame No.
Engine Model
Odometer Reading
km
miles
Problem Symptoms
Engine does
not Start
Difficult to
Start
Poor Idling
Poor
Drive ability
Engine Stall
Others
Engine does not crankNo initial combustionNo complete combustion
Engine cranks slowly
Other
Incorrect first idleIdling rpm is abnormalHigh ( rpm)Low ( rpm)
Rough idling
Other
HesitationBack fireMuffler explosion (after-fire)Surging
Knocking
Other
Soon after startingAfter accelerator pedal depressed
After accelerator pedal released
During A/C operation
Shifting from N to D
Other
Datas Problem
ConstantSometimes ( times per day/month)
Inspector's
Name
CUSTOMER PROBLEM ANALYSIS CHECK
- INTRODUCTIONHOW TO TROUBLESHOOT ECU CONTROLLED
SYSTEMSIN-19
19 Author: Date:
1997 SUPRA (RM502U)
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 judgment. 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 the troubleshooting section for each
system for your use.
Page 67 of 1807

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.
IN-20- INTRODUCTIONHOW TO TROUBLESHOOT ECU CONTROLLED
SYSTEMS
20 Author: Date:
1997 SUPRA (RM502U)
2. SYMPTOM CONFIRMATION AND DIAGNOSTIC TROUBLE CODE CHECK
The diagnostic system in the TOYOTA SUPRA fulfills various functions. The first function is the Diagnostic
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 TOYOTA SU-
PRA.
SystemDiagnostic Trouble
Code CheckInput Signal Check
(Sensor Check)Other Diagnosis
Function
Engine
Automatic Transmission
Anti-Lock Brake System
ABS & Traction Control System
Supplemental Restraint System
Cruise Control
Air Conditioning (with Check
Mode)
(with Check
Mode)
Diagnostic Test
Mode
Diagnostic Test
Mode
Actuator Check
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.
Page 68 of 1807

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-28).
- INTRODUCTIONHOW TO TROUBLESHOOT ECU CONTROLLED
SYSTEMSIN-21
21 Author: Date:
1997 SUPRA (RM502U)
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.
Page 69 of 1807

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 if the
malfunction occurs.Shake Slightly
Swing Slightly
Vibrate Slightly
HINT: Applying strong vibration to relays may result in open
relays. IN-22
- INTRODUCTIONHOW TO TROUBLESHOOT ECU CONTROLLED
SYSTEMS
22 Author: Date:
1997 SUPRA (RM502U)
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 may be, if he proceeds to troubleshoot without confirming the problem
symptoms he 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 en-
gine is cold, or for a problem which occurs due to vibration caused by the road during driving, etc., the prob-
lem can never be determined so long as the symptoms are confirmed with the engine hot condition or the
vehicle at a standstill. Since vibration, heat or water penetration (moisture) are likely causes for problems
which are 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 matrix chart of problem symptoms for each system to narrow down the
possible causes of the symptom.
Page 70 of 1807

V07469
HEAT METHOD: When the problem seems to occur when the suspect area is heated. 2
NOTICE:
(1) Do not heat to more than 60 °C (140 °F). (Temperature
is limited not to damage the components.)
(2) Do not apply heat directly to parts in the ECU.
3 WATER SPRINKLING METHOD:
NOTICE:
(1) Never sprinkle water directly into the engine
compartment, but indirectly change the temperature and
humidity by applying water spray onto the radiator front
surface.
(2) Never apply water directly onto the electronic
components.
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 (Service 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
- INTRODUCTIONHOW TO TROUBLESHOOT ECU CONTROLLED
SYSTEMSIN-23
23 Author: Date:
1997 SUPRA (RM502U)
Page 71 of 1807

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.
Mass Air Flow Circuit MalfunctionDetection Item
Open or short in mass air flow meter circuit
Mass air flow meter
ECM DTC No.
(See page)Trouble AreaMIL*MemoryP0100
(DI-23)
P0101
(DI-27)Mass Air Flow Circuit
Range/Performance Problem Mass air flow meter
P0115
(DI-32) Open or short in intake air temp. sensor circuit
Intake air temp. sensor
ECM Intake Air Temp. Circuit Malfunction P0110
(DI-28)
Engine Coolant Temp. Circuit
Range/Performance Problem Open or short in engine coolant temp. sensor circuit
Engine coolant temp. sensor
ECM
P0120
(DI-37)
Throttle/ Pedal Position Sensor/Switch
ºAº Circuit Range/Performance
P0116
(DI-36)
Throttle/Pedal Position Sensor/Switch
ºAº Circuit Malfunction
Insufficient Coolant Temp. for Closed Engine coolant temp. sensor
Cooling system Engine Coolant Temp. Circuit
Malfunction
Open or short in throttle position sensor circuit
Throttle position sensor
ECM
Throttle position sensor
Open or short in heated oxygen sensor circuit
Heated oxygen sensor
DTC CHART (SAE Controlled)
HINT: Parameters listed in the chart may not be exactly the same as your reading due to the type of instrument
or other factors.
If a malfunction code is displayed during the DTC check mode, check the circuit for that code listed in the table
below. For details of each code, turn to the page referred to under the ºSee pageº for the respective ºDTC No.º
in the DTC chart.
IN-24- INTRODUCTIONHOW TO TROUBLESHOOT ECU CONTROLLED
SYSTEMS
24 Author: Date:
1997 SUPRA (RM502U)
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 engine diagnostic trouble code chart is shown below as an example.
Page 72 of 1807

- INTRODUCTIONHOW TO TROUBLESHOOT ECU CONTROLLED
SYSTEMSIN-25
25 Author: Date:
1997 SUPRA (RM502U)
5. PROBLEM SYMPTOMS TABLE
The suspect circuits or parts for each problem symptom are shown in the table below. Use this table to trou-
bleshooting 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
Engine does not crank (Does not start)
No initial combustion (Does not start)
No complete combustion (Does not start)1. Starter and starter relay
1. ECM power source circuit
2. Fuel pump control circuit
3. Engine control module (ECM)
1. Starter signal circuit
2. Fuel pump control circuit1. Fuel pump control circuit
PROBLEM SYMPTOMS TABLE
1. Compression
2. Fuel pump control circuit 1. A/C signal circuit
2. Fuel pump control circuit 1. A/C signal circuit (Compressor circuit)
2. ECM power source circuit 1. Starter signal circuit
2. Fuel pump control circuit1. Starter signal circuit
2. Fuel pump control circuit
3. Compression
idling) Hot engine Cold engine (Difficult to start)Engine cranks normally (Difficult to start)
Problem Symptom Page
Indicates the page where the flow chart for each circuit
is located.
Circuit Inspection, Inspection Order
Indicates the circuit which needs to be checked for each problem
symptom. Check in the order indicated by the numbers.
Circuit or Part Name
Indicates the circuit or part which needs to be checked.
ST-14,ST-15
DI-144
DI-148
SF-67
DI-141
EM-3
DI-825 DI-148
DI-148
DI-148
DI-148 DI-141
DI-141