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 branch line or V1 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 "CAN Bus Check" function of the Techstream (when the DLC3 branch wire and V1 bus main wire are normal).
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 power management control ECU detects malfunctions in the power management 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 (multiplex network body ECU) 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 AND CLEAR DTC* |
Using the Techstream, perform the Health Check (all DTCs check).
| |||||
| 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 V1 BUS CIRCUIT MAIN WIRE AND SHORT CIRCUIT (CANH - CANL) |
Disconnect the cable from the negative (-) battery terminal before measuring the resistances of the main wire and branch wire.
![]() |
Measure the resistance of the DLC3.
| Tester Connection | Switch Condition | Specified Condition | Proceed to |
| F13-6 (CANH) - F13-14 (CANL) | Ignition switch off | OK (54 to 69 Ω) | A |
| F13-6 (CANH) - F13-14 (CANL) | Ignition switch off | NG (Higher than 69 Ω) | B |
| F13-6 (CANH) - F13-14 (CANL) | Ignition switch off | NG (Below 54 Ω) | C |
| *a | Front view of DLC3 |
|
| ||||
|
| ||||
| |||||
| 6.CHECK FOR SHORT TO +B IN CAN V1 BUS (CANH, CANL - BAT) |
![]() |
Measure the resistance of the DLC3.
| Tester Connection | Switch Condition | Specified Condition |
| F13-6 (CANH) - F13-16 (BAT) | Ignition switch off | 6 kΩ or higher |
| F13-14 (CANL) - F13-16 (BAT) | Ignition switch off | 6 kΩ or higher |
| *a | Front view of DLC3 |
|
| ||||
| |||||
| 7.CHECK FOR SHORT TO GND IN CAN V1 BUS (CANH, CANL - CG) |
![]() |
Measure the resistance of the DLC3.
| Tester Connection | Switch Condition | Specified Condition |
| F13-6 (CANH) - F13-4 (CG) | Ignition switch off | 200 Ω or higher |
| F13-14 (CANL) - F13-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 "CAN Bus Check" from the screen on the Techstream (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 displayed on screen (CAN bus circuit currently normal) | A |
| w/ Smart Key System: Except for power management control ECU (Power Management1), no ECUs connected to power management bus are displayed (power management bus main wire open or short malfunction) | B |
| w/ Smart Key System: No ECUs connected to power management bus are displayed (the power management bus circuit is open) | C |
| w/ CRAWL Control: Except for main body ECU (multiplex network body ECU), no ECUs connected to MS bus are displayed (MS bus main wire open or short malfunction) | D |
| w/ Seat Position Memory: Except for main body ECU (multiplex network body ECU), no ECUs connected to MS bus are displayed (MS bus main wire open or short malfunction) | E |
| No ECUs connected to MS bus are displayed (branch wire between main body ECU (multiplex network body ECU) and MS bus circuit is open) | F |
| Only one ECU or sensor that should be connected to CAN communication is not displayed (ECU or sensor branch wire open or communication stop) | G |
| ECU or sensor that should be connected to CAN communication is not displayed or display is intermittent during check (ECU or sensor branch wire open on one side) | H |
|
| ||||
|
| ||||
|
| ||||
|
| ||||
|
| ||||
|
| ||||
|
| ||||
| |||||
| 9.CHECK COMMUNICATION MALFUNCTION DTC (PAST DTC CHECK)* |
Select "CAN Bus Check" from the screen on the Techstream (Click here).
Write down all of the DTCs output from each ECU.
| Inspection Result | Proceed to |
| ECU connected to V1 bus outputs communication trouble code | A |
| w/ Smart Key System: Power management control ECU (Power Management1) outputs network malfunction trouble code (U1002) (power management bus main wire past malfunction) | B |
| w/ Smart Key System: Power management control ECU (Power Management1) outputs trouble code other than network malfunction trouble code (U1002) (past malfunction of ECU or branch wire connected to power management bus) | C |
| w/ CRAWL Control: Main body ECU (multiplex network body ECU) outputs network malfunction trouble code (U1002) (MS bus main wire past malfunction) | D |
| w/ Seat Position Memory: Main body ECU (multiplex network body ECU) outputs network malfunction trouble code (U1002) (MS bus main wire past malfunction) | E |
| Main body ECU (multiplex network body ECU) outputs trouble code other than network malfunction trouble code (U1002) (past malfunction of ECU or branch wire connected to MS bus) | F |
|
| ||||
|
| ||||
|
| ||||
|
| ||||
|
| ||||
| |||||
| 10.CHECK DTC COMBINATION TABLE (V1 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 (V1 BUS CIRCUIT MAIN WIRE PAST MALFUNCTION)* |
Using the Techstream, clear all DTCs.
Perform a malfunction simulation test on all harnesses and connectors related to the V1 bus 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 |
|
| ||||
|---|---|---|---|---|---|