| Table 1: | Class 2 Control Module ID |
| Table 2: | GMLAN High Speed Control Module ID |
| Table 3: | Failure Type Byte (FTB) |
Circuit Description
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-10 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. The following modules communicate on class 2 serial data circuit:
Control Module | ID Number |
|---|---|
Body Control Module (BCM) | 064 |
Inflatable Restraint Sensing and Diagnostic Module (SDM) | 088 |
Instrument Panel Cluster (IPC) | 096 |
Head Up Display (HUD) | 098 |
Radio | 128 |
Digital Radio Receiver (DRR) | 137 |
Communication Interface Module (OnStar®) | 151 |
HVAC Control Module | 153 |
Driver Door Module (DDM) | 160 |
Passenger Door Module (PDM) | 161 |
Driver Door Switch (DDS) | 164 |
Driver Position Module (DPM) | 166 |
Fold Top Controller (FTC) | 177 |
Remote Control Door Lock Receiver (RCDLR) | 193 |
Steering Column Lock Control Module (SCLCM) | 194 |
The BCM emulates some devices that are on high speed GMLAN serial data circuit to the modules on class 2 serial data circuit. The BCM transmits multiple Node Alive messages using source IDs that correspond to each of those high speed GMLAN nodes. This is in addition to the BCM behaving itself as a real node. The following module communicate on high speed GMLAN serial data circuit and are emulated by BCM on class 2 serial data circuit:
Control Module | ID Number |
|---|---|
Engine Control Module (ECM) | 017 |
Transmission Control Module (TCM) | 024 |
Electronic Brake Control Module (EBCM) | 040 |
When more than one Loss of Communication DTC is set in either one module or in several modules, diagnose the DTCs in the following order:
- Current DTCs before history DTCs unless told otherwise in the diagnostic table.
- The DTC which is reported the most times.
- From the lowest number DTC to the highest number DTC.
DTC Symptom | DTC Symptom Descriptor |
|---|---|
00 | No additional information |
Conditions for Running the DTC
| • | The following diagnostic trouble codes do not have a current status: |
| - | U1300 |
| - | U1301 |
| - | U1305 |
| • | The vehicle power mode requires serial data communication to occur. |
Conditions for Setting the DTC
A node alive message has not been received from a module with a learned identification number within the last 5-10 seconds.
Action Taken When the DTC Sets
The module uses a default value for the missing parameter.
Conditions for Clearing the DTC
| • | A current DTC clears when the malfunction is no longer present. |
| • | A history DTC clears when the module ignition cycle counter reaches the reset threshold, without a repeat of the malfunction. |
Diagnostic Aids
| • | An intermittent open between the inoperative module and a star connector may cause these codes. |
| • | A poor connection at the inoperative module or a star connector may cause these codes. |
| • | An intermittent open in a star connector may cause these codes. |
| • | An improperly powered module may cause these codes. |
| • | An improperly communication on the high speed GMLAN serial data circuit may cause these codes. |
Test Description
The numbers below refer to the step numbers on the diagnostic table.
-
A module that does not communicate in high speed GMLAN link may cause the setting of the class 2 DTCs.
-
A module which loses power during an ignition cycle will cause other modules to set lost communication DTCs.
-
A module which loses power during an ignition cycle will cause other modules to set lost communication DTCs.
-
The malfunction is due to an open in the class 2 serial data circuit or an open in the module.
-
The module which was not communicating may have set lost communication DTCs for those modules that it was monitoring.
-
The modules which can communicate indicate the module which cannot communicate. You must clear the DTC from these modules to avoid future misdiagnosis.
Step | Action | Yes | No | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Schematic Reference: Data Communication Schematics Connector End View Reference: Master Electrical Component List | |||||||||||||||
1 | Did you perform the Diagnostic System Check - Vehicle? | Go to Step 2 | |||||||||||||
Did you record any DTCs in the range of U2105-U2177 or U0100-U0299? | Go to Step 3 | ||||||||||||||
|
Important: Use the control module ID number list in order to determine which module is not communicating. Test the following circuits of the module that is not communicating for an open or short to ground:
Refer to the following:
Did you find and correct the condition? | Go to Step 11 | Go to Step 4 | |||||||||||||
Did you find and correct the condition? | Go to Step 11 | Go to Step 5 | |||||||||||||
Did you find and correct the condition? | Go to Step 9 | Go to Step 6 | |||||||||||||
6 | Test the class 2 serial data circuit of the module that is not communicating for an open between the module and the star connectors. Refer to Circuit Testing and Wiring Repairs . Did you find and correct the condition? | Go to Step 9 | Go to Step 7 | ||||||||||||
7 | Test the following circuits of the module that is not communicating for poor connections:
Refer to Testing for Intermittent Conditions and Poor Connections and Connector Repairs . Did you find and correct the condition? | Go to Step 9 | Go to Step 8 | ||||||||||||
8 | Replace the module which is not communicating. Refer to Control Module References for replacement, setup, and programming. Did you complete the replacement? | Go to Step 11 | -- | ||||||||||||
Does the scan tool display any DTCs which do not begin with a "U"? | Go to Step 10 | ||||||||||||||
10 | Use the scan tool in order to clear the DTCs. Did you complete the action? | Go to Step 11 | -- | ||||||||||||
Retrieve DTCs from the modules which had the Lost Communication with XXX DTC set. Does the scan tool display any DTCs which do not begin with a "U"? | Go to Step 12 | ||||||||||||||
12 |
Did you complete the action? | System OK | -- | ||||||||||||
