DTC Combination Table [10/2017 - 09/2018]

HINT: 

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.

1. If multiple ECUs store a communication DTC for a particular ECU, a communication stop of the ECU is suspected.
   Fig 1: DTC Reference Chart

   Courtesy of © TOYOTA, LICENSE AGREEMENT TMS1002

   *a

   Items to be Checked

   -

   -

   NOTE:

   • 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 Techstream may differ depending on the ECU that stores the DTC. (Regarding output DTCs, refer to the DTC Table by ECU.)

     Refer to DIAGNOSIS SYSTEM [10/2017 - 09/2018]

   HINT: 

   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.

2. If almost all of the communication DTCs of an ECU are stored, a communication stop of the ECU is suspected.
   Fig 2: DTC Reference Chart

   Courtesy of © TOYOTA, LICENSE AGREEMENT TMS1002

   *a

   Items to be Checked

   -

   -

   NOTE:

   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.

   HINT: 

   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.

3. 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.

Fig 3: DTCs Stored In The Gateway Function Equipped ECU

Courtesy of © TOYOTA, LICENSE AGREEMENT TMS1002

HINT: 

• As gateway function equipped ECUs (non-bus 2 monitor ECU) monitor signals from all ECUs that are connected to non-bus 2, 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.

• 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

HINT: 

• 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 line and a communication stop that is currently occurring, the malfunctioning part can be confirmed easily by performing the CAN bus check using the Techstream because the ECU or sensor connected to the CAN branch line 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 short to ground or +B 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 Techstream screen. In this case, check the resistance of the CAN bus (steps 10 to 18) first.

  Refer to HOW TO PROCEED WITH TROUBLESHOOTING [10/2016 - 09/2018]

• If an open occurs in just one of the lines of a CAN bus line(s), 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.
• ◦: DTC is output.
• -: DTC is not output.
• If an open occurs in just one of the lines of a CAN bus line, DTCs which are not related to malfunctioning parts may be output.
• *1: DTC U0073 may be stored when communication is lost.
• *2: DTC U1000 may be stored when communication is lost.
• *3: Gateway function equipped ECUs relay signals between the ECUs connected to the different buses.

HINT: 

• 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 line and a communication stop that is currently occurring, the malfunctioning part can be confirmed easily by performing the CAN bus check using the Techstream because the ECU or sensor connected to the CAN branch line 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 short to ground or +B 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 Techstream screen. In this case, check the resistance of the CAN bus (steps 10 to 18) first.

  Refer to HOW TO PROCEED WITH TROUBLESHOOTING [10/2016 - 09/2018]

• If an open occurs in just one of the lines of a CAN bus line(s), 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.
• ◦: DTC is output.
• -: DTC is not output.
• If an open occurs in just one of the lines of a CAN bus line, DTCs which are not related to malfunctioning parts may be output.
• *1: DTC U0073 may be stored when communication is lost.
• *2: DTC U1000 may be stored when communication is lost.
• *3: Gateway function equipped ECUs relay signals between the ECUs connected to the different buses.

HINT: 

• 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 line and a communication stop that is currently occurring, the malfunctioning part can be confirmed easily by performing the CAN bus check using the Techstream because the ECU or sensor connected to the CAN branch line 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 short to ground or +B 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 Techstream screen. In this case, check the resistance of the CAN bus (steps 10 to 18) first.

  Refer to HOW TO PROCEED WITH TROUBLESHOOTING [10/2016 - 09/2018]

• If an open occurs in just one of the lines of a CAN bus line(s), 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.
• ◦: DTC is output.
• -: DTC is not output.
• If an open occurs in just one of the lines of a CAN bus line, DTCs which are not related to malfunctioning parts may be output.
• *1: DTC U0073 may be stored when communication is lost.
• *2: DTC U1000 may be stored when communication is lost.
• *3: Gateway function equipped ECUs relay signals between the ECUs connected to the different buses.