October 30: LEMON manuals on a temporary server, it is slow and having issues, download the manuals you need! Later in November we will switch back to the fast server.
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 device on the data communication circuit was disconnected while the communication circuit is awake.
- Power to one or more devices was interrupted during diagnosis.
- A low battery condition was present, so some devices stop communicating when battery voltage drops below a certain threshold.
- Battery power was restored to the vehicle and devices 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 device may have a U code stored in history that does not require any repairs. Issues with late or corrupted messages between devices can be temporary with no apparent symptom or complaint; this does not mean the device is faulty. Do not replace a device based only on a history U code.
- Do not replace a device reporting a U code. The U code identifies which device needs to be diagnosed for a communication issue.
- Communication may be available between some devices and the scan tool with either the low or high speed GMLAN serial data system inoperative. This condition is due to those devices using multiple serial data communication systems.
- Use Data Link References to determine what serial data communications the device uses.
- Some devices 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 device.
- Some intermittent communication concerns may be caused by fretting corrosion on the serial data circuit terminals. Inspect all connectors at the device that set the communication DTC, the device that the communication DTC was set against, and any inline harness connectors between the two devices. Do not replace a device based only on fretting corrosion. Refer to bulletin 09-06-03-004 for assistance with the diagnosis and repair of this condition, if applicable.
- This diagnostic can be used for any device that is not communicating, regardless of the type of serial data circuit it is connected to, providing the vehicle is equipped with the device.
- This diagnostic procedure can be used to diagnose the common no communication DTCs: U0100, U0101, U0102, U0103, U0104, U0105, U0106, U0109, U010E, U010F, U0111, U0112, U0115, U0117, U0121, U0122, U0123, U0125, U0126, U0128, U0129, U012A, U0130, U0131, U0132, U0133, U0136, U0137, U0139, U0140, U0146, U0151, U0155, U0158, U0159, U0160, U0164, U0166, U0167, U0168, U016B, U0170, U0181, U0182, U0184, U0186, U0191, U0193, U0196, U0197, U0198, U0201, U0203, U0204, U0207, U0208, U0209, U0210, U0230, U0232, U0233, U0236, U0237, U023A, U0248, U0249, U0250, U0252, U0254, U025B, U0264, U0265, U0268, U0269, U026A, U026B, U0293, U029D, U029E, U02A3, and other DTCs within U0100-U02FF range.