1997 TOYOTA SUPRA engine

IN04B-01
B02571
A
B
Z09443
- INTRODUCTIONIDENTIFICATION INFORMATION
IN-3
3 Author
: Date
:
1997 SUPRA (RM502U)
IDENTIFICATION INFORMATION
VEHICLE IDENTIFICATION AND
ENGINE SERIAL NUMBER
1. VEHICLE IDENTIFICATION NUMBER
The vehicle identification number is stamped on the vehicle
identification number plate and certification label.
A: Vehicle Identification Number plate
B: Certification Label
2. ENGINE SERIAL NUMBER
The engine serial number is stamped on the engine block as
shown.

IN0253
WRONG CORRECT
IN0252
WRONG CORRECT
IN0002
Example IN-6
- INTRODUCTIONREPAIR INSTRUCTIONS
6 Author
: Date
:
1997 SUPRA (RM502U)
(l) Observe the following precautions to avoid damage to the
following parts:
(1) Do not open the cover or case of the ECU, ECM,
PCM or TCM unless absolutely necessary. (If the IC
terminals are touched, the IC may be destroyed by
static electricity.)


(2) To disconnect vacuum hoses, pull on the end, not
the middle of the hose.
(3) To pull apart electrical connectors, pull on the con-
nector itself, not the wires.
(4) Be careful not to drop electrical components, such
as sensors or relays. If they are dropped on a hard
floor, they should be replaced and not reused.
(5) When steam cleaning an engine, protect the elec-
tronic components, air filter and emissions-related
components from water.
(6) Never use an impact wrench to remove or install
temperature switches or temperature sensors.
(7) When checking continuity at the wire connector, in-
sert the tester probe carefully to prevent terminals
from bending.
(8) When using a vacuum gauge, never force the hose
onto a connector that is too large. Use a step-down
adapter for adjustment. Once the hose has been
stretched, it may leak.
(m) Tag hoses before disconnecting them:
(1) When disconnecting vacuum hoses, use tags to
identify how they should be reconnected.
(2) After completing a job, double check that the vacu-
um hoses are properly connected. A label under the
hood shows the proper layout.
(n) Unless otherwise stated, all resistance is measured at an
ambient temperature of 20°C (68°F). Because the resis-
tance may be outside specifications if measured at high
temperatures immediately after the vehicle has been run-
ning, measurements should be made when the engine
has cooled down.

N02541DLC2
IN0247
N08868
2JZ-GE Engine
DLC1
N08869
2JZ-GTE Engine
DLC1
- INTRODUCTIONREPAIR INSTRUCTIONS
IN-7
7 Author
: Date
:
1997 SUPRA (RM502U)
2. FOR VEHICLE WITH DATA LINK CONNECTOR 2
(DLC2)
(a) The DLC2 is provided inside the cabin (located under the
left side of instrument panel) as a connector exclusively
for diagnosis of data from the engine, automatic transmis-
sion, ABS, A/C, Airbag, Traction Control and Cruise Con-
trol System to improve serviceability.
(b) The DLC1 inside the engine compartment is used for en-
gine adjustment.
(c) Connecting the following terminals of the DLC2 to termi-
nal E
1 selects the diagnosis mode shown in the table.
NOTICE:
Pay enough attention to the terminal connection position
as this will cause a malfunction.
TerminalSystem
TE1Engine and automatic transmission (Normal mode)
TE2 and TE1Engine and automatic transmission (Test mode)
TCABS, A/C, Airbag, Traction Control and Cruise Control
System
TTAutomatic transmission
(d) Refer to the respective system for the inspection method.
HINT:
By connecting the DLC2 up to a monitor specifically designed
for use with the DLC2, the diagnosis result for each system can
be read easily.

IN-14
- INTRODUCTIONFOR ALL OF VEHICLES
14 Author
: Date
:
1997 SUPRA (RM502U)
(f) AIRBAG SENSOR ASSEMBLY
(1) Never reuse the airbag sensor assembly involved
in a collision when the SRS has deployed.
(2) The connectors to the airbag sensor assembly
should be connected or disconnected with the sen-
sor mounted on the floor. If the connectors are con-
nected or disconnected while the airbag sensor as-
sembly is not mounted to the floor, it could cause
undesired ignition of the supplemental restraint sys-
tem.
(3) Work must be started after 90 seconds from the
time the ignition switch is turned to the ºLOCKº posi-
tion and the negative (-) terminal cable is discon-
nected from the battery, even if only loosening the
set bolts of the airbag sensor assembly.
(g) WIRE HARNESS AND CONNECTOR
The SRS wire harness is integrated with the cowl wire har-
ness assembly and floor wire harness assembly. The
wires for the SRS wire harness are encased in a yellow
corrugated tube. All the connectors for the system are
also a standard yellow color. If the SRS wire harness be-
comes disconnected or the connector becomes broken
due to an accident, etc., repair or replace it as shown on
page RS-38.
2. FOR VEHICLES EQUIPPED WITH A CATALYTIC CONVERTER
If large amounts of unburned gasoline flow into the converter, it may overheat and create a fire hazard. To
prevent this, observe the following precautions and explain them to your customer.
(a) Use only unleaded gasoline.
(b) Avoid prolonged idling.
Avoid running the engine at idle speed for more than 20 minutes.
(c) Avoid spark jump test.
(1) Perform spark jump test only when absolutely necessary. Perform this test as rapidly as possible.
(2) While testing, never race the engine.
(d) Avoid prolonged engine compression measurement.
Engine compression tests must be done as rapidly as possible.
(e) Do not run engine when fuel tank is nearly empty.
This may cause the engine to misfire and create an extra load on the converter.
(f) Avoid coasting with ignition turned off and prolonged braking.
(g) Do not dispose of used catalyst along with parts contaminated with gasoline or oil.
3. IF VEHICLE IS EQUIPPED WITH MOBILE COMMUNICATION SYSTEM
(a) For vehicles with mobile communication systems such as two-way radios and cellular telephones, ob-
serve the following precautions.
(b) Install the antenna as far as possible away from the ECU and sensors of the vehicle's electronic sys-
tem.

B02572
TRAC OFF
Indicator Light
TRAC Cut
Switch
N19405
- INTRODUCTIONFOR ALL OF VEHICLES
IN-15
15 Author
: Date
:
1997 SUPRA (RM502U)
(c) Install the antenna feeder at least 20 cm (7.87 in.) away from the ECU and sensors of the vehicle's
electronics systems. For details about ECU and sensors locations, refer to the section on the applica-
ble component.
(d) Do not wind the antenna feeder together with the other wiring. As much as possible, also avoid running
the antenna feeder parallel with other wire harnesses.
(e) Confirm that the antenna and feeder are correctly adjusted.
(f) Do not install powerful mobile communications system.
4. FOR USING OBDII SCAN TOOL OR TOYOTA HAND-HELD TESTER
Observe the following for safety reasons:

Before using the OBDII scan tool or TOYOTA hand-held tester, the OBDII scan tool's instruction
book or TOYOTA hand-held tester's operator manual should be read thoroughly.

Be sure to route all cables securely when driving with the OBDII scan tool or TOYOTA hand-held
tester connected to the vehicle. (i.e. Keep cables away from feet, pedals, steering wheel and shift
lever.)

Two persons are required when test driving with the OBDII scan tool or TOYOTA hand-held tes-
ter, one person to drive the vehicle and one person to operate the OBDII scan tool or TOYOTA
hand-held tester.
5. FOR VEHICLES EQUIPPED WITH TRACTION CON-
TROL (TRAC) SYSTEM
When using a 2 wheel drum tester such as a speedometer tes-
ter or chassis dynamometer, etc., or jacking up the rear wheels
and driving the wheels, always push in the TRAC cut (ºTRAC
OFFº) switch and turn the TRAC system OFF.
(a) Confirm TRAC system is OFF
(1) Press the TRAC cut (ºTRAC OFFº) switch.
(2) Check that the TRAC OFF indicator light comes on
when the TRAC system is turned off by the TRAC
cut switch.
HINT:
The TRAC OFF indicator light should always operate right after
the engine is restarted.
(3) Begin measurements.

IN04F-02
- INTRODUCTIONHOW TO TROUBLESHOOT ECU CONTROLLED
SYSTEMSIN-17
17 Author
: Date
:
1997 SUPRA (RM502U)
HOW TO TROUBLESHOOT ECU CONTROLLED SYSTEMS
GENERAL INFORMATION
A large number of ECU controlled systems are used in the TOYOTA SUPRA. In general, the ECU controlled
system is considered to be a very intricate system requiring a high level of technical knowledge and expert
skill to troubleshoot. However, the fact is that if you proceed to inspect the circuits one by one, troubleshoot-
ing of these systems is not complex. If you have adequate understanding of the system and a basic knowl-
edge of electricity, accurate diagnosis and necessary repair can be performed to locate and fix the problem.
This manual is designed through emphasis of the above standpoint to help service technicians perform ac-
curate and effective troubleshooting, and is compiled for the following major ECU controlled systems:
SystemPage
1. Engine (2JZ-GE)DI-1
2. Engine (2JZ-GTE)DI-145
3. Automatic Transmission (2JZ-GE)DI-316
4. Automatic Transmission (2JZ-GTE)DI-371
5. Anti-Lock Brake SystemDI-440
6. ABS & Traction control SystemDI-499
7. Supplemental Restraint SystemDI-555
8. Theft Deterrent SystemDI-608
9. Cruise Control SystemDI-660
11. Air Conditioning SystemDI-71 1
The troubleshooting procedure and how to make use of it are described on the above pages.
FOR USING OBDII SCAN TOOL OR TOYOTA HAND-HELD TESTER

Before using the OBDII scan tool or TOYOTA hand-held tester, the OBDII scan tool's instruction book
or TOYOTA hand-held tester's operator manual should be read thoroughly.

If the OBDII scan tool or TOYOTA hand-held tester cannot communicate with ECU controlled systems
when you have connected the cable of the OBDII scan tool or TOYOTA hand-held tester to DLC3,
turned the ignition switch ON and operated the scan tool, there is a problem on the vehicle side or tool
side.
(1) If communication is normal when the tool is connected to another vehicle, inspect the diagnosis
data link line (Bus
line) or ECU power circuit of the vehicle.
(2) If communication is still not possible when the tool is connected to another vehicle, the problem
is probably in the tool itself, so perform the Self Test procedures outlined in the Tester Operator's
Manual.

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.

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.