Caution / Notice / Hint

HINT: 

• If any other DTCs are output, perform troubleshooting for those DTCs first.
• Make sure to reproduce the conditions present when the malfunction occurred.
• Using the GTS, read the Data List to confirm the engine operating conditions. This information can be useful when troubleshooting.
• The vehicle condition when the problem symptoms occurred can be determined using the Vehicle Control History.
• As the Vehicle Control History data may be overwritten whenever the trigger conditions are met, make sure to save the Vehicle Control History data before performing any inspections.
• If the problem symptoms do not recur, attempt to reproduce the symptoms and conditions when the malfunction occurred based on the result of the customer problem analysis and Vehicle Control History. Place the priority on confirming the symptoms.
• When performing inspections, jiggle the relevant wire harnesses and connectors in an attempt to reproduce malfunctions that do not always occur.
• The suspected cause of the problem symptoms can be determined using the codes, items, and Freeze Frame Data within the Vehicle Control History.
• When confirming the Freeze Frame Data, be sure to check all multi Freeze Frame Data.
• When confirming the Freeze Frame Data, if there are multiple items related to the cause of the malfunction, perform troubleshooting for all related items.
• If the malfunction is currently occurring, use the Data List to confirm the current vehicle condition. By using the Data List, more detailed vehicle information can be confirmed than by using the Vehicle Control History Freeze Frame Data by itself.
• As Vehicle Control History may be stored when performing an Active Test, learning, etc., make sure to clear the Vehicle Control History before returning the vehicle to the customer.