LEMON Manuals: Even more car manuals for everyone: 1960-2025
Home >> Toyota >> 2016 >> Prius C Four >> Repair and Diagnosis >> Restraints >> Restraints Control Systems >> Pre-Collision System - Diagnostics - Introduction >> Pre-Collision System >> How To Proceed With Troubleshooting [06/2017 - ] >> Procedure
April 5, 2026: LEMON Manuals is launched! Read the announcement.

How To Proceed With Troubleshooting [06/2017 - ]: Procedure

  1. VEHICLE BROUGHT TO WORKSHOP 

    Result

    Proceed to
    NEXT

    NEXT 

    See step  2

  2. INSPECT AUXILIARY BATTERY VOLTAGE 
    1. Measure the auxiliary battery voltage with the power switch off.

      Standard Voltage

      11 to 14 V

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

      Result

      Proceed to
      NEXT

    NEXT 

    See step  3

  3. CHECK CAN COMMUNICATION SYSTEM* 
    1. Use the Techstream to check if the CAN communication system is functioning normally.

      Refer to DIAGNOSIS SYSTEM [06/2017 - ]

      Result

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

    Result: 

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

    Result: 

    See step  4

  4. INSPECT WARNING LIGHT 
    1. Check the condition of the warning lights on the combination meter assembly.

      Result

      DTC Condition Proceed to
      Only the PCS warning light is blinking or illuminated A
      The PCS warning light is not blinking or illuminated
      The PCS warning light and other warning lights are illuminated or blinking B

    Result: 

    REFER TO MALFUNCTIONING SYSTEM 

    Result: 

    See step  5

  5. INSPECT MULTI-INFORMATION DISPLAY 
    1. Check if a pre-collision system warning message is displayed on the multi-information display in the combination meter assembly.

      Result

      DTC Condition Proceed to
      "PRE-COLLISION SYSTEM MALFUNCTION VISIT YOUR DEALER" is displayed A
      Any of the following messages is displayed:
      • "PRE-COLLISION SYSTEM UNAVAILABLE"
      • "FRONT CAMERA UNAVAILABLE"
      • "FRONT CAMERA VISION BLOCKED CLEAN AND DEMIST WINDSHIELD"
      B
      Warning message is not displayed C

    Result: 

    See step  8

    Result: 

    See step  12

    Result: 

    See step  6

  6. CHECK FOR DTCs* 
    1. Clear the DTCs (Refer to DTC CHECK / CLEAR [11/2015 - ] ).
    2. Check for DTCs (Refer to DTC CHECK / CLEAR [11/2015 - ] ).

      Result

      DTC Condition Proceed to
      DTCs are not output (symptoms can be confirmed or reproduced) A
      DTCs are not output (symptoms cannot be confirmed or reproduced) B
      DTCs are output C

    Result: 

    REFER TO SYMPTOM SIMULATION 

    Result: 

    REFER TO DIAGNOSTIC TROUBLE CODE CHART 

    Result: 

    See step  7

  7. READ VALUE USING TECHSTREAM 
    1. Read the Data List according to the display on the Techstream (Refer to DATA LIST / ACTIVE TEST [06/2017 - ] ).
      CHASSIS > PCS/LDA/RSA/LVN > DATA LIST

      Tester Display Measurement Item/Range Normal Condition Diagnostic Note
      History of Blockage Displays whether there are camera or laser sensor obstruction history / ON or OFF ON: Pre-collision city sensor (camera or laser sensor) obstruction history exists
      OFF: Pre-collision city sensor (camera or laser sensor) obstruction history does not exist
      -
      History of Low Voltage Displays whether there is low voltage history / ON or OFF ON: Pre-collision city sensor low voltage history exists
      OFF: Pre-collision city sensor low voltage history does not exist
      -
      History of High Voltage Displays whether there is high voltage history / ON or OFF ON: Pre-collision city sensor high voltage history exists
      OFF: Pre-collision city sensor high voltage history does not exist
      -
      History of Low Temperature Displays whether there is low temperature history / ON or OFF ON: Pre-collision city sensor low temperature history exists
      OFF: Pre-collision city sensor low temperature history does not exist
      -
      History of High Temperature Displays whether there is high temperature history / ON or OFF ON: Pre-collision city sensor high temperature history exists
      OFF: Pre-collision city sensor high temperature history does not exist
      -
      Blockage Status Displays whether there is a camera obstruction malfunction / ON or OFF ON: Pre-collision city sensor (camera) obstructed
      OFF: Pre-collision city sensor (camera) not obstructed
      -
      Low Voltage Status Displays whether there is a low voltage malfunction / ON or OFF ON: Pre-collision city sensor low voltage malfunction exists
      OFF: Pre-collision city sensor low voltage malfunction does not exist
      -
      High Voltage Status Displays whether there is a high voltage malfunction / ON or OFF ON: Pre-collision city sensor high voltage malfunction exists
      OFF: Pre-collision city sensor high voltage malfunction does not exist
      -
      Low Temperature Status Displays whether there is a low temperature malfunction / ON or OFF ON: Pre-collision city sensor low temperature malfunction exists
      OFF: Pre-collision city sensor low temperature malfunction does not exist
      -
      High Temperature Status Displays whether there is a high temperature malfunction / ON or OFF ON: Pre-collision city sensor high temperature malfunction exists
      OFF: Pre-collision city sensor high temperature malfunction does not exist
      -
      Lidar Blockage Status Displays whether laser sensor is dirty / ON or OFF ON: Dirt on pre-collision city sensor (laser sensor)
      OFF: No dirt on pre-collision city sensor (laser sensor)
      -

      Result

      Result Proceed to
      Malfunction history exists A
      No malfunction history exists B

    Result: 

    See step  9

    Result: 

    See step  8

  8. PROBLEM SYMPTOMS TABLE 
    1. Refer to Problem Symptoms Table DATA LIST / ACTIVE TEST [06/2017 - ] ).

      Result

      Result Proceed to
      Fault is not listed in Problem Symptoms Table A
      Fault is listed in Problem Symptoms Table B

    Result: 

    See step  10

    Result: 

    See step  9

  9. OVERALL ANALYSIS AND TROUBLESHOOTING 
    1. Terminals of ECU (Refer to TERMINALS OF ECU [06/2017 - ] )
    2. Data List / Active Test (Refer to DATA LIST / ACTIVE TEST [06/2017 - ] )

      Result

      Proceed to
      NEXT

    NEXT 

    See step  10

  10. ADJUST, REPAIR OR REPLACE 
    NOTE:

    If the pre-collision city sensor has been replaced, be sure to perform Pre-collision City Sensor Learning (Refer to ADJUSTMENT [11/2015 - ] ).

    Result

    Proceed to
    NEXT

    NEXT 

    See step  11

  11. CONFIRMATION TEST 

    Result

    Proceed to
    NEXT

    NEXT 

    END 

  12. INSPECT CONDITIONS WHEN PRE-COLLISION SYSTEM DID NOT OPERATE 
    1. Check if the problem occurred under any of the following conditions.
      Situations in which the pre-collision system may not function properly
      When driving on roads with sharp bends or uneven surfaces
      If a vehicle suddenly moves in front of the vehicle, such as at an intersection
      If a vehicle suddenly cuts in front of the vehicle
      If the vehicle is skidding
      When the front part of the vehicle is raised or lowered
      When the windshield is dirty or covered with raindrops, condensation, ice, snow, etc.
      When the sensor is misaligned due to a strong impact being applied to the sensor, etc.
      When a preceding vehicle is a poor reflector of laser (the rear part of the vehicle lowered, very dirty, etc.)
      When a very bright light, such as the sun or the headlights of oncoming traffic, shines directly into the pre-collision city sensor
      When driving in inclement weather such as heavy rain, fog, snow or a sand storm
      When the surrounding area is dark, such as while in a tunnel or during nighttime

      Result

      DTC Condition Proceed to
      Problem occurred under condition above A
      Problem did not occur under condition above B

    Result: 

    END 

    Result: 

    See step  6