ECUS OR SENSORS WHICH COMMUNICATE THROUGH CAN COMMUNICATION SYSTEM
V Bus
ECM
Brake actuator assembly (skid control ECU)
Spiral with sensor cable sub-assembly (steering angle sensor)
Airbag sensor assembly
Combination meter assembly
CHECK FOR INSTALLED SYSTEMS (ECUS AND SENSORS) THAT USE 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 on the vehicle.
The names of ECUs and sensors shown on the GTS display may differ from those shown in the DTC Table by ECU section that follows.
| ECU/Sensor Name | GTS Display | Installed on |
|---|---|---|
| ECM | ECM (Engine) | All vehicles |
| Brake actuator assembly (skid control ECU) | Skid Control (ABS/VSC/TRAC) | All vehicles |
| Spiral with sensor cable sub-assembly (steering angle sensor) | Spiral cable (Steering Angle Sensor) | All vehicles |
| Combination meter assembly | Combination Meter | All vehicles |
| Airbag sensor assembly | Airbag | All vehicles |
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.
Different connection statuses are indicated by the background color of ECUs and sensors that are displayed.
| Bus Type | Background Color | Connection Status |
|---|---|---|
| V Bus | 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 was established at least once since the start of the CAN bus check, but communication is currently not occurring (unstable communication). | |
| Not displayed | Communication stop has continued since the start of the CAN bus check.*1 | |
| Sub bus (gateway function equipped ECU that does not have history of connected ECUs)*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 was established at least once since the start of the CAN bus check, but communication is currently not occurring (unstable communication). | |
| Not displayed | Communication stop has continued since the start of the CAN bus check.*1 | |
| Sub bus (gateway function equipped ECU that has history of connected ECUs)*3 |
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 | Currently not communicating (either of the following):
·
Communication stop has continued since the start of the CAN bus check.
·
Communication was established at least once since the start of the CAN bus check, but communication is currently not occurring (unstable communication). |
|
| Not displayed | Either of the following:
·
If a gateway function equipped ECU cannot communicate, the sub bus and ECUs connected to the sub bus will not be displayed.
·
If no ECUs are connected to the sub bus, "There is no system found on the Communication Bus" will be displayed. |
Gateway function equipped ECUs relay signals between the ECUs connected to the different buses.
*1: ECUs that are present in the vehicle but are not displayed on the CAN Bus Check.
*2: Gateway function equipped ECU that does not memorize the sub bus ECUs that are connected to it.
*3: Gateway function equipped ECU that memorizes the sub bus ECUs that are connected to it.
If none of the connected ECUs are displayed, or there is no response from the vehicle to the GTS, check the DLC3 branch and the V bus main wires for a malfunction.
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 to ON (or simulate the driving conditions that enable the malfunction to be reproduced) and select the 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.
Example: Open in both CAN branch wires of ECU B on the V bus
| *a | V Bus | *b | Sub bus |
| *c | Terminating Resistor | *d | Location of malfunction |
| *e | Not displayed or background color changes to red or yellow | *f | CAN Bus Check screen |
When there are communication stops, ECUs are present in the vehicle even though they are not displayed on the CAN Bus Check screen.
| *a | Background color periodically changes to yellow or red |
| *b | Not displayed or background color is yellow or red |
| *c | Not displayed |
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 a sensor which is not displayed) is suspected.
Example: Open in a CAN branch wire for ECU D on the V bus
| Bus Type | Background Color | Connection Status |
|---|---|---|
| V Bus | 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 was established at least once since the start of the CAN bus check, but communication is currently not occurring (unstable communication). | |
| Not displayed | Communication stop has continued since the start of the CAN bus check.*1 | |
| Sub bus (gateway function equipped ECU that does not have history of connected ECUs)*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 was established at least once since the start of the CAN bus check, but communication is currently not occurring (unstable communication). | |
| Not displayed | Communication stop has continued since the start of the CAN bus check.*1 | |
| Sub bus (gateway function equipped ECU that has history of connected ECUs)*3 |
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 | Currently not communicating (either of the following):
·
Communication stop has continued since the start of the CAN bus check.
·
Communication was established at least once since the start of the CAN bus check, but communication is currently not occurring (unstable communication). |
|
| Not displayed | Either of the following:
·
If a gateway function equipped ECU cannot communicate, sub bus and ECUs connected to the sub bus will not be displayed.
·
If no ECUs are connected to the sub bus, "There is no system found on the Communication Bus" will be displayed. |
Gateway function equipped ECUs relay signals between the ECUs connected to the different buses.
*1: ECUs that are present in the vehicle but are not displayed on the CAN Bus Check screen.
*2: Gateway function equipped ECU that does not memorize the sub bus ECUs that are connected to it.
*3: Gateway function equipped ECU that memorizes the sub bus ECUs that are connected to it.
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 wire of ECU D (output from the other branch line is unstable) and the communication of ECU C is also unstable. In addition, in this example, ECU C is equipped with a gateway function. Therefore, communication is also unstable between the sub bus ECUs of ECU C and the V bus.
The example in the illustration shows that ECU D is not displayed on the CAN Bus Check screen. This indicates a more significant communication stop. In this case, a communication stop of ECU D is suspected.
| *a | Not displayed or background color changes to red |
If a communication error is indicated on both the V bus and sub bus on the CAN Bus Check screen, suspect any communication stop displayed for the V bus first.
Example: Open in both CAN branch wires of ECU C on the V bus
In the CAN bus check, it is possible to confirm the communication status of ECUs connected to the V bus after connecting the GTS to the DLC3. As for sub buses, it is possible to confirm which sub bus connected ECUs can communicate with a gateway function equipped ECU on the V 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 C has a gateway function and a communication stop in ECU C is suspected.
| *a | Background color changes to yellow or red |
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 wires of ECU G on the sub bus
A communication error in a sub bus does not affect the V bus or 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 V bus main wires are open, ECUs or sensors that are located farther away from the DLC3 than the open part will be displayed as a communication stop on the CAN Bus Check screen.
(In this case, ECU A and B are not displayed or their background color changes to red.)
| *a | V Bus | *b | Sub Bus |
| *c | Terminating Resistor | *d | Location of malfunction |
| *e | Not displayed or background color is red | *f | CAN Bus Check screen |
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 wires 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, ECU I and J are not displayed or their background color changes to red.)
| *a | V Bus | *b | Sub Bus |
| *c | Terminating Resistor | *d | Location of malfunction |
| *e | Not displayed or background color is red | *f | CAN Bus Check screen |
| *g | Gateway function equipped ECU | - | - |
| *a | When any of the following malfunctions occur on the V bus |
| *b | When any of the following malfunctions occur on a sub bus |
| *c | Not displayed |
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 wires (CANH and CANL) |
| Short between a CAN wire (CANH or CANL) and +B |
| Short between a CAN wire (CANH or CANL) and ground |
| Open in a CAN main wire |
When a malfunction occurs on the V bus, almost all ECUs and sensors on the V 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 V 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 V bus or 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.
DTC TABLE BY ECU
In the CAN communication system, the CAN communication DTCs of each ECU can be displayed using the GTS.
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".
If system function temporarily returns to normal, DTCs may not be output again even though the following DTC check procedures are used.
BRAKE ACTUATOR ASSEMBLY (SKID CONTROL ECU) / GTS "ABS/VSC/TRC"
DTC communication uses the CAN communication system.
| DTC No. | Detection Item | DTC Detection Condition | DTC Detection Precondition | DTC Check Procedure | Warning Indication in Meter | DTC Storage Method |
|---|---|---|---|---|---|---|
| U0073 | Control Module Communication Bus Off | Either condition is met:
·
The response sent to the brake actuator assembly (skid control ECU) from the spiral with sensor cable sub-assembly (steering angle sensor) is invalid for 1 second or more.
·
The following condition occurs 10 times consecutively within 60 seconds: The response sent to the brake actuator assembly (skid control ECU) from the spiral with sensor cable sub-assembly (steering angle sensor) is invalid at least once within 5 seconds.
·
The brake actuator assembly (skid control ECU) cannot send or receive data (the bus is off) 10 times consecutively. |
Both conditions are met:
·
1 second or more elapses after turning the ignition switch to ON.
·
The brake actuator assembly (skid control ECU) power supply voltage is between 10 and 17.4 V. |
Turn the ignition switch to ON and wait at least 60 seconds. |
·
ABS indicator light illuminates.
·
SLIP indicator light illuminates. |
The DTC remains stored until it is cleared using the GTS. |
| U0100 | Lost Communication With ECM/PCM "A" | The brake actuator assembly (skid control ECU) is unable to receive certain data from the ECM for 2 seconds or more. | All conditions are met:
·
1 second or more elapses after turning the ignition switch to ON.
·
The vehicle speed is 15 km/h (9 mph) or more.
·
The brake actuator assembly (skid control ECU) power supply voltage is between 10 and 17.4 V. |
Drive the vehicle for 3 seconds at a speed of 15 km/h (9 mph) or more. | SLIP indicator light illuminates. | The DTC remains stored until it is cleared using the GTS. |
| U0124 | Lost Communication With Lateral Acceleration Sensor Module | Either condition is met:
·
The brake actuator assembly (skid control ECU) is unable to receive certain data from the airbag sensor assembly for 1 second or more.
·
The following condition occurs 10 times or more consecutively within 60 seconds: The brake actuator assembly (skid control ECU) is unable to receive certain data from the airbag sensor assembly at least once within 5 seconds. |
Both conditions are met:
·
1 second or more elapses after turning the ignition switch to ON.
·
The brake actuator assembly (skid control ECU) power supply voltage is between 10 and 17.4 V. |
Turn the ignition switch to ON and wait at least 60 seconds. |
·
ABS indicator light illuminates.
·
SLIP indicator light illuminates. |
The DTC remains stored until it is cleared using the GTS. |
| U0126 | Lost Communication With Steering Angle Sensor Module | Either condition is met:
·
The brake actuator assembly (skid control ECU) is unable to receive certain data from the spiral with sensor cable sub-assembly (steering angle sensor) for 1 second or more.
·
The following condition occurs 10 times or more consecutively within 60 seconds: The brake actuator assembly (skid control ECU) is unable to receive certain data from the spiral with sensor cable sub-assembly (steering angle sensor) at least once within 5 seconds. |
Both conditions are met:
·
1 second or more elapses after turning the ignition switch to ON.
·
The brake actuator assembly (skid control ECU) power supply voltage is between 10 and 17.4 V. |
Turn the ignition switch to ON and wait at least 60 seconds. | SLIP indicator light illuminates. | The DTC remains stored until it is cleared using the GTS. |
COMBINATION METER ASSEMBLY / GTS "Combination Meter"
DTC communication uses the CAN communication system.
| DTC No. | Detection Item | DTC Detection Condition | DTC Check Procedure | DTC Check Procedure | Warning Indication in Meter | DTC Storage Method |
|---|---|---|---|---|---|---|
| U0100 | Lost Communication with ECM/PCM "A" | The combination meter assembly is unable to receive certain data from the ECM for 2 seconds or more. | Both conditions are met:
·
Turning the ignition switch to ON.
·
The voltage at the IG power supply terminal of the combination meter assembly is 11.5 V or higher. |
Turn the ignition switch to ON and wait at least 2 seconds. | MIL illuminates. | The DTC remains stored until it is cleared using the GTS. |
| U0129 | Lost Communication with Brake System Control Module | Either condition is met:
·
The combination meter assembly is unable to receive certain data from the brake actuator assembly (skid control ECU) for 2 seconds or more.
·
The combination meter assembly is unable to receive certain data from the brake actuator assembly (skid control ECU) for 3 seconds or more. |
Both conditions are met:
·
Turning the ignition switch to ON.
·
The voltage at the IG power supply terminal of the combination meter assembly is 11.5 V or higher. |
Turn the ignition switch to ON and wait at least 3 seconds. |
·
ABS indicator light illuminates.
·
SLIP indicator light illuminates.
·
Brake warning light illuminates. |
The DTC remains stored until it is cleared using the GTS. |
| U0151 | Lost Communication with Restraints Control Module | The combination meter assembly is unable to receive certain data from the airbag sensor assembly for 10 seconds or more. | Both conditions are met:
·
Turning the ignition switch to ON.
·
The voltage at the IG power supply terminal of the combination meter assembly is 11.5 V or higher. |
Turn the ignition switch to ON and wait at least 10 seconds. | SRS warning light illuminates. | The DTC remains stored until it is cleared using the GTS. |
ECM
The ECM is connected to the CAN communication system but CAN communication DTCs are not stored.
SPIRAL WITH SENSOR CABLE SUB-ASSEMBLY (STEERING ANGLE SENSOR)
The spiral with sensor cable sub-assembly (steering angle sensor) 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.
CAN BUS WAVEFORMS
This waveform is measured between terminals CANH and GND, and terminals CANL and GND of the DLC3. (Use this as a reference for diagnosis of CAN communication lines.)
When malfunctions in multiple ECUs are suspected based on the CAN bus check and DTCs checked using the GTS, check the resistance of the CAN bus using an ohmmeter first. If no problems are found, check the following waveforms.
If a waveform is not similar to one of the following 3 patterns (Group 1), then an open in a CAN main wire, an open in a CAN branch wire, or a short between a CAN wire (CANH or CANL) and ground is suspected (Group 2).
Wiggle the connector and wire harness to check if the waveform changes.
CAN bus waveforms (Group 1)
Normal waveform
Open in both of the lines (CANH and CANL) of a CAN branch
Waveforms (waveforms shown using dotted lines) are not output from an ECU or sensor connected to a CAN branch with an open circuit in both lines. (Waveforms from other ECUs or sensors are normal.)
Because this waveform is similar to a normal waveform, instead of using the waveform, the malfunctioning part can be narrowed down by performing a CAN bus check.
Short between the CAN bus lines (CANH and CANL)
Waveforms disappear.
If the malfunction is in an ECU, disconnecting the ECU will change the waveform. If the waveform does not change, a malfunction in the wire harness is suspected.
CAN bus waveforms (reference) (Group 2)
The following CAN bus waveforms can be used only as reference. The actual measured waveform may differ significantly depending on the location of the open or short circuit.
Open in a CAN branch wire (CANH)
An abnormal waveform is output from an ECU with an open in one of its CAN branch wires. Because this abnormal output interferes with the signals from other ECUs, the output of other ECUs will also appear abnormal.
Narrow down the malfunctioning part by checking DTCs or performing a CAN bus check, or by checking waveform changes when ECUs or sensors are disconnected. The waveform will change to one for an open in both sides of a CAN branch when the ECU or sensor with an open CAN branch wire is disconnected.
Open in a CAN branch wire (CANL)
An abnormal waveform is output from an ECU with an open in one of its CAN branch wires. Because this abnormal output interferes with the signals from other ECUs, the output of other ECUs will also appear abnormal.
Narrow down the malfunctioning part by checking DTCs or performing a CAN bus check, or by checking waveform changes when ECUs or sensors are disconnected. The waveform will change to one for an open in both sides of a CAN branch when the ECU or sensor with an open CAN branch wire is disconnected.
Open in a CAN main wire (CANH)
Waveforms of ECUs or sensors that are closer to the DLC3 than the open part are almost normal.
Waveforms of ECUs or sensors that are on the opposite side of the DLC3 from the open part are abnormal.
An open in a CAN main wire can be confirmed by measuring the resistance between the CANH and CANL terminals of any CAN branch.
Short between a CAN bus line (CANH) and ground
Narrow down the shorted part by checking for waveform changes when disconnecting connector(s) from the CAN junction connector(s) or when disconnecting ECUs or sensors.
A short to ground in the CANH line can be confirmed by measuring the resistance between CANH and ground using an ohmmeter.
Short between a CAN bus line (CANL) and ground
Narrow down the shorted part by checking for waveform changes when disconnecting connector(s) from the CAN junction connector(s) or when disconnecting ECUs or sensors.
A short to ground in the CANL line can be confirmed by measuring the resistance between CANL and ground using an ohmmeter.
DATA SENDING/RECEIVING TABLE
Data sending/receiving table
If Data List items related to sent/received data are not displayed properly, the part for which communication is interrupted can be determined using the table below.