Door Lock

Malfunction

~9min read

DESCRIPTION

If the doors lock by themselves even though no door lock operation has been performed, possible causes include a vehicle malfunction, an environmental malfunction, or customer involvement (including any other passenger in the vehicle). Using the operation history, the possible causes of the malfunction can be narrowed down, and the problem can be resolved by repair, replacement or, in some cases, by explaining environmental or usage-related issues.

If the doors unlock by themselves even though no door unlock operation has been performed, possible causes include a vehicle malfunction, an environmental malfunction, or customer involvement (including any other passenger in the vehicle). Using the operation history, the possible causes of the malfunction can be narrowed down, and the problem can be resolved by repair, replacement or, in some cases, by explaining environmental or usage-related issues.

PRECAUTION / NOTICE / HINT

NOTICE:

  • If the vehicle or vehicle controls are operated (for example, during inspection when the vehicle is brought in for repairs) before the operation history is read and recorded, the operation history information may be lost.
  • The "Read Operation History" function uses the current system time setting in Techstream and the clock in the inspection ECU to calculate the times shown in the operation history. For this reason, before reading the operation history, first make sure the Techstream system clock is set accurately to the current time.

PROCEDURE

  1. CONFIRM VEHICLE OPERATING CONDITIONS

(a) Confirm the vehicle symptoms.

Result:

Result

Proceed to

The doors lock unintentionally.

A

The doors unlock unintentionally.

B

B

GO TO STEP 6

A
  1. CHECK LOCK OPERATION HISTORY

(a) Using the Techstream, check the door lock operation history up to the time the customer reported the malfunction, based on the customer interview, and the latest lock operation history record up to the time the problem is said to have occurred.

(1) On the Techstream screen, select the following menus: Body / Main Body / Utility / Operation History Analysis. Read the operation history according to the Techstream display.

Click here

(2) Confirm that there is a door lock operation history, as reported by the customer.

Click here

HINT:

Based on the operation history display, perform the vehicle-side inspection and carry out repairs if a problem is found. If the vehicle has no malfunction, ask the customer to describe the probable causes as "driver" or "environment / other than driver".

Result:

Result

Proceed to

There is an operation history close to the time of the malfunction reported by the customer, but the malfunction could not be identified even by following the instructions to check the corresponding components.

A

There is an operation history close to the time of the malfunction reported by the customer, and by following the instructions to check the corresponding components, the malfunction was identified.

B

There is no operation history around the time the malfunction supposedly occurred, according to the customer.

C

B

END (VEHICLE MALFUNCTION)

C

GO TO STEP 4

A
  1. CUSTOMER INTERVIEW

(a) If the symptom cannot be confirmed or reproduced, explain it to the customer, and also explain the history of input signals from systems such as the multiplex network main switch assembly and the electronic key (electronic key transmitter sub-assembly) for the appropriate date/time in the operation history.

Click here

Standard:

The cause has been identified

OK

END

NG

CHECK FOR INTERMITTENT PROBLEMS

  1. CHECK UNLOCK OPERATION HISTORY

(a) Using the Techstream, check the door unlock operation history up to the time the customer reported the malfunction, based on the customer interview, and the latest unlock operation history record up to the time the problem is said 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, select the following menus: Body / Main Body / Utility / Operation History Analysis. Read the operation history according to the Techstream display.

Click here

(2) Confirm that there is a door lock operation history, as reported by the customer.

Click here

HINT:

Based on the operation history display, perform the vehicle-side inspection and carry out repairs if a problem is found. If the vehicle has no malfunction, ask the customer to describe the probable causes as "driver" or "environment / other than driver".

Result:

Result

Proceed to

There is no operation history around the time the malfunction supposedly occurred, according to the customer.

A

There is an operation history close to the time of the malfunction reported by the customer, but the malfunction could not be identified even by following the instructions to check the corresponding components.

There is an operation history close to the time of the malfunction reported by the customer, and by following the instructions to check the corresponding components, the malfunction was identified.

B

B

END

A
  1. TROUBLESHOOT BY SYMPTOM

(a) Perform troubleshooting based on the malfunction symptoms.

Standard:

The malfunction has been identified.

OK

END

NG

CHECK FOR INTERMITTENT PROBLEMS

  1. CHECK UNLOCK OPERATION HISTORY

(a) Use the Techstream to check the operation history that led to the malfunction, based on the customer interview and the last door unlock operation recorded near the time the problem reportedly occurred according to the customer.

(1) On the Techstream screen, select the following menus: Body / Main Body / Utility / Operation History Analysis. Read the operation history according to the Techstream display.

Click here

(2) Confirm that there is a door lock operation history, as reported by the customer.

Click here

HINT:

Based on the operation history display, perform the vehicle-side inspection and carry out repairs if a problem is found. If the vehicle has no malfunction, ask the customer to describe the probable causes as "driver" or "environment / other than driver".

Result:

Result

Proceed to

There is an operation history close to the time of the malfunction reported by the customer, but the malfunction could not be identified even by following the instructions to check the corresponding components.

A

There is an operation history close to the time of the malfunction reported by the customer, and by following the instructions to check the corresponding components, the malfunction was identified.

B

There is no operation history around the time the malfunction supposedly occurred, according to the customer.

C

B

END

C

GO TO STEP 8

A
  1. CUSTOMER INTERVIEW

(a) If the symptom cannot be confirmed or reproduced, explain it to the customer, and also explain the history of input signals from systems such as the multiplex network main switch assembly and the electronic key (electronic key transmitter sub-assembly) for the appropriate date/time in the operation history.

Click here

Standard:

The cause has been identified

OK

END

NG

CHECK FOR INTERMITTENT PROBLEMS

  1. CHECK LOCK OPERATION HISTORY

(a) Use the Techstream to check the door lock operation history near the time the malfunction reportedly occurred according to the customer.

HINT:

Check the operation history to confirm whether the door was locked as stated by the customer.

(1) On the Techstream screen, select the following menus: Body / Main Body / Utility / Operation History Analysis. Read the operation history according to the Techstream display.

Click here

(2) After checking the items displayed for "Vehicle Condition" and "Detected Operation History", perform the check according to the "Inspection Areas" section.

Click here

HINT:

Based on the operation history display, perform the vehicle-side inspection and carry out repairs if a problem is found. If the vehicle has no malfunction, ask the customer to describe the probable causes as "driver" or "environment / other than driver".

Result:

Result

Proceed to

There is no operation history around the time the malfunction supposedly occurred, according to the customer.

A

There is an operation history close to the time of the malfunction reported by the customer, but the malfunction could not be identified even by following the instructions to check the corresponding components.

There is an operation history close to the time of the malfunction reported by the customer, and by following the instructions to check the corresponding components, the malfunction was identified.

B

B

END

A
  1. TROUBLESHOOT BY SYMPTOM

(a) Perform troubleshooting based on the malfunction symptoms.

Standard:

The malfunction has been identified.

OK

END

NG

CHECK FOR INTERMITTENT PROBLEMS