Diagnostic Aids
- Sometimes, while diagnosing a specific customer concern or after a repair, you may notice a history U-code present. However, there is no associated "current" or "active" status. Loss-of- communication U-codes such as these can set for a variety of reasons. Many times, they are transparent to the vehicle operator and technician, and/or have no associated symptoms. Eventually, they will erase themselves automatically after a number of fault-free ignition cycles. This condition would most likely be attributed to one of these scenarios:
- A control module on the data communication circuit was disconnected while the communication circuit is awake.
- Power to one or more control modules was interrupted during diagnosis.
- A low battery condition was present, so some control modules stop communicating when battery voltage drops below a certain threshold.
- Battery power was restored to the vehicle and control modules on the communication circuit did not all re-initialize at the same time.
- If a loss-of-communication U-code appears in history for no apparent reason, it is most likely associated with one of the scenarios above. These are all temporary conditions and should never be interpreted as an intermittent fault, causing you to replace a part.
- A control module may have a U-code stored in history that does not require any repairs. Issues with late or corrupted messages between control modules can be temporary with no apparent symptom or complaint; this does not mean the control module is faulty. Do not replace a control module based only on a history U-code.
- Do not replace a control module reporting a U-code. The U-code identifies which control module needs to be diagnosed for a communication issue.
- Communication may be available between the BCM and the scan tool with either the low or high speed GMLAN serial data system inoperative. This condition is due to the BCM using both the low and high speed GMLAN systems.
- Use Data Link References to determine if the control module uses high or low speed GMLAN serial data communications.
- Some control modules may not have internal protection for specific control circuits and may open a B+ or ignition fuse. If a fuse is open and the B+ or ignition circuit is not shorted to ground, ensure none of the control circuits are shorted to ground before replacing the control module.
- Some intermittent communication concerns may be caused by fretting corrosion on the serial data circuit terminals. Inspect all connectors at the control module that set the communication DTC, the control module that the communication DTC was set against, and any inline harness connectors between the two control modules. Do not replace a control module based only on fretting corrosion. Refer to bulletin 09-06-03-004 for assistance with the diagnosis and repair of this condition..
- Multiple control modules may not communicate due to the serial data circuits being shorted, faulty terminating resistor, corrosion or poor connections in various control module connectors or inline connectors. Refer to bulletin 08-07-30-021 for assistance with the diagnosis and repair of these conditions, if applicable.
- This diagnostic can be used for any control module that is not communicating, regardless of the type of serial data circuit it is connected to, providing the vehicle is equipped with the control module.