2001 TOYOTA AVALON immobilizer

DI-522
- DIAGNOSTICSTHEFT DETERRENT SYSTEM
678 Author
: Date
:
2001 AVALON (RM808U)
Indicator light output:
ConditionIndicator light
Disarming conditionOFF
Arming preparation conditionON
Arming conditionOFF
Alarming conditionON
HINT:
Even in disarming condition, the indicator light flash. (Due to the
signal output form immobilizer system). The indicator always
flashes receiving the signal from the immobilizer system at any
time in the arming condition.
Flashing frequency:
0.2 seconds (ON)
1.8 seconds (OFF)
3. PASSIVE ARMING MODE
This mode can be switched according to the specified op-
eration.
All initially set modes (when shipped from factory) are ac-
tive mode. (No passive mode)

Door
Indicator
Alarming output
System condition
Arming condition Alarming
condition Entry delay time Close
Open
ON
OFF
ON
OFF
- DIAGNOSTICSTHEFT DETERRENT SYSTEM
DI-525
681 Author
: Date
:
2001 AVALON (RM808U)
HINT:
In arming condition either closed door is opened, entry delay
occurs. (14 secs.)
During this time, the mode transfers to disarming condition
when the condition described above * is met.
When the condition is not met, the system judges theft occurs,
the mode transfers to alarming condition.
Indicator light output:
ConditionIndicator light
Disarming conditionOFF
Arming preparation conditionON
Arming condition
(Entry delay time)OFF
(ON)
Alarming conditionON
HINT:
Even in disarming condition, the indicator light flash. (Due to the
signal output form immobilizer system). The indicator always
flashes receiving the signal from the immobilizer system at any
time in the arming condition.
Flashing frequency:
0.2 seconds (ON)
1.8 seconds (OFF)

IN05Y-17
- INTRODUCTIONHOW TO TROUBLESHOOT ECU CONTROLLED
SYSTEMSIN-19
19 Author
: Date
:
2001 AVALON (RM808U)
HOW TO TROUBLESHOOT ECU CONTROLLED SYSTEMS
GENERAL INFORMATION
A large number of ECU controlled systems are used in the AVALON. 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, troubleshooting of
these systems is not complex. If you have adequate understanding of the system and a basic knowledge
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 accurate
and effective troubleshooting, and is compiled for the following major ECU controlled systems:
The troubleshooting procedure and how to make use of it are described on the following pages.
SystemPage
1. EngineDI-1
2. Automatic TransaxleDI-158
3. Anti-Lock Brake System With Electronic Brake Force Distribution (EBD)DI-210
4. ABS With EBD & BA & TRAC & VSC SystemDI-250
5. Supplemental Restraint SystemDI-347
6. Power Seat Control System (w/ Driving position memory)DI-488
7. Theft Deterrent SystemDI-517
8. Cruise Control SystemDI-549
9. Engine Immobilizer SystemDI-597
10.Body Control SystemDI-615
11. Driver Door Control SystemDI-676
12.Passenger Door Control SystemDI-700
13.Multiplex Communication SystemDI-718
14.Air Conditioning SystemDI-752
FOR USING OBD II SCAN TOOL OR TOYOTA HAND-HELD TESTER

Before using the scan tool or tester, the scan tool's instruction book or tester's operator manual should
be read thoroughly.

If the scan tool or tester cannot communicate with ECU controlled systems when you have connected
the cable of the scan tool or 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 outline in the Tester Operator's
Manual.

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-22- INTRODUCTIONHOW TO TROUBLESHOOT ECU CONTROLLED
SYSTEMS
22 Author
: Date
:
2001 AVALON (RM808U)
2. SYMPTOM CONFIRMATION AND DIAGNOSTIC TROUBLE CODE CHECK
The diagnostic system in the AVALON 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 AVALON.
SystemDiagnostic Trouble
Code CheckInput Signal Check
(Sensor Check)Diagnostic Test
Mode (Active Test)
Engine
Automatic Transaxle
Anti-Lock Brake System With Electronic Brake Force Distribution (EBD)
ABS With EBD & BA & TRAC & VSC System
Supplemental Restraint System
Cruise Control System
Engine Immobilizer System
Multiplex Communication System
Air Conditioning System (with Check
Mode)
 (with Check
Mode)











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.