Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Look up keyword
Like this
16Activity
0 of .
Results for:
No results containing your search query
P. 1
Diagnostics-Engine

Diagnostics-Engine

Ratings: (0)|Views: 187 |Likes:
Published by api-3833108

More info:

Published by: api-3833108 on Nov 29, 2009
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

09/12/2014

pdf

text

original

DI4SF-01
Vehicle Brought to Workshop
Customer Problem Analysis P.DI-146
Problem Symptom Confirmation
If the engine does not start, perform steps 10 and 12 first
Connect the OBD II scan tool or TOYOTA hand-held tester to DLC3 P.DI-147
If the display indicates a communication fault in the tool, inspect DLC3 P.DI-147
Check DTC and Freezed Frame Data (Precheck)
Record or Print DTC and Freezed Frame Data P.DI-147
Clear DTC and Freezed Frame Data P.DI-147
Visual Inspection
Setting the Check Mode Diagnosis P.DI-147
Symptom Simulation P.IN-18
DTC Chart P.DI-158
Matrix Chart of Problem Symptoms P.DI-169
Circuit Inspection P.DI-170
Adjustment, Repair
DTC Check P.DI-14
Titles inside
are titles of pages in
in the bottom portion. See the indicated
pages for detailed explanations.
this manual, with the page number indicated
Malfunction
occurs.
Malfunction does not occur.
Parts Inspection
Check for Intermittent Problems P.DI-147
Identification of Problem
Confirmation Test
End
123456710
8
9
11
12
13
15
14
16
Normal
Malfunction code.
17
Basic Inspection P.DI-147
-
DIAGNOSTICS
ENGINE (2JZ-GTE)
DI-145
373
Author\ue000:
Date\ue000:
1997 SUPRA (RM502U)
ENGINE (2JZ-GTE)
HOW TO PROCEED WITH TROUBLESHOOTING
Troubleshoot in accordance with the produce on the following page.
DI4SG-01
ENGINE CONTROL SYSTEM Check Sheet
Customer\u2019s Name
Driver\u2019s Name
Date Vehicle
Brought in
License No.
Model and Model
Year
Frame No.
Engine Model
Odometer Reading
km
miles
ProblemSymp
toms
Engine does
not Start
Difficult to
Start
Poor Idling
Poor
Driveability
Engine Stall
Others
Engine does not crank
No initial combustion
No complete combustion
Engine cranks slowly
Other
Incorrect first idle
Idling rpm is abnormal
High (
rpm)
Low (
rpm)
Rough idling
Other
Hesitation
Back fire
Muffler explosion (after-fire)
Surging
Knocking
Other
Soon after starting
After accelerator pedal depressed
After accelerator pedal released
During A/C operation
Shifting from N to D
Other
Dates Problem
Occurred
Problem Frequency
ConditionWh
en
ProblemOccu
rs
Weather
Engine Operation
Engine Temp.
Place
Outdoor
Temperature
Constant
Sometimes (
times per
day/month)
Once only
Other
Fine
Cloudy
Rainy
Snowy
Various/Other
Hot
Warm
Cool
Cold (approx.
\u00b0F/
\u00b0C)
Highway
Suburbs
Inner city
Uphill
Downhill
Rough road
Other
Cold
Warming up
After warming up
Any temp.
Other
Starting
Just after starting (
min.)
Idling
Racing
Driving
Constant speed
Acceleration
Deceleration
A/C switch ON/OFF
Other
Condition of MIL
Remains on
Sometimes light up
Does not light up
Normal
Malfunction code(s) (code
)
Freezed frame data (
)
Normal
Malfunction code(s) (code
)
Freezed frame data (
)
Normal Mode
(Precheck)
Check Mode
DTC Inspection
Inspector\u2019s
Name
DI-146
-
DIAGNOSTICS
ENGINE (2JZ-GTE)
374
Author\ue000:
Date\ue000:
1997 SUPRA (RM502U)
CUSTOMER PROBLEM ANALYSIS CHECK
DI4SH-01
FI0534
Q08242
TOYOTA Hand-Held Tester
DLC3
-
DIAGNOSTICS
ENGINE (2JZ-GTE)
DI-147
375
Author\ue000:
Date\ue000:
1997 SUPRA (RM502U)
PRE-CHECK
1.
DIAGNOSIS SYSTEM
(a) Description

When troubleshooting OBD II vehicles, the only differ- ence from the usual troubleshooting procedure is that you connect to the vehicle the OBD II scan tool complying with SAE J1978 or TOYOTA hand-held tester, and read off various data output from the vehicle\u2019s ECM.

OBD II regulations require that the vehicle\u2019s on-board computer lights up the Malfunction Indicator Lamp (MIL) on the instrument panel when the computer detests a malfunction in the computer itself or in drive system com- ponents which affect vehicle emissions. In addition to the MIL lighting up when a malfunction is detected, the appli- cable Diagnostic Trouble Codes (DTC) prescribed by SAE J2012 are recorded in the ECM memory.

(See pageDI-158 )
If the malfunction does not reoccur in 3 trips, the MIL goes
off but the DTC remain recorded in the ECM memory.

To check the DTC, connect the OBD II scan tool or TOYO- TA hand-held tester to Data Link Connector 3 (DLC3) on the vehicle. The OBD II scan tool or TOYOTA hand-held tester also enables you to erase the DTC and check freezed frame data and various forms of engine data. (For operating instructions, see the OBD II scan tool\u2019s instruc- tion book.)

DTC include SAE controlled codes and Manufacturer
controlled codes.

SAE controlled codes must be set as prescribed by the SAE, while Manufacturer controlled codes can be set freely by the manufacturer within the prescribed limits. (See DTC chart on pageDI-158 )

The diagnosis system operates in normal mode during normal vehicle use. It also has a check mode for techni- cians to simulate malfunction symptoms and trouble- shoot. Most DTC use 2 trip detection logic* to prevent er- roneous detection and ensure thorough malfunction detection. By switching the ECM to check mode when troubleshooting, the technician can cause the MIL to light up for a malfunction that is only detected once or momen- tarily. (TOYOTA hand-held tester only)

(See pageDI-147 )

*2 trip detection logic: When a logic malfunction is first de- tected, the malfunction is temporarily stored in the ECM memory. If the same malfunction is detected again during the second drive test, this second detection causes the MIL to light up.

Activity (16)

You've already reviewed this. Edit your review.
meowmixsd liked this
1 thousand reads
1 hundred reads
mumstel liked this
djtsaby liked this
lcz37296 liked this
lcz37296 liked this
dtipianc liked this
shrek4891 liked this

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->