DESCRIPTION
In cases where doors locked (lock) by themselves even though a door lock operation was not performed, possible causes include vehicle-side malfunction, environmental malfunction, or operation by the customer (including other passengers in the vehicle). By using the operation history, the possible causes of the malfunction can be narrowed down, allowing the problem to be resolved by repair, replacement, or in some cases explaining the environmental or usage issues to the customer.
In cases where doors unlock by themselves even though a door unlock operation was not performed, possible causes include vehicle-side malfunction, environmental malfunction, or operation by the customer (including other passengers in the vehicle). By using the operation history, the possible causes of the malfunction can be narrowed down, allowing the problem to be resolved by repair, replacement, or in some cases explaining the environmental or usage issues to the customer.
CAUTION / NOTICE / HINT
NOTICE:
PROCEDURE
1. |
CONFIRM VEHICLE CONDITION |
(a) Confirm the vehicle symptoms.
Result |
Proceed to |
---|---|
Doors locked unintentionally |
A |
Doors unlocked unintentionally |
B |
B |
GO TO STEP 6 |
|
2. |
CHECK LOCK OPERATION HISTORY |
(a) Use the Techstream to check the door lock operation history around the time that the malfunction reported by the customer occurred, based on the contents of the customer interview and the last recorded door lock operation history around the time that the problem is reported to have occurred.
(1) On the Techstream screen, enter the following menus: Body / Main Body / Utility / Operation History Analysis. According to the display on the Techstream, read the operation history.
Click here
(2) Check that there is door lock operation history as reported by the customer.
Click here
HINT:
Based on the displayed operation history, perform vehicle-side inspection, and perform repairs if a problem is found. If the vehicle has no malfunction, interview the customer about possible causes such as "the driver" and "environmental / other than the driver".
Result |
Proceed to |
---|---|
There is operational history around the time that the customer reported the malfunction to have occurred, but the malfunction could not be identified even by following the instructions to inspect the relevant areas |
A |
There is operational history around the time that the customer reported the malfunction to have occurred, and by following the instructions to inspect the relevant areas, the malfunction was identified |
B |
There is no operational history around the time that the customer reported the malfunction to have occurred. |
C |
B |
END (VEHICLE MALFUNCTION) |
C |
GO TO STEP 4 |
|
3. |
INTERVIEW THE CUSTOMER |
(a) If the phenomenon could not be confirmed or reproduced, after explaining this to the customer, also explain the history of input signals involving systems such as the multiplex network master switch assembly and electronic key (electrical key transmitter sub-assembly) for the relevant date/time in the operation history.
Click here
Standard:
Cause was identified
OK |
END |
NG |
CHECK INTERMITTENT PROBLEMS |
4. |
CHECK UNLOCK OPERATION HISTORY |
(a) Use the Techstream to check the door unlock operation history around the time that the malfunction reported by the customer occurred, based on the contents of the customer interview and the last recorded door unlock operation history around the time that the problem is reported to have occurred.
HINT:
Check the operation history to confirm whether the door was unlocked as reported by the customer.
(1) On the Techstream screen, enter the following menus: Body / Main Body / Utility / Operation History Analysis. According to the display on the Techstream, read the operation history.
Click here
(2) Check that there is door lock operation history as reported by the customer.
Click here
HINT:
Based on the displayed operation history, perform vehicle-side inspection, and perform repairs if a problem is found. If the vehicle has no malfunction, interview the customer about possible causes such as "the driver" and "environmental / other than the driver".
Result |
Proceed to |
---|---|
There is no operational history around the time that the customer reported the malfunction to have occurred. |
A |
There is operational history around the time that the customer reported the malfunction to have occurred, but the malfunction could not be identified even by following the instructions to inspect the relevant areas |
|
There is operational history around the time that the customer reported the malfunction to have occurred, and by following the instructions to inspect the relevant areas, the malfunction was identified |
B |
B |
END |
|
5. |
PERFORM TROUBLESHOOTING BASED ON MALFUNCTION SYMPTOM |
(a) Perform troubleshooting based on the malfunction symptoms.
Standard:
Malfunction was identified.
OK |
END |
NG |
CHECK INTERMITTENT PROBLEMS |
6. |
CHECK UNLOCK OPERATION HISTORY |
(a) Use the Techstream to check for operation history leading to the malfunction, based on the contents of the customer interview and the last recorded door unlock operation history around the time that the problem is reported by the customer to have occurred.
(1) On the Techstream screen, enter the following menus: Body / Main Body / Utility / Operation History Analysis. According to the display on the Techstream, read the operation history.
Click here
(2) Check that there is door lock operation history as reported by the customer.
Click here
HINT:
Based on the displayed operation history, perform vehicle-side inspection, and perform repairs if a problem is found. If the vehicle has no malfunction, interview the customer about possible causes such as "the driver" and "environmental / other than the driver".
Result |
Proceed to |
---|---|
There is operational history around the time that the customer reported the malfunction to have occurred, but the malfunction could not be identified even by following the instructions to inspect the relevant areas |
A |
There is operational history around the time that the customer reported the malfunction to have occurred, and by following the instructions to inspect the relevant areas, the malfunction was identified |
B |
There is no operational history around the time that the customer reported the malfunction to have occurred. |
C |
B |
END |
C |
GO TO STEP 8 |
|
7. |
INTERVIEW THE CUSTOMER |
(a) If the phenomenon could not be confirmed or reproduced, after explaining this to the customer, also explain the history of input signals involving systems such as the multiplex network master switch assembly and electronic key (electrical key transmitter sub-assembly) for the relevant date/time in the operation history.
Click here
Standard:
Cause was identified
OK |
END |
NG |
CHECK INTERMITTENT PROBLEMS |
8. |
CHECK LOCK OPERATION HISTORY |
(a) Use the Techstream to check the door lock operation history around the time that the malfunction reported by the customer occurred.
HINT:
Check the operation history to confirm whether the door was locked as reported by the customer.
(1) On the Techstream screen, enter the following menus: Body / Main Body / Utility / Operation History Analysis. According to the display on the Techstream, read the operation history.
Click here
(2) After checking the items displayed for "Vehicle Condition" and "Detected Operation History", perform inspection according to "Inspection Areas".
Click here
HINT:
Based on the displayed operation history, perform vehicle-side inspection, and perform repairs if a problem is found. If the vehicle has no malfunction, interview the customer about possible causes such as "the driver" and "environmental / other than the driver".
Result |
Proceed to |
---|---|
There is no operational history around the time that the customer reported the malfunction to have occurred. |
A |
There is operational history around the time that the customer reported the malfunction to have occurred, but the malfunction could not be identified even by following the instructions to inspect the relevant areas |
|
There is operational history around the time that the customer reported the malfunction to have occurred, and by following the instructions to inspect the relevant areas, the malfunction was identified |
B |
B |
END |
|
9. |
PERFORM TROUBLESHOOTING BASED ON MALFUNCTION SYMPTOM |
(a) Perform troubleshooting based on the malfunction symptoms.
Standard:
Malfunction was identified.
OK |
END |
NG |
CHECK INTERMITTENT PROBLEMS |
Toyota CH-R Service Manual > Rear Brake(for Tmc Made): Removal
REMOVAL
CAUTION / NOTICE / HINT
HINT:
Use the same procedure for the RH side and LH side.
The following procedure is for the LH side.
PROCEDURE
1. PRECAUTION
Click here
2. REMOVE REAR WHEEL
Click here
3. PERFORM REAR BRAKE PAD REPLACEMENT MODE
Click here
4. D ...
Toyota CH-R Service Manual > Front Speed Sensor: Installation
INSTALLATION
CAUTION / NOTICE / HINT
HINT:
Use the same procedure for the RH side and LH side.
The following procedure is for the LH side.
The front speed sensor rotor is a component of the front axle hub sub-assembly.
If the front speed sensor rotor is malfunctioning, replace ...