Experiencing a no-start issue with your 2003 Yukon 5.3L and encountering an OBD2 communication error can be incredibly frustrating. You turn the key, all the lights come on, but the engine refuses to crank, and your code reader can’t even connect to the vehicle’s computer. This article will walk you through a step-by-step diagnostic approach to tackle this problem, drawing from a real-world scenario to help you pinpoint the cause.
Understanding the Symptoms
Let’s break down the symptoms presented in a recent case to get a clearer picture of what we’re dealing with:
- No Start, No Crank: The engine doesn’t even attempt to turn over when the key is turned.
- No Starter Signal: Testing at the starter relay reveals a lack of signal, indicating the issue is upstream of the starter itself. However, jumping the relay does cause the engine to crank, confirming the starter motor is functional.
- No Check Engine Light (CEL): The absence of a CEL, while seemingly positive, can be misleading in communication fault scenarios.
- Instrument Lights Normal (Mostly): Initial instrument lights illuminate as expected, but the battery and gauge warning lights remain on.
- Fuel Gauge Issues: The fuel gauge is now reading empty despite the tank being over 3/4 full, and the low fuel light is illuminated.
- Security Light Activation: After leaving the key in the ‘on’ position for a period, the security light illuminates, hinting at potential security system involvement or communication issues affecting it.
- Normal Accessory Function: Dash lights, headlights, heater, radio, turn signals, windows, and wipers all function correctly, suggesting the battery and general power supply are adequate.
- OBD2 Communication Failure with Standard Reader: A generic OBD2 code reader fails to establish communication with the vehicle’s computer, despite power being present at the OBD2 port.
- Limited Communication with Advanced Scanner: A Snap-On scanner can recognize only 10 systems and retrieves 8 codes, many of which are communication related (U-codes). It also fails to Auto ID the vehicle, further indicating a communication problem. However, the Snap-On scanner can perform function tests within the Body Control Module (BCM), showing partial communication.
Alt text: Location of the OBD2 port, typically found under the dashboard on the driver’s side of a vehicle.
Diagnostic Codes and Module Communication Issues
The Snap-On scanner provided crucial information by retrieving codes and highlighting communication failures with specific modules. The recognized modules and their codes were:
- Anti-lock Brakes (ABS): 0 codes – Communicating.
- Airbag: 2 Codes – U1000 Class 2 Data Link Fault (Current & History) – Communication fault.
- Body Control Module (BCM): 2 codes – U1000 Loss of Class 2 Serial Communications – Communication fault.
- Door Module – Drive: 0 codes – Communicating.
- Heating Air Conditioning (HVAC): 2 codes – U1000 Class 2 Data Link Fault (Current & History) – Communication fault.
- Instrument Panel Cluster (IPC): 0 codes – Communicating.
- Lift Gate: 0 codes – Communicating.
- Passenger Presence System: 1 code – U101 Class 2 Serial Communication Problem (Current) – Communication fault.
- Transfer Case: 1 code – U101 Class 2 Serial Communication Problem (Current) – Communication fault.
- Door Module – Passenger: 0 codes (History) – Communicating.
Modules that the Snap-On scanner reported as existing but could not communicate with are critical clues:
- Engine Control Module (ECM/PCM): No Communication – This is a major concern as the ECM controls engine starting and operation.
- Radio: No Communication (likely aftermarket, potentially less relevant to starting issue).
- Seat module – driver: No Communication – Less likely to be directly related to starting.
- Theft Deterrent (Security): No Communication – Potentially significant given the security light symptom and no-start condition.
- Transmission Control Module (TCM): No Communication – While less directly involved in starting, communication loss here can still cause issues.
The recurring U1000 and U101 codes across multiple modules strongly indicate a Class 2 serial data communication problem. Class 2 serial data is a communication network used in many older GM vehicles to allow different modules to share information. A fault in this network can disrupt communication between modules, leading to various issues, including no-start conditions and OBD2 communication errors.
Alt text: Example of a vehicle wiring harness, highlighting the complexity of automotive electrical systems and potential points of failure.
Step-by-Step Diagnostic Approach
Based on these symptoms and codes, here’s a logical troubleshooting process:
-
Fuse Inspection: Begin with a thorough fuse check. The original case mentioned checking the “CIGAR” fuse #13, which is good practice. However, systematically inspect all fuses in both the under-hood and under-dash fuse boxes. Pay close attention to fuses related to the ECM/PCM, BCM, and ignition system. Use a multimeter to test each fuse for continuity, don’t just rely on visual inspection. A blown fuse in a critical circuit can easily cause a no-start and communication issues.
-
Wiring Harness Inspection: The history of mouse damage in the original case is a red flag. Rodents are notorious for chewing on wiring harnesses in vehicles. Carefully inspect the engine compartment wiring harness, paying particular attention to areas where wires are bundled together or routed near the firewall and under the air cleaner assembly (as mentioned in the original post). Look for:
- Visually Damaged Wires: Chewed, frayed, or cut wires.
- Corrosion: Green or white powdery residue on connectors or wires, indicating corrosion.
- Loose Connectors: Ensure all connectors are fully seated and locked.
-
OBD2 Port Power and Ground Check: While power to the OBD2 port was confirmed in the original case, it’s a crucial step to verify. Use a multimeter to check for:
- Pin 16: Battery voltage (12V+) – This is the power supply pin.
- Pin 4 & 5: Ground – Verify good ground connections.
- Pin 2: J1850 VPW Bus (+) – For Class 2 systems, this pin is part of the communication network. (Less critical to check voltage here initially, focus on power and ground first).
-
Module Connector Inspection (BCM and ECM/PCM): Since the BCM and ECM/PCM are heavily implicated in the communication errors, inspect their connectors. Carefully disconnect and reconnect the connectors to these modules, looking for any signs of corrosion, bent pins, or damage. Sometimes, simply reseating connectors can resolve intermittent communication issues caused by poor contact. Important: Disconnect the negative battery terminal before disconnecting any module connectors to prevent accidental shorts or damage.
-
Module Isolation (Advanced Technique): The original poster mentioned the idea of disconnecting modules one at a time. This is a valid but more advanced troubleshooting step. If you suspect a faulty module is “dragging down” the communication bus and preventing other modules from communicating, you can try disconnecting non-essential modules one by one to see if communication is restored with the ECM/PCM. Start with modules that are reporting communication errors or are less critical for starting (like door modules, radio, etc.). After disconnecting each module, try to communicate with the ECM/PCM using your scan tool. Proceed with caution and consult a wiring diagram for your specific vehicle before disconnecting modules, especially critical ones. Incorrectly disconnecting certain modules could cause further issues.
-
Consider Security System Issues: The security light activation and the inability to communicate with the Theft Deterrent module suggest a possible security system problem. While less common in 2003 Yukons compared to later models, security system malfunctions can sometimes prevent starting. If all other checks are inconclusive, further investigation into the security system might be necessary, potentially requiring specialized diagnostic equipment or dealer intervention.
Conclusion
Diagnosing an OBD2 communication error and no-start issue requires a systematic approach. By methodically checking fuses, wiring, connectors, and considering module issues, you can narrow down the potential causes. In the case of the 2003 Yukon 5.3L, the U-codes and lack of ECM/PCM communication strongly point towards a fault in the Class 2 serial data communication network, likely due to wiring problems, a faulty module (potentially the BCM or ECM/PCM itself), or connector issues. If these DIY steps don’t resolve the problem, seeking professional diagnosis from a qualified automotive technician with advanced diagnostic tools is the next logical step to pinpoint the root cause and get your Yukon back on the road.
