The ABS-VI contains sophisticated onboard diagnostics that, when accessed with a bi-directional "Scan" tool, are designed to identify the source of any system fault as specifically as possible, including whether or not the fault is intermittent. There are 58 diagnostic fault codes to assist the service technician with diagnosis. The last diagnostic fault code to occur is specifically identified, and specific ABS data is stored at the time of this fault, also, the first five codes set. Additionally, using a bi-directional "Scan" tool, each input and output can be monitored, thus enabling fault confirmation and repair verification. Manual control of components and automated functional tests are also available when using a GM approved "Scan" tool. Details of many of these functions are contained in the following sections.
Enhanced Diagnostic Information, found in the CODE HISTORY function of the bi-directional "Scan" tool, is designed to provide the service technician with specific fault occurrence information. For each of the first five (5) and the very last diagnostic fault codes stored, data is stored to identify the specific fault code number, the number of failure occurrences, and the number of drive cycles since the failure first and last occurred (a drive cycle occurs when the ignition is turned "ON" and the vehicle is driven faster than 10 mph). However, if a fault is present, the drive cycle counter will increment by turning the ignition "ON" and "OFF". These first five (5) diagnostic fault codes are also stored in the order of occurrence. The order in which the first 5 faults occurred can be useful in determining if a previous fault is linked to the most recent faults, such as an intermittent wheel speed sensor which later becomes completely open.
During difficult diagnosis situations, this information can be used to identify fault occurrence trends. Does the fault occur more frequently now than it did during the last time when it only failed 1 out of 35 drive cycles- Did the fault only occur once over a large number of drive cycles, indication an unusual condition present when the fault occurred- Does the fault occur infrequently over a large number of drive cycles, indication special diagnosis techniques may be required to identify the source of the fault-
If a fault occurred 1 out of 20 drive cycles, the fault is intermittent and has not reoccurred for 19 drive cycles. This fault may be difficult or impossible to duplicate and may have been caused by a severe vehicle impact ( large pot hole, speed bump at high speed, etc.) that momentarily opened an electrical connector or caused unusual vehicle suspension movement. Problem resolution is unlikely, and the problem may never reoccur (check diagnostic aids proved for that code). If the fault occurred 3 out of 15 drive cycles, the odds of finding the cause are still not good, but you know how often it occurs and you can determine whether or not the fault is becoming more frequent based on an additional or past occurrences visit if the source of the problem can not or could not be found. If the fault occurred 10 out of 20 drive cycles, the odds of finding the cause are very good, as the fault may be easily reproduced.
By using the additional fault data, you can also determine if a failure is randomly intermittent or if it has not reoccurred for long periods of time due to weather changes or a repair prior to this visit. Say a diagnostic fault code occurred 10 of 20 drive cycles but has not reoccurred for 10 drive cycles. This means the failure occurred 10 of 10 drive cycles but has not reoccurred since. A significant environmental change or a repair occurred 10 drive cycles ago. A repair may not be necessary if a recent repair can be confirmed. If no repair was made, the service can focus on diagnosis techniques used to locate difficult to recreate problems.
As with most electronic systems, intermittent failures may be difficult to accurately diagnose. The following is a method to try to isolate an intermittent failure especially wheel speed circuitry failures.
If an ABS fault occurs, the "ABS" warning light indicator will be "ON" during the ignition cycle in which the fault was detected. If it is an intermittent problem which seems to have corrected itself ("ABS" warning light "OFF"), a history trouble code will be stored. Also stored will be the history data of the code at the time the fault occurred. The Tech 1 must be used to read ABS history data.
INTERMITTENTS AND POOR CONNECTIONS
Most intermittents are caused by faulty electrical connections or wiring, although occasionally a sticking relay or solenoid can be a problem. Some items to check are:
- Poor mating of connector halves, or terminals not fully seated in the connector body (backed out).
- Dirt or corrosion on the terminals. The terminals must be clean and free of any foreign material which could impede proper terminal contact.
- Damaged connector body, exposing the terminals to moisture and dirt, as well as not maintaining proper terminal orientation with the component or mating connector.
- Improperly formed or damaged terminals. All connector terminals in problem circuits should be checked carefully to ensure good contact tension. Use a corresponding mating terminal to check for proper tension. Refer to "Checking Terminal Contact" in this section for the specific procedure.
- The J 35616-A Connector Test Adapter Kit must be used whenever a diagnostic procedure requests checking or probing a terminal. Using the adapter will ensure that no damage to the terminal will occur, as well as giving an idea of whether contact tension is sufficient. If contact tension seems incorrect, refer to "Checking Terminal Contact" in this section for specifics.
- Poor terminal-to-wire connection. Checking this requires removing the terminal from the connector body. Some conditions which fall under this description are poor crimps, poor solder joints, crimping over wire insulation rather than the wire itself, corrosion in the wire-to-terminal contact area, etc.
- Wire insulation which is rubbed through, causing an intermittent short as the bare area touches other wiring or parts of the vehicle.
- Wiring broken inside the insulation. This condition could cause a continuity check to show a good circuit, but if only 1 or 2 strands of a multi-strand type wire are intact, resistance could be far too high.
When diagnosing an electrical system that uses Metri-Pack 150/280/480/630 series terminals (refer to Terminal Repair Kit J 38125-A instruction manual J 38125-4 for terminal identification), it is important to check terminal contact between a connector and component, or between inline connectors, before replacing a suspect component.
Frequently, a diagnostic chart leads to a step that reads "Check for poor connection". Mating terminals must be inspected to ensure good terminal contact. A poor connection between the male and female terminal at a connector may be the result of contamination or deformation.
Contamination is caused by the connector halves being improperly connected, a missing or damaged connector seal, or damage to the connector itself, exposing the terminals to moisture and dirt. Contamination, usually in underhood or underbody connectors, leads to terminal corrosion, causing an open circuit or an intermittently open circuit.
Deformation is caused by probing the mating side of a connector terminal without the proper adapter, improperly joining the connector halves or repeatedly separating and joining the connector halves. Deformation, usually to the female terminal contact tang, can result in poor terminal contact causing an open or intermittently open circuit.
Follow the procedure below to check terminal contact.
- Separate the connector halves. Refer to Terminal Repair Kit J 38125-A instruction manual J 38125-4, if available.
- Inspect the connector halves for contamination. Contamination will result in a white or green buildup within the connector body or between terminals, causing high terminal resistance, intermittent contact or an open circuit. An underhood or underbody connector that shows signs of contamination should be replaced in its entirety: terminals, seals, and connector body.
- Using an equivalent male terminal from the Terminal Repair Kit J 38125-A, check the retention force of the female terminal in question by inserting and removing the male terminal to the female terminal in the connector body. Good terminal contact will require a certain amount of force to separate the terminals.
- Using an equivalent female terminal from the Terminal Repair Kit J 38125-A, compare the retention force of this terminal to the female terminal in question by joining and separating the male terminal to the female terminal in question. If the retention force is significantly different between the two female terminals, replace the female terminal in question, using a terminal from Terminal Repair Kit J 38125-A.
See Figures 1, 2, 3, 4, 5 and 6
Diagnostic fault codes can only be read through the use of a TECH 1® or equivalent bi-directional scan tool. There are no provisions for flash code diagnostics.
The trouble codes in EBCM memory are erased in one of two ways:
- TECH 1® "Clear Codes" selection.
- Ignition cycle default.
These two methods are detailed below. Be sure to verify proper system operation and absence of codes when clearing procedure is completed. The EBCM will not permit code clearing until all of the codes have been displayed. Also, codes cannot be cleared by unplugging the EBCM, disconnecting the battery cables, or turning the ignition "OFF" (except on an ignition cycle default).TECH 1® "Clear Codes" Method
Select F2 for trouble codes. After codes have been viewed completely, TECH 1® will ask, "CLEAR ABS CODES"; ANSWER "yes." TECH 1® will then read, "DISPLAY CODE HIST. DATA"- "LOST" IF CODES CLEARED. "NO" TO CLEAR CODES. Answer "NO" and codes will be cleared.Ignition Cycle Default
If no diagnostic fault code occurs for 100 drive cycles (a drive cycle occurs when the ignition is turned "ON" and the vehicle is driven faster than 10 mph), any existing fault codes are cleared from the EBCM memory.
See Figures 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18 and 19
When servicing the ABS-VI, the following steps should be followed in order. Failure to follow these steps may result in the loss of important diagnostic data and may lead to difficult and time consuming diagnosis procedures.
- Using a TECH 1®, or equivalent bi-directional "Scan" tool, read all current and history diagnostic codes. Be certain to note which codes are current diagnostic code failures. DO NOT CLEAR CODES unless directed to do so.
- Using a bi-directional "Scan" tool, read the CODE HISTORY data. Note the diagnostic fault codes stored and their frequency of failure. Specifically note the last failure that occurred and the conditions present when this failure occurred. This "last failure" should be the starting point for diagnosis and repair.
Perform a vehicle preliminary diagnosis inspection. This should include:
- Inspection of the compact master cylinder for proper brake fluid level.
- Inspection of the ABS hydraulic modulator for any leaks or wiring damage.
- Inspection of brake components at all four (4) wheels. Verify no drag exists. Also verify proper brake apply operation.
- Inspection for worn or damaged wheel bearings that allow a wheel to "wobble."
- Inspection of the wheel speed sensors and their wiring. Verify correct air gap range, solid sensor attachment, undamaged sensor toothed ring, and undamaged wiring, especially at vehicle attachment points.
- Verify proper outer CV joint alignment and operation.
- Verify tires meet legal tread depth requirements.
- If no codes are present, or mechanical component failure codes are present, perform the automated modulator test using the Tech 1 or T-100 to isolate the cause of the problem. If the failure is intermittent and not reproducible, test drive the vehicle while using the automatic snapshot feature of the bi-directional "Scan" tool.
Perform normal acceleration, stopping, and turning maneuvers. If this does not reproduce the failure, perform an ABS stop, on a low coefficient surface such as gravel, from approximately 30-50 mph (48-80 km/h) while triggering on any ABS code. If the failure is still not reproducible, use the enhanced diagnostic information found in CODE HISTORY to determine whether or not this failure should be further diagnosed.
Once all system failures have been corrected, clear the ABS codes. The Tech 1 and T-100, when plugged into the ALDL connector, becomes part of the vehicle's electronic system. The Tech 1 and T-100 can also perform the following functions on components linked by the Serial Data Link (SDL):
Display ABS data
Each test mode has specific diagnosis capabilities which depend upon various keystrokes. In general, five (5) keys control sequencing: "YES," "NO," "EXIT," "UP" arrow and "DOWN" arrow. The FO through F9 keys select operating modes, perform functions within an operating mode, or enter trouble code or model year designations.
In general, the Tech 1 has five (5) test modes for diagnosing the antilock brake system. The five (5) test modes are as follows:MODE FO: DATA LIST
- In this test mode, the Tech 1 continuously monitors wheel speed data, brake switch status and other inputs and outputs.MODE F1: CODE HISTORY
- In this mode, fault code history data is displayed. This data includes how many ignition cycles since the fault code occurred, along with other ABS information. The first five (5) and last fault codes set are included in the ABS history data.MODE F2: TROUBLE CODES
- In this test mode, trouble codes stored by the EBCM, both current ignition cycle and history, may be displayed or cleared.MODE F3: ABS SNAPSHOT
- In this test mode, the Tech 1 captures ABS data before and after a fault occurrence or a forced manual trigger.MODE F4: ABS TESTS
- In this test mode, the Tech 1 performs hydraulic modulator functional tests to assist in problem isolation during troubleshooting. Included here is manual control of the motors which is used prior to bleeding the brake system.Press F7
to covert from English to metric.