Neon, 2000 - 2005

Changes In Diagnostic Routines

Print

In some cases, a new Engine Control system may be similar to an earlier system, but it can have more indepth control of vehicle emissions, input and output devices and it may include a diagnostic "monitor" embedded in the engine controller designed to run a thorough set of emission control system tests.

OBD I Diagnostic Flowchart



The OBD I Diagnostic Flowchart on this page can be used to find the cause of problems related to Engine Control system trouble codes or driveability symptoms detected on OBD I systems. It includes a step-by-step procedure to use to repair these systems. To compare this flowchart with the one used on OBD II systems, refer to the next page.

The steps in this flow chart should be followed as described below (from top to bottom).

Click image to see an enlarged view

Fig.



Do the Pre-Computer Checks.
 
Check for any trouble codes stored in memory.
 
Read the trouble codes - If trouble codes are set, record them and then clear the codes.
 
Start the vehicle and see if the trouble code(s) reset. If they do, then use the correct trouble code repair chart to make the repair.
 
If the codes do not reset, than the problem may be intermittent in nature. In this case, refer to the test steps used to find the cause of an intermittent fault (wiggle test).
 
In no trouble codes are found at the initial check, then determine if a driveability symptom is present. If so, then refer to the approriate driveability symptom repair chart to make the repair. If the first symptom chart does not isolate the cause of the condition, then go on to another driveability symptom and follow that procedure to conclusion.
 
If the problem is intermittent in nature, then refer to the special intermittent tests. Follow all available intermittent tests to determine the cause of this type of fault (usually an electrical connection problem).
 

OBD II System Diagnostics



The diagnostic approach used in OBD II systems is more complex than that of the one for OBD I systems. This complexity will effect how you approach diagnosing the vehicle. On an OBD II system, the onboard diagnostics will identify sensor faults (i.e., open, shorted or grounded circuits) as well as those that lose calibration. Another new test that arrived with OBD II is the rationality test (a test that checks whether the value for one input makes rational sense when compared against other sensor input values). The changes plus the use of OBD II Monitors have dramatically changed OBD II diagnostics.

The use of a repeatable test routine can help you quickly get to the root cause of a customer complaint, save diagnostic time and result in a higher percentage of properly repaired vehicles. You can use this Diagnostic Flow Chart to keep on track as you diagnose an Engine Control problem or a base engine fault on vehicles with OBD II.

Click image to see an enlarged view

Fig.

Flow Chart Steps

Here are some of the steps included in the Diagnostic Routine:



Review the repair order and verify the customer complaint as described
 
Perform a Visual Inspection of underhood or engine related items
 
If the engine will not start, refer to No Start Tests
 
If codes are set, refer to the trouble code list, select a code and use the repair chart
 
If no codes are set, and a symptom is present, refer to the Symptom List
 
Check for any related technical service bulletins (for both Code and No Code Faults)
 
If the problem is intermittent in nature, refer to the special Intermittent Tests
 

 
label.common.footer.alt.autozoneLogo