Equinox 2005-2007, Torrent 2006-07

Introduction

Print

Diagnostic Tools & Circuit Testing



Circuit Testing Tools

You should know when to use and when NOT to use a 12-volt test light during diagnosis of electronic controls (Do NOT use this tester unless specifically instructed to do so by a test procedure). Instead of using a 12-volt test light, you should use a DVOM or Lab Scope with a breakout box whenever a diagnostic procedure calls for a measurement at a PCM connector or component wiring harness.

Electricity & Electrical Circuits

You should understand basic electricity and know the meaning of voltage (volts), current (amps), and resistance (ohms). You should understand what happens in an electrical circuit when it is open or shorted, and you should be able to identify an open circuit or shorted circuit using a DVOM. You should also be able to read and understand automotive electrical wiring diagrams and schematics.

Electronic Controls

You should have a basic knowledge of electronic controls when performing test procedures to keep from making an incorrect diagnosis or damaging components. Do NOT attempt to diagnose an electronic control problem without this basic knowledge!

Hand Tools & Meter Operation

To effectively use this or any diagnostic information, you should have a solid understanding of how to operate required tools and test equipment.

Click image to see an enlarged view

Fig.

Malfunction Indicator Lamp

Emission regulations require that a Malfunction Indicator Lamp (MIL) be illuminated when an emissions related fault is detected and that a Diagnostic Trouble Code be stored in the vehicle controller (PCM) memory.

When the MIL is illuminated, it is an indication of a problem within one of the electronic components or circuits. When the scan tool is attached to the Data Link Connector (DLC) in the vehicle, it can access the DTCs. In some situations, without the use of a scan tool, the MIL can be activated to flash a series of long and short flashes, which correspond to the numbering of the DTC.

OBD II guidelines define when an emissions-related fault will cause the MIL to activate and set a Diagnostic Trouble Code (DTC). There are some DTCs that will not cause the MIL to illuminate. OBD II guidelines determine how quickly the onboard diagnostics must be able to identify a fault, set the trouble code in memory and activate the MIL (lamp).

Scan Tools

Domestic vehicle manufacturers designed their computers to have an accessible data line where a diagnostic tester could retrieve data on sensors and the status of operation for components.

These testers became known in the automotive repair industry as -Scan Tools- because they scanned the data on the computers and provided information for the technician.

The Scan Tool is your basic tool link into the on-board electronic control system of the vehicle. Scan Tools are equipped with, or have separate software cards, for each OEM needed to be diagnosed. In this case, always secure a scan tool that has the latest OEM-specific diagnostic software included.

Ford specifies the use of an -NGS- scan tool with its diagnostic processes. However, there are aftermarket scan tools, when equipped with the right software that can provide proper diagnosis as well.

Effective Diagnostics



Getting Started

If you are reasonably certain that the problem is related to a particular electronic control system, the first step is to check for any stored trouble codes in that controller.

On vehicles with more than one vehicle controller (i.e., PCM, BCM, MIC, TCM, etc.), if you are unsure whether the problem is Powertrain related, start by checking for codes in the other controllers to determine if the problem is related to another vehicle system.

If there are no codes set, and you are certain which Powertrain subsystem has a problem, you can start by checking one of the subsystems. The subsystems include the Charging, Cooling, Fuel, Ignition and Speed Control systems.

If a wiring problem is found during testing, you will need to refer to wiring diagrams in the appropriate information resource. Using a wiring schematic can help you determine:



Wiring circuits, circuit numbers, and wire colors
 
Electrical component connector and component relationships within a circuit
 
Power, ground, and splice locations within a circuit
 
Related circuits connected into the circuit you are reviewing
 

Once you decide how to repair the vehicle, in addition to performing the repair, it is a good idea to clear any trouble codes that were set and to verify they do not reset.

To verify a repair, you should confirm that the Check Engine Light is operational and goes out after the 4-second key-on bulb check. Then, you need to duplicate the conditions present when the customer complaint occurred or when a trouble code set; these are the actual code conditions that caused a code to set. The individual code conditions and possible causes are included under Diagnostic Trouble Codes. You can use this information to find out how to drive a vehicle for problem verification.

How To Use This Section



The General Motors (GM) OBD II Section contains information grouped into the three main categories described below:



Vehicle Coverage - This information identifies GM vehicles equipped with OBD II Systems by year, body and engine. Each vehicle has its own Vehicle Identification Number (VIN). This information can be used to look up OBD II P0xxx and P1xxx type codes and their individual descriptions. GM began phase-in of the OBD II System in 1995 on 115,000 vehicles spread across several models. All GM vehicles were equipped with OBD II Systems from 1996-2002.
 
PCM Diagnostics - This information includes an explanation of how the OBD II system incorporates changes to the PCM diagnostics that include new emission control monitoring and control of the Malfunction Indicator Lamp. The articles in this section explain how certain test Conditions: or enable criteria must be met before an OBD II Monitor will run a diagnostic test. An explanation of how each OBD II Monitor runs a particular test is also included in this section.
 
Reference Information - This information includes OBD II Code Descriptions in a two-column table format. The codes are split into two categories: a P0xxx series (SAE defined) and a P1xxx series (OEM defined). The first column in each row contains code numbers and trip designations that identify the type of monitor test (CCM, EGR, etc.) and whether the code is a One Trip (1T) or Two-Trip (2T) type of code. The next column contains the trouble code conditions. Special notes are shown in italics at the bottom of the condition explanation.
 

To use this information, first look up the year, make, model, and in some cases, the specific engine application. Then read the code conditions containing the enable criteria that explain why a code set. Note: Trouble code repair charts are not included in this data.

Example of Trouble Code Information

DTCTrouble Code Title, Conditions & Possible Causes
P0131 1T O2S, MIL Yes 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2004, 2005 C/K Series Truck, G Series Van, S/T Series Pickup and Blazer, Envoy Escalade & TrailBlazer 4.8L VIN V, 5.3L VIN P, 5.3L VIN T, 5.3L VIN Z, 6.0L VIN N, 6.0L VIN U, 8.1L VIN G Transmissions AllHO2S-11 (Bank 1 Sensor 1) Circuit Low Input Conditions DTCP0101, P0102, P0103, P0106, P0107, P0108, P0112, P0113, P0116, P0117, P0118, P0120, P0121, P0122, P0123, P0169, P0178, P0179, P0200, P0220, P0300, P0442, P0446, P0452, P0453, P0455, P0496, P1125, P1258, P1514, P1515, P1516, P1518, P2108 and P2135 not set, engine started, engine running in closed loop, system voltage from 10-18v, Fuel Alcohol content less than 90%, fuel level over 10%, TP angle from 3-70% more than the idle value, then during the Lean Test period, the PCM detected the HO2S signal was less than 200 mv for 165 seconds or with engine runtime over 30 seconds, and during the Power Enrichment test period, the PCM detected the HO2S signal was less than 400 mv for 10 seconds. Possible Causes l Engine misfire condition present (look for P0300 series codes) l Fuel system too lean (possible low fuel pressure, water in fuel) l HO2S signal circuit is shorted to the sensor or chassis ground l HO2S is damaged (i.e., cracked) or air reference hole clogged l PCM has failed
P0131 2T O2S, MIL Yes 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2004, 2005 Deville, Eldorado & Seville 4.6L VIN 9, 4.6L VIN Y Transmissions A/THO2S-11 (Bank 1 Sensor 1) Circuit Low Input Conditions DTCP0101-P0103, P0106-P0108, P0112-P0113, P0116-P0118, P0121-P0123, P0125, P0128, P0200, P0300, P0410-P0446, P0452-P0453, P1258, P1415-P1416 and P1441 not set, AIR, Catalyst and EGR Flow tests off, system voltage 8-18v, no injectors disabled, TP angle from 3-25%, A/F ratio at 14.5-14.81, engine running in closed loop for 3 seconds, and the PCM detected the HO2S signal was less than 75 mv for 5 seconds while in closed loop, or it was less than 575 mv for 8 seconds while operating in Power Enrichment mode. Possible Causes l Air leaks in the exhaust system, intake manifold, vacuum lines l Engine misfire condition present (look for P0300 series codes) l Fuel system too lean (possible low fuel pressure, water in fuel) l HO2S signal circuit is shorted to the sensor or chassis ground l HO2S is damaged (i.e., cracked) or air reference hole clogged l PCM has failed

Notes & Cautions



Before servicing any vehicle, please be sure to read all of the following precautions, which deal with personal safety, prevention of component damage, and important points to take into consideration when servicing a motor vehicle:



Observe all applicable safety precautions when working around fuel. Whenever servicing the fuel system, always work in a well-ventilated area. Do NOT allow fuel spray or vapors to come in contact with a spark, open flame, or excessive heat (a hot drop light, for example). Keep a dry chemical fire extinguisher near the work area. Always keep fuel in a container specifically designed for fuel storage; also, always properly seal fuel containers to avoid the possibility of fire or explosion. Refer to the additional fuel system precautions later in this section.
 
Fuel injection systems often remain pressurized, even after the engine has been turned OFF. The fuel system pressure must be relieved before disconnecting any fuel lines. Failure to do so may result in fire and/or personal injury.
 
Brake fluid often contains Polyglycol Ethers and Polyglycols. Avoid contact with the eyes and wash your hands thoroughly after handling brake fluid. If you do get brake fluid in your eyes, flush your eyes with clean, running water for 15 minutes. If eye irritation persists, or if you have taken brake fluid internally, IMMEDIATELY seek medical assistance.
 
The EPA warns that prolonged contact with used engine oil may cause a number of skin disorders, including cancer. You should make every effort to minimize your exposure to used engine oil. Protective gloves should be worn when changing oil. Wash your hands and any other exposed skin areas as soon as possible after exposure to used engine oil. Soap and water, or waterless hand cleaner should be used.
 
The air bag system must be disabled (negative battery cable disconnected and/or air bag system main fuse removed) for at least 30 seconds before performing service on or around system components, steering column, instrument panel components, wiring and sensors. Failure to follow safety and disabling procedures could result in accidental air bag deployment, possible personal injury and unnecessary system repairs.
 
Always wear safety goggles when working with, or around, the air bag system. When carrying a non-deployed air bag, be sure the bag and trim cover are pointed away from your body. When placing a non-deployed air bag on a work surface, always face the bag and trim cover upward, away from the surface. This will reduce the motion of the module if it is accidentally deployed. Refer to the additional air bag system precautions later in this section.
 
Disconnecting the negative battery cable on some vehicles may interfere with the functions of the on-board computer system(s) and may require the computer to undergo a relearning process once the negative battery cable is reconnected.
 
It is critically important to observe all instructions regarding ground disconnects, ignition switch positions, etc., in each diagnostic routine provided. Ignoring these instructions can result in false readings, damage to electronic components or circuits, or personal injury.
 

Preliminary Diagnostics



Changes In Diagnostic Routines

In some cases, a new Engine Control system may be similar to an earlier system, but it can have more in-depth 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 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
 

Common Terminology

OBD II introduces common terms, connectors, diagnostic language and new emissions-related monitoring procedures. The most important benefit of OBD II is that all vehicles will have a common data output system with a common connector. This allows equipment Scan Tool manufacturers to read data from every vehicle and pull codes with common names and similar descriptions of fault conditions. In the future, emissions testing will require the use of an OBD II certifiable Scan Tool.

History Of OBD Systems

Starting in 1978, several vehicle manufacturers introduced a new type of control for several vehicle systems and computer control of engine management systems. These computer-controlled systems included programs to test for problems in the engine mechanical area, electrical fault identification and tests to help diagnose the computer control system. Early attempts at diagnosis involved expensive and specialized diagnostic testers that hooked up externally to the computer in series with the wiring connector and monitored the input/output operations of the computer.

By early 1980, vehicle manufacturers had designed systems in which the onboard computer incorporated programs to monitor selected components, and to store a trouble code in its memory that could be retrieved at a later time. These trouble codes identified failure conditions that could be used to refer a technician to diagnostic repair charts or test procedures to help pinpoint the problem area.

Click image to see an enlarged view

Fig.

OBD II System Overview

The OBD II system was developed as a step toward compliance with California and Federal regulations that set standards for vehicle emission control monitoring for all automotive manufacturers. The primary goal of this system is to detect when the degradation or failure of a component or system will cause emissions to rise by 50%. Every manufacturer must meet OBD II standards by the 1996 model year. Some manufacturers began programs that were OBD II mandated as early as 1992, but most manufacturers began an OBD II phase-in period starting in 1994.

The changes to On-Board Diagnostics influenced by this new program include:



Common Diagnostic Connector
 
Expanded Malfunction Indicator Light Operation
 
Common Trouble Code and Diagnostic Language
 
Common Diagnostic Procedures
 
New Emissions-Related Procedures, Logic and Sensors
 
Expanded Emissions-Related Monitoring

Click image to see an enlarged view

Fig.

 

OBD System Diagnostics

One of the most important things to understand about the automotive repair industry is the fact that you have to continually learn new systems and new diagnostic routines (the test procedures designed to isolate a problem on a vehicle system). For OBD I and II systems, a diagnostic routine can be defined as a procedure (a series of steps) that you follow to find the cause of a problem, make a repair and then verify the problem is fixed.

Where To Begin



Diagnosis of engine performance or drivability problems on a vehicle with an onboard computer requires that you have a logical plan on how to approach the problem. The -Six Step Test Procedure- is designed to provide a uniform approach to repair any problems that occur in one or more of the vehicle subsystems.

The diagnostic flow built into this test procedure has been field-tested for several years at dealerships - it is the starting point when a repair is required!

It should be noted that a commonly overlooked part of the -Problem Resolution- step is to check for any related Technical Service Bulletins.

Click image to see an enlarged view

Fig.

Six-Step Test Procedure

The steps outlined below were defined to help you determine how to perform a proper diagnosis. Refer to the flow chart that outlines the Six Step Test Procedure on the previous page as needed. The recommended steps include:

Engine Vacuum Tests

An engine vacuum test can be used to determine if each cylinder is contributing an equal share of power. Engine vacuum, defined as any pressure lower than atmospheric pressure, is produced in each cylinder during the intake stroke. If each cylinder produces an equal amount of vacuum, the measured vacuum in the intake manifold will be even during engine cranking, at idle speed, and at off-idle speeds.

Engine vacuum is measured with a vacuum gauge calibrated to show the difference between engine vacuum (the lack of pressure in the intake manifold) and atmospheric pressure. Vacuum gauge measurements are usually shown in inches of Mercury (in. Hg).


NOTE
In the tests described in this article, connect the vacuum gauge to an intake manifold vacuum source at a point below the throttle plate on the throttle body.

Engine Cranking Vacuum Test Procedure

The Engine Cranking Vacuum Test can be used to verify that low engine vacuum is not the cause of a No Start, Hard Start, Starts and Dies or Rough Idle condition (symptom).

The vacuum gauge needle fluctuations that occur during engine cranking are indications of individual cylinder problems. If a cylinder produces less than normal engine vacuum, the needle will respond by fluctuating between a steady high reading (from normal cylinders) and a lower reading (from the faulty cylinder). If more than one cylinder has a low vacuum reading, the needle will fluctuate very rapidly.

  1. Prior to starting this test, set the parking brake, place the gearshift in P/N and block the drive wheels for safety. Then block the PCV valve and disable the idle air control device.
  2.  
  3. Disable the fuel and/or ignition system to prevent the vehicle from starting during the test (while it is cranking).
  4.  
  5. Close the throttle plate and connect a vacuum gauge to an intake manifold vacuum source. Crank the engine for three seconds (do this step at least twice).
  6.  

The test results will vary due to engine design characteristics, the type of PCV valve and the position of the AIS or IAC motor and throttle plate. However, the engine vacuum should be steady between 1.0-4.0 in. Hg during normal cranking.

Engine Running Vacuum Test Procedure
  1. Allow the engine to run until fully warmed up. Connect a vacuum gauge to a clean intake manifold source. Connect a tachometer or Scan Tool to read engine speed.
  2.  
  3. Start the engine and let the idle speed stabilize. Raise the engine speed rapidly to just over 2000 rpm. Repeat the test (3) times. Compare the idle and cruise readings.
  4.  

Evaluating The Test Results

If the engine wear is even, the gauge should read over 16 in. Hg and be steady. Test results can vary due to engine design and the altitude above or below sea level.

Click image to see an enlarged view

Fig. Engine Running Vacuum Test Graphic

 
label.common.footer.alt.autozoneLogo