How To Proceed With Troubleshooting [12/2017 - 09/2018]: Procedure

HINT: 

• If the engine switch can be turned on (IG) (the power source mode can be changed to on [IG]) when the vehicle is brought in for repair, check for DTCs and check the illumination condition of the indicators in the combination meter assembly and the basic operation of the vehicle (such as steering operation) promptly.
• Do not turn the engine switch off until the inspection of the vehicle is finished, as some fail-safe functions are canceled when the engine switch is turned off.
• If the engine switch cannot be turned on (IG) (the power source mode cannot be changed to on [IG]) when the vehicle is brought in, measure the voltage of the battery. If the voltage is below 11 V, recharge or replace the battery before performing troubleshooting.
• If the engine switch cannot be turned on (IG) (the power source mode cannot be changed to on [IG]) even though the battery voltage is normal, repair this malfunction before performing troubleshooting.

  Refer to PROBLEM SYMPTOMS TABLE [12/2017 - 10/2022]

• Even when the engine switch cannot be turned on (IG) (the power source mode cannot be changed to on [IG]), data from ECUs that can communicate with the Techstream when the engine switch is off can be read by connecting the Techstream to the vehicle and repeatedly pressing a courtesy switch of a door on and off at intervals of 1.5 seconds or less until communication between the Techstream and the vehicle starts.

Result

Result: 

NEXT 

See step  2

HINT: 

• When troubleshooting, confirm that the problem symptoms have been accurately identified. Preconceptions should be discarded in order to make an accurate judgment. To clearly understand what the problem symptoms are, it is extremely important to ask the customer about the problems and the conditions at the time the malfunction occurred.
• Ask the customer if the vehicle is/was equipped with additional devices such as a theft deterrent device or monitor. (If equipped, explain to the customer that the additional devices will be removed before performing troubleshooting as the malfunction cannot be checked properly.)
• Examples of points to be confirmed are shown below.

1. It is useful to confirm the symptoms and the conditions in which the vehicle was operating at the time when a malfunction occurred. This helps to narrow down the malfunctioning part.

   HINT: 

   • What was affected (system, part or meter warning indicators)
   • What happened (details of the malfunction)
   • When (occurrence date and time, frequency and if it recurs or not)
   • Under what kind of situation did the problem occur (driving and operating condition at the occurrence and weather)
   • Road type or condition (city, suburb, paved road, unpaved road, highway, etc.)
   • Conditions when vehicle returned to normal (engine switch was turned off, etc.)
   POINTS TO BE CONFIRMED
   
   

   Symptom

   Air conditioning - Whether the air conditioning system operated - Whether the blower fan operated - The air conditioning functions cannot be operated at all Electric power steering - Normal - A little heavier than usual - There was no assist Drive monitor display - Whether the update of multi-information display items stopped - Whether the numeric part of the drivable distance was displayed - Not displayed at all Eco navigation (eco drive) display - Whether the average fuel consumption graph is updated every minute - Whether the updated section average fuel consumption graph is displayed - Whether the distance-to-empty is displayed on the section average fuel consumption graph display - Not displayed at all Interior lights - Whether the interior light illumination changes when the door is opened or closed - Whether the interior lights turned off when the engine switch is turned on (IG) - Not illuminated at all Wireless door lock function and entry function - Whether the lock/unlock function operated - Whether the entry warning function operated - Whether the illumination was turned on when the key was brought into a smart detection area 4WD/AWD operation - Normal - Slip detected when starting off Memory call - Normal - Memory write error - Memory read error - Whether the auto return or auto away control is performed Operation of other systems of concern

   Meter warning lights

   Illumination of warning lights and the order in which they illuminated - Master - Check engine (MIL) - Brake - ABS - Slip - EPS - SRS - Others Meter display - Speedometer - Tachometer - Engine coolant temperature gauge Content displayed on the multi-information display - Whether the odometer to TRIP meter has stopped - Whether the value of the average fuel economy is displayed on the multi-information display - Whether a warning message is displayed on the multi-information display

   Result

   Proceed to
   NEXT

Result: 

NEXT 

See step  3

1. Measure the battery voltage.

   Standard voltage

   11 to 14 V

   If the voltage is below 11 V, recharge or replace the battery before proceeding to the next step.

   HINT: 

   • It can be determined if the battery is completely drained by operating the horn.
   • If the engine switch cannot be turned on (IG), measure the voltage of the battery. If it is below 11 V, perform inspection after replacing or recharging the battery.
   • If the engine switch cannot be turned on (IG) even though the battery voltage is normal, repair this malfunction before performing troubleshooting.

     Refer to PROBLEM SYMPTOMS TABLE [12/2017 - 10/2022]

   Result

   Proceed to
   OK
   NG

Result: 

NG 

CHARGE OR REPLACE BATTERY 

Result: 

OK 

See step  4

1. Measure the voltage according to the value(s) in the table below.

   Standard Voltage

   Tester Connection	Condition	Specified Condition
   P12-16 (BAT) - Body ground	Always	11 to 14 V

   Result

   Proceed to
   OK
   NG

Result: 

NG 

REPAIR OR REPLACE HARNESS OR CONNECTOR 

Result: 

OK 

See step  5

1. Measure the resistance according to the value(s) in the table below.

   Standard Resistance

   Tester Connection	Condition	Specified Condition
   P12-4 (CG) - Body ground	Always	Below 1 Ω

   Result

   Result	Proceed to
   OK (w/ Pre-collision System [for Stereo Camera Type])	A
   OK (w/ Pre-collision System [for Mono Camera Type])	B
   NG	C

Result: 

B 

See step  11

Result: 

C 

REPAIR OR REPLACE HARNESS OR CONNECTOR 

Result: 

A 

See step  6

HINT: 

Read the Techstream operator's manual before use.

Refer to GENERAL INFORMATION [12/2017 - 09/2018]

1. Connect the Techstream to the DLC3.
2. Turn the engine switch on (IG).
3. Turn the Techstream on.
4. Check that the Techstream and ECUs can communicate with the engine switch on (IG).

   HINT: 

   • ECUs and sensors are not displayed on the "Communication Bus Check" screen when the Techstream cannot communicate with the vehicle.
   • If communication between the Techstream and ECUs is not possible, either the Techstream or vehicle has a malfunction.
   • If communication between the Techstream and ECUs is still not possible even when the Techstream is connected to another vehicle, the Techstream has a malfunction. Perform the self-tests described in the Techstream operators manual. (The Techstream may be malfunctioning or its battery may be discharged.)

   Result

   Result	Proceed to
   OK (Communication between the Techstream and the vehicle is possible.)	A
   OK (Communication between the Techstream and the vehicle is not possible but communication is possible when connected to another vehicle.)	B
   NG (Communication is not possible between the Techstream and the vehicle, nor between the Techstream and another vehicle.)	C

Result: 

B 

See step  19

Result: 

C 

REFER TO TECHSTREAM OPERATOR'S MANUAL 

Result: 

A 

See step  7

1. Using the Techstream, perform Health Check to read current and history DTCs and record them.
   NOTE:

   • CAN communication DTCs are output when there is an open or short in any of the communication lines. Any problems with the power source of a corresponding ECU or sensor, or problems in the ECU or sensor itself also cause these DTCs to be output.
   • If a CAN communication line connector is disconnected with the engine switch on (IG or ACC), the ECUs of the corresponding system and related systems store a DTC.

   HINT: 

   If an open occurs in just one of the wires of a CAN branch line, 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.

2. Read the freeze frame data using the Techstream and record it.

   Result

   Result	Proceed to
   OK (Only CAN communication DTCs are output.)	A
   NG (DTCs other than CAN communication DTCs are also output.)	B

Result: 

B 

GO TO DIAGNOSTIC TROUBLE CODE CHART OF RELATED SYSTEM 

Result: 

A 

See step  8

1. Proceed to the "Communication Malfunction Check" screen from the "Communication Bus Check" screen.
2. Record all the DTCs stored for ECUs and sensors.
3. Check if the stored DTCs are listed in the Diagnostic Trouble Code Chart of the CAN Communication System.

   HINT: 

   • For details on how to change to and from the "Communication Malfunction Check" screen, refer to Communication Bus Check (Communication Malfunction Check).

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

   • For the definition of central bus, sub bus and local bus, refer to Definition of Terms.

     Refer to SYSTEM DESCRIPTION [12/2017 - 10/2023] 

   • A sub bus monitoring ECU is a gateway function equipped ECU that monitors ECUs and sensors on its respective bus.
   • When the vehicle is equipped with a sub bus, refer to System Diagram to confirm the sub bus monitoring ECU.

     Refer to SYSTEM DIAGRAM [12/2017 - 09/2018] 

   • Sub bus monitoring ECUs monitor all ECUs and sensors connected to their respective sub bus and can accurately detect when an ECU or sensor stops communicating.
   • When CAN communication DTCs are stored but all ECUs and sensors connected to the CAN communication system are displayed as normal on the "Communication Bus Check" screen of the Techstream, a past malfunction is suspected.
   • When a sub bus monitoring ECU detects a communication error in the network, or an ECU or sensor has stopped communicating, it stores a DTC.
   • When CAN communication DTCs are stored in an ECU connected to the central bus and in a sub bus monitoring ECU, inspect the corresponding sub bus and perform repairs if necessary before inspecting the central bus.
   • A malfunctioning local bus will not affect the central bus or sub buses.
   • When CAN communication DTCs are stored for a local bus, inspect related systems and perform repairs if necessary.

   Result

   Result	Proceed to
   The stored DTCs are not listed in the Diagnostic Trouble Code Chart for CAN Communication System.	A
   The stored DTCs are listed in the Diagnostic Trouble Code Chart for CAN Communication System.	B

Result: 

B 

See step  12

Result: 

A 

See step  9

1. Based on the vehicle equipment and specifications, confirm the systems that use CAN communication.

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

2. Select "CAN Bus Check" from the screen on the Techstream.
3. Observe the screen for approximately 2 minutes to check the ECUs and sensors displayed on the screen.
4. Check for ECUs or sensors with a background color that indicates that they are currently not communicating.
   NOTE:

   • A sub bus monitoring ECU outputs DTCs for its respective ECUs and sensors. Identify the malfunctioning ECU or sensor using the output DTCs.
   • ECUs or sensors that are not installed to the vehicle will not be displayed. Do not mistake these for ECUs or sensors that are not communicating.
   • When using the combo box, it may be possible to select a sub bus from the drop down list that does not have any connected ECUs or sensors. This is not a malfunction and occurs when there is no optional device connected to a sub bus which is monitored by a sub bus monitoring ECU (gateway function equipped ECU).

   HINT: 

   • For details on how to read the "Communication Bus Check" screen, refer to Description of "Communication Bus Check" screen.

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

   • If there is an ECU or sensor whose connection status changes intermittently while checking the "Communication Bus Check" screen, there may be an open circuit in one of the wires of a branch line of an ECU or sensor in the bus. If an open occurs in one of the wires of a CAN branch line, it may interfere with the communication of other ECUs or sensors resulting in an incorrect state being displayed.
   • The central gateway ECU (network gateway ECU) displays the connection status of ECUs and sensors connected to the central bus on the Techstream.
   • Sub bus monitoring ECUs display the connection status of ECUs and sensors connected to their respective sub bus on the Techstream.
   • If a CAN commutation DTC is output from an ECU connected to the sub bus, refer to the corresponding diagnostic procedure.

     Refer to DIAGNOSTIC TROUBLE CODE CHART [12/2017 - 09/2018]

   Result

   Result	Proceed to
   An ECU or sensor is not communicating (An ECU or sensor has a red or red and yellow background)	A
   All ECU and sensors are communicating (All ECUs or sensors have a white or white and yellow background)	B

Result: 

B 

See step  16

Result: 

A 

See step  10

1. Confirm the suspected cause of the problem symptoms by referring to How to Use "Communication Bus Check" Screen in Inspection and using the result of Bus Inspection (Check Connected ECUs and Sensors Using Techstream).

   HINT: 

   • For details on how to inspect buses, refer to How to Use "Communication Bus Check" Screen in Inspection.

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

   • If there are multiple ECUs or sensors that are not communicating, check for blown fuses before proceeding with troubleshooting.
   • If there are multiple ECUs or sensors that are not communicating, after confirming that there are no power supply malfunctions, check for an open or short in CAN bus lines (CANH or CANL) or a short to ground or +B in CAN bus lines.
   • If there is an ECU or sensor that is not communicating, there may be an open circuit in one of the wires of its branch line. In this situation, the malfunctioning wire harness may affect noise immunity and interfere with the communication of other ECUs or sensors on the same bus. This may affect the validity of the displayed data.

   Result

   Result	Proceed to
   The problem symptom is found in the table for Problem Symptom Patterns other than Patterns A or B.	A
   The problem symptom is not found in Problem Symptoms Table in How to Use "Communication Bus Check" Screen in Inspection. The problem symptom is found in the table for Problem Symptom Patterns A or B.	B

Result: 

A 

GO TO PROBLEM SYMPTOMS TABLE. Refer to  PROBLEM SYMPTOMS TABLE [12/2017 - 10/2020]  

Result: 

B 

See step  13

1. Disconnect the cable from the negative (-) battery terminal.
2. Disconnect the G68 driving support ECU assembly connector.
3. Measure the resistance according to the value(s) in the table below.

   Standard Resistance

   Tester Connection	Condition	Specified Condition
   G68-12 (CA3H) - G68-13 (CA3L)	Cable disconnected from negative (-) battery terminal	54 to 69 Ω

4. Reconnect the cable to the negative (-) battery terminal.

   Result

   Proceed to
   OK
   NG

Result: 

OK 

See step  6

Result: 

NG 

See step  14

1. Based on the vehicle equipment and specifications, confirm the systems that use CAN communication.

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

2. Select "CAN Bus Check" from the screen on the Techstream.
3. Observe the screen for approximately 2 minutes to check the ECUs and sensors displayed on the screen.
4. Check for ECUs or sensors with a background color that indicates that they are currently not communicating.
   NOTE:

   • A sub bus monitoring ECU outputs DTCs for its respective ECUs and sensors. Identify the malfunctioning ECU or sensor using the output DTCs.
   • ECUs or sensors that are not installed to the vehicle will not be displayed. Do not mistake these for ECUs or sensors that are not communicating.
   • When using the combo box, it may be possible to select a sub bus from the drop down list that does not have any connected ECUs or sensors. This is not a malfunction and occurs when there is no optional device connected to a sub bus which is monitored by a sub bus monitoring ECU (gateway function equipped ECU).

   HINT: 

   • For details on how to read the "Communication Bus Check" screen, refer to Description of "Communication Bus Check" screen.

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

   • If there is an ECU or sensor whose connection status changes intermittently while checking the "Communication Bus Check" screen, there may be an open circuit in one of the wires of a branch line of an ECU or sensor in the bus. If an open occurs in one of the wires of a CAN branch line, it may interfere with the communication of other ECUs or sensors resulting in an incorrect state being displayed.
   • The central gateway ECU (network gateway ECU) displays the connection status of ECUs and sensors connected to the central bus on the Techstream.
   • Sub bus monitoring ECUs display the connection status of ECUs and sensors connected to their respective sub bus on the Techstream.
   • If a CAN commutation DTC is output from an ECU connected to the sub bus, refer to the corresponding diagnostic procedure.

     Refer to DIAGNOSTIC TROUBLE CODE CHART [12/2017 - 09/2018]

   Result

   Result	Proceed to
   An ECU or sensor is not communicating (An ECU or sensor has a red or red and yellow background)	A
   All ECU and sensors are communicating (All ECUs or sensors have a white or white and yellow background)	B

Result: 

A 

See step  10

Result: 

B 

See step  15

1. Disconnect the cable from the negative (-) battery terminal.
2. Measure the resistance of any suspected buses that were specified by the result of Confirm Problem Symptoms (Check Connected ECUs and Sensors Using Techstream).

   HINT: 

   • For details on the terminal arrangement of the central gateway ECU (network gateway ECU), refer to Terminals of ECU.

     Refer to TERMINALS OF ECU [12/2017 - 09/2018]

   • If the CAN bus main line is normal and there is an ECU or sensor whose connection status changes intermittently while checking the "Communication Bus Check" screen, there may be an open circuit in one of the wires of a branch line of an ECU or sensor in the bus. If an open occurs in one of the wires of a CAN branch line, it may interfere with the communication of other ECUs or sensors resulting in an incorrect state being displayed.

     Performing the bus inspection again may help in determining the suspected area.

   Standard Resistance

   Tester Connection	Condition	Specified Condition	Result
   CANH - CANL of a suspected bus	Cable disconnected from negative (-) battery terminal	54 to 69 Ω	Below 54 Ω: Short circuit between bus lines
   			70 Ω or higher: Open circuit in main bus lines
   CANH - body ground of a suspected bus	Cable disconnected from negative (-) battery terminal	200 Ω or higher	Below 200 Ω: CANH short to ground
   CANL - body ground of a suspected bus	Cable disconnected from negative (-) battery terminal	200 Ω or higher	Below 200 Ω: CANL short to ground
   CANH - +B of a suspected bus	Cable disconnected from negative (-) battery terminal	6 kΩ or higher	Below 6 kΩ: CANH +B short
   CANL - +B of a suspected bus	Cable disconnected from negative (-) battery terminal	6 kΩ or higher	Below 6 kΩ: CANL +B short

   Result

   Result	Proceed to
   OK (CAN bus main lines are normal)	Go to Inspection for Open Circuit in a Branch Line
   NG (There is an open or short in a CAN bus main line of a suspected bus)	Go to Respective Inspection

Result: 

Go to Inspection for Open Circuit in a Branch Line 

GO TO PROBLEM SYMPTOMS TABLE. Refer to  PROBLEM SYMPTOMS TABLE [12/2017 - 10/2020]  

Result: 

Go to Respective Inspection 

GO TO PROBLEM SYMPTOMS TABLE. Refer to  PROBLEM SYMPTOMS TABLE [12/2017 - 10/2020]  

Result: 

See step  6

1. Disconnect the cable from the negative (-) battery terminal.
2. Measure the resistance according to the value(s) in the table below.

   Standard Resistance

   Tester Connection	Condition	Specified Condition	Result
   L133-3 (CANP) - L133-2 (CANN)	Cable disconnected from negative (-) battery terminal	54 to 69 Ω	Below 54 Ω: Short circuit between bus lines
   			70 Ω or higher: Open circuit in main bus lines
   L133-3 (CANP) - G20-4 (CG)	Cable disconnected from negative (-) battery terminal	200 Ω or higher	Below 200 Ω: CANH short to ground
   L133-2 (CANN) - G20-4 (CG)	Cable disconnected from negative (-) battery terminal	200 Ω or higher	Below 200 Ω: CANL short to ground
   L133-3 (CANP) - G20-16 (BAT)	Cable disconnected from negative (-) battery terminal	6 kΩ or higher	Below 6 kΩ: CANH +B short
   L133-2 (CANN) - G20-16 (BAT)	Cable disconnected from negative (-) battery terminal	6 kΩ or higher	Below 6 kΩ: CANL +B short

   Courtesy of © TOYOTA, LICENSE AGREEMENT TMS1002

   *a	Component with harness connected (No. 8 CAN Junction Connector)

   Result

   Result	Proceed to
   OK (CAN bus main lines are normal)	Go to Inspection for Open Circuit in a Branch Line
   NG (There is an open or short in a CAN bus main line of a suspected bus)	Go to Respective Inspection

Result: 

Go to Inspection for Open Circuit in a Branch Line 

GO TO DIAGNOSTIC TROUBLE CODE CHART. Refer to  DIAGNOSTIC TROUBLE CODE CHART [12/2017 - 09/2018] 

Result: 

Go to Respective Inspection 

GO TO PROBLEM SYMPTOMS TABLE. Refer to  PROBLEM SYMPTOMS TABLE [12/2017 - 10/2020]  

1. Using the Techstream, display the "Communication Bus Check (Detail)" screen.

   HINT: 

   For details on how to inspect buses using the "Communication Bus Check (Detail)" screen, refer to Description of "Communication Bus Check" Screen.

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

2. Check the display for ECUs or sensors which have communication error history.
   NOTE:

   • ECUs or sensors that are not installed to the vehicle will not be displayed. Do not mistake these for ECUs or sensors that are not communicating.
   • When using the combo box, it may be possible to select a sub bus from the drop down list that does not have any connected ECUs or sensors. This is not a malfunction and occurs when there is no optional device connected to a sub bus which is monitored by a sub bus monitoring ECU (gateway function equipped ECU).

   HINT: 

   • The communication history of ECUs or sensors which have communication error history can be displayed on the "Communication Bus Check (Detail)" screen.
   • Lost Communication Time and Lost Communication Trip are only displayed for the central bus.
   • Lost Communication Time and Lost Communication Trip are not displayed for sub buses.
3. Check for ECUs or sensors with a red background.

   Result

   Result	Proceed to
   An ECU or sensor has communication stop history. (The background color of an ECU or sensor is red.)	A
   No ECUs or sensors have communication stop history. (The background color of an ECU or sensor is not red.)	B

Result: 

B 

See step  18

Result: 

A 

See step  17

1. Confirm the suspected cause of the problem symptoms by referring to How to Use "Communication Bus Check (Detail)" Screen in Inspection and using the result of Bus Inspection (Detail) (Check Connected ECUs and Sensors Using Techstream).
   NOTE:

   • ECUs or sensors that are not installed to the vehicle will not be displayed. Do not mistake these for ECUs or sensors that are not communicating.
   • When using the combo box, it may be possible to select a sub bus from the drop down list that does not have any connected ECUs or sensors. This is not a malfunction and occurs when there is no optional device connected to a sub bus which is monitored by a sub bus monitoring ECU (gateway function equipped ECU).

   HINT: 

   • For details on "Communication Bus Check (Detail)" screen, refer to How to Use "Communication Bus Check (Detail)" Screen in Inspection.

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

   • Lost Communication Time and Lost Communication Trip are only displayed for the central bus.
   • Lost Communication Time and Lost Communication Trip are not displayed for sub buses.
   • If an ECU or sensor has communication stop history, the background color of the ECU or sensor will be red.
   • If more than one ECU or sensor has a background color of red, check the values of Lost Communication Trip and Lost Communication Time. Communication error of an ECU or sensor with the value of Lost Communication Trip closest to the Current Trip and the largest value of Lost Communication Time is suspected.

   Result

   Result	Proceed to
   Suspected cause of problem symptom is found.	A
   Suspected cause of problem symptom is not found.	B

Result: 

A 

GO TO PROBLEM SYMPTOMS TABLE. Refer to  PROBLEM SYMPTOMS TABLE [12/2017 - 10/2020]  

Result: 

B 

See step  18

1. Determine the ECUs or sensors that were not communicating based on the combination of DTCs output from each ECU.

   Refer to DTC COMBINATION TABLE [12/2017 - 09/2018]

   Result

   Result	Proceed to
   Combination of DTCs is not in DTC Combination Table	A
   Combination of DTCs is in DTC Combination Table	B

Result: 

A 

INSPECT FOR INTERMITTENT PROBLEMS. Refer to  HOW TO PROCEED WITH TROUBLESHOOTING [12/2017 - 09/2018] 

Result: 

B 

INSPECT PROBLEMS ACCORDING TO DTC COMBINATION TABLE 

HINT: 

Operate the engine switch, any other switches or door triggers related ECU and sensor communication on the CAN. This communication will cause the resistance value to change.

1. Disconnect the cable from the negative (-) battery terminal.
2. Measure the resistance according to the value(s) in the table below.

   Courtesy of © TOYOTA, LICENSE AGREEMENT TMS1002

   *a	Front view of DLC3

   Standard Resistance

   Tester Connection	Condition	Specified Condition
   P12-6 (CANH) - P12-14 (CANL)	Cable disconnected from negative (-) battery terminal	54 to 69 Ω
   P12-6 (CANH) - P12-4 (CG)	Cable disconnected from negative (-) battery terminal	200 Ω or higher
   P12-14 (CANL) - P12-4 (CG)
   P12-6 (CANH) - P12-16 (BAT)	Cable disconnected from negative (-) battery terminal	6 kΩ or higher
   P12-14 (CANL) - P12-16 (BAT)

   HINT: 

   If the resistance between CANH and CANL is not as specified, a connector may have been loose or disconnected during inspection. If a connector is loose or disconnected, connect it and perform the inspection again.

   Result

   Proceed to
   OK
   NG

Result: 

NG 

REPAIR OR REPLACE HARNESS OR CONNECTOR (DLC3 - CENTRAL GATEWAY ECU [NETWORK GATEWAY ECU]) 

Result: 

OK 

See step  20

1. Disconnect the central gateway ECU (network gateway ECU) connector.
2. Measure the resistance according to the value(s) in the table below.

   Standard Resistance

   Tester Connection	Condition	Specified Condition
   P59-10 (GND) - Body ground	Cable disconnected from negative (-) battery terminal	Below 1 Ω

   Result

   Result
   OK
   NG

Result: 

NG 

REPAIR OR REPLACE HARNESS OR CONNECTOR (GND TERMINAL) 

Result: 

OK 

See step  21

1. Reconnect the cable to the negative (-) battery terminal.
2. Measure the voltage according to the value(s) in the table below.

   Standard Voltage

   Tester Connection	Condition	Specified Condition
   P59-1 (BATT) - Body ground	Always	11 to 14 V
   P59-2 (ACC) - Body ground	Engine switch on (ACC)	11 to 14 V
   	Engine switch off	Below 1 V
   P59-11 (IG1) - Body ground	Engine switch on (IG)	11 to 14 V
   	Engine switch off	Below 1 V
   P59-12 (IG2) - Body ground	Engine switch on (IG)	11 to 14 V
   	Engine switch off	Below 1 V

   Result

   Proceed to
   OK
   NG

Result: 

OK 

REPLACE CENTRAL GATEWAY ECU (NETWORK GATEWAY ECU). Refer to  REMOVAL [12/2017 - 10/2023] 

Result: 

NG 

REPAIR OR REPLACE HARNESS OR CONNECTOR (POWER SOURCE CIRCUIT)