IMPORTANT POINTS CONCERNING TROUBLESHOOTING
CAUTION:
Wait at least 90 seconds after disconnecting the cable from the negative (-) battery terminal to disable the SRS system.
Note
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.
w/ Navigation System (for HDD):
After the ignition switch is turned off, the HDD navigation system requires approximately a minute to record various types of memory and settings. As a result, after turning the ignition switch off, wait a minute or more before disconnecting the cable from the negative (-) battery terminal.
When disconnecting the cable, some systems need to be initialized after the cable is reconnected Click here.
Tech Tips
Operating the ignition switch, any switches or any doors triggers related ECU and sensor communication with the CAN, which causes resistance variation.
*: Use the intelligent tester.
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.
Note
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 intelligent tester (when the DLC3 branch wire and V1 bus main wire are normal).
Tech Tips
When checking "Bus Check", ECUs (sensors) whose branch line is open or that cannot communicate via CAN communication do not respond to the intelligent tester (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 power management control ECU (Power Management1) 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 (instrument panel junction block) 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.
The power management control ECU (Power Management2) detects malfunctions in the power management 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.
VEHICLE BROUGHT TO WORKSHOP
| NEXT |
|
INSPECT BATTERY VOLTAGE
| Standard voltage |
|---|
| 11 to 14 V |
If the voltage is below 11 V, recharge or replace the battery before proceeding.
| NEXT |
|
CHECK AND CLEAR DTC*
Using the intelligent tester, perform the all DTCs check.
Note
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.
| NEXT |
|
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.
| NEXT |
|
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 the branch wire.
| *1 | Front view of DLC3 |
Measure the resistance of the DLC3.
| Standard Resistance | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| B |
|
Go to "Open in CAN Main Wire" Click here |
| C |
|
Go to "Short in CAN Bus Lines" Click here |
| A |
|
CHECK FOR SHORT TO +B IN CAN V1 BUS (CANH, CANL - BAT)
| *1 | Front view of DLC3 |
Measure the resistance of the DLC3.
| Standard Resistance | |||||||||
|---|---|---|---|---|---|---|---|---|---|
|
| NG |
|
Go to "Short to B+ in CAN Bus Lines" Click here |
| OK |
|
CHECK FOR SHORT TO GND IN CAN V1 BUS (CANH, CANL - CG)
| *1 | Front view of DLC3 |
Measure the resistance of the DLC3.
| Standard Resistance | |||||||||
|---|---|---|---|---|---|---|---|---|---|
|
| NG |
|
Go to "Short to GND in CAN Bus Lines" Click here |
| OK |
|
CHECK ECUS CONNECTED TO CAN BUS*
Connect the cable to the negative (-) battery terminal.
Note
When disconnecting the cable, some systems need to be initialized after the cable is reconnected Click here.
Select "Bus Check" from "System Select".
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 |
| Except for power management control ECU (Power Management1), no ECUs connected to V2 bus are displayed (V2 bus main wire open or short malfunction). | B |
| No ECUs connected to V2 bus are displayed (the branch wire between the power management control ECU and V2 bus circuit is open). | C |
| Except for power management control ECU (Power Management2), no ECUs connected to power management bus are displayed (power management bus main wire open or short malfunction). | D |
| No ECUs connected to power management bus are displayed (the power management bus circuit is open). | E |
| Except for main body ECU (instrument panel junction block assembly), no ECUs connected to MS bus are displayed (MS bus main wire open or short malfunction). | F |
| No ECUs connected to MS bus are displayed (branch wire between main body ECU (instrument panel junction block assembly) and MS bus circuit is open). | G |
| A single ECU or sensor that should be connected to CAN communication is not displayed (ECU or sensor branch wire open or communication stop). | H |
| 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). | I |
Note
ECUs and sensors that are not present will not be displayed. Be careful not to mistake them for communication stop malfunctions.
Tech Tips
If the display of an ECU is intermittent during the check, one side of an ECU or sensor branch wire is open (the signal of the ECU is treated as noise, which affects the response and display of the intelligent tester).
The power management control ECU checks for proper ECU communication for ECUs that are connected to the V2 bus and the results are displayed on the intelligent tester. ECUs that stop communicating with the power management control ECU for 3 seconds or more will stop being displayed on the intelligent tester.
The power management control ECU may be malfunctioning if both of the following occur: 1) all ECUs connected to the V2 bus are not displayed on the intelligent tester; and 2) DTC U1002 Lost Communication with Gateway Module (V2 Bus) is not output.
The power management control ECU checks for proper ECU communication for ECUs that are connected to the power management bus and the results are displayed on the intelligent tester. ECUs that stop communicating with the power management control ECU for 3 seconds or more will stop being displayed on the intelligent tester.
The power management control ECU may be malfunctioning if both of the following occur: 1) all ECUs connected to the power management bus are not displayed on the intelligent tester; and 2) DTC U1002 Lost Communication with Gateway Module (Power Management Bus) is not output.
The main body ECU (instrument panel junction block assembly) checks for proper ECU communication for ECUs that are connected to the MS bus and the results are displayed on the intelligent tester. ECUs that stop communicating with the main body ECU (instrument panel junction block assembly) for 10 seconds or more will stop being displayed on the intelligent tester.
The main body ECU (instrument panel junction block assembly) may be malfunctioning if both of the following occur: 1) all ECUs connected to the MS bus are not displayed on the intelligent tester; and 2) DTC U1002 Lost Communication with Gateway Module (MS Bus) is not output.
| B |
|
Go to "DTC U1002" Click here |
| C |
|
Go to "Power Management Control ECU Communication Stop Mode" Click here |
| D |
|
Go to "DTC U1002" Click here |
| E |
|
Go to "Power Management Control ECU Communication Stop Mode" Click here |
| F |
|
Go to "DTC U1002" Click here |
| G |
|
Go to "Main Body ECU Communication Stop Mode" Click here |
| H |
|
Go to "Problem Symptoms Table" Click here |
| I |
|
Go to "Open in One Side of CAN Branch Wire" Click here |
| A |
|
CHECK COMMUNICATION MALFUNCTION DTC (PAST DTC CHECK)*
Select "Bus Check" from "System Select".
Write down all of the DTCs stored in each ECU.
Tech Tips
If there are communication malfunction DTCs stored but the intelligent tester "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 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 power management control ECU.
For power management bus malfunctions, DTCs are stored based on the detection of communication stop malfunctions and network malfunctions of ECUs that are connected by the power management control ECU.
For MS bus malfunctions, DTCs are stored based on the detection of communication stop malfunctions and network malfunctions of ECUs that are connected by the main body ECU (instrument panel junction block assembly).
| Inspection Result | Proceed to |
|---|---|
| An ECU connected to the V1 bus outputs a communication trouble code | A |
| The power management control ECU (Power Management1) outputs the network malfunction trouble code (U1002) (V2 bus main wire past malfunction) |
B |
| The power management control ECU (Power Management2) outputs the network malfunction trouble code (U1002) (power management bus main wire past malfunction) |
C |
| The main body ECU (instrument panel junction block assembly) outputs the network malfunction trouble code (U1002) (MS bus main wire past malfunction) |
D |
| The power management control ECU (Power Management1) outputs a trouble code other than the network malfunction trouble code (U1002) (past malfunction of ECU or branch wire connected to V2 bus) |
E |
| The power management control ECU (Power Management2) outputs a trouble code other than the network malfunction trouble code (U1002) (past malfunction of ECU or branch wire connected to power management bus) |
E |
| The main body ECU (instrument panel junction block assembly) outputs a trouble code other than the network malfunction trouble code (U1002) (past malfunction of ECU or branch wire connected to MS bus) |
E |
| B |
|
Go to "DTC U1002" Click here |
| C |
|
Go to "DTC U1002" Click here |
| D |
|
Go to "DTC U1002" Click here |
| E |
|
Go to "Diagnostic Trouble Code Chart" Click here |
| A |
|
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.
| NEXT |
|
PERFORM MALFUNCTION SIMULATION TEST (V1 BUS CIRCUIT MAIN WIRE PAST MALFUNCTION)*
Using the intelligent tester, 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.
| NEXT |
|
ADJUST, REPAIR AND REPLACE
| NEXT |
|
CLEAR DTC*
Using the intelligent tester, clear all DTCs.
| NEXT |
|
CONFIRMATION TEST
| NEXT |
|
| END |