Honda CRV/Odyssey 1995-2000 Repair Information

Reading Codes

Print

OBD-I SYSTEMS1995 Odyssey Models



Listings of the trouble codes for the various engine control systems covered in this guide are located in this section. Remember that a code only points to the faulty circuit NOT necessarily to a faulty component. Loose, damaged or corroded connections may contribute to a fault code on a circuit when the sensor or component is operating properly. Be sure that the components are faulty before replacing them, especially the expensive ones.

To activate the blink code system proceed as follows:

  1. Turn the ignition switch OFF .
  2.  
  3. Locate the two wire Service Check Connector (SCS) located behind the passenger's side center console.
  4.  
  5. Install the SCS Service Connector tool no. 07PAZ-0010100 or equivalent into the connector, or carefully back probe the connector using a suitable small paper clip.
  6.  
  7. Turn the ignition switch to the ON position and observe the Malfunction Indicator Lamp (MIL) or Check Engine Light. If the warning light stays on, there are no stored faults. If the warning light begins to blink, for each fault that is stored, a blink code will be present.
  8.  

After making repairs, clear the trouble codes and operate the vehicle to see if it will reset, indicating further problems.

It's a good idea to have a pencil and paper handy when reading a blink code to note the long and short flashes of the warning lightSee Figure 1

Click image to see an enlarged view

Fig. Fig. 1: The ECM is capable of storing multiple blink codes. Using the codes can be useful for diagnosis purposes

OBD-II SYSTEMS



On all 1996-00 models, an On Board Diagnostic version II (OBD-II) compliant Data Scan Tool (DST) must be used to retrieve the Diagnostic Trouble Codes (DTCs). Follow the DST manufacturer's instructions on how to connect the scan tool to the vehicle and how to retrieve the DTCs.

See Figure 2

Click image to see an enlarged view

Fig. Fig. 2: The Diagnostic Trouble Codes (DTCs) are easily interpreted when using an OBD-II compliant scan tool

 
label.common.footer.alt.autozoneLogo