CHECK FOR INSTALLED SYSTEMS (ECUS AND SENSORS) THAT ADOPT CAN COMMUNICATION
The systems (ECUs and sensors) that use CAN communication vary depending on the vehicle and optional equipment. Check which systems (ECUs and sensors) are installed to the vehicle.
GTS display and installed systems
The names of ECUs and sensors shown on the GTS display may differ from those shown in DTC Table by ECU.
| Connected to | Code | ECU/Sensor Name | GTS Display | Applicability |
|---|---|---|---|---|
| - | CGW | Central gateway ECU (network gateway ECU) | - | Installed on all vehicles |
| V Bus | DLC3 | DLC3 | CAN gateway | Installed on all vehicles |
| Bus 2 | F-CAM | Pre-crash safety city sensor | Front Camera Module | Installed on all vehicles |
| BRK | Skid control ECU (brake actuator assembly) | Skid Control (ABS/VSC/TRAC) | Installed on all vehicles | |
| ENG | ECM | ECM (Engine) | Installed on all vehicles | |
| STR | Steering angle sensor (spiral cable sub-assembly) | Spiral cable (Steering Angle Sensor) | Installed on all vehicles | |
| EPS | Power steering ECU assembly | Power Steering (EPS) | Installed on all vehicles | |
| SRS | Airbag sensor assembly | Airbag | Installed on all vehicles | |
| A/C | Air conditioning amplifier assembly | Air Conditioning Amplifier | Installed on all vehicles | |
| MB | Main Body ECU (Multiplex Network Body ECU) | Main Body | Installed on all vehicles | |
| MET | Combination meter assembly | Combination Meter | Installed on all vehicles | |
| Bus 3 | AV | Radio and display receiver assembly | Display and navigation (AVN1) | Vehicles with radio and display type |
| Navigation receiver assembly | Vehicles with navigation receiver type |
CAN BUS CHECK
The ECUs and sensors that are properly connected to the CAN communication system can be displayed using the GTS.
Using the GTS, select the CAN Bus Check screen.
It may be possible to select buses that do not have ECUs or sensors from the bus selection pull-down menu. This is not a malfunction. (This occurs when optional devices are not on a sub bus that is monitored by a gateway function equipped ECU.)
In the bus selection pull down menu, all buses applicable to the model are displayed (e.g. LIN communication buses are also displayed). Therefore, refer to the wiring diagrams to check the names of sub buses for CAN communication.
Click herePower Source / Network>NETWORKING>CAN COMMUNICATION SYSTEM(w/ Toyota Safety Sense)>SYSTEM DIAGRAM
Different connection statuses are indicated by the background color of ECUs and sensors that are displayed.
| Bus Type | Background Color | Connection Status |
|---|---|---|
| Bus | White | Communication has been normal. |
| Yellow | Communication stop occurred at least once since the start of the CAN bus check, but communication is currently occurring (unstable communication). | |
| Red | Currently not communicating (either of the following):
·
Not communicating since the start of the CAN bus check ·
Communication occurred at least once since the start of the CAN bus check, but is currently not occurring. |
|
| Not displayed | Either of the following:
·
The central gateway ECU (network gateway ECU) has an internal malfunction or cannot communicate with the GTS.*4 ·
No ECUs or sensors are connected to the bus.*5 |
|
| Sub bus with a gateway function equipped ECU that does not memorize connected ECUs or sensors*2 | White | Communication has been normal since the start of the CAN bus check. |
| Yellow | Communication stop occurred at least once since the start of the CAN bus check, but communication is currently occurring (unstable communication). | |
| Red | Communication occurred at least once since the start of the CAN bus check, but is currently not occurring. | |
| Not displayed | Communication stop has continued since the start of the CAN bus check.*1 | |
| Sub bus with a gateway function equipped ECU that memorizes connected ECUs and sensors*3 | White | Communication has been normal. |
| Yellow | Communication stop occurred at least once since the start of the CAN bus check, but communication is currently occurring (unstable communication). | |
| Red | Currently not communicating (either of the following):
·
Not communicating since the start of the CAN bus check ·
Communication occurred at least once since the start of the CAN bus check, but is currently not occurring. |
|
| Not displayed | Either of the following:
·
The gateway function equipped ECU cannot communicate with the central gateway ECU.*6 ·
No ECUs or sensors are connected to the sub bus.*7 |
Gateway function equipped ECUs relay signals between ECUs and sensors connected to different buses.
*1: An ECU or sensor is installed to the vehicle but is not displayed on the "Communication Bus Check" screen.
*2: The gateway function equipped ECU does not memorize ECUs and sensors connected to its respective sub bus.
*3: The gateway function equipped ECU memorizes ECUs and sensors connected to its respective sub bus.
*4: When the central gateway ECU has an internal malfunction or cannot communicate with the GTS, the name of buses, sub buses, ECUs and sensors will not be displayed.
*5: When no ECUs or sensors are connected to a bus, the message "There is no system found on the communication Bus." will be displayed.
*6: When a gateway function equipped ECU cannot communicate with the central gateway ECU, the name of sub buses and ECUs or sensors connected to the sub bus will not be displayed.
*7: When no ECUs or sensors are connected to the sub bus, the message "There is no system found on the communication Bus." will be displayed.
If there is no communication between the GTS and the vehicle, or no ECUs or sensors are displayed as connected, check the central gateway ECU and V bus (the bus that connects the DLC3 to the central gateway ECU) for malfunctions.
Observe the connection response screen for approximately 2 minutes to check for a change in connection status of the connected ECUs and sensors.
If an open occurs in one of the lines of a CAN branch (except DLC3), output from the other branch line (the line that is not open) will be unstable and it may interfere with the response (display) of other ECUs and sensors.
If the connection status changes during the inspection, repair the open in the branch line of the ECU or sensor that does not respond (is not detected) and then perform the CAN bus check again.
HOW TO INTERPRET CAN BUS CHECK SCREEN
When a communication stop is currently occurring, the probable malfunctioning part can be determined from the CAN bus check and by using the following methods.
The following CAN bus wiring diagram is provided only as an example. This wiring diagram is different from the actual wiring diagram for this vehicle.
When a communication stop is currently occurring, it is easier to determine the probable malfunctioning part from the CAN bus check rather than from communication DTCs.
Wait for approximately 2 minutes after turning the ignition switch on (IG) (or simulate the driving conditions that enable the malfunction to be reproduced) and select "CAN Bus Check". Then observe the communication status of each ECU on the screen.
If a communication error of only 1 ECU or sensor is indicated on the CAN Bus Check screen, a communication stop of the ECU or sensor is suspected.
Open in both CAN branch lines of HV on the bus 4
| *a | Bus 2 | *b | Bus 4 |
| *c | Sub Bus | *d | V Bus |
| *e | Location of Malfunction | *f | Background color is red |
When there are communication stops, ECUs that are present in the vehicle may not be displayed on the CAN Bus Check screen.
If communication errors for multiple ECUs or sensors are indicated on the CAN Bus Check screen, then a communication stop of the ECU or sensor that shows a more serious communication stop (an ECU or sensor whose background color is red) is suspected.
Example: Open in a CAN branch line for HV on the bus 4
| *a | Background color is red | *b | Background color intermittently becomes yellow or red |
| *c | Not displayed or background color is yellow or red | - | - |
| Bus Type | Background Color | Connection Status |
|---|---|---|
| Bus | White | Communication has been normal. |
| Yellow | Communication stop occurred at least once since the start of the CAN bus check, but communication is currently occurring (unstable communication). | |
| Red | Currently not communicating (either of the following):
·
Not communicating since the start of the CAN bus check ·
Communication occurred at least once since the start of the CAN bus check, but is currently not occurring. |
|
| Not displayed | Either of the following:
·
The central gateway ECU (network gateway ECU) has an internal malfunction or cannot communicate with the GTS.*4 ·
No ECUs or sensors are connected to the bus.*5 |
|
| Sub bus with a gateway function equipped ECU that does not memorize connected ECUs or sensors*2 | White | Communication has been normal since the start of the CAN bus check. |
| Yellow | Communication stop occurred at least once since the start of the CAN bus check, but communication is currently occurring (unstable communication). | |
| Red | Communication occurred at least once since the start of the CAN bus check, but is currently not occurring. | |
| Not displayed | Communication stop has continued since the start of the CAN bus check.*1 | |
| Sub bus with a gateway function equipped ECU that memorizes connected ECUs and sensors*3 | White | Communication has been normal. |
| Yellow | Communication stop occurred at least once since the start of the CAN bus check, but communication is currently occurring (unstable communication). | |
| Red | Currently not communicating (either of the following):
·
Not communicating since the start of the CAN bus check ·
Communication occurred at least once since the start of the CAN bus check, but is currently not occurring. |
|
| Not displayed | Either of the following:
·
The gateway function equipped ECU cannot communicate with the central gateway ECU.*6 ·
No ECUs or sensors are connected to the sub bus.*7 |
Gateway function equipped ECUs relay signals between ECUs and sensors connected to different buses.
*1: An ECU or sensor is installed to the vehicle but is not displayed on the "Communication Bus Check" screen.
*2: The gateway function equipped ECU does not memorize ECUs and sensors connected to its respective sub bus.
*3: The gateway function equipped ECU memorizes ECUs and sensors connected to its respective sub bus.
*4: When the central gateway ECU (network gateway ECU) has an internal malfunction or cannot communicate with the GTS, the name of buses, sub buses, ECUs and sensors will not be displayed.
*5: When no ECUs or sensors are connected to a bus, the message "There is no system found on the communication Bus." will be displayed.
*6: When a gateway function equipped ECU cannot communicate with the central gateway ECU (network gateway ECU), the name of sub buses and ECUs or sensors connected to the sub bus will not be displayed.
*7: When no ECUs or sensors are connected to the sub bus, the message "There is no system found on the communication Bus." will be displayed.
The example of the CAN Bus Check screen in the illustration shows the result of electrical noise on the CAN bus which is caused by an open in a CAN branch line of HV is also unstable. In addition, in this example, MB is equipped with a gateway function. Therefore, communication is also unstable between the Sub bus ECUs of MB and the bus 4.
The example in the illustration shows that HV has a red background color on the CAN Bus Check screen. This indicates a more significant communication stop. In this case, a communication stop of HV is suspected.
If a communication error is indicated on both the bus 4 and Sub bus on the CAN Bus Check screen, suspect any communication stop displayed for the bus 4 first.
Example: Open in both CAN branch lines of MB on the bus 4
| *a | Background color is red | *b | Not displayed |
In the CAN bus check, it is possible to confirm the communication status of ECUs connected to the bus after connecting the GTS to the DLC3. As for sub bus, it is possible to confirm which sub bus connected ECUs can communicate with a gateway function equipped ECU on the bus.
If a gateway function equipped ECU has a communication error, ECUs connected to the gateway function equipped ECU are also affected, and communication stops will be indicated.
The CAN Bus Check screen in the illustration shows that ECU G has a gateway function and a communication stop in ECU MB is suspected.
If the CAN Bus Check screen indicates a communication stop only in the sub bus, a communication stop in the sub bus is suspected.
Example: Open in both CAN branch lines of MIR-R on the sub bus
| *a | Background color is red | - | - |
A communication error in a sub bus does not affect the other buses.
When a gateway function equipped ECU has memorized the ECUs that are connected to the sub bus, if any of the ECUs connected to the gateway function equipped ECU has a communication error, the background color changes to yellow or red. (The displayed name will not disappear.)
If both of the bus 2 main bus lines are open, ECUs or sensors that are located farther away from the central gateway ECU than the open part will be displayed as a communication stop on the CAN Bus Check screen.
(In this case, HVB, R-MGC and ENG background color changes to red.)
| *a | Bus 2 | *b | Bus 4 |
| *c | Sub Bus | *d | V Bus |
| *e | Location of Malfunction | *f | Background color is red |
If a communication error occurs in an ECU, it is not displayed on the CAN Bus Check screen even though the ECU is present.
If both of the sub bus main bus lines are open, ECUs that are located farther away from the gateway function equipped ECU than the open part will be displayed as a communication stop on the CAN Bus Check screen.
(In this case, MIR-L background color changes to red.)
| *a | Bus 2 | *b | Bus 4 |
| *c | Sub Bus | *d | V Bus |
| *e | Location of Malfunction | *f | Background color is red |
When any of the following malfunctions occur, CAN communication cannot be established and almost all ECUs and sensors on the bus show a communication error on the CAN Bus Check screen.
| Short between CAN lines (CANH and CANL) |
| Short between a CAN line (CANH or CANL) and +B |
| Short between a CAN line (CANH or CANL) and ground |
| Open in a CAN main bus line |
| *a | When any of the following malfunctions occur on the bus 4 | *b | When any of the following malfunctions occur on a sub bus |
| *c | Background color is red | *d | Not displayed |
When a malfunction occurs in the bus, almost all ECUs and sensors on the bus and sub bus indicate a communication error (almost all ECUs are not displayed). As communication with the gateway function equipped ECU that is connected to the bus stops, communication from the ECUs connected to the sub bus that is monitored by the gateway function equipped ECU also stops (these ECUs are not displayed).
When a malfunction occurs in a sub bus, almost all ECUs connected to the sub bus indicate a communication error.
A communication error in a sub bus does not affect the other buses.
The malfunctioning part can be determined by checking for a short circuit between CAN bus lines or between a CAN bus line and ground or +B short using an electrical tester.
If a communication error of all ECUs and sensors is indicated on the CAN Bus Check screen, a communication stop of the V bus (DLC3 - central gateway ECU) is suspected.
Open in both CAN branch lines in the V bus
| *a | Bus 2 | *b | Bus 4 |
| *c | Sub Bus | *d | V Bus |
| *e | Location of Malfunction | *f | Not displayed |
When there is no communication between the GTS and the vehicle, no ECUs or sensors will be displayed.
HOW TO INTERPRET COMMUNICATION DTCS (DTCS THAT START WITH U)
If a CAN communication error cannot be reproduced, determine the suspected malfunctioning part using the DTCs stored in ECUs that are connected to the CAN buses by following the procedure below.
Communication DTCs (DTCs that start with U) indicate a communication error between the ECU that stores the DTC and the ECU that is indicated by the DTC.
If multiple ECUs store a communication DTC for a particular ECU, a communication stop of the ECU is suspected.
| *a | Items to be Checked | - | - |
This DTC table is from another model, and is only used here to show an example of DTCs that are output when there is an open in a CAN branch line for the main body ECU. This table does not show DTCs applicable to this vehicle.
Even though a DTC title may indicate a communication error with a specific ECU, the ECU name used in the DTC name on the GTS may differ depending on the ECU that stores the DTC. (Regarding output DTCs, refer to the DTC chart for each ECU.)
As multiple ECUs indicate a communication stop with the main body ECU, the possibility of a communication stop of the main body ECU is high.
If almost all of the communication DTCs of an ECU are stored, a communication stop of the ECU is suspected.
| *a | Items to be Checked | - | - |
This DTC table is from another model, and is only used here to show an example of DTCs that are output when there is an open in a CAN branch line for the main body ECU. This table does not show DTCs applicable to this vehicle.
Even though a DTC title may indicate a communication error with a specific ECU, the ECU name used in the DTC name on the GTS may differ depending on the ECU that stores the DTC. (Regarding output DTCs, refer to DTC Table by ECU.)
If almost all of the DTCs of the main body ECU are stored, the possibility of a communication stop of the main body ECU is high.
When a CAN communication error occurs, many DTCs are output. DTCs other than communication error DTCs (such as DTCs that start with C or B) and communication DTCs for the ABS system are important DTCs, however it may be easier to determine the malfunctioning part by examining the overall situation without considering these DTCs.
To help determine the part of the sub bus that has a communication error, prioritize the communication stop DTCs stored in the gateway function equipped ECU.
| *a | Items to be Checked | *b | ECM |
| *c | Gateway Function Equipped ECU | *d | Location of Malfunction |
| *e | Bus | *f | Sub Bus |
This DTC table is from another model, and is only used here to show the ECUs connected to both a bus and a sub bus. It shows DTCs output when there is an open in the main bus lines for the ECM on the sub bus. This table does not show DTCs applicable to this vehicle.
As gateway function equipped ECUs (sub bus monitor ECU) monitor signals from all ECUs that are connected to sub bus, gateway function equipped ECUs can detect ECUs with a communication stop more accurately.
When there is a communication stop for the gateway function equipped ECU (gateway), communication with ECUs connected to other buses such as the bus 2 stops. Therefore, communication DTCs for ECUs connected to other buses are also stored.
When any of the following malfunctions occurs, many DTCs are likely to be output from many ECUs. Because of this, it may be difficult to determine the probable malfunctioning part.
Short between CAN lines (CANH and CANL)
Short between a CAN line (CANH or CANL) and ground
Short between a CAN line (CANH or CANL) and +B
Open in a CAN branch line (CANH or CANL) of an ECU or sensor
Open in a CAN main bus line (CANH or CANL) between 2 ECUs that have a terminating resistor
DTC TABLE BY ECU
In the CAN communication system, CAN communication system DTCs stored by the ECU can be output from the ECU by using the intelligent tester.
If CAN communication system DTCs are output, the trouble cannot be determined solely from the DTCs. Perform troubleshooting according to "How to Proceed with Troubleshooting".
ECM
DTC communication uses the CAN communication system.
| DTC No. | Detection Item |
|---|---|
| U0129 | Lost Communication with Brake System Control Module |
MAIN BODY ECU (MULTIPLEX NETWORK BODY ECU)
DTC communication uses the CAN communication system.
| DTC No. | Detection Item |
|---|---|
| U0100 | Lost Communication With ECM/PCM "A" |
| U0101 | Lost Communication with TCM |
| U0151 | Lost Communication With Restraints Control Module |
| U0155 | Lost Communication with Instrument Panel Cluster (IPC) Control Module |
| U0164 | Lost Communication with HVAC Control Module |
| U023A | Lost Communication with Image Processing Module "A" |
SKID CONTROL ECU (BRAKE ACTUATOR ASSEMBLY)
DTC communication uses the CAN communication system.
| DTC No. | Detection Item |
|---|---|
| U0073 | Control Module Communication Bus Off |
| U0100 | Lost Communication With ECM/PCM "A" |
| U0124 | Lost Communication with Lateral Acceleration Sensor Module |
| U0126 | Lost Communication with Steering Angle Sensor Module |
POWER STEERING ECU ASSEMBLY
DTC communication uses the CAN communication system.
| DTC No. | Detection Item |
|---|---|
| U0100 | Lost Communication with ECM/PCM "A" |
| U0129 | Lost Communication With Brake System Control Module |
COMBINATION METER ASSEMBLY
DTC communication uses the CAN communication system.
| DTC No. | Detection Item |
|---|---|
| U0100 | Lost Communication with ECM/PCM "A" |
| U0129 | Lost Communication with Brake System Control Module |
| U0131 | Lost Communication with Power Steering Control Module |
| U0151 | Lost Communication with Restraints Control Module |
| U023A | Lost Communication with Front Camera Module |
AIR CONDITIONING AMPLIFIER ASSEMBLY
DTC communication uses the CAN communication system.
| DTC No. | Detection Item |
|---|---|
| U0100 | Lost Communication With ECM/PCM "A" |
| U0131 | Lost Communication With Power Steering Control Module |
| U0142 | Lost Communication With Body Control Module "B" |
| U0155 | Lost Communication With Instrument Panel Cluster (IPC) Control Module |
RADIO AND DISPLAY RECEIVER ASSEMBLY (for Radio and Display Type)
DTC communication uses the CAN communication system.
| DTC No. | Detection Item |
|---|---|
| U0073 | Control Module Communication Bus off |
| U0100 | Lost Communication with ECM/PCM "A" |
| U0129 | Lost Communication with Brake System Control Module |
| U0140 | Lost Communication with Main Body ECU |
| U0155 | Lost Communication with Combination Meter |
| U0164 | Lost Communication with HVAC control Module |
NAVIGATION RECEIVER ASSEMBLY (for Navigation Receiver Type)
DTC communication uses the CAN communication system.
| DTC No. | Detection Item |
|---|---|
| U0073 | Control Module Communication Bus off |
| U0100 | Lost Communication with ECM/PCM "A" |
| U0129 | Lost Communication with Brake System Control Module |
| U0140 | Lost Communication with Main Body ECU |
| U0155 | Lost Communication with Combination Meter |
| U0164 | Lost Communication with HVAC control Module |
STEERING ANGLE SENSOR (SPIRAL CABLE SUB-ASSEMBLY)
The steering angle sensor (spiral cable sub-assembly) is connected to the CAN communication system but CAN communication DTCs are not stored.
AIRBAG SENSOR ASSEMBLY
The airbag sensor assembly is connected to the CAN communication system but CAN communication DTCs are not stored.
PRE-CRASH SAFETY CITY SENSOR
DTC communication uses the CAN communication system.
The pre-crash safety city sensor incorporates the pre-crash safety system, lane departure alert system and automatic high beam system.
When the pre-crash safety city sensor is extremely hot or cold, a communication error may occur and DTC U023A may be stored. Communication will return to normal when the temperature of the pre-crash safety city sensor returns to normal.
| DTC No. | Detection Item |
|---|---|
| U0100 | Lost Communication with ECM/PCM "A" |
| U0123 | Lost Communication with Yaw Rate Sensor Module |
| U0126 | Lost Communication with Steering Angle Sensor Module |
| U0129 | Lost Communication with Brake System Control Module |
| U0155 | Lost Communication With Instrument Panel Cluster (IPC) Control Module |
| U023A | Lost Communication with Front Camera Module |
CENTRAL GATEWAY ECU (NETWORK GATEWAY ECU)
The central gateway ECU (network gateway ECU) is connected to the CAN communication system but CAN communication DTCs are not stored.
DTC COMBINATION TABLE (OPEN IN CAN BRANCH OF BUS 2, PAST COMMUNICATION ERROR)
Regarding the past communication error of ECUs and sensors connected to the bus 2 (in this case, normal was displayed when performing the communication bus check, but communication DTCs are output), the probable CAN branch that had a malfunction can be determined based on the following DTC combination table.
Based on the table below and DTCs output from ECUs connected via CAN communication, the probable part for which communication stop occurred can be determined.
Regarding an open in a CAN branch and a communication stop that is currently occurring, the malfunctioning part can be confirmed easily by performing the communication bus check using the GTS because the ECU or sensor connected to the CAN branch does not respond (the ECU or sensor name will not be displayed on the screen).
If an open in a CAN main bus line, a short between the CAN bus lines (CANH and CANL) or a +B or ground short in the CAN bus occurs, DTCs of almost all ECUs (or sensors) on the CAN bus may be output, or a message indicating a communication error may be displayed on the GTS screen. In this case, check the resistance of the CAN bus (steps 10 to 12) first (See pagePower Source / Network>NETWORKING>CAN COMMUNICATION SYSTEM(w/ Toyota Safety Sense)>HOW TO PROCEED WITH TROUBLESHOOTING).
If an open occurs in just one of the lines of a CAN branch, DTCs which are not related to malfunctioning parts may be output (DTCs may be displayed randomly), or a message indicating a communication error may be displayed.
*1: U0073 may be stored when communication is lost.
X: DTC is likely to be output.
▲: DTC is not likely to be output.
-: DTC is not output.
*1: U0073 may be stored when communication is lost.
X: DTC is likely to be output.
▲: DTC is not likely to be output.
-: DTC is not output.
*1: U0073 may be stored when communication is lost.
○ : DTC is output.
-: DTC is not output.
*1: U0073 may be stored when communication is lost.
○ : DTC is output.
-: DTC is not output.
*1: U0073 may be stored when communication is lost.
X: DTC is likely to be output.
▲: DTC is not likely to be output.
-: DTC is not output.
| Bus 2 (CAN bus line short circuit) | Bus 2 (CAN bus line short to GND) | ||||
|---|---|---|---|---|---|
| Trouble Mode | Trouble Mode | ||||
| Output ECU | Output DTC | CANH to CANL | CANH to GND | CANL to GND | |
| Bus 2 | Airbag Sensor Assembly | - | - | - | - |
| Air Conditioning Amplifier Assembly | U0100 | ○ | ○ | ○ | |
| U0131 | ○ | ○ | ○ | ||
| U0142 | ○ | ○ | ○ | ||
| U0155 | ○ | ○ | ○ | ||
| Main Body ECU (Multiplex Network Body ECU) | U0100 | ○ | ○ | ○ | |
| U0101 | ○ | ○ | ○ | ||
| U0120 | ○ | ○ | ○ | ||
| U0151 | ○ | ○ | ○ | ||
| U0155 | ○ | ○ | ○ | ||
| U0164 | ○ | ○ | ○ | ||
| U023A | ○ | ○ | ○ | ||
| Central Gateway ECU (Network Gateway ECU) | - | - | - | - | |
| ECM | U0129 | ○ | ○ | ○ | |
| Power Steering ECU Assembly | U0100 | ○ | ○ | ○ | |
| U0129 | ○ | ○ | ○ | ||
| Combination Meter Assembly | U0100 | ○ | ○ | ○ | |
| U0129 | ○ | ○ | ○ | ||
| U0131 | ○ | ○ | ○ | ||
| U0151 | ○ | ○ | ○ | ||
| U023A | ○ | ○ | ○ | ||
| Pre-crash Safety City Sensor | U0100 | ○ | ○ | ○ | |
| U0123 | ○ | ○ | ○ | ||
| U0126 | ○ | ○ | ○ | ||
| U0129 | ○ | ○ | ○ | ||
| U0155 | ○ | ○ | ○ | ||
| Steering Angle Sensor (Spiral Cable Sub-assembly) | - | - | - | - | |
| Skid Control ECU (Brake Actuator Assembly)*1 | U0100 | ○ | ○ | ○ | |
| U0124 | ○ | ○ | ○ | ||
| U0126 | ○ | ○ | ○ | ||
| Bus 3 | Radio and Display Receiver Assembly or Navigation Receiver Assembly*1 | U0100 | ○ | ○ | ○ |
| U0129 | ○ | ○ | ○ | ||
| U0140 | ○ | ○ | ○ | ||
| U0155 | ○ | ○ | ○ | ||
| U0164 | ○ | ○ | ○ | ||
| Central Gateway ECU (Network Gateway ECU) | - | - | - | - | |
*1: U0073 may be stored when communication is lost.
○ : DTC is output.
-: DTC is not output.
DTC COMBINATION TABLE (OPEN IN CAN BRANCH OF BUS 3, PAST COMMUNICATION ERROR)
Regarding the past communication error of ECUs and sensors connected to the bus 3 (in this case, normal was displayed when performing the communication bus check, but communication DTCs are output), the probable CAN branch that had a malfunction can be determined based on the following DTC combination table.
Based on the table below and DTCs output from ECUs connected via CAN communication, the probable part for which communication stop occurred can be determined.
Regarding an open in a CAN branch and a communication stop that is currently occurring, the malfunctioning part can be confirmed easily by performing the communication bus check using the GTS because the ECU or sensor connected to the CAN branch does not respond (the ECU or sensor name will not be displayed on the screen).
If an open in a CAN main bus line, a short between the CAN bus lines (CANH and CANL) or a +B or ground short in the CAN bus occurs, DTCs of almost all ECUs (or sensors) on the CAN bus may be output, or a message indicating a communication error may be displayed on the GTS screen. In this case, check the resistance of the CAN bus (steps 13 to 15) first (See pagePower Source / Network>NETWORKING>CAN COMMUNICATION SYSTEM(w/ Toyota Safety Sense)>HOW TO PROCEED WITH TROUBLESHOOTING)
If an open occurs in just one of the lines of a CAN branch, DTCs which are not related to malfunctioning parts may be output (DTCs may be displayed randomly), or a message indicating a communication error may be displayed.
*1: U0073 may be stored when communication is lost.
X: DTC is likely to be output.
▲: DTC is not likely to be output.
-: DTC is not output.
*1: U0073 may be stored when communication is lost.
○ : DTC is output.
-: DTC is not output.
| Bus 3 (Open in one CAN main line) | Bus 3 (Open in Both CAN main line) | |||||
|---|---|---|---|---|---|---|
| Trouble Mode | Trouble Mode | |||||
| Output ECU | Output DTC | Central Gateway ECU (CA3H and CA3L Terminal) | Central Gateway ECU (CAYH and CAYL Terminal) | Central Gateway ECU (CA3H and CA3L Terminal) | Central Gateway ECU (CAYH and CAYL Terminal) | |
| Bus 2 | Airbag Sensor Assembly | - | - | - | - | - |
| Air Conditioning Amplifier Assembly | U0100 | - | - | - | - | |
| U0131 | - | - | - | - | ||
| U0142 | - | - | - | - | ||
| U0155 | - | - | - | - | ||
| Main Body ECU (Multiplex Network Body ECU) | U0100 | - | - | - | - | |
| U0101 | - | - | - | - | ||
| U0120 | - | - | - | - | ||
| U0151 | - | - | - | - | ||
| U0155 | - | - | - | - | ||
| U0164 | - | - | - | - | ||
| U023A | - | - | - | - | ||
| Central Gateway ECU (Network Gateway ECU) | - | - | - | - | - | |
| ECM | U0129 | - | - | - | - | |
| Power Steering ECU Assembly | U0100 | - | - | - | - | |
| U0129 | - | - | - | - | ||
| Combination Meter Assembly | U0100 | - | - | - | - | |
| U0129 | - | - | - | - | ||
| U0131 | - | - | - | - | ||
| U0151 | - | - | - | - | ||
| U023A | - | - | - | - | ||
| Pre-crash Safety City Sensor | U0100 | - | - | - | - | |
| U0123 | - | - | - | - | ||
| U0126 | - | - | - | - | ||
| U0129 | - | - | - | - | ||
| U0155 | - | - | - | - | ||
| Steering Angle Sensor (Spiral Cable Sub-assembly) | - | - | - | - | - | |
| Skid Control ECU (Brake Actuator Assembly)*1 | U0100 | - | - | - | - | |
| U0124 | - | - | - | - | ||
| U0126 | - | - | - | - | ||
| Bus 3 | Radio and Display Receiver Assembly or Navigation Receiver Assembly*1 | U0100 | X | ▲ | ○ | - |
| U0129 | X | ▲ | ○ | - | ||
| U0140 | X | ▲ | ○ | - | ||
| U0155 | X | ▲ | ○ | - | ||
| U0164 | X | ▲ | ○ | - | ||
| Central Gateway ECU (Network Gateway ECU) | - | - | - | - | - | |
*1: U0073 may be stored when communication is lost.
X: DTC is likely to be output.
▲: DTC is not likely to be output.
-: DTC is not output.
| Bus 3 (CAN bus line short circuit) | Bus 3 (CAN bus line short to GND) | ||||
|---|---|---|---|---|---|
| Trouble Mode | Trouble Mode | ||||
| Output ECU | Output DTC | CANH to CANL | CANH to GND | CANL to GND | |
| Bus 2 | Airbag Sensor Assembly | - | - | - | - |
| Air Conditioning Amplifier Assembly | U0100 | - | - | - | |
| U0131 | - | - | - | ||
| U0142 | - | - | - | ||
| U0155 | - | - | - | ||
| Main Body ECU (Multiplex Network Body ECU) | U0100 | - | - | - | |
| U0101 | - | - | - | ||
| U0120 | - | - | - | ||
| U0151 | - | - | - | ||
| U0155 | - | - | - | ||
| U0164 | - | - | - | ||
| U023A | - | - | - | ||
| Central Gateway ECU (Network Gateway ECU) | - | - | - | - | |
| ECM | U0129 | - | - | - | |
| Power Steering ECU Assembly | U0100 | - | - | - | |
| U0129 | - | - | - | ||
| Combination Meter Assembly | U0100 | - | - | - | |
| U0129 | - | - | - | ||
| U0131 | - | - | - | ||
| U0151 | - | - | - | ||
| U023A | - | - | - | ||
| Pre-crash Safety City Sensor | U0100 | - | - | - | |
| U0123 | - | - | - | ||
| U0126 | - | - | - | ||
| U0129 | - | - | - | ||
| U0155 | - | - | - | ||
| Steering Angle Sensor (Spiral Cable Sub-assembly) | - | - | - | - | |
| Skid Control ECU (Brake Actuator Assembly)*1 | U0100 | - | - | - | |
| U0124 | - | - | - | ||
| U0126 | - | - | - | ||
| Bus 3 | Radio and Display Receiver Assembly or Navigation Receiver Assembly*1 | U0100 | ○ | ○ | ○ |
| U0129 | ○ | ○ | ○ | ||
| U0140 | ○ | ○ | ○ | ||
| U0155 | ○ | ○ | ○ | ||
| U0164 | ○ | ○ | ○ | ||
| Central Gateway ECU (Network Gateway ECU) | - | - | - | - | |
*1: U0073 may be stored when communication is lost.
○ : DTC is output.
-: DTC is not output.