2015-2020 Toyota Tundra OEM Service & Repair Manual

Last Modified: 9-16-2014 6.6 F Doc ID: RM000000UZ20F9X Model Year: 2015 Model: Tundra Prod Date Range: [08/2014 - ] Title: INTRODUCTION: HOW TO TROUBLESHOOT ECU CONTROLLED SYSTEMS: GENERAL INFORMATION; 2015 MY Tundra [08/2014 - ] GENERAL INFORMATION A large number of ECU controlled systems are used in the TOYOTA TUNDRA. In general, ECU controlled systems are considered to be very intricate, requiring a high level of technical knowledge to troubleshoot. However, most problem checking procedures only involve inspecting the ECU controlled system's circuits one by one. An adequate understanding of the system and a basic knowledge of electricity is enough to perform effective troubleshooting, accurate diagnoses and necessary repairs. 1. TROUBLESHOOTING PROCEDURES The troubleshooting procedures consist of diagnosis procedures for when a DTC is stored and diagnosis procedures for when no DTC is stored. The basic idea is explained in the following table. PROCEDURE TYPE DETAILS TROUBLESHOOTING METHOD DTC Based Diagnosis The diagnosis procedure is based on the DTC that is stored. The malfunctioning part is identified based on the DTC detection conditions using a process of elimination. The possible trouble areas are eliminated one-by-one by use of the Techstream and inspection of related parts. Symptom Based Diagnosis (No DTCs stored) The diagnosis procedure is based on problem symptoms. The malfunctioning part is identified based on the problem symptoms using a process of elimination. The possible trouble areas are eliminated one-by-one by use of the Techstream and inspection of related parts. Vehicle systems are complex and use many ECUs that are difficult to inspect independently. Therefore, a process of elimination is used, where components that can be inspected individually are inspected, and if no problems are found in these components, the related ECU is identified as the problem and replaced. It is extremely important to ask the customer about the environment and the conditions present when the problem occurred (Customer Problem Analysis). This makes it possible to simulate the conditions and confirm the symptom. If the symptom cannot be confirmed or the DTC does not recur, the malfunctioning part may not be identified using the troubleshooting procedure, and the ECU for the related system may be replaced even though it is not defective. If this happens, the original problem will not be solved. In order to prevent endless expansion of troubleshooting procedures, the troubleshooting procedures are written with the assumption that multiple malfunctions do not occur simultaneously for a single problem symptom. To identify the malfunctioning part, troubleshooting procedures narrow down the target by separating components, ECUs and wire harnesses during the inspection. If the wire harness is identified as the cause of the problem, it is necessary to inspect not only the connections to components and ECUs but also all of the wire harness connectors between the component and the ECU. DIAGNOSTIC TESTER INTRODUCTION: HOW TO TROUBLESHOOT ECU CONTROLLE... https://techinfo.toyota.com/t3Portal/document/rm/RM26B0U/xhtml/RM... 1 of 3 2/18/2015 11:11 AM

2. DESCRIPTION System data and the Diagnostic Trouble Codes (DTCs) can be read from the Data Link Connector 3 (DLC3) of the vehicle. When the system seems to be malfunctioning, use the Techstream* to check for a malfunction and perform repairs. HINT: *: Techstream is the name for the diagnostic tester in North America. 3. DATA LINK CONNECTOR 3 (DLC3) (a) The vehicle's ECU uses the ISO 15765-4 communication protocol. The terminal arrangement of the DLC3 complies with SAE J1962 and matches the ISO 15765-4 format. TERMINAL NO. (SYMBOLS) TERMINAL DESCRIPTION CONDITION SPECIFIED CONDITION 7 (SIL) - 5 (SG) Bus "+" line During transmission Pulse generation 4 (CG) - Body ground Chassis ground Always Below 1 Ω 5 (SG) - Body ground Signal ground Always Below 1 Ω 16 (BAT) - Body ground Battery positive Always 11 to 14 V 6 (CANH) - 14 (CANL) CAN bus line Ignition switch OFF* 54 to 69 Ω 6 (CANH) - 4 (CG) HIGH-level CAN bus line Ignition switch OFF* 200 Ω or higher 14 (CANL) - 4 (CG) LOW-level CAN bus line Ignition switch OFF* 200 Ω or higher 6 (CANH) - 16 (BAT) HIGH-level CAN bus line Ignition switch OFF* 6 kΩ or higher 14 (CANL) - 16 (BAT) LOW-level CAN bus line Ignition switch OFF* 6 kΩ or higher NOTICE: *: Before measuring the resistance, leave the vehicle as is for at least 1 minute and do not operate the ignition switch, any other switches, or the doors. If the result is not as specified, the DLC3 may have a malfunction. Repair or replace the harness and connector. (b) Connect the cable of the Techstream to the DLC3, turn the ignition switch ON and attempt to use the tester. If the display indicates that a communication error has occurred, there is a problem either with the vehicle or with the tester. HINT: If communication is normal when the tester is connected to another vehicle, inspect the DLC3 of the INTRODUCTION: HOW TO TROUBLESHOOT ECU CONTROLLE... https://techinfo.toyota.com/t3Portal/document/rm/RM26B0U/xhtml/RM... 2 of 3 2/18/2015 11:11 AM

original vehicle. If communication is still not possible when the tester is connected to another vehicle, the problem may be in the tester itself. Consult the Service Department listed in the tester's instruction manual. INTRODUCTION: HOW TO TROUBLESHOOT ECU CONTROLLE... https://techinfo.toyota.com/t3Portal/document/rm/RM26B0U/xhtml/RM... 3 of 3 2/18/2015 11:11 AM

NEXT NEXT NEXT Last Modified: 9-16-2014 6.6 F Doc ID: RM000002V5U01FX Model Year: 2015 Model: Tundra Prod Date Range: [08/2014 - ] Title: INTRODUCTION: HOW TO TROUBLESHOOT ECU CONTROLLED SYSTEMS: HOW TO PROCEED WITH TROUBLESHOOTING; 2015 MY Tundra [08/2014 - ] HOW TO PROCEED WITH TROUBLESHOOTING 1. OPERATION FLOW HINT: Perform troubleshooting in accordance with the procedures below. The following is an outline of basic troubleshooting procedures. Confirm the troubleshooting procedures for the circuit you are working on before beginning troubleshooting. 1. VEHICLE BROUGHT TO WORKSHOP 2. CUSTOMER PROBLEM ANALYSIS (a) Ask the customer about the conditions and environment when the problem occurred. 3. INSPECT BATTERY VOLTAGE Standard voltage: 11 to 14 V If the voltage is below 11 V, recharge or replace the battery before proceeding. 4. SYMPTOM CONFIRMATION AND DTC (INCLUDING FREEZE FRAME DATA) CHECK (a) Visually check the wire harnesses, connectors and fuses for open and short circuits. (b) Warm up the engine to the normal operating temperature. INTRODUCTION: HOW TO TROUBLESHOOT ECU CONTROLLE... https://techinfo.toyota.com/t3Portal/document/rm/RM26B0U/xhtml/RM... 1 of 10 2/18/2015 11:11 AM

A NEXT NEXT (c) Confirm the problem symptoms and conditions, and check for DTCs. Result RESULT PROCEED TO DTC is output A DTC is not output B B Go to step 6 5. DTC CHART (a) Check the results obtained in the DTC check. Then find the output DTC in the DTC chart. Look at the "Trouble Area" column for a list of potentially malfunctioning circuits and / or parts. NEXT Go to step 7 6. PROBLEM SYMPTOMS TABLE (a) Check the results obtained in the symptom confirmation. Then find the problem symptoms in the problem symptoms table. Look at the "Suspected Area" column for a list of potentially malfunctioning circuits and / or parts. 7. CIRCUIT INSPECTION OR PARTS INSPECTION (a) Confirm the malfunctioning circuit or part. 8. ADJUST, REPAIR OR REPLACE INTRODUCTION: HOW TO TROUBLESHOOT ECU CONTROLLE... https://techinfo.toyota.com/t3Portal/document/rm/RM26B0U/xhtml/RM... 2 of 10 2/18/2015 11:11 AM

NEXT (a) Adjust, repair or replace the malfunctioning circuit or parts. 9. CONFIRMATION TEST (a) After the adjustment, repairs or replacement, confirm that the malfunction no longer exists. If the malfunction does not reoccur, perform a confirmation test under the same conditions and in the same environment as when the malfunction occurred the first time. NEXT END 2. CUSTOMER PROBLEM ANALYSIS HINT: In 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 problem and the conditions at the time the malfunction occurred. Gather as much information as possible for reference. Past problems that seem unrelated may also help in some cases. The following 5 questions are important points in the problem analysis: What Vehicle model, system name When Date, time, occurrence frequency Where Road conditions Under what conditions? Running conditions, driving conditions, weather conditions How did it happen? Problem symptoms 3. SYMPTOM CONFIRMATION AND DIAGNOSTIC TROUBLE CODE HINT: The diagnostic system in the TOYOTA TUNDRA has various functions. The first function is the Diagnostic Trouble Code (DTC) check. A DTC is a code stored in the ECU memory whenever a malfunction in the signal circuits to the ECU occurs. In a DTC check, a previous malfunction's DTC can be checked by a technician during troubleshooting. Another function is the Input Signal Check, which checks if the signals from various switches are sent to the ECU correctly. By using these functions, the problem areas can be narrowed down and troubleshooting is more effective. Diagnostic functions are incorporated in the following systems in the TOYOTA TUNDRA. SYSTEM DTC CHECK (NORMAL MODE) DTC CHECK (CHECK MODE) FREEZE FRAME DATA SENSOR CHECK / TEST MODE (INPUT SIGNAL CHECK) DATA LIST ACTIVE TEST CUSTOMIZE PARAMETER INTRODUCTION: HOW TO TROUBLESHOOT ECU CONTROLLE... https://techinfo.toyota.com/t3Portal/document/rm/RM26B0U/xhtml/RM... 3 of 10 2/18/2015 11:11 AM

SYSTEM DTC CHECK (NORMAL MODE) DTC CHECK (CHECK MODE) FREEZE FRAME DATA SENSOR CHECK / TEST MODE (INPUT SIGNAL CHECK) DATA LIST ACTIVE TEST CUSTOMIZE PARAMETER SFI System (for 1UR-FE) ○ ○ ○ - ○ ○ - SFI System (for 3UR-FE) ○ ○ ○ - ○ ○ - SFI System (for 3UR-FBE) ○ ○ ○ - ○ ○ - Automatic Transmission System (for A760E) ○ ○ ○ - ○ ○ - Automatic Transmission System (for A760F) ○ ○ ○ - ○ ○ - Automatic Transmission System (for AB60E) ○ ○ ○ - ○ ○ - Automatic Transmission System (for AB60F) ○ ○ ○ - ○ ○ - Tire Pressure Warning System ○ - - ○ ○ ○ - Touch Select 2-4 and High-low System ○ - - - - - - Vehicle Stability Control System ○ - ○ ○ ○ ○ - Trailer Brake Control System ○ - - - ○ ○ - Power Tilt and Power Telescopic Steering Column System ○ - ○ - ○ ○ ○ Air Conditioning System (for Automatic Air Conditioning System) ○ - - - ○ ○ ○ Air Conditioning System (for Manual Air Conditioning System) ○ - - - ○ ○ - Airbag System ○ ○ - - ○ - - Occupant Classification System ○ - - - ○ - - Seat Belt Warning System - - - - ○ ○ - Theft Deterrent System - - - - ○ ○ ○ Engine Immobiliser System ○ - - - ○ ○ - Cruise Control System ○ - - - ○ ○ - INTRODUCTION: HOW TO TROUBLESHOOT ECU CONTROLLE... https://techinfo.toyota.com/t3Portal/document/rm/RM26B0U/xhtml/RM... 4 of 10 2/18/2015 11:11 AM

SYSTEM DTC CHECK (NORMAL MODE) DTC CHECK (CHECK MODE) FREEZE FRAME DATA SENSOR CHECK / TEST MODE (INPUT SIGNAL CHECK) DATA LIST ACTIVE TEST CUSTOMIZE PARAMETER Lighting System ○ - - - ○ ○ ○ Wiper and Washer System - - - - ○ - - Power Door Lock Control System - - - - ○ ○ ○ Wireless Door Lock Control System ○ - - - ○ ○ ○ Key Reminder Warning System - - - - ○ - - Meter / Gauge System ○ - - - ○ ○ ○ Audio and Visual System ○ - ○ - ○ - - Navigation System ○ - ○ - ○ - - Blind Spot Monitor System ○ ○ ○ - ○ - - Rear View Monitor System (for Radio and Display Type) ○ - - - - - - Rear View Monitor System (for Navigation Receiver Type) ○ - - - - - - Power Window Control System (w/ Jam Protection Function) ○ - - - ○ ○ ○ Power Window Control System (w/o Jam Protection Function) - - - - ○ ○ - Windshield Deicer System - - - - - ○ - Window Defogger System - - - - - ○ - Power Seat Control System (w/ Memory) ○ - - - ○ ○ ○ Sliding Roof System ○ - - - ○ ○ ○ CAN Communication System ○ - - - - - - LIN Communication System ○ - - - ○ - - In the DTC check, it is very important to determine whether the problem indicated by the DTC is either: 1) still occurring; or 2) occurred in the past but has since returned to normal. In addition, the DTC should be compared to the problem symptom to see if they are related. For this reason, DTCs should be checked before and after confirmation of symptoms (i.e., whether or not problem symptoms exist) to determine current system conditions, as shown in the flowchart below. Never skip the DTC check. Failing to check DTCs may, depending on the case, result in unnecessary troubleshooting for systems operating normally or lead to repairs not related to the problem. Follow the procedures listed in the flowchart in the correct order. INTRODUCTION: HOW TO TROUBLESHOOT ECU CONTROLLE... https://techinfo.toyota.com/t3Portal/document/rm/RM26B0U/xhtml/RM... 5 of 10 2/18/2015 11:11 AM

NEXT NEXT A NEXT The following flowchart shows how to proceed with troubleshooting using the DTC check. Directions from the flowchart will indicate how to proceed either to DTC troubleshooting or to the troubleshooting of each problem symptom. 1. DTC CHECK 2. MAKE A NOTE OF DTCS DISPLAYED AND THEN CLEAR MEMORY 3. SYMPTOM CONFIRMATION Result RESULT PROCEED TO No symptoms exist A Symptoms exist B B Go to step 5 4. SIMULATION TEST USING SYMPTOM SIMULATION METHODS 5. DTC CHECK Result INTRODUCTION: HOW TO TROUBLESHOOT ECU CONTROLLE... https://techinfo.toyota.com/t3Portal/document/rm/RM26B0U/xhtml/RM... 6 of 10 2/18/2015 11:11 AM

A RESULT PROCEED TO DTC is not output A DTC is output B B TROUBLESHOOTING OF PROBLEM INDICATED BY DTC 6. SYMPTOM CONFIRMATION Result RESULT PROCEED TO Symptoms exist A No symptoms exist B If a DTC was displayed in the initial DTC check, the problem may have occurred in a wire harness or connector in that circuit in the past. Check the wire harness and connectors. B SYSTEM NORMAL A TROUBLESHOOTING OF EACH PROBLEM SYMPTOM The problem is still occurring in a place other than the diagnostic circuit (the DTC displayed first is either for a past problem or a secondary problem). 4. SYMPTOM SIMULATION HINT: The most difficult case in troubleshooting is when no problem symptoms occur. In such a case, a thorough problem analysis must be carried out. A simulation of the same or similar conditions and environment in which the problem occurred in the customer's vehicle should be carried out. No matter how much skill or experience a technician has, troubleshooting without confirming the problem symptoms will lead to important repairs being overlooked and mistakes or delays. For example: With a problem that only occurs when the engine is cold or as a result of vibration caused by the road during driving, the problem can never be determined if the symptoms are being checked on a stationary vehicle or on a vehicle with a warmed-up engine. Vibration, heat or water penetration (moisture) is difficult to reproduce. The symptom simulation tests below are effective substitutes for the conditions and can be applied on a stationary vehicle. Important points in the symptom simulation test: In the symptom simulation test, the problem symptoms as well as the problem area or parts must be confirmed. First, narrow down the possible problem circuits according to the symptoms. Then, connect the INTRODUCTION: HOW TO TROUBLESHOOT ECU CONTROLLE... https://techinfo.toyota.com/t3Portal/document/rm/RM26B0U/xhtml/RM... 7 of 10 2/18/2015 11:11 AM

2015-2020 Toyota Tundra OEM Service & Repair Manual

You're Reading a Preview

Recently Viewed