Lexus ES: How To Proceed With Troubleshooting
CAUTION / NOTICE / HINT
HINT:
- Use the following procedure to troubleshoot the vehicle proximity notification system.
- *: Use the Techstream.
PROCEDURE
| 1. | VEHICLE BROUGHT TO WORKSHOP |
|
.gif)
| 2. | CUSTOMER PROBLEM ANALYSIS AND SYMPTOM CHECK |
HINT:
- In troubleshooting, confirm that the problem symptoms have been accurately identified. Preconceptions should be discarded in order to make an accurate judgment. To clearly understand what the problem symptoms are, it is extremely important to ask the customer about the problem and the conditions at the time the malfunction occurred.
- Gather as much information as possible for reference. Past problems that seem unrelated may also help in some cases.
-
The following 5 items are important points for problem analysis:
What
Vehicle model, system name
When
Date, time, occurrence frequency
Where
Road conditions
Under what conditions?
Driving conditions, weather conditions
How did it happen?
Problem symptoms
|
| 3. | PRE-CHECK |
(a) Measure the auxiliary battery voltage with the power switch off.
Standard Voltage:
11 to 14 V
If the voltage is below 11 V, recharge or replace the auxiliary battery before proceeding to the next step.
(b) Check the fuses and relays.
(c) Check the connector connections and terminals to make sure that there are no abnormalities such as loose connections, deformation, etc.
|
| 4. | CHECK CAN COMMUNICATION SYSTEM* |
(a) Using the Techstream, check for CAN communication system DTCs.
Click here .gif)
| Result | Proceed to |
|---|---|
| CAN DTCs are not output | A |
| CAN DTCs are output | B |
| B | .gif) | GO TO CAN COMMUNICATION SYSTEM |
|
| 5. | CHECK FOR DTC* |
(a) Check for DTCs.
Body Electrical > Vehicle Proximity Notification System > Trouble Codes| Result | Proceed to |
|---|---|
| DTCs are not output | A |
| DTCs are output | B |
| B | | GO TO DIAGNOSTIC TROUBLE CODE CHART |
|
| 6. | PROBLEM SYMPTOMS TABLE |
(a) Refer to Problem Symptoms Table.
Click here
| Result | Proceed to |
|---|---|
| Fault is not listed in Problem Symptoms Table | A |
| Fault is listed in Problem Symptoms Table | B |
| B | | GO TO PROBLEM SYMPTOMS TABLE |
|
| 7. | OVERALL ANALYSIS AND TROUBLESHOOTING* |
(a) Operation Check.
Click here
(b) Data List / Active Test
Click here
(c) Terminals of ECU
Click here
(d) Inspection
|
| 8. | REPAIR OR REPLACE |
|
| 9. | CONFIRMATION TEST |
| NEXT | | END |
READ NEXT:
Operation Check
OPERATION CHECK VEHICLE PROXIMITY NOTIFICATION SYSTEM OPERATION CHECK (a) System operation check (vehicle stopped) (1) Apply the parking brake. (2) Turn the power switch on (IG). (3) With the brake pe
Problem Symptoms Table
PROBLEM SYMPTOMS TABLE HINT:
Use the table below to help determine the cause of problem symptoms. If multiple suspected areas are listed, the potential causes of the symptoms are listed in order of
Terminals Of Ecu
TERMINALS OF ECU CHECK VEHICLE APPROACHING SPEAKER CONTROLLER (a) Disconnect the G42 vehicle approaching speaker controller connector. (b) Measure the voltage and resistance according to the value(s)
SEE MORE:
Terminals Of Ecu
TERMINALS OF ECU CHECK AIR CONDITIONING AMPLIFIER ASSEMBLY *A w/o Seat Heater *B w/ Seat Heater (a) Disconnect the G39 air conditioning amplifier assembly connector. (b) Measure the voltage and resistance according to the value(s) in the table below. HINT: Measure the values on the wire
Operation Check
OPERATION CHECK DCM OPERATION HISTORY HINT:
This function shows the telematics network status when the DCM (telematics transceiver) was operated. Use this when no DTC is present but this telematics system was unable to connect to the call center. This symptom may occur if cell phone signal streng
