CAN COMMUNICATION SYSTEM > HOW TO PROCEED WITH TROUBLESHOOTING |
| IMPORTANT POINTS CONCERNING TROUBLESHOOTING |
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 CAN branch line or V bus main line for malfunctions by inspecting the terminals of the DLC3 using SST.
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 V bus CAN main wire are normal).
For past malfunctions of the V 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 stores 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 (driver side junction block assembly) detects malfunctions in the MS bus circuit and stores 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.
| 1.VEHICLE BROUGHT TO WORKSHOP |
| |||||
| 2.INSPECT BATTERY VOLTAGE |
| |||||
| 3.CHECK FOR DTC* |
Using the Techstream, check for all DTCs.
| |||||
| 4.CHECK INSTALLED SYSTEMS (ECU AND SENSOR) THAT USE CAN COMMUNICATION |
Based on the vehicle equipment and specifications, confirm the systems that use CAN communication (Click here).
| |||||
| 5.CHECK FOR OPEN CIRCUIT IN DLC3 BRANCH WIRE AND V BUS CIRCUIT CAN MAIN WIRE AND SHORT CIRCUIT (CANH - CANL) |
![]() |
Disconnect the cable from the negative (-) battery terminal before measuring the resistances of the CAN main wire and CAN branch wire.
Measure the resistance according to the value(s) in the table below.
| Tester Connection | Switch Condition | Specified Condition | Proceed to |
| J17-6 (CANH) - J17-14 (CANL) | Ignition switch off | OK (54 to 69 Ω) | A |
| J17-6 (CANH) - J17-14 (CANL) | Ignition switch off | NG (Higher than 70 Ω) | B |
| J17-6 (CANH) - J17-14 (CANL) | Ignition switch off | NG (Below 53 Ω) | C |
| *a | Front view of DLC3 |
|
| ||||
|
| ||||
| |||||
| 6.CHECK FOR SHORT TO B+ IN CAN V BUS (CANH, CANL - BAT) |
![]() |
Measure the resistance according to the value(s) in the table below.
| Tester Connection | Switch Condition | Specified Condition |
| J17-6 (CANH) - J17-16 (BAT) | Ignition switch off | 6 kΩ or higher |
| J17-14 (CANL) - J17-16 (BAT) | Ignition switch off | 6 kΩ or higher |
| *a | Front view of DLC3 |
|
| ||||
| |||||
| 7.CHECK FOR SHORT TO GND IN CAN V BUS (CANH, CANL - CG) |
![]() |
Measure the resistance according to the value(s) in the table below.
| Tester Connection | Switch Condition | Specified Condition |
| J17-6 (CANH) - J17-4 (CG) | Ignition switch off | 200 Ω or higher |
| J17-14 (CANL) - J17-4 (CG) | Ignition switch off | 200 Ω or higher |
| *a | Front view of DLC3 |
|
| ||||
| |||||
| 8.CHECK ECUS CONNECTED TO CAN BUS* |
Connect the cable to the negative (-) battery terminal.
Select "Bus Check" from "System Select" (Click here).
Check the display of the connected ECUs and sensors for a minute.
| Inspection 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). | B |
| No ECUs connected to V2 bus are displayed (CAN branch wire between network gateway ECU and V bus circuit is open). | C |
| Except for main body ECU (driver side junction block assembly), no ECUs connected to MS bus are displayed (MS bus CAN main wire open or short malfunction). | D |
| No ECUs connected to MS bus are displayed (CAN branch wire between main body ECU [driver side junction block assembly] and V 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 |
|
| ||||
|
| ||||
|
| ||||
|
| ||||
|
| ||||
|
| ||||
| |||||
| 9.CHECK COMMUNICATION MALFUNCTION DTC (PAST DTC CHECK)* |
Select "Bus Check" from "System Select" (Click here).
Write down all of the DTCs output from each ECU.
| Inspection Result | Proceed to |
| ECU connected to V bus outputs communication trouble code. | A |
| Network gateway ECU outputs network malfunction trouble code (U1002). (V2 bus CAN main wire past malfunction) | B |
| Main body ECU (driver side junction block assembly) outputs network malfunction trouble code (U1002). (MS bus CAN main wire past malfunction) | C |
| Network gateway ECU outputs trouble code other than the network malfunction trouble code (U1002). (past malfunction of ECU or CAN branch wire connected to V2 bus) | D |
| Main body ECU (driver side junction block assembly) outputs trouble code other than the network malfunction trouble code (U1002). (past malfunction of ECU or CAN branch wire connected to MS bus) | D |
|
| ||||
|
| ||||
|
| ||||
| |||||
| 10.CHECK DTC COMBINATION TABLE (V BUS BRANCH WIRE OPEN, PAST COMMUNICATION STOP MALFUNCTION) |
Based on the combination of output CAN communication system DTCs, determine which ECUs and sensors have a communication stop malfunction (Click here).
| |||||
| 11.PERFORM MALFUNCTION SIMULATION TEST (V BUS CIRCUIT CAN MAIN WIRE PAST MALFUNCTION)* |
Using the Techstream, clear all DTCs.
Perform a malfunction simulation test on all harnesses and connectors related to the V bus CAN main wire.
Check the DTCs that were output as a result of the malfunction simulation test. Then determine the malfunctioning area.
| |||||
| 12.ADJUST, REPAIR AND REPLACE |
| |||||
| 13.CLEAR DTC* |
Using the Techstream, clear all DTCs.
| |||||
| 14.CONFIRMATION TEST |
|
| ||||
|---|---|---|---|---|---|