1996 TOYOTA T100 engine

Downloaded from www.Manualslib.com manuals search engine IN−14
− INTRODUCTIONFOR ALL OF VEHICLES
14 Author: Date:
1996 TOYOTA T100 (RM449U)
3. IF VEHICLE IS EQUIPPED WITH MOBILE COMMUNICATION SYSTEM
For vehicles with mobile communication systems such as two−way radios and cellular telephones, observe
the following precautions.
(1) Install the antenna as far as possible away from the ECU and sensors of the vehicle’s electronic
system.
(2) Install the antenna feeder at least 20 cm (7.87 in.) away from the ECU and sensors of the ve-
hicle’s electronics systems. For details about ECU and sensors locations, refer to the section on
the applicable component.
(3) Avoid winding the antenna feeder together with the other wiring as much as possible, and also
avoid running the antenna feeder parallel with other wire harnesses.
(4) Confirm that the antenna and feeder are correctly adjusted.
(5) Do not install powerful mobile communications system.

Downloaded from www.Manualslib.com manuals search engine IN02I−02
− INTRODUCTIONHOW TO TROUBLESHOOT ECU CONTROLLED
SYSTEMSIN−15
15 Author: Date:
1996 TOYOTA T100 (RM449U)
HOW TO TROUBLESHOOT ECU CONTROLLED SYSTEMS
GENERAL INFORMATION
A large number of ECU controlled systems are used in the TOYOTA T100. 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. 3RZ−FE EngineDI−1
2. 5VZ−FE EngineDI−127
3. Automatic TransmissionDI−263
4. Anti−Lock Brake systemDI−319
5. Supplemental Restraint SystemDI−363
6. Cruise ControlDI−408
The troubleshooting procedure and how to make use of it are described on the above pages.

Downloaded from www.Manualslib.com manuals search engine IN02J−03
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−16− INTRODUCTIONHOW TO TROUBLESHOOT ECU CONTROLLED
SYSTEMS
1996 TOYOTA T100 (RM449U)
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 each section, showing the most effective methods for each circuit.
Confirm the troubleshooting procedures first for the relevant circuit before beginning troubleshooting of that
circuit.

Downloaded from www.Manualslib.com manuals search engine 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−17
1996 TOYOTA T100 (RM449U)
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 the troubleshooting section for each
system for your use.

Downloaded from www.Manualslib.com manuals search engine 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−18− INTRODUCTIONHOW TO TROUBLESHOOT ECU CONTROLLED
SYSTEMS
1996 TOYOTA T100 (RM449U)
2. SYMPTOM CONFIRMATION AND DIAGNOSTIC TROUBLE CODE CHECK
The diagnostic system in the TOYOTA T100 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
T100.
SystemDiagnostic Trouble
Code CheckInput Signal Check
(Sensor Check)Other Diagnosis
Function
Engine (3RZ−FE, 5VZ−FE)
Automatic Transmission
Anti−Lock Brake system
Supplemental Restraint System
Cruise Control (with Test Mode)
 (with Test Mode)






Cancel Signal
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.

Downloaded from www.Manualslib.com manuals search engine 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−26).
− INTRODUCTIONHOW TO TROUBLESHOOT ECU CONTROLLED
SYSTEMSIN−19
1996 TOYOTA T100 (RM449U)
Taking into account the points on the previous page, a flow chart showing how to proceed with troubleshoot-
ing using the diagnostic trouble code check is shown below. This flow chart shows how to utilize the diagnos-
tic 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.

Downloaded from www.Manualslib.com manuals search engine 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−20
− INTRODUCTIONHOW TO TROUBLESHOOT ECU CONTROLLED
SYSTEMS
1996 TOYOTA T100 (RM449U)
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) is likely cause for problem which
is difficult to reproduce, the symptom simulation tests introduced here are effective measures in that the ex-
ternal 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.

Downloaded from www.Manualslib.com manuals search engine 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−21
1996 TOYOTA T100 (RM449U)