Data Communications: Diagnosis Hummer H3 I

DIAGNOSTIC CODE INDEX

DIAGNOSTIC CODE INDEX

Begin the system diagnosis with Diagnostic System Check - Vehicle . The Diagnostic System Check - Vehicle will provide the following information

1. The identification of the control modules which are not communicating
2. The identification of any stored diagnostic trouble codes (DTCs) and their status

The use of the Diagnostic System Check - Vehicle will identify the correct procedures to begin vehicle diagnosis. These must be performed before system DTC or symptom diagnosis.

Circuit Description

The internal fault detection is handled inside the control module. No external circuits are involved.

DTC Descriptor

This diagnostic procedure supports the following DTC

DTC B1000 Electronic Control Unit (ECU) Performance

Conditions for Running the DTC

The module runs the program to detect an internal fault when power up is commanded. The only requirements are voltage and ground. This program runs even if the voltage is out of the valid operating range.

Conditions for Setting the DTC

The module has detected an internal malfunction.

Action Taken When the DTC Sets

The module refuses all additional inputs.

Conditions for Clearing the DTC

1. A current DTC clears when the malfunction is no longer present.
2. A history DTC clears when the module ignition cycle counter reaches the reset threshold, without a repeat of the malfunction.

Diagnostic Aids

1. This DTC may be stored as a history DTC without affecting the operation of the module. If stored only as a history DTC and not retrieved as a current DTC, do not replace the module.
2. If this DTC is retrieved as both a current and history DTC, replace the module.

DTC B1000

Diagnostic Instructions

1. Perform the «Diagnostic System Check - Vehicle»(ref-266892-S29697290792007100900000) prior to using this diagnostic procedure.
2. Review «Strategy Based Diagnosis»(ref-266892-S29323814592007100900000) for an overview of the diagnostic approach.
3. «Diagnostic Procedure Instructions»(ref-266892-S28015579312007100900000) provides an overview of each diagnostic category.

Battery voltage is between 9-16 volts and data link communications operate normally.

The restraints ID stored in the BCM memory is zero.

1. A current DTC clears when the condition is no longer present.
2. A history DTC clears when the module ignition cycle counter reaches the reset threshold, without a repeat of the malfunction.

The internal fault detection is handled inside the control module. No external circuits are involved.

This diagnostic procedure supports the following DTC

DTC B1004 Keep Alive Memory (KAM) Reset

The module microprocessor must be active/awake.

This DTC indicates the keep alive memory (KAM) in the module has been reset. It is a normal occurrence when battery positive voltage or ground is removed from the module, such as a battery disconnect.

The microprocessor reverts back to the base programmed critical operating data until new data is learned and stored in KAM.

1. A current DTC clears when the malfunction is no longer present.
2. A history DTC clears when the module ignition cycle counter reaches the reset threshold, without a repeat of the malfunction.

1. This DTC may be stored as a history DTC without affecting the operation of the module. If stored only as a history DTC and not retrieved as a current DTC, do not replace the module.
2. If this DTC is retrieved as both a current and history DTC, replace the module.

DTC B1004

As part of normal data processing, the module performs a data programming check on its writes to the electrically erasable read only memory (EEPROM). The EEPROM write error detection is handled inside the control module. No external circuits are involved.

This diagnostic procedure supports the following DTC

DTC B1007 EEPROM Write Error

The module runs the program to detect an EEPROM write error. The only requirements are battery positive voltage and ground. This program runs even if the battery positive voltage is out of the valid operating range.

The module writes information to a data block in the EEPROM. The module then reads the data and compares it to what was sent to the data block. If the data does not match after 3 consecutive attempts, the module sets the DTC.

The module writes to another area of the EEPROM, this becomes the new permanent area to store the data. The data location is allowed to change until all of the available EEPROM is used. If a DTC B1004 is also set, the module reverts to base operation values programmed for those blocks of data that have failed. The blocks of data that have not failed the checksum test are not affected.

1. A current DTC clears when the malfunction is no longer present.
2. A history DTC clears when the module ignition cycle counter reaches the reset threshold, without a repeat of the malfunction.

1. This DTC may be stored as a history DTC without affecting the operation of the module. If stored only as a history DTC and not retrieved as a current DTC, do not replace the module.
2. If this DTC is retrieved as both a current and history DTC, replace the module.

DTC B1007

The electrically erasable programmable read-only memory (EEPROM) check sum error detection is handled inside the control module. No external circuits are involved.

This diagnostic procedure supports the following DTC

DTC B1009 EEPROM Checksum Mismatch

The module runs the program to detect an EEPROM checksum error after each wake-up. The only requirements are battery positive voltage and ground. This program runs even if the voltage is out of the valid operating range.

The module retains an inverse copy of the digital value stored in certain blocks of memory in the EEPROM. The module then reads the information from those certain blocks and adds the stored inverse value to the current value. If they do not equal 0, the module sets the DTC.

The module reverts to base operation values programed for those blocks of data that have failed the check sum test. The blocks of data that have not failed the check sum test are not affected.

1. A current DTC clears when the malfunction is no longer present.
2. A history DTC clears when the module ignition cycle counter reaches the reset threshold, without a repeat of the malfunction.

1. This DTC may be stored as a history DTC without affecting the operation of the module. If stored only as a history DTC and not retrieved as a current DTC, do not replace the module.
2. If this DTC is retrieved as both a current and history DTC, replace the module.

DTC B1009

Modules connected to the class 2 serial data circuit monitor for serial data communications during normal vehicle operation. Operating information and commands are exchanged among the modules. When a module receives a message for a critical operating parameter, the module records the identification number of the module which sent the message for State of Health monitoring. A critical operating parameter is one which, when not received, requires that the module use a default value for that parameter. When a module does not associate an identification number with at least one critical parameter within 5 seconds of beginning serial data communication, DTC U1000 or U1255 are set. When more than one critical parameter does not have an identification number associated with it, the DTC will only be reported once.

The class 2 serial data line on this vehicle is a star configuration. The following modules communicate on the class 2 serial data line

1. The body control module (BCM)
2. The electronic brake control module (EBCM)
3. The inflatable restraint sensing and diagnostic module (SDM)
4. The instrument panel cluster (IPC)
5. The powertrain control module (PCM)
6. The radio
7. The Rear Seat Entertainment (RSE) module
8. The Transfer Case Shift Control Module (TCSCM)
9. The Vehicle Communication Interface Module (VCIM)

DTC Descriptors

This diagnostic procedure supports the following DTC

DTC U1000 Class 2 Data Link

1. Voltage supplied to the module is in the normal operating voltage range of 9-16 volts.
2. DTCs U1300, U1301 or U1305 do not have a current status.
3. The vehicle power mode requires serial data communication to occur.

A node alive message has not been received from an unidentified module within the last 5 seconds after establishing class 2 serial data communication.

The module uses a default value for the missing parameter.

1. A current DTC clears when the malfunction is no longer present.
2. A history DTC clears when the module ignition cycle counter reaches the reset threshold, without a repeat of the malfunction.

When a malfunction occurs while modules are communicating, a lost communication DTC is set as a current DTC. When the modules stop communicating the current lost communication DTC is cleared but the history DTC remains. When the modules begin to communicate again, the module with the open fuse will not be learned by the other modules so U1000 or U1255 are set current by the other modules. If the malfunction occurs when the modules are not communicating, only U1000 or U1255 are set.

Modules connected to the class 2 serial data circuit monitor for serial data communications during normal vehicle operation. Operating information and commands are exchanged among the modules. When a module receives a message for a critical operating parameter, the module records the identification number of the module which sent the message for State of Health monitoring. A critical operating parameter is one which, when not received, requires that the module use a default value for that parameter. Once an identification number is learned by a module, it will monitor for that module's Node Alive message. Each module on the class 2 serial data circuit which is powered and performing functions that require detection of a communications malfunction is required to send a Node Alive message every 2 seconds. When no message is detected from a learned identification number for 5 seconds, a DTC U1xxx where xxx is equal to the 3-digit identification number is set.

The control module ID number list below provides a method for determining which module is not communicating. A module with a class 2 serial data circuit malfunction or which loses power during the current ignition cycle will have a Loss of Communication DTC set by other modules that depend on information from that failed module. The modules that can communicate will set a DTC indicating the module that can not communicate.

DTC U1001-U1254

When more than one Loss of Communication DTC is set in either 1 module or in several modules, diagnose the DTCs in the following order

1. Current DTCs before history DTCs unless told otherwise in the diagnostic table.
2. The DTC which is reported the most times.
3. From the lowest number DTC to the highest number DTC.

1. The following diagnostic trouble codes do not have a current status: U1300 U1301 U1305
2. The vehicle power mode requires serial data communication to occur.

A message from a learned identification number has not been detected for the past 5 seconds.

The module uses a default value for the missing parameter.

1. A current DTC clears when the malfunction is no longer present.
2. A history DTC clears when the module ignition cycle counter reaches the reset threshold, without a repeat of the malfunction.

1. An intermittent open between the inoperative module and a star connector may cause this code to set.
2. A poor connection at the inoperative module or a star connector may cause this code to set.
3. An intermittent open in a star connector may cause this code to set.
4. An improperly powered module may cause this code to set.

Modules connected to the class 2 serial data circuit monitor for serial data communications during normal vehicle operation. Operating information and commands are exchanged among the modules. In addition to this, Node Alive messages are transmitted by each module on the class 2 serial data circuit about once every 2 seconds. When the module detects one of the following conditions on the class 2 serial data circuit for approximately 3 seconds, the setting of all other class 2 serial communication DTCs is inhibited and a DTC will set.

This diagnostic procedure supports the following DTCs

1. DTC U1300 Class 2 Data Link Low
2. DTC U1301 Class 2 Data Link High

Conditions for Running the DTCs

1. Voltage supplied to the module is in the normal operating voltage range.
2. The vehicle power mode requires serial data communication to occur.

1. A current DTC clears when the malfunction is no longer present.
2. A history DTC clears when the module ignition cycle counter reaches the reset threshold, without a repeat of the malfunction.

1. These DTCs cannot be retrieved with a current status. Diagnosis of current DTC is accomplished via the symptom, Scan Tool Does Not Communicate with a Class 2 Device. Refer to «Scan Tool Does Not Communicate with Class 2 Device»(ref-266900-S35304707782007100900000) .
2. An intermittent condition is likely to be caused by a short on the class 2 serial data circuit. Use the Scan Tool Does Not Communicate with a Class 2 Device procedure in order to isolate an intermittent condition. Refer to «Scan Tool Does Not Communicate with Class 2 Device»(ref-266900-S35304707782007100900000) .

1. Perform the «Diagnostic System Check - Vehicle»(ref-266892-S29697290792007100900000) before using the symptom tables in order to verify that all of the following are true: There are no DTCs set. The control modules can communicate via the serial data links.
2. Review the system operation in order to familiarize yourself with the system functions. Refer to the following: «Data Link Communications Description and Operation»(ref-266900-S05006845712007100900000) «Body Control System Description and Operation»(ref-266900-S06988118162007100900000)

Visual/Physical Inspection

1. Inspect for aftermarket devices which could affect the operation of the systems. Refer to «Checking Aftermarket Accessories»(ref-266894-S42790233922007100900000) .
2. Inspect the easily accessible or visible system components for obvious damage or conditions which could cause the symptom.

Symptom List

Refer to a symptom diagnostic procedure from the following list in order to diagnose the symptom

1. «Scan Tool Does Not Power Up»(ref-266900-S00342066172007100900000)
2. «Scan Tool Does Not Communicate with Class 2 Device»(ref-266900-S35304707782007100900000)

1. Perform the «Diagnostic System Check - Vehicle»(ref-266892-S29697290792007100900000) prior to using the diagnostic procedure.
2. Review «Strategy Based Diagnosis»(ref-266892-S29323814592007100900000) for an overview of the diagnostic approach.
3. «Diagnostic Procedure Instructions»(ref-266892-S28015579312007100900000) provides an overview of each diagnostic category.

Diagnostic Fault Information

Scan Tool Does Not Power Up

1. The scan tool will power up with the ignition OFF. Some modules however, will not communicate unless the ignition is ON and the power mode master (PMM) module sends the appropriate power mode message.
2. If the battery positive voltage, ground circuits and connections of the DLC are functioning properly, the malfunction must be due to the scan tool/CANdi module.
3. Use the DMM MIN/MAX function to capture/locate intermittent conditions.

Circuit/System Testing

1. Ignition ON, test for battery voltage between the battery positive voltage circuit of the DLC and ground. If less than battery voltage, repair the voltage supply circuit for a short to ground or an open/high resistance.
2. Test for less than 1 ohm of resistance between the ground circuit of the DLC and ground. If greater than 1 ohm, repair the ground circuit for an open/high resistance.
3. If all tests normal, refer to the scan tool/CANdi module user guide.

Modules connected to the class 2 serial data circuit monitor for serial data communications during normal vehicle operation. Operating information and commands are exchanged among the modules. Connecting a scan tool to the data link connector (DLC) allows communication with the modules for diagnostic purposes.

The engine will not start when there is a total loss of class 2 serial data communication while the ignition is OFF. The following conditions will cause a total loss of class 2 serial data communication

1. A class 2 serial data circuit shorted to ground.
2. A class 2 serial data circuit shorted to voltage.
3. An internal condition within a module or connector on the class 2 serial data circuit, that causes a short to voltage or ground to the class 2 serial data circuit.

The data link connector (DLC) allows a scan tool to communicate with the class 2 serial data line. The serial data line is the means by which the microprocessor-controlled modules in the vehicle communicate with each other. Once the scan tool is connected to the class 2 serial data line through the DLC, the scan tool can be used to monitor each module for diagnostic purposes and to check for diagnostic trouble codes (DTCs). Class 2 serial data is transmitted on a single wire at an average of 10.4 kbps. This value is an average, class 2 uses a variable pulse width modulation to carry data and depending on the message it may operate faster or slower. The bus will float at a nominal 7 volts during normal operation. Each module can pull this lower during the transmission. The bus is not at battery positive voltage or ground potential during normal operation. When the ignition switch is in RUN, each module communicating on the class 2 serial data line sends a State Of Health (SOH) message every 2 seconds to ensure that the module is operating properly. When a module stops communicating on the class 2 serial data line, for example if the module loses power or ground, the SOH message it normally sends on the data line every 2 seconds disappears. Other modules on the class 2 serial data line, which expect to receive that SOH message, detect its absence; those modules in turn set an internal DTC associated with the loss of SOH of the non-communicating module. The DTC is unique to the module which is not communicating, for example, when the inflatable restraint sensing and diagnostic module (SDM) SOH message disappears, several modules set DTC U1088. Note that a loss of serial data DTC does not normally represent a failure of the module that set it.