IMPORTANT POINT CONCERNING TROUBLESHOOTING
Wait at least 90 seconds after disconnecting the cable from the negative (-) battery terminal to disable the SRS system.
Refer to the troubleshooting procedures of each system if DTCs regarding the CAN communication system are not output.
Before measuring the resistance, leave the vehicle for at least 1 minute and do not operate the ignition switch, any switches or any doors. If doors need to be opened in order to check connectors, open the doors and leave them open.
When disconnecting the cable, some systems need to be initialized after the cable is reconnected.
Click hereGeneral>INTRODUCTION>REPAIR INSTRUCTION>PRECAUTION
After turning the ignition switch off, waiting time may be required before disconnecting the cable from the battery terminal. Therefore, make sure to read the disconnecting the cable from the battery terminal notice before proceeding with work.
Click hereGeneral>INTRODUCTION>REPAIR INSTRUCTION>INITIALIZATION
Operating the ignition switch, any switches or any doors triggers related ECU and sensor communication with the CAN, which causes resistance variation.
*: Use the Techstream.
DTCs indicating a CAN communication malfunction are also stored due to internal or power source-related problems in ECUs or sensors of systems using CAN communication. Therefore, check whether codes indicating internal or power source-related problems in those systems are output together with the CAN communication DTCs.
It is possible to inspect the circuit of the DLC3 branch line or V1 bus main line for malfunctions by inspecting the terminals of the DLC3 using SST.
It is only possible to inspect branch lines to ECUs (sensors) or the V1 bus from the DLC3.
It is possible to check which ECUs (sensors) are not able to communicate via CAN communication by checking the "Bus Check" function of the Techstream (when the DLC3 CAN branch wire and V1 bus CAN main wire are normal).
When checking "Bus Check", ECUs (sensors) whose branch line is open or that cannot communicate via CAN communication do not respond to the Techstream (they are not displayed on the screen).
When checking "Bus Check", if a DTC indicating a CAN communication malfunction is output even though all ECUs (sensors) respond (they are displayed on the screen), use the DTC combination table to determine the suspected trouble area and perform symptom simulation.
For past malfunctions of the V1 bus, the ECUs (sensors) which cannot communicate via CAN communication can be determined from the combination of CAN communication DTCs that are output.
The network gateway ECU detects malfunctions in the V2 bus circuit and outputs DTCs depending on the malfunctioning areas. The ECUs (sensors) which cannot communicate via CAN communication can be determined from the combination of CAN communication DTCs that are output.
The main body ECU (cowl side junction block LH) detects malfunctions in the MS bus circuit and outputs DTCs depending on the malfunctioning areas. The ECUs (sensors) which cannot communicate via CAN communication can be determined from the combination of CAN communication DTCs that are output.
When an open circuit malfunction is confirmed, before disconnecting the connectors for inspection, check whether the connectors are loose by pushing in the connector case.
When a connector is disconnected, check if the connector terminals or case is damaged, deformed, deteriorated, etc.
| Result |
|---|
| NEXT |
NEXT
11 to 14 V
If the voltage is below 11 V, recharge or replace the battery before proceeding.
| Result |
|---|
| NEXT |
NEXT
Using the Techstream, check for all DTCs.
Click herePower Source / Network>NETWORKING>CAN COMMUNICATION SYSTEM>DIAGNOSIS SYSTEM
If codes indicating internal or power source-related malfunctions of ECUs or sensors are output together with codes indicating that those ECUs or sensors cannot communicate via CAN communication, it is likely that the problem is not in the CAN communication line. Therefore, perform troubleshooting for the DTCs related to the malfunctioning parts first.
If a connector of a system which includes a CAN communication line is disconnected when the ignition switch is ON or ACC, CAN communication DTCs will be stored by that system and any related systems.
| Result |
|---|
| NEXT |
NEXT
Based on the vehicle equipment and specifications, confirm the systems that use CAN communication.
Click herePower Source / Network>NETWORKING>CAN COMMUNICATION SYSTEM>DIAGNOSIS SYSTEM
| Result |
|---|
| NEXT |
NEXT
Disconnect the cable from the negative (-) battery terminal before measuring the resistances of the CAN main wire and CAN branch wire.
| *a | Front view of DLC3 |
Measure the resistance of the DLC3.
| Tester Connection | Switch Condition | Specified Condition | Proceed to |
|---|---|---|---|
| H19-6 (CANH) - H19-14 (CANL) | Ignition switch off | OK (54 to 69 Ω) | A |
| H19-6 (CANH) - H19-14 (CANL) | Ignition switch off | NG (70 Ω or higher) | B |
| H19-6 (CANH) - H19-14 (CANL) | Ignition switch off | NG (less than 54 Ω) | C |
A
B
C
| *a | Front view of DLC3 |
Measure the resistance of the DLC3.
| Tester Connection | Switch Condition | Specified Condition |
|---|---|---|
| H19-6 (CANH) - H19-16 (BAT) | Ignition switch off | 6 kΩ or higher |
| H19-14 (CANL) - H19-16 (BAT) | Ignition switch off | 6 kΩ or higher |
| Result |
|---|
| OK |
| NG |
OK
NG
| *a | Front view of DLC3 |
Measure the resistance of the DLC3.
| Tester Connection | Switch Condition | Specified Condition |
|---|---|---|
| H19-6 (CANH) - H19-4 (CG) | Ignition switch off | 200 Ω or higher |
| H19-14 (CANL) - H19-4 (CG) | Ignition switch off | 200 Ω or higher |
| Result |
|---|
| OK |
| NG |
OK
NG
Connect the cable to the negative (-) battery terminal.
When disconnecting the cable, some systems need to be initialized after the cable is reconnected.
Click hereGeneral>INTRODUCTION>REPAIR INSTRUCTION>INITIALIZATION
Select "Bus Check" from "System Select".
Click herePower Source / Network>NETWORKING>CAN COMMUNICATION SYSTEM>DIAGNOSIS SYSTEM
Check the display of the connected ECUs and sensors for a minute.
| Result | Proceed to |
|---|---|
| All ECUs and sensors connected to CAN communication system are displayed on screen (CAN bus circuit currently normal) | A |
| Except for network gateway ECU, no ECUs connected to V2 bus are displayed (V2 bus CAN main wire open or short malfunction) (w/ Network Gateway ECU) | B |
| Except for main body ECU (cowl side junction block LH), no ECUs connected to MS bus are displayed (MS bus CAN main wire open or short malfunction) (w/ Seat Memory) | C |
| No ECUs connected to V2 bus are displayed (CAN branch wire between network gateway ECU and V2 bus circuit is open) | D |
| No ECUs connected to MS bus are displayed (CAN branch wire between main body ECU (cowl side junction block LH) and MS bus circuit is open) | E |
| Single ECU or sensor that should be connected to CAN communication is not displayed (ECU or sensor CAN branch wire open or communication stop) | F |
| ECU or sensor that should be connected to CAN communication is not displayed or display is intermittent during check (ECU or sensor CAN branch wire open on one side) | G |
ECUs and sensors that are not present will not be displayed. Be careful not to mistake them for communication stop malfunctions.
If the display of an ECU is intermittent during the check, one side of an ECU or sensor CAN branch wire is open (the signal of the ECU is treated as noise, which affects the response and display of the Techstream).
The network gateway ECU checks for proper ECU communication for ECUs that are connected to the MS bus and the results are displayed on the Techstream. ECUs that stop communicating with the main body ECU for 10 seconds or more will stop being displayed on the Techstream.
The network gateway ECU may be malfunctioning if both of the following occur: 1) all ECUs connected to the V2 bus are not displayed on the Techstream; and 2) DTC U1002 (Lost Communication with Gateway Module [V2 Bus]) is not output.
The main body ECU (cowl side junction block LH) checks for proper ECU communication for ECUs that are connected to the MS bus and the results are displayed on the Techstream. ECUs that stop communicating with the main body ECU for 10 seconds or more will stop being displayed on the Techstream.
The main body ECU (cowl side junction block LH) may be malfunctioning if both of the following occur: 1) all ECUs connected to the MS bus are not displayed on the Techstream; and 2) DTC U1002 (Lost Communication with Gateway Module [MS Bus]) is not output.
A
B
C
D
Click herePower Source / Network>NETWORKING>CAN COMMUNICATION SYSTEM>Gateway ECU Communication Stop Mode
E
Click herePower Source / Network>NETWORKING>CAN COMMUNICATION SYSTEM>Main Body ECU Communication Stop Mode
F
G
Click herePower Source / Network>NETWORKING>CAN COMMUNICATION SYSTEM>Open in One Side of CAN Branch Line
Select "Bus Check" from "System Select".
Click herePower Source / Network>NETWORKING>CAN COMMUNICATION SYSTEM>DIAGNOSIS SYSTEM
Write down all of the DTCs stored in each ECU.
If there are communication malfunction DTCs output but the Techstream "Bus Check - Communication Bus Check" screen displays all of the ECUs and sensors connected to the CAN system, the communication malfunction DTCs may be past malfunctions that are no longer present.
For V1 bus CAN main wire malfunctions, DTCs for related ECUs are also output. Therefore, determine the malfunctioning area based on all of the DTCs that are output.
For V2 bus malfunctions, DTCs are stored based on the detection of communication stop malfunctions and network malfunctions of ECUs that are connected by the network gateway ECU.
For MS bus malfunctions, DTCs are output based on the detection of communication stop malfunctions and network malfunctions of ECUs that are connected by the main body ECU (cowl side junction block LH).
| Result | Proceed to |
|---|---|
| ECU connected to V1 bus outputs communication trouble code | A |
| Network gateway ECU outputs network malfunction trouble code (U1002) (V2 bus CAN main wire past malfunction) (w/ Network Gateway ECU) | B |
| Main body ECU (cowl side junction block LH) outputs network malfunction trouble code (U1002) (MS bus CAN main wire past malfunction) (w/ Seat Memory) | C |
| Network gateway ECU outputs trouble code other than network malfunction trouble code (U1002) (past malfunction of ECU or CAN branch wire connected to V2 bus) | D |
| Main body ECU (cowl side junction block LH) outputs trouble code other than network malfunction trouble code (U1002) (past malfunction of ECU or CAN branch wire connected to MS bus) | D |
A
B
C
D
Based on the combination of output CAN communication system DTCs, determine which ECUs and sensors have a communication stop malfunction.
Click herePower Source / Network>NETWORKING>CAN COMMUNICATION SYSTEM>DIAGNOSIS SYSTEM
| Result |
|---|
| NEXT |
NEXT
Using the Techstream, clear all DTCs.
Perform a malfunction simulation test on all harnesses and connectors related to the V1 bus CAN main wire.
Check the DTCs that were output as a result of the malfunction simulation test. Then determine the malfunctioning area.
| Proceed to |
|---|
| NEXT |
NEXT
| Proceed to |
|---|
| NEXT |
NEXT
Using the Techstream, clear all DTCs.
| Proceed to |
|---|
| NEXT |
NEXT
| Proceed to |
|---|
| NEXT |
NEXT