codes TOYOTA T100 1996 Factory Service Manual

Downloaded from www.Manualslib.com manuals search engine IN02H−03
BO4111
Negative Cable
− INTRODUCTIONFOR ALL OF VEHICLES
IN−9
9 Author: Date:
1996 TOYOTA T100 (RM449U)
FOR ALL OF VEHICLES
PRECAUTION
1. FOR VEHICLES EQUIPPED WITH SRS AIRBAG
(a) The TOYOTA T100 is equipped with an SRS (Supple-
mental Restraint System), such as the driver airbag.
Failure to carry out service operations in the correct se-
quence could cause the supplemental restraint system to
unexpectedly deploy during servicing, possibly leading to
a serious accident.
Further, if a mistake is made in servicing the supplemental
restraint system, it is possible the SRS may fail to operate
when required. Before servicing (including removal or
installation of parts, inspection or replacement), be sure
to read the following items carefully, then follow the cor-
rect procedure described in this manual.
(b) GENERAL NOTICE
(1) Malfunction symptoms of the supplemental re-
straint system are difficult to confirm, so the diag-
nostic trouble codes become the most important
source of information when troubleshooting. When
troubleshooting the supplemental restraint system,
always inspect the diagnostic trouble codes before
disconnecting the battery (See page DI−365).
(2) 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.
(The supplemental restraint system is equipped
with a back−up power source so that if work is
started within 90 seconds of disconnecting the neg-
ative (−) terminal cable from the battery, the SRS
may deploy.)
When the negative (−) terminal cable is discon-
nected from the battery, memory of the clock and
audio systems will be cancelled. So before starting
work, make a record of the contents memorized by
the each memory system. Then when work is fin-
ished, reset the clock and audio systems as before.
To avoid erasing the memory of each memory sys-
tem, never use a back−up power supply from out-
side the vehicle.
(3) Even in cases of a minor collision where the SRS
does not deploy, the steering wheel pad should be
inspected (See page RS−9).

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 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  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 − 26)
P0101
(DI − 31)Mass Air Flow Circuit
Range/Performance Problem Mass air flow meter
P0115
(DI − 37) Open or short in intake air temp. sensor circuit
 Intake air temp. sensor
 ECM Intake Air Temp. Circuit Malfunction P0110
(DI − 32)
Engine Coolant Temp. Circuit
Range/Performance Problem Open or short in engine coolant temp. sensor circuit
 Engine coolant temp. sensor
 ECM
P0120
(DI − 43)
Throttle/ Pedal Position Sensor/Switch
”A” Circuit Range/Performance
P0116
(DI − 41)
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−22− INTRODUCTIONHOW TO TROUBLESHOOT ECU CONTROLLED
SYSTEMS
1996 TOYOTA T100 (RM449U)
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.

Downloaded from www.Manualslib.com manuals search engine FI0046
FI0047
FI0048
IN02K−03
IN−26− INTRODUCTIONHOW TO TROUBLESHOOT ECU CONTROLLED
SYSTEMS
1996 TOYOTA T100 (RM449U)
HOW TO USE THE DIAGNOSTIC
CHART AND INSPECTION
PROCEDURE
1. CONNECTOR CONNECTION AND TERMINAL IN-
SPECTION
For troubleshooting, diagnostic trouble code charts or
problem symptom table are provided for each circuit with
detailed inspection procedures on the following pages.
When all the component parts, wire harnesses and con-
nectors of each circuit except the ECU are found to be
normal in troubleshooting, then it is determined that the
problem is in the ECU. Accordingly, if diagnosis is per-
formed without the problem symptoms occurring,refer to
step 8 to replace the ECU, even if the problem is not in the
ECU. So always confirm that the problem symptoms are
occurring, or proceed with inspection while using the
symptom simulation method.
The instructions ”Check wire harness and connector” and
”Check and replace ECU” which appear in the inspection
procedure, are common and applicable to all diagnostic
trouble codes. Follow the procedure outlined below
whenever these instructions appear.
OPEN CIRCUIT:
This could be due to and a disconnected wire harness, faulty
contact in the connector, a connector terminal pulled out, etc.
HINT:
It is rarely the case that a wire is broken in the middle of
it. Most cases occur at the connector. In particular, care-
fully check the connectors of sensors and actuators.
Faulty contact could be due to rusting of the connector
terminals, to foreign materials entering terminals or a de-
formation of connector terminals between the male and
female terminals of the connector. Simply disconnecting
and reconnecting the connectors once changes the
condition of the connection and may result in a return to
normal operation. Therefore, in troubleshooting, if no ab-
normality is found in the wire harness and connector
check, but the problem disappears after the check, then
the cause is considered to be in the wire harness or con-
nectors.
SHORT CIRCUIT:
This could be due to a connect between the wire harness and
the body ground or to a short occurred inside the switch etc.
HINT:
When there is a short circuit between the wire harness and body
ground, check thoroughly whether the wire harness is caught
in the body or is clamped properly.

Downloaded from www.Manualslib.com manuals search engine FI0534
DI0T7−03
FI7231
TOYOTA Hand−Held Tester
DLC3
− DIAGNOSTICSENGINE (3RZ−FE)
DI−3
1996 TOYOTA T100 (RM449U)
PRE−CHECK
1. DIAGNOSIS SYSTEM
(a) Description
When troubleshooting OBD II vehicles, the only dif-
ference 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’s ECM.
OBD II regulations require that the vehicle’s on−
board computer lights up the Malfunction Indicator
Lamp (MIL) on the instrument panel when the com-
puter detects a malfunction in the computer itself or
in drive system components which affect vehicle
emissions. In addition to the MIL lighting up when
a malfunction is detected, the applicable Diagnostic
Trouble Code (DTC) prescribed by SAE J2012 are
recorded in the ECM memory (See page DI−13).
If the malfunction does not reoccur in 3 trips, the MIL goes off
but the DTCs remain recorded in the ECM memory.
To check the DTCs, connect the OBD II scan tool or
TOYOTA hand−held tester to the Data Link Con-
nector 3 (DLC3) on the vehicle. The OBD II scan
tool or TOYOTA hand−held tester also enables you
to erase the DTCs and check freezed frame data
and vaious forms of engine data (For operating
instructions, see the OBD II scan tool’s instruction
book.).
DTCs include SAE controlled codes and manufac-
turer controlled codes. SAE controlled codes must
be set as prescribed by the SAE, while manufactur-
er controlled codes can be set freely by the
manufacturer within the prescribed limits (See DTC
chart on page DI−13).
The diagnosis system operates in normal mode
during normal vehicle use. It also has a check mode
for technicians to simulate malfunction symptoms
and troubleshoot. Most DTCs use 2 trip detection
logic* to prevent erroneous 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 mal-
function that is only detected once or momentarily
(TOYOTA hand−held tester only) (See step 2).
*2 trip detection logic: When a logic malfunction is
first detected, the malfunction is temporarily stored
in the ECM memory. If the same malfunction is de-
tected again during the 2nd drive test, this 2nd
detection causes the MIL to light up.

Downloaded from www.Manualslib.com manuals search engine − DIAGNOSTICSENGINE (3RZ−FE)
DI−7
1996 TOYOTA T100 (RM449U)
(b) Clear the DTC.
The following actions will erase the DTCs and freezed
frame data.
(1) Operating the OBD II scan tool (complying with SAE
J1978) or TOYOTA hand−held tester to erase the
codes. (See the OBD II scan tool’s instruction book
for operating instructions.)
(2) Disconnecting the battery terminals or EFI fuse.
NOTICE:
If the TOYOTA hand−held tester switches the ECM from
normal mode to check mode or vice−versa, or if the igni-
tion switch is turned from ON to ACC or OFF during check
mode, the DTCs and freezed frame data will be erased.
4. FAIL−SAFE CHART
If any of the following codes is recorded, the ECM enters fail−safe mode.
DTC No.Fail−Safe OperationFail−Safe Deactivation Conditions
P0100
Ignition timing fixed at 5° BTDC
Injection time fixed
Starting − − − − − − − − 11.6 msec.
CTP switch ON − − − − 3.2 msec.
CTP switch OFF − − − − 6.0 msec.
Returned to normal condition
P0110Intake air temp. is fixed at 20°C (68°F)Returned to normal condition
P0115Engine coolant temp. is fixed at 80°(176°F)Returned to normal condition
P0120VTA is fixed at 0°
Following condition must be repeated at least 2 times
consecutively
When closed throttle position switch is ON:
0.1 V  VTA  0.95 V
P0135
P0141Heater circuit in which an abnormality is detected is
turned offIgnition switch OFF
P0325Max. timing retardationIgnition switch OFF
P0336Fuel cutReturned to normal condition
P1300Fuel cutReturned to normal condition
5. CHECK FOR INTERMITTENT PROBLEMS
HINT:
TOYOTA HAND−HELD TESTER only:
By putting the vehicle’s ECM in check mode, 1 trip detection logic is possible instead of 2 trip detection logic
and sensitivity to detect open circuits is increased. This makes it easier to detect intermittent problems.
(a) Clear the DTC (See step 3).
(b) Set the check mode (See step 3).
(c) Perform a simulation test (See page IN−16).
(d) Check the connector and terminal (See page IN−26).
(e) Handle the connector (See page IN−26).

Downloaded from www.Manualslib.com manuals search engine DI−26
− DIAGNOSTICSENGINE (3RZ−FE)
1996 TOYOTA T100 (RM449U)
DTC P0101 Mass Air Flow Circuit Range/Performance
Problem
CIRCUIT DESCRIPTION
Refer to DTC P0100 on page DI−22.
DTC No.DTC Detecting ConditionTrouble Area
P0101
Conditions (a), (b) and (c) continue with engine speed 900
rpm or less:
(2 trip detection logic)
(a) Closed throttle position switch: ON
(b) Mass air flow meter output > 2.2 V
(c) THW  70°C (158°F)
Mass air flow meter
Conditions (a) and (b) continue with engine speed 1,850 rpm or
more:
(a) VTA  0.75 V
(b) Mass air flow meter output < 1.0 V
WIRING DIAGRAM
Refer to DTC P0110 (Intake Air Temp Circuit Malfunction) on page DI−27 for the WIRING DIAGRAM.
INSPECTION PROCEDURE
1 Are there any other codes (besides DTC P0101) being output?
YES Go to relevant DTC chart.
NO
Replace mass air flow meter.
DI0TD−02

Downloaded from www.Manualslib.com manuals search engine DI−38
− DIAGNOSTICSENGINE (3RZ−FE)
1996 TOYOTA T100 (RM449U)
DTC P0116 Engine Coolant Temp. Circuit Range/
Performance Problem
CIRCUIT DESCRIPTION
Refer to DTC P0115 on page DI−33.
DTC No.DTC Detecting ConditionTrouble Area
P0116
When engine starts, water temp. is − 7°C (20°F) or less
And, 20 min. or more after engine starts, engine coolant
temp. sensor value is 20°C (68°F) or less
(2 trip detection logic)
Engine coolant temp. sensor
Cooling system
When engine starts, water temp. is between − 7°C (19.4°F)
and 10°C (50°F)
And, 5 min. or more after engine starts, engine coolant temp.
sensor value is 20°C (68°F) or less
(2 trip detection logic)
When engine starts, water temp. is 10°C (50°F) or more
And, 2 min. or more after engine starts, engine coolant temp.
sensor value is 20°C (68°F) or less
(2 trip detection logic)
INSPECTION PROCEDURE
HINT:
If DTCs P0115 and P0116 are output simultaneously, engine coolant temp. sensor circuit may be open.
Perform troubleshooting of DTC P0115 first.
1 Are there any other codes (besides DTC P0116) being output?
YES Go to relevant DTC chart.
NO
2 Check thermostat (See page CO−9).
NG Replace thermostat.
OK
Replace engine coolant temp. sensor (See
page MF−45).
DI0TG−03