Honda CRV/Odyssey 1995-2000 Repair Information

Diagnosis and Testing

Print

Diagnosis of a driveability and/or emissions problems requires attention to detail and following the diagnostic procedures in the correct order. Resist the temptation to perform any repairs before performing the preliminary diagnostic steps. In many cases this will shorten diagnostic time and often cure the problem without electronic testing.

The proper troubleshooting procedure for these vehicles is as follows:

VISUAL/PHYSICAL INSPECTION



This is possibly the most critical step of diagnosis and should be performed immediately after retrieving any codes. A detailed examination of connectors, wiring and vacuum hoses can often lead to a repair without further diagnosis. Performance of this step relies on the skill of the technician performing it; a careful inspector will check the undersides of hoses as well as the integrity of hard-to-reach hoses blocked by the air cleaner or other component. Wiring should be checked carefully for any sign of strain, burning, crimping, or terminal pullout from a connector. Checking connectors at components or in harnesses is required; usually, pushing them together will reveal a loose fit.

INTERMITTENTS



If a fault occurs intermittently, such as a loose connector pin breaking contact as the vehicle hits a bump, the PCM will note the fault as it occurs and may energize the dash-warning lamp. If the problem self-corrects, as with the terminal pin again making contact, the dash lamp will extinguish after 10 seconds but a code will remain stored in the computer control module's memory.

When an unexpected code appears during diagnostics, it may have been set during an intermittent failure that self-corrected itself. These codes are still useful in diagnosis and should not be discounted.

CIRCUIT/COMPONENT REPAIR



The fault codes and the scan tool data will lead to diagnosis and checking of a particular circuit. It is important to note that the fault code indicates a fault or loss of signal in an ECM/PCM-controlled system, not necessarily in the specific component. A sensor's wire may be shorted, corroded or disconnected, and though the actual sensor is operating properly, the signal received by the ECM/PCM is beyond specification.

Refer to the appropriate Diagnostic Code chart to determine the code's meaning. The component may then be tested following the appropriate component test procedures found in this section. If the component is OK, check the wiring for shorts or an open circuit. Sometimes a second opinion is valuable from an experienced driveability technician.

If a code indicates the ECM/PCM to be faulty and the ECM/PCM is replaced, but does not correct the problem, one of the following may be the reason:



There is a problem with the ECM/PCM terminal connections: The terminals may have to be removed from the connector in order to check them properly.
 
The ECM/PCM or PROM is not correct for the application: The incorrect ECM/PCM or PROM may cause a malfunction and may or may not set a code.
 
The problem is intermittent: This means that the problem is not present at the time the system is being checked. In this case, make a careful physical inspection of all portions of the system involved.
 
Shorted solenoid, relay coils or harness: Solenoids and relays are turned on and off by the ECM/PCM using internal electronic switches called drivers. Each driver is part of a group of four called Quad-Drivers. A shorted solenoid, relay coil or harness could cause an PCM to fail, and a replacement PCM to fail when it is installed.
 
The Programmable Read Only Memory (PROM) may be faulty: Although the PROM rarely fails, it operates as part of the ECM/PCM. Therefore, it could be the cause of the problem. Substitute a known good PROM.
 
The replacement ECM/PCM may be faulty: After the ECM/PCM is replaced, the system should be rechecked for proper operation. If the diagnostic code again indicates the ECM/PCM is the problem, substitute a known good PCM. Although this is a very rare condition, it could happen.
 

 
label.common.footer.alt.autozoneLogo