Code
U1153
HUMMER
U — Network/User
Loss of Communications with CCP
AI status
Completed
Completed
100%
Causes
- Open or short in CAN / communications wiring
- Poor or missing module power or ground
- Corroded/loose connector or pin at the CCP
- Faulty CCP module
- Failed CAN transceiver in CCP or another module on the bus
- Blown fuse or supply interruption to CCP
Symptoms
- Malfunction or loss of the system controlled by CCP (dependent on what CCP controls)
- Inability of scan tool to communicate with CCP (no module present)
- One or more U-codes or CAN bus-related DTCs present
- Intermittent operation of functions tied to CCP
- Possible instrument cluster warnings or message center errors relating to network communication
What to check
- Connect a factory-level scan tool and confirm U1153 and any other network codes; capture freeze-frame and history
- Check for presence of other U-codes indicating wider bus issues (U0100, U0121, U1100, etc.)
- Visually inspect CCP connector for corrosion, bent pins, water intrusion, or poor mating
- Check fuses and dedicated power feeds to CCP for continuity and correct voltage with key on/run
- Verify good chassis and battery grounds at module and common ground points
- Measure CAN bus termination resistance between CANH and CANL (~60 Ω typical for two 120 Ω resistors in parallel) with ignition off
Signal parameters
- Idle CAN voltages (key on, engine off): CANH ≈ 2.5–3.5 V, CANL ≈ 1.5–2.5 V (nominal ≈2.5 V common-mode)
- Dominant vs recessive levels: dominant typically pulls CANL low (~1.2–1.5 V) and raises CANH (~3.5–3.8 V) on transmission
- Termination resistance between CANH and CANL ≈ 60 Ω (measured at two-wire system with ignition off)
- Typical CAN data rates used on vehicle networks: 125 kbps, 250 kbps or 500 kbps — confirm correct rate for CCP bus
- Module supply voltage at CCP pin: battery voltage (~11–14 V) with key on/run; ground resistance
Diagnostic algorithm
- Verify and record all stored DTCs and freeze-frame data with a capable scan tool. Note whether CCP responds to a module request.
- Check vehicle battery voltage and perform a basic electrical system health check.
- Visually inspect CCP connector and wiring harness for damage, corrosion, or water ingress. Repair any obvious issues.
- Verify fuses and power/ground circuits to CCP. Backprobe connector: confirm supply voltage and good ground with key on.
- With ignition off, measure termination resistance between CANH and CANL at CCP connector (~60 Ω).
- With ignition on, measure static voltages on CANH and CANL at CCP and compare to other known-good modules on same bus.
- Use an oscilloscope or capable lab meter to observe CAN bus waveforms while attempting communications; look for missing frames, dominant bus stuck, collisions, or excessive noise.
- If wiring and bus parameters are correct, disconnect the CCP module and check whether the rest of the bus returns to normal (isolate suspected faulty module).
- If CCP is suspected faulty, try known-good replacement or bench test where possible. Reprogram/configure replacement per manufacturer procedures.
- After repairs, clear codes and perform drive or functional cycle to confirm repair. Monitor for return of U1153 or related U-codes.
Likely causes
- Loose or corroded connector at CCP
- Power or ground fault to CCP (fuse, connector, chassis ground)
- Broken or shorted CANH/CANL wiring between CCP and bus
- Faulty CCP CAN transceiver or internal module failure
Fault status
Status
Communication timeout or no response detected from CCP on the vehicle network. CCP is not responding to network requests or messages are not present on the bus.
Repair difficulty: Medium
Diagnostic time: 1.0-3.0 hours
Repair manuals
Manual library for HUMMER
138
Browse 138 HUMMER manuals: repair procedures, diagnostics, wiring diagrams, component locations, service data and Labor Times by year, model and trim.
HUMMER
-
HUMMER: 2009
-
HUMMER: 2008
-
HUMMER: 2007
-
HUMMER: 2005
-
HUMMER: 2004
-
HUMMER: 2000
-
HUMMER: 1999
-
HUMMER: 1994
-
HUMMER: 1993
Your experience will help others
+100 karma for a short comment :)
Was this AI description helpful?
Your feedback helps improve AI descriptions.
👍 Like
0
👎 Dislike
0
Send to email
Code
U1153
Other
U — Network/User
SCP (J1850) Invalid or Missing Data for Experimental #3
AI status
Completed
Completed
100%
Causes
- Open or short in CAN / communications wiring
- Poor or missing module power or ground
- Corroded/loose connector or pin at the CCP
- Faulty CCP module
- Failed CAN transceiver in CCP or another module on the bus
- Blown fuse or supply interruption to CCP
Symptoms
- Malfunction or loss of the system controlled by CCP (dependent on what CCP controls)
- Inability of scan tool to communicate with CCP (no module present)
- One or more U-codes or CAN bus-related DTCs present
- Intermittent operation of functions tied to CCP
- Possible instrument cluster warnings or message center errors relating to network communication
What to check
- Connect a factory-level scan tool and confirm U1153 and any other network codes; capture freeze-frame and history
- Check for presence of other U-codes indicating wider bus issues (U0100, U0121, U1100, etc.)
- Visually inspect CCP connector for corrosion, bent pins, water intrusion, or poor mating
- Check fuses and dedicated power feeds to CCP for continuity and correct voltage with key on/run
- Verify good chassis and battery grounds at module and common ground points
- Measure CAN bus termination resistance between CANH and CANL (~60 Ω typical for two 120 Ω resistors in parallel) with ignition off
Signal parameters
- Idle CAN voltages (key on, engine off): CANH ≈ 2.5–3.5 V, CANL ≈ 1.5–2.5 V (nominal ≈2.5 V common-mode)
- Dominant vs recessive levels: dominant typically pulls CANL low (~1.2–1.5 V) and raises CANH (~3.5–3.8 V) on transmission
- Termination resistance between CANH and CANL ≈ 60 Ω (measured at two-wire system with ignition off)
- Typical CAN data rates used on vehicle networks: 125 kbps, 250 kbps or 500 kbps — confirm correct rate for CCP bus
- Module supply voltage at CCP pin: battery voltage (~11–14 V) with key on/run; ground resistance
Diagnostic algorithm
- Verify and record all stored DTCs and freeze-frame data with a capable scan tool. Note whether CCP responds to a module request.
- Check vehicle battery voltage and perform a basic electrical system health check.
- Visually inspect CCP connector and wiring harness for damage, corrosion, or water ingress. Repair any obvious issues.
- Verify fuses and power/ground circuits to CCP. Backprobe connector: confirm supply voltage and good ground with key on.
- With ignition off, measure termination resistance between CANH and CANL at CCP connector (~60 Ω).
- With ignition on, measure static voltages on CANH and CANL at CCP and compare to other known-good modules on same bus.
- Use an oscilloscope or capable lab meter to observe CAN bus waveforms while attempting communications; look for missing frames, dominant bus stuck, collisions, or excessive noise.
- If wiring and bus parameters are correct, disconnect the CCP module and check whether the rest of the bus returns to normal (isolate suspected faulty module).
- If CCP is suspected faulty, try known-good replacement or bench test where possible. Reprogram/configure replacement per manufacturer procedures.
- After repairs, clear codes and perform drive or functional cycle to confirm repair. Monitor for return of U1153 or related U-codes.
Likely causes
- Loose or corroded connector at CCP
- Power or ground fault to CCP (fuse, connector, chassis ground)
- Broken or shorted CANH/CANL wiring between CCP and bus
- Faulty CCP CAN transceiver or internal module failure
Fault status
Status
Communication timeout or no response detected from CCP on the vehicle network. CCP is not responding to network requests or messages are not present on the bus.
Repair difficulty: Medium
Diagnostic time: 1.0-3.0 hours
Repair manuals
Brands with available manuals
9,534
The library contains 9,534 repair and diagnostic manuals. Choose a brand to open the full manual tree by year, model and trim.
Your experience will help others
+100 karma for a short comment :)
Was this AI description helpful?
Your feedback helps improve AI descriptions.
👍 Like
0
👎 Dislike
0
Send to email