DTC U0100-U02FF (Using Network Communication Status)
Diagnostic Instructions Perform the Diagnostic System Check prior to using this diagnostic procedure: Diagnostic System Check - Vehicle Review the description of Strategy Based Diagnosis: Strategy Based Diagnosis An overview of each diagnostic category can be found here: Diagnostic Procedure Instructions DTC Descriptor For device DTC descriptors, refer to Control Module U Code List. For symptom byte information, refer to Symptom Byte List. Diagnostic Fault Information
| Circuit | Short to Ground | Open/High Resistance | Short to Voltage | Signal Performance |
|---|---|---|---|---|
| B+ | U0100-U02FF | U0100-U02FF | — | — |
| Ignition | U0100-U02FF | U0100-U02FF | — | — |
| CAN 1 Serial Data [+] (circuit 4987) | U0075* | U0100-U02FF | U0075* | — |
| CAN 1 Serial Data [-] (circuit 4986) | U0075* | U0100-U02FF | U0075* | — |
| CAN 2 Serial Data [+] (circuit 4979) | U0073* | U0100-U02FF | U0073* | — |
| CAN 2 Serial Data [-] (circuit 4978) | U0073* | U0100-U02FF | U0073* | — |
| CAN 3 Serial Data [+] (circuit 4977) | U0074* | U0100-U02FF | U0074* | — |
| CAN 3 Serial Data [-] (circuit 4976) | U0074* | U0100-U02FF | U0074* | — |
| CAN 4 Serial Data [+] (circuit 4101) | U0079* | U0100-U02FF | U0079* | — |
| CAN 4 Serial Data [-] (circuit 4100) | U0079* | U0100-U02FF | U0079* | — |
| CAN 5 Serial Data [+] (circuit 4985) | U007B* | U0100-U02FF | U007B* | — |
| CAN 5 Serial Data [-] (circuit 4984) | U007B* | U0100-U02FF | U007B* | — |
| CAN 8 Serial Data [+] (circuit 4105) | U007E* | U0100-U02FF | U007E* | — |
| CAN 8 Serial Data [-] (circuit 4104) | U007E* | U0100-U02FF | U007E* | — |
| LIN Serial Data | U0100-U02FF | U0100-U02FF | U0100-U02FF | — |
| Ground | — | U0100-U02FF | — | — |
| * Other DTCs may set with this fault. |
Circuit/System Description The serial data circuit is the means by which the devices in the vehicle communicate with each other. Once the scan tool is connected to the serial data circuit through the X84 Data Link Connector (DLC), the scan tool can be used to monitor each device for diagnostic purposes and to check for Diagnostic Trouble Codes (DTC). Each device communicating on the serial data circuit sends data to each other. When a device stops communicating on the serial data circuit, for example if the device loses power or ground, the data it normally sends on the serial data circuit disappears. Other devices on the serial data circuit, which expect to receive that data, detect its absence; those devices in turn set a DTC associated with the loss of data of the non-communicating device. The DTC is unique to the device which is not communicating and one or more devices may set the same exact code. A loss of serial data communications DTC does not represent a failure of the devices that contain the stored code. Conditions for Running the DTC The system voltage is between 9-16 V. Serial data communication is active. Conditions for Setting the DTC A supervised periodic message has not been received for specified period of time depending on the rate of message. Action Taken When the DTC Sets Specific subsystems will not function. Conditions for Clearing the DTC A current DTC will change to history status when the diagnostic runs and passes. A history DTC will clear after 40-100 consecutive malfunction-free ignition cycles depending on the device. 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. 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. Reference Information Schematic Reference Data Communication Schematics Control Module References Connector End View Reference Master Electrical Component List Description and Operation Data Link Communications Description and Operation Electrical Information Reference Circuit Testing Connector Repairs Testing for Intermittent Conditions and Poor Connections Wiring Repairs DTC Type Reference Powertrain Diagnostic Trouble Code (DTC) Type Definitions Scan Tool Reference Control Module References for scan tool information Circuit/System Verification
- Ignition ON/Vehicle In Service Mode.
- Refer to Control Module U Code List and Data Link References to determine the device that is not communicating and its communication protocol.
- Verify the non communicating device is not a LIN device. ⇒ If the device is a LIN device Refer to Circuit/System Testing — Testing a LIN Device. ⇓ If the device is not a LIN device
- Ignition/Vehicle OFF, access the Network Communication Status application in scan tool under Vehicle Diagnostics > Vehicle Communication Diagnostics > Network Communication Status.
- Verify one or more CAN devices are not communicating. Refer to Network Communication Status to determine the CAN devices that are not communicating. ⇒ If only one CAN device is not communicating Refer to Circuit/System Testing — Testing a CAN Device. The possible fault can be device’s ground, power, or an open in the CAN serial data circuit between that non communicating device and the K56 Serial Data Gateway Module. ⇒ If two or more CAN devices are not communicating, but not all Refer to Circuit/System Testing — Testing a CAN Device. The possible fault can be an open in the CAN serial data circuit at the non communicating device closet to the K56 Serial Data Gateway Module. Use the schematic for CAN bus being tested to determine the non communicating device closest to the K56 Serial Data Gateway Module. ⇒ If all devices are not communicating Refer to Circuit/System Testing — Testing a CAN Device. One of the following faults can occur: A short to voltage in a CAN serial data circuit. A short to ground in a CAN serial data circuit. A short together between CAN serial data circuits. An open/high resistance in a CAN serial data circuit between the K56 Serial Data Gateway Module and the closet non communicating device if the K56 Serial Data Gateway Module is at one end of the bus. Use the schematic for CAN bus being tested to determine the non communicating device closest to the K56 Serial Data Gateway Module. ⇓ If all CAN devices are communicating
- A fault is currently not present and may be an intermittent condition. Circuit/System Testing
- Ignition/Vehicle OFF, disconnect all the harness connectors at the CAN device that is not communicating.
- Verify a test lamp illuminates between each of the ground circuit terminals and B+. ⇒ If the test lamp does not illuminate Repair the open/high resistance in the ground circuit or ground connection. ⇓ If the test lamp illuminates
- Ignition ON/Vehicle In Service Mode.
- If equipped, verify a test lamp illuminates between each of the B+ circuit terminals and ground. ⇒ If the test lamp does not illuminate and the circuit fuse is good 4.1. Test for an open/high resistance in the B+ circuit. ⇒ If an open/high resistance is found, repair the fault in the circuit. ⇓ If an open/high resistance is not found 4.2. Verify the fuse is not open and there is voltage at the fuse. ⇒ If the test lamp does not illuminate and the circuit fuse is open 4.1. Test for a short to ground in the B+ circuit. ⇒ If a short to ground is found, repair the fault in the circuit. ⇓ If a short to ground is not found 4.2. Replace the disconnected device. ⇓ If the test lamp illuminates
- If equipped, verify a test lamp illuminates between each of the ignition circuit terminals, which has a fuse in the circuit, and ground. ⇒ If the test lamp does not illuminate and the circuit fuse is good 5.1. Test for an open/high resistance in the ignition circuit. ⇒ If an open/high resistance is found, repair the fault in the circuit. ⇓ If an open/high resistance is not found 5.2. Verify the fuse is not open and there is voltage at the fuse. ⇒ If the test lamp does not illuminate and the circuit fuse is open 5.1. Test for a short to ground in the ignition circuit. ⇒ If a short to ground is found, repair the fault in the circuit. ⇓ If a short to ground is not found 5.2. Replace the disconnected device. ⇓ If the test lamp illuminates
- Test for less than 4.5 V between each of the CAN serial data circuit terminals and ground. ⇒ If 4.5 V or greater between a CAN 1 serial data circuit and ground Refer to Scan Tool Does Not Communicate with Device on CAN 1 to test for a short to voltage. ⇒ If 4.5 V or greater between a CAN 2 serial data circuit and ground Refer to Scan Tool Does Not Communicate with Device on CAN 2 to test for a short to voltage. ⇒ If 4.5 V or greater between a CAN 3 serial data circuit and ground Refer to Scan Tool Does Not Communicate with Device on CAN 3 to test for a short to voltage. ⇒ If 4.5 V or greater between a CAN 4 serial data circuit and ground Refer to Scan Tool Does Not Communicate with Device on CAN 4 to test for a short to voltage. ⇒ If 4.5 V or greater between a CAN 5 serial data circuit and ground Refer to Scan Tool Does Not Communicate with Device on CAN 5 to test for a short to voltage. ⇒ If 4.5 V or greater between a CAN 8 serial data circuit and ground Refer to Scan Tool Does Not Communicate with Device on CAN 8 to test for a short to voltage. ⇓ If less than 4.5 V
- Ignition/Vehicle OFF, all access doors closed, all vehicle systems OFF, and all keys at least 3 m (9.8 ft) away from vehicle. It may take up to 10 min for all vehicle systems to power down.
- Test for greater than 100 Ω between each of the CAN serial data circuit terminals and ground. ⇒ If 100 Ω or less between a CAN 1 serial data circuit and ground Refer to Scan Tool Does Not Communicate with Device on CAN 1 to test for a short to ground. ⇒ If 100 Ω or less between a CAN 2 serial data circuit and ground Refer to Scan Tool Does Not Communicate with Device on CAN 2 to test for a short to ground. ⇒ If 100 Ω or less between a CAN 3 serial data circuit and ground Refer to Scan Tool Does Not Communicate with Device on CAN 3 to test for a short to ground. ⇒ If 100 Ω or less between a CAN 4 serial data circuit and ground Refer to Scan Tool Does Not Communicate with Device on CAN 4 to test for a short to ground. ⇒ If 100 Ω or less between a CAN 5 serial data circuit and ground Refer to Scan Tool Does Not Communicate with Device on CAN 5 to test for a short to ground. ⇒ If 100 Ω or less between a CAN 8 serial data circuit and ground Refer to Scan Tool Does Not Communicate with Device on CAN 8 to test for a short to ground. ⇓ If greater than 100 Ω
- Test for greater than 35 Ω between each pair of the CAN serial data circuit terminals. ⇒ If 35 Ω or less between the CAN 1 serial data circuits Refer to Scan Tool Does Not Communicate with Device on CAN 1 to test for a short between the serial data circuits. ⇒ If 35 Ω or less between the CAN 2 serial data circuits Refer to Scan Tool Does Not Communicate with Device on CAN 2 to test for a short between the serial data circuits. ⇒ If 35 Ω or less between the CAN 3 serial data circuits Refer to Scan Tool Does Not Communicate with Device on CAN 3 to test for a short between the serial data circuits. ⇒ If 35 Ω or less between the CAN 4 serial data circuits Refer to Scan Tool Does Not Communicate with Device on CAN 4 to test for a short between the serial data circuits. ⇒ If 35 Ω or less between the CAN 5 serial data circuits Refer to Scan Tool Does Not Communicate with Device on CAN 5 to test for a short between the serial data circuits. ⇒ If 35 Ω or less between the CAN 8 serial data circuits Refer to Scan Tool Does Not Communicate with Device on CAN 8 to test for a short between the serial data circuits. ⇓ If greater than 35 Ω
- Test for less than infinite resistance between each of the CAN serial data circuit terminals and ground. ⇒ If infinite resistance Repair the open/high resistance in the serial data circuit. ⇓ If less than infinite resistance
- Inspect both harness and component connectors for contamination, corrosion, and terminal tension.
- Reconnect the harness connectors at the CAN device. Verify all connectors/terminals are fully seated.
- Ignition ON/Vehicle In Service Mode.
- Verify the DTC is not set again. ⇒ If the DTC is set Replace the device that is not communicating. ⇓ If the DTC is not set
- A fault is currently not present and may be an intermittent condition. Testing a LIN Device
- Ignition/Vehicle OFF, disconnect all the harness connectors at a LIN device that is not communicating.
- Verify a test lamp illuminates between each of the ground circuit terminals and B+. ⇒ If the test lamp does not illuminate Repair the open/high resistance in the ground circuit or ground connection. ⇓ If the test lamp illuminates
- Ignition ON/Vehicle In Service Mode.
- If equipped, verify a test lamp illuminates between each of the B+ circuit terminals and ground. ⇒ If the test lamp does not illuminate and the circuit fuse is good 4.1. Test for an open/high resistance in the B+ circuit. ⇒ If an open/high resistance is found, repair the fault in the circuit. ⇓ If an open/high resistance is not found 4.2. Verify the fuse is not open and there is voltage at the fuse. ⇒ If the test lamp does not illuminate and the circuit fuse is open 4.1. Test for a short to ground in the B+ circuit. ⇒ If a short to ground is found, repair the fault in the circuit. ⇓ If a short to ground is not found 4.2. Replace the disconnected device. ⇓ If the test lamp illuminates
- If equipped, verify a test lamp illuminates between each of the ignition circuit terminals, which has a fuse in the circuit, and ground. ⇒ If the test lamp does not illuminate and the circuit fuse is good 5.1. Test for an open/high resistance in the ignition circuit. ⇒ If an open/high resistance is found, repair the fault in the circuit. ⇓ If an open/high resistance is not found 5.2. Verify the fuse is not open and there is voltage at the fuse. ⇒ If the test lamp does not illuminate and the circuit fuse is open 5.1. Test for a short to ground in the ignition circuit. ⇒ If a short to ground is found, repair the fault in the circuit. ⇓ If a short to ground is not found 5.2. Replace the disconnected device. ⇓ If the test lamp illuminates
- If equipped, verify a test lamp illuminates between each of the ignition circuit terminals, which is controlled by a control module, and ground. ⇒ If the test lamp does not illuminate 6.1. Ignition/Vehicle OFF, remove the test lamp, disconnect the harness connectors at the control module that controls the ignition circuit and all devices that share the same ignition circuit. 6.2. Test for infinite resistance between the ignition circuit and ground. ⇒ If less than infinite resistance, repair the short to ground in the circuit. ⇓ If infinite resistance 6.3. Test for less than 2 Ω in the ignition circuit end to end. ⇒ If 2 Ω or greater, repair the open/high resistance in the circuit. ⇓ If less than 2 Ω 6.4. Reconnect the control module that controls the ignition circuit. 6.5. Ignition ON/Vehicle In Service Mode. 6.6. Verify a test lamp illuminates between the ignition circuit terminal and ground. ⇒ If the test lamp does not illuminate, replace the control module that controls the ignition circuit. ⇓ If the test lamp illuminates 6.7. Ignition/Vehicle OFF, reconnect the first device that shares the same ignition circuit. 6.8. Ignition ON/Vehicle In Service Mode. 6.9. Verify a test lamp illuminates between the ignition circuit terminal and ground. ⇒ If the test lamp does not illuminate, replace the device that was just connected. ⇒ If the test lamp illuminates and there are more devices to connect, connect the next device and repeat step 6.9 until there are no more devices to connect. ⇓ If the test lamp illuminates
- Ignition/Vehicle OFF, disconnect all LIN devices that share the same LIN serial data circuit.
- Ignition ON/Vehicle In Service Mode.
- Test for 3.5-12 V between the LIN serial data circuit terminal and ground. ⇒ If less than 3.5 V 9.1. Ignition/Vehicle OFF, disconnect the harness connectors at the control module setting the DTC. 9.2. Test for infinite resistance between the LIN serial data circuit terminal and ground. ⇒ If less than infinite resistance, repair the short to ground in the circuit. ⇓ If infinite resistance 9.3. Test for less than 2 Ω in the LIN serial data circuit end to end. ⇒ If 2 Ω or greater, repair the open/high resistance in the circuit. ⇓ If less than 2 Ω 9.4. Replace the control module that sets the DTC. ⇒ If greater than 12 V 9.1. Ignition/Vehicle OFF, disconnect the harness connectors at the control module setting the DTC. 9.2. Ignition ON/Vehicle In Service Mode. 9.3. Test for less than 1 V between the LIN serial data circuit terminal and ground. ⇒ If 1 V or greater, repair the short to voltage in the circuit. ⇓ If less than 1 V 9.4. Replace the control module that sets the DTC. ⇓ If between 3.5-12 V
- Verify how many LIN devices are connected to this LIN circuit. ⇒ If there is only one LIN device 10.1. Ignition/Vehicle OFF, inspect both harness and component connectors for contamination, corrosion, and terminal tension. 10.2. Reconnect the harness connectors at the LIN device. Verify all connectors/terminals are fully seated. 10.3. Ignition ON/Vehicle In Service Mode. 10.4. Verify the DTC is not set again. ⇒ If the DTC is set, replace the LIN device that is not communicating. ⇓ If the DTC is not set 10.5. A fault is currently not present and may be an intermittent condition. ⇓ If there are two or more LIN devices
- Ignition/Vehicle OFF, disconnect the harness connectors at the control module setting the DTC.
- Reconnect the harness connectors at the first LIN device.
- Ignition ON/Vehicle In Service Mode.
- Test for 3.5-12 V between the LIN serial data circuit terminal at the control module setting the DTC and ground. ⇒ If less than 3.5 V or greater than 12 V Replace the LIN device that was just connected. ⇓ If between 3.5-12 V
- Ignition/Vehicle OFF, reconnect the harness connectors at another LIN device.
- Ignition ON/Vehicle In Service Mode.
- Test for 3.5-12 V between the LIN serial data circuit terminal at the control module setting the DTC and ground. ⇒ If less than 3.5 V or greater than 12 V Replace the LIN device that was just connected. ⇓ If between 3.5-12 V
- Repeat steps 15-17 for the remaining LIN devices until a faulty LIN device is identified. If there is no faulty LIN device, replace the LIN device that is not communicating. Repair Instructions Perform the Diagnostic Repair Verification after completing the repair: Diagnostic Repair Verification. For control module replacement, programming, and setup, refer to: Control Module References