LEMON Manuals: Even more car manuals for everyone: 1960-2025
Home >> Lexus >> 2017 >> RX 350 Base, FWD >> Repair and Diagnosis >> Accessories & Equipment >> Cruise Control Systems >> Lane Control System - Diagnostics - Introduction >> Lane Control System >> How To Proceed With Troubleshooting [08/2019 - ] >> Procedure
April 5, 2026: LEMON Manuals is launched! Read the announcement.

How To Proceed With Troubleshooting [08/2019 - ]: Procedure

  1. VEHICLE BROUGHT TO WORKSHOP 

    Result

    Proceed to
    NEXT

    Result: 

    NEXT 

    See step  2

  2. CUSTOMER PROBLEM ANALYSIS 

    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

    Result

    Proceed to
    NEXT

    Result: 

    NEXT 

    See step  3

  3. PRE-CHECK 
    1. Measure the battery voltage.

      Standard Voltage

      11 to 14 V

      If the voltage is below 11 V, recharge or replace the battery before proceeding to the next step.

    2. Check the fuses and relays.
    3. Check the connector connections and terminals to make sure that there are no abnormalities such as loose connections, deformation, etc.

      Result

      Proceed to
      NEXT

    Result: 

    NEXT 

    See step  4

  4. CHECK COMMUNICATION FUNCTION OF CAN COMMUNICATION SYSTEM* 
    1. Using the Techstream, check for CAN communication system DTCs.

      Refer to DIAGNOSIS SYSTEM [08/2019 - ]

      Result

      Result Proceed to
      CAN DTCs are not output A
      CAN DTCs are output B

    Result: 

    GO TO CAN COMMUNICATION SYSTEM. Refer to  HOW TO PROCEED WITH TROUBLESHOOTING [09/2015 - ] 

    Result: 

    See step  5

  5. CHECK FOR DTCs* 
    1. Using the Techstream, Check for DTCs.

      Chassis > Lane Control > Trouble Codes 

    2. Make a note of the output DTCs.

      Result

      Result Proceed to
      DTCs are not output A
      DTCs are output B

    Result: 

    See step  7

    Result: 

    See step  6

  6. RECONFIRM DTC OUTPUT* 
    1. Using the Techstream, Clear the DTCs.

      Chassis > Lane Control > Clear DTCs 

    2. Reproduce the vehicle conditions that were present when the DTCs that were noted were stored.

      HINT: 

      Refer to each corresponding DTC for details on the detection conditions.

      Refer to DIAGNOSTIC TROUBLE CODE CHART [08/2019 - ] 

    3. Using the Techstream, check for DTCs.

      Chassis > Lane Control > Trouble Codes 

      Result

      Result Proceed to
      DTCs are not output A
      DTCs are output B

    Result: 

    GO TO DTC CHART. Refer to  DIAGNOSTIC TROUBLE CODE CHART [08/2019 - ]  

    Result: 

    See step  7

  7. CHECK VEHICLE CONTROL HISTORY* 
    1. Using the Techstream, check for Vehicle Control History (RoB).

      Chassis > Lane Control > Utility 

      Tester Display
      Vehicle Control History (RoB)
    2. Make a note of the output Vehicle Control History (RoB).

      Result

      Result Proceed to
      Vehicle Control History (RoB) is not output A
      Vehicle Control History (RoB) is output B

    Result: 

    GO TO SYMPTOM SIMULATION. Refer to  HOW TO PROCEED WITH TROUBLESHOOTING [08/2019 - ] 

    Result: 

    See step  8

  8. RECONFIRM VEHICLE CONTROL HISTORY* 
    1. Using the Techstream, clear the Vehicle Control History (RoB).

      Chassis > Lane Control > Utility 

      Tester Display
      Vehicle Control History (RoB)
    2. Using the Techstream, check for Vehicle Control History (RoB).

      Chassis > Lane Control > Utility 

      Tester Display
      Vehicle Control History (RoB)

      Result

      Result Proceed to
      Vehicle Control History (RoB) is not output A
      Vehicle Control History (RoB) is output B

    Result: 

    GO TO SYMPTOM SIMULATION. Refer to  HOW TO PROCEED WITH TROUBLESHOOTING [08/2019 - ] 

    Result: 

    GO TO VEHICLE CONTROL HISTORY. Refer to  VEHICLE CONTROL HISTORY [08/2019 - ]