ECUS WHICH COMMUNICATE THROUGH CAN COMMUNICATION SYSTEM
V Bus
ECM
TCM*1
Combination meter assembly*2
*1 : for A/T
*2 : w/ Multi Information Display
CHECK FOR INSTALLED SYSTEMS (ECUS) THAT ADOPT CAN COMMUNICATION
The systems (ECUs) that adopt CAN communication vary depending on the vehicle and optional equipment. Check which systems (ECUs) are installed on the vehicle.
The names of ECUs shown on the intelligent tester or Techstream display may differ from those shown in the DTC Table by ECU section that follows.
| ECU Name | Tester Display | Applicability |
|---|---|---|
| ECM | EFI | Installed on all vehicles |
| TCM | ECT | for A/T |
| Combination meter assembly | Combination Meter | w/ Multi Information Display |
CAN BUS CHECK
The ECUs and sensors that are properly connected to the CAN communication system can be displayed using the intelligent tester or Techstream.
Using the intelligent tester or Techstream, select "CAN Bus Check" from "System Select".
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 (See page Power Source / Network>NETWORKING>CAN COMMUNICATION SYSTEM>SYSTEM DIAGRAM).
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. |
|
| 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.
*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 intelligent tester or Techstream, check the DLC3 branch and the V bus main bus lines 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 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 (COMMUNICATION 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 lines 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 line 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 |
|
| 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 line 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 lines 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 intelligent tester or Techstream 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.
| *a | Background color changes to 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 lines 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 bus lines 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 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, ECU I and J are not displayed or the 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 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 |
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.
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 intelligent tester or Techstream may differ depending on the ECU that stores the DTC. (Regarding output DTCs, refer to step 6 and 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.
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 | V Bus | *f | Sub Bus |
This DTC table is from another model, and is only used here to show the ECUs connected to both a V 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 buses, 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 V bus 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, the CAN communication DTCs of each ECU can be displayed using the intelligent tester or Techstream.
If CAN communication system DTCs are output, trouble cannot be determined only by the DTCs. Perform troubleshooting according to How to Proceed with Troubleshooting.
Click herePower Source / Network>NETWORKING>CAN COMMUNICATION SYSTEM>DIAGNOSIS SYSTEM
If system function temporarily returns to normal, DTCs may not be output again even though the following DTC check procedures are used.
ECM / Intelligent Tester or Techstream Display "EFI"
| DTC | Detection Item | DTC Detection Condition | DTC Detection Pre-condition | DTC Check Procedure | Warning Indication in Meter | DTC Storage Method |
|---|---|---|---|---|---|---|
| U0001 | High Speed CAN Communication Bus | No communication between ECM, combination meter assembly and TCM for 2 seconds or more.
(1 trip detection logic) |
Both conditions are met:
·
The ignition switch is turned ON. ·
The power source voltage of the ECM is 10.5 V or more. |
Turn the ignition switch to ON and wait at least 1 second. | MIL illuminates. | DTC is stored until it is cleared using the intelligent tester or Techstream. |
| U0101 | Lost Communication with TCM | Either of following condition met:
(1 trip detection logic) (a) No communication from TCM (reception) for 1 second or more (b) No communication from ECM (transmission) for 0.3 seconds or more |
Both conditions are met:
·
The ignition switch is turned ON. ·
The power source voltage of the ECM is 10.5 V or more. |
Turn the ignition switch to ON and wait at least 1 second. | MIL illuminates. | DTC is stored until it is cleared using the intelligent tester or Techstream. |
| U0156 | Lost Communication with Instrument Panel Cluster Control Module (Combination Meter) | No communication from combination meter (reception) for 1 second or more
(1 trip detection logic) |
Both conditions are met:
·
The ignition switch is turned ON. ·
The power source voltage of the ECM is 10.5 V or more. |
Turn the ignition switch to ON and wait at least 1 second. | MIL illuminates. | DTC is stored until it is cleared using the intelligent tester or Techstream. |
This ECU uses the CAN communication system for DTC communication.
TCM / Intelligent Tester or Techstream Display "ECT"
This ECU uses the CAN communication system for DTC communication.
| DTC | Detection Item | DTC Detection Condition | DTC Detection Pre-condition | DTC Check Procedure | Warning Indication in Meter | DTC Storage Method |
|---|---|---|---|---|---|---|
| U0100/82 | Lost Communication with ECM/PCM | When TCM cannot receive communication signals from ECM for 1 second or more.
(1 trip detection logic) |
Both conditions are met:
·
The ignition switch is turned ON. ·
The power source voltage of the TCM is 10.5 V or more. |
Turn the ignition switch to ON and wait at least 1 second. | MIL illuminates. | DTC is stored until it is cleared using the intelligent tester or Techstream. |
This ECU uses the CAN communication system for DTC communication.
TABLE OF ON-BOARD DTC DISPLAYED IN COMBINATION METER ASSEMBLY
DTCs can be displayed on the multi information display in the combination meter assembly.
DTCs are displayed when connecting terminals 13 (ECUT) and 4 (E) of DLC3 with the ignition switch ON.
Combination Meter Assembly / Intelligent Tester or Techstream Display "-"
| DTC | Detection Item | DTC Detection Condition | DTC Detection Pre-condition | DTC Check Procedure | Warning Indication in Meter | DTC Storage Method |
|---|---|---|---|---|---|---|
| 0041 | Lost AT-shift Communication with ECT | The combination meter assembly does not receive data from the ECM for 1 second or more. | Both conditions are met:
·
The ignition switch is turned ON. ·
The power source voltage of the combination meter assembly is 10.5 V or more. |
Turn the ignition switch to ON and wait at least 1 second. | - | DTCs are not stored. |
| 0042 | Lost proper AT-shift Communication with ECT | The combination meter assembly does not receive proper data from the ECM for 1 second or more. | Both conditions are met:
·
The ignition switch is turned ON. ·
The power source voltage of the combination meter assembly is 10.5 V or more. |
Turn the ignition switch to ON and wait at least 1 second. | - | DTCs are not stored. |
| 0043 | Lost proper EEPROM Communication with MET itself | The combination meter assembly does not control EEPROM module. | Both conditions are met:
·
The ignition switch is turned ON. ·
The power source voltage of the combination meter assembly is 10.5 V or more. |
Turn the ignition switch to ON. | - | DTCs are not stored. |
| 0051 | Lost Communication with ECM | The combination meter assembly does not receive data from the ECM for 1 second or more. | Both conditions are met:
·
The ignition switch is turned ON. ·
The power source voltage of the combination meter assembly is 10.5 V or more. |
Turn the ignition switch to ON and wait at least 1 second. | - | DTCs are not stored. |
| 0052 | Lost Communication with Transmission control ECU | The combination meter assembly does not receive data from the TCM for 1 second or more. | Both conditions are met:
·
The ignition switch is turned ON. ·
The power source voltage of the combination meter assembly is 10.5 V or more. |
Turn the ignition switch to ON and wait at least 1 second. | - | DTCs are not stored. |
DTC COMBINATION TABLE (OPEN IN CAN BRANCH OF V BUS, PAST COMMUNICATION ERROR)
Regarding the past communication error of ECUs connected to the V bus (in this case, normal was displayed when performing the CAN 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 CAN bus check using the intelligent tester or Techstream because the ECU connected to the CAN branch does not respond (the ECU 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 on the CAN bus may be output, or a message indicating a communication error may be displayed on the intelligent tester or Techstream screen. In this case, check the resistance of the CAN bus (steps 5 to 7) first.
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.
○: Set
X: Not set or may be set according to the malfunctioning part when one line of a CAN branch is open.
DATA SENDING/RECEIVING TABLE
Data sending/receiving table
Refer to the Service Bulletin for Data Sending/Receiving Table.
Details of relevant Data List items (Selected system: EFI)
Using the intelligent tester or Techstream to read the Data List allows the values or states of switches, sensors, actuators and other items to be read without removing any parts. This non-intrusive inspection can be very useful because intermittent conditions or signals may be discovered before parts or wiring is disturbed. Reading the Data List information early in troubleshooting is one way to save diagnostic time.
In the table below, the values listed under "Normal Condition" are reference values. Do not depend solely on these reference values when deciding whether a part is faulty or not.
Normal Condition: If no conditions are specifically stated for "idling", the shift lever should be in N or P, the A/C volume switch should be off and all accessory switches should be off.
Warm up the engine.
Turn the A/C volume switch off.
Turn the ignition switch off.
Connect the intelligent tester or Techstream to the DLC3.
Turn the ignition switch to ON.
Turn the intelligent tester or Techstream on.
Enter the following menus: Powertrain / EFI / Data List.
| Tester Display |
|---|
| MAP |
| Engine Speed |
| Vehicle Speed |
| Coolant Temp |
| Throttle Position |
| Injection Volume |
| Stop Light Signal |
| Shift Signal |
According to the display on the intelligent tester or Techstream, read the Data List.
| Tester Display | Measurement Item | Range | Normal Condition | Diagnostic Note |
|---|---|---|---|---|
| MAP | Manifold absolute pressure | Min.: 0 kPa, Max.: 255 kPa | 70 to 104 kPa: Ignition switch ON (engine not started)
20 to 40 kPa: Idling |
If value approximately 0 kPa: ·
PIM circuit short If value 120 kPa or more ·
VCPM circuit open or short ·
PIM circuit open ·
E2PM circuit open |
| Engine Speed | Engine speed | Min.: 0 rpm, Max.: 16383.75 rpm | 700 to 800 rpm (neutral position): Idling | - |
| Vehicle Speed | Vehicle speed | Min.: 0 km/h (0 mph), Max.: 255 km/h (158 mph) | Actual vehicle speed | - |
| Coolant Temp | Coolant temperature | Min.: -40°C (-40°F), Max.: 215°C (419°F) | 80 to 102°C (176 to 215°F): After warming up engine | ·
If value -40°C (-40°F) or less: sensor circuit open ·
If value 130°C (266°F) or more: sensor circuit shorted |
| Throttle Position | Absolute throttle valve opening angle | Min.: 0 %, Max.: 100 % | ·
0 to 15 %: Throttle fully closed ·
70 to 100 %: Throttle fully open |
Read value with ignition switch ON (Do not start engine) |
| Injection Volume | Injection volume of No. 1 cylinder (cumulative value for 10 times) | Min.: 0 ml, Max.: 2.047 ml | 0.003 to 0.015 ml: Idling | Read value with A/C OFF and shift lever N position |
| Stop Light Signal | Stop light switch | OFF / ON | ON: When operating brake | - |
| Shift Signal | Shift position signal received from TCM | N / R / 1st / 2nd / 3rd / 4th | - | - |
Details of relevant Data List items (Selected system: ECT)
Using the intelligent tester or Techstream to read the Data List allows the values or states of switches, sensors, actuators and other items to be read without removing any parts. This non-intrusive inspection can be very useful because intermittent conditions or signals may be discovered before parts or wiring is disturbed. Reading the Data List information early in troubleshooting is one way to save diagnostic time.
In the table below, the values listed under "Normal Condition" are reference values. Do not depend solely on these reference values when deciding whether a part is faulty or not.
Normal Condition: If no conditions are specifically stated for "idling", the shift lever should be in N or P, the A/C volume switch should be off and all accessory switches should be off.
Connect the intelligent tester or Techstream to the DLC3.
Turn the ignition switch to ON.
Turn the intelligent tester or Techstream on.
Enter the following menus: Body Electrical / ECT / Data List.
| Tester Display |
|---|
| Engine Speed |
| Vehicle Speed |
| Throttle POS |
| Stop Light Switch |
| A/T Oil Temperature 1 |
| Shift SW Status(P) |
| Shift SW Status(R) |
| Shift SW Status(N) |
| Shift SW Status(D) |
| Shift SW Status(3) |
| Shift SW Status(2) |
| Shift SW Status(L) |
| Shift Status |
Check the value(s) by referring to the table below.
| Tester Display | Measurement Item | Range | Normal Condition | Diagnostic Note |
|---|---|---|---|---|
| Engine Speed | Engine Speed | Min.: 0 rpm, Max.:10200rpm | 700 to 800 rpm: idle after engine warmed-up | - |
| Vehicle Speed | Vehicle speed | Min.: 0 km/h (0 mph), Max.: 255 km/h (158 mph) | Same as speedometer indication | - |
| Throttle POS | Throttle position (TP) | Min.: 0 %, Max.: 100 % | ·
0 to 5 %: Throttle fully closed ·
95 to 100 %: Throttle fully open |
- |
| Stop Light Switch | Stop light SW status | OFF / ON | ·
Brake pedal is depressed: ON ·
Brake pedal is released: OFF |
- |
| A/T Oil Temperature 1 | ATF Temperature sensor value | Min.: -50°C (-58°F), Max.: 205°C (401°F) | ·
After Stall Test; Approximately 80 to 100°C (176 to 212°F) ·
Equal to ambient temperature when the engine is cold |
If the value is "-50°C (-58°F)" or "205°C (401°F)", ATF temperature sensor circuit is opened or shorted. |
| Shift SW Status(P) | PNP SW status | OFF / ON | ·
ON: Shift lever in P ·
OFF: Shift lever not in P |
When the shift lever position displayed on the intelligent tester or Techstream differs from the actual position, adjustment of the PNP switch, transmission control switch or the shift cable may be incorrect. (*1) |
| Shift SW Status(R) | PNP SW status | OFF / ON | ·
ON: Shift lever in R ·
OFF: Shift lever not in R |
When the shift lever position displayed on the intelligent tester or Techstream differs from the actual position, adjustment of the PNP switch, transmission control switch or the shift cable may be incorrect. (*1) |
| Shift SW Status(N) | PNP SW status | OFF / ON | ·
ON: Shift lever in N ·
OFF: Shift lever not in N |
When the shift lever position displayed on the intelligent tester or Techstream differs from the actual position, adjustment of the PNP switch, transmission control switch or the shift cable may be incorrect. (*1) |
| Shift SW Status(D) | PNP SW status | OFF / ON | ·
ON: Shift lever in D ·
OFF: Shift lever not in D |
When the shift lever position displayed on the intelligent tester or Techstream differs from the actual position, adjustment of the PNP switch, transmission control switch or the shift cable may be incorrect. (*1) |
| Shift SW Status(3) | PNP SW status | OFF / ON | ·
ON: Shift lever in 3 ·
OFF: Shift lever not in 3 |
When the shift lever position displayed on the intelligent tester or Techstream differs from the actual position, adjustment of the PNP switch, transmission control switch or the shift cable may be incorrect. (*1) |
| Shift SW Status(2) | PNP SW status | OFF / ON | ·
ON: Shift lever in 2 ·
OFF: Shift lever not in 2 |
When the shift lever position displayed on the intelligent tester or Techstream differs from the actual position, adjustment of the PNP switch, transmission control switch or the shift cable may be incorrect. (*1) |
| Shift SW Status(L) | PNP SW status | OFF / ON | ·
ON: Shift lever in L ·
ON: Shift lever in L |
When the shift lever position displayed on the intelligent tester or Techstream differs from the actual position, adjustment of the PNP switch, transmission control switch or the shift cable may be incorrect. (*1) |
| Shift Status | TCM gearshift command | N / R / 1st / 2nd / 3rd / 4th | Shift lever in; ·
N: Neutral ·
R: Reverse ·
L: 1st ·
2: 1st or 2nd ·
3: 1st, 2nd or 3rd ·
D : 1st, 2nd, 3rd or 4th |
- |
*1: When the failure still occurs even after adjusting these parts (See page Drivetrain>A4Q AUTOMATIC TRANSMISSION / TRANSAXLE>AUTOMATIC TRANSMISSION SYSTEM>P0705).
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 CAN Bus Check and DTCs checked using the intelligent tester or Techstream, check the resistance of the CAN bus using an ohmmeter first (See page Power Source / Network>NETWORKING>CAN COMMUNICATION SYSTEM>DIAGNOSIS SYSTEM). 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 bus line, an open in a CAN branch line, or a short between a CAN line (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 present 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 each 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 line (CANH)
An abnormal waveform is output from an ECU with an open in one of its CAN branch lines. 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 line is disconnected.
Open in a CAN branch line (CANL)
An abnormal waveform is output from an ECU with an open in one of its CAN branch lines. 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 line is disconnected.
Open in a CAN main bus line (CANH)
Waveforms of ECUs or sensors that are nearer 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 bus line 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 connectors from the CAN junction connector 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 connectors from the CAN junction connector 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.