Lexus ES manuals

Lexus ES: General Information


  • A large number of ECU controlled systems are used in this vehicle. In general, ECU controlled systems are considered to be very intricate, requiring a high level of technical knowledge to troubleshoot. However, most problem checking procedures only involve inspecting the ECU controlled system circuits one by one. An adequate understanding of the system and a basic knowledge of electricity is enough to perform effective troubleshooting, accurate diagnosis and necessary repairs.
  • When using the Techstream*


    *: The Techstream is the name for the diagnostic tester in North America.

    • Before using the Techstream, read the operator's manual thoroughly.
    • If the Techstream cannot communicate with the ECU controlled systems when connected to the DLC3 with the ignition switch ON and the Techstream on, there is a problem on the vehicle side or the Techstream side.
      1. If communication is possible when the Techstream is connected to another vehicle, inspect the diagnosis data link line (bus (+) line), CANH and CANL lines, and the power source circuits of the vehicle ECUs.
      2. If communication is still not possible when the Techstream is connected to another vehicle, the problem is probably in the Techstream itself. Perform the Self Test procedure outlined in the Techstream operator's manual.


  • The troubleshooting procedures consist of diagnostic procedures for when a DTC is stored and diagnostic procedures for when no DTCs are stored. The basic idea is explained in the following table.

    Procedure Type


    Troubleshooting Method

    DTC Based Diagnosis

    The diagnostic procedure is based on the DTC that is stored.

    The malfunctioning part is identified based on the DTC detection conditions using a process of elimination.

    The possible trouble areas are eliminated one-by-one using the Techstream and inspection of related parts.

    Symptom Based Diagnosis

    (No DTCs stored)

    The diagnostic procedure is based on problem symptoms.

    The malfunctioning part is identified based on the problem symptoms using a process of elimination.

    The possible trouble areas are eliminated one-by-one using the Techstream and inspection of related parts.

  • Vehicle systems are complex and use many ECUs that are difficult to inspect independently. Therefore, a process of elimination is used, where components that can be inspected individually are inspected, and if no problems are found in these components, the related ECU is identified as the problem and replaced.
  • It is extremely important to ask the customer about the environment and the conditions present when the problem occurred (Customer Problem Analysis). This makes it possible to simulate the conditions and confirm the symptom. If the symptom cannot be confirmed or the DTC does not recur, the malfunctioning part may not be identified using the troubleshooting procedure, and the ECU for the related system may be replaced even though it is not defective. If this happens, the original problem will not be solved.
  • In order to prevent endless expansion of troubleshooting procedures, the troubleshooting procedures are written with the assumption that multiple malfunctions do not occur simultaneously for a single problem symptom.
  • To identify the malfunctioning part, troubleshooting procedures narrow down the target by separating components, ECUs and wire harnesses during the inspection. If the wire harness is identified as the cause of the problem, it is necessary to inspect not only the connections to components and ECUs but also all of the wire harness connectors between the component and the ECU.


(a) The data of each system and Diagnostic Trouble Codes (DTCs) can be read from the Data Link Connector 3 (DLC3) of the vehicle. When the system seems to be malfunctioning, use the Techstream to check for malfunctions and perform repairs.


(a) The vehicle ECUs use ISO 15765-4 communication protocol. The terminal arrangement of the DLC3 complies with SAE J1962 and matches the ISO 15765-4 format.

Terminal No. (Symbol)

Terminal Description


Specified Condition

7 (SIL) - 5 (SG)

Bus "+" line

During transmission

Pulse generation

4 (CG) - Body ground

Chassis ground


Below 1 Ω

5 (SG) - Body ground

Signal ground


Below 1 Ω

16 (BAT) - Body ground

Auxiliary battery positive


11 to 14 V

6 (CANH) - 14 (CANL)

CAN bus line

Ignition switch off*

54 to 69 Ω

6 (CANH) - 4 (CG)

HIGH-level CAN bus line

Ignition switch off*

200 Ω or higher

14 (CANL) - 4 (CG)

LOW-level CAN bus line

Ignition switch off*

200 Ω or higher

6 (CANH) - 16 (BAT)

HIGH-level CAN bus line

Ignition switch off*

6 kΩ or higher

14 (CANL) - 16 (BAT)

LOW-level CAN bus line

Ignition switch off*

6 kΩ or higher


*: Before measuring the resistance, leave the vehicle as is for at least 1 minute and do not operate the ignition switch, any other switches or the doors.

If the result is not as specified, the DLC3 may be malfunctioning. Repair or replace the harness or connector.


 Electronic Circuit Inspection Procedure

ELECTRONIC CIRCUIT INSPECTION PROCEDURE BASIC INSPECTION (a) WHEN MEASURING RESISTANCE OF ELECTRONIC PARTS (1) Unless otherwise stated, all resistance measurements are standard values measured at

 How To Proceed With Troubleshooting

HOW TO PROCEED WITH TROUBLESHOOTING OPERATION FLOW HINT: Perform troubleshooting in accordance with the procedure below. The following is an outline of basic troubleshooting procedure. Confirm th

 How To Use This Manual

General Information GENERAL INFORMATION GENERAL DESCRIPTION (a) This manual is written in accordance with SAE J2008. (b) Repair operations can be separated mainly into the following 3 processes:



REMOVAL CAUTION / NOTICE / HINT The necessary procedures (adjustment, calibration, initialization, or registration) that must be performed after parts are removed, installed, or replaced during brake actuator assembly removal/installation are shown below. Necessary Procedures After Parts Removed/Ins

 How To Proceed With Troubleshooting

CAUTION / NOTICE / HINT HINT: Use the following procedure to troubleshoot the parking support alert system. *: Use the Techstream. PROCEDURE 1. VEHICLE BROUGHT TO WORKSHOP NEXT 2. CUSTOMER PROBLEM ANALYSIS NEXT 3. INSPECT AUXILIARY BA

© 2016-2024 Copyright