Diagnosis System

1. When troubleshooting OBD II vehicles, the only difference from the usual troubleshooting procedure is that you need to connect an OBD II scan tool complying with SAE J1987 or a hand-held tester to the vehicle, and read off various data output from the vehicle's ECM.
2. OBD II regulations require that the vehicle's onboard computer illuminate the Malfunction Indicator Lamp (MIL) on the instrument panel when the computer detects a malfunction in the computer itself or in the drive system components which affect the vehicle emissions. In addition to the MIL illuminating when a malfunction is detected, the applicable DTCs prescribed by SAE J2012 are recorded in the ECM memory (see DIAGNOSTIC TROUBLE CODE CHART ).

   If the malfunction does not occur in 3 consecutive trips, the MIL goes off but the DTCs remain in the ECM memory.

3. To check the DTCs, connect the OBD II scan tool or hand-held tester to the DLC3 of the vehicle. The OBD II scan tool or hand-held tester also enables you to erase the DTCs and check freeze frame data and various forms of engine data (For instruction book).
4. The DTCs include SAE controlled codes and Manufacturer controlled codes. SAE controlled codes must be set as prescribed by the SAE, while Manufacturer controlled codes can be set freely by a manufacturer within the prescribed limits (see the DTC chart on DIAGNOSTIC TROUBLE CODE CHART ).
5. The diagnosis system operates in the normal mode during the normal vehicle use, and also has a check mode for technicians to simulate malfunction symptoms and perform troubleshooting. Most DTCs use 2 trip detection logic (*) to prevent erroneous detection. By switching the ECM to the check mode when troubleshooting, the technician can cause the MIL to illuminate for a malfunction that is only detected once or momentarily (hand-held tester).
6. *2 trip detection logic:

   When a malfunction is first detected, the malfunction is temporarily stored in the ECM memory. If the same malfunction is detected again during the second test drive, this second detection causes the MIL to illuminate.

   Fig 1: Malfunction Indicator Lamp

   Courtesy of © TOYOTA, LICENSE AGREEMENT TMS1002

The vehicle's ECM uses ISO 9141-2 for communication. The terminal arrangement of DLC3 complies with SAE J1962 and matches the ISO 9141-2 format.

Fig 2: Inspecting DLC3

Courtesy of © TOYOTA, LICENSE AGREEMENT TMS1002

Fig 3: Tester Specification

Courtesy of © TOYOTA, LICENSE AGREEMENT TMS1002

HINT:

If your display shows UNABLE TO CONNECT TO VEHICLE when you have connected the cable of the OBD II scan tool or hand-held tester to the DLC3, turned the ignition switch to the ON position and operated the scan tool, there is a problem on the vehicle side or tool side.

• If the communication is normal when the tool is connected to another vehicle, inspect the DLC3 on the original vehicle.
• If the communication is still impossible when the tool is connected to another vehicle, the problem is probably in the tool itself, so consult the Service Department listed in the tool's instruction manual.

Battery Voltage: 11 to 14 V 

If voltage is below 11 V, recharge the battery before proceeding.

1. The MIL comes on when the ignition switch is turned to the ON position and the engine is not running.

   HINT:

   If the MIL does not light up, troubleshoot the combination meter.

2. When the engine is started, the MIL should go off. If the lamp remains on, it means that the diagnosis system has detected a malfunction or abnormality in the system.