U1136

Code

Other U — Network/User

SCP (J1850) Invalid or Missing Data for Telltales

Brand: Other

Type: U — Network/User

Views: UK: 31 EN: 47 RU: 35

AI status

Completed

ready

Completed 100%

Page language: EN

Causes

Open, short, or intermittent wiring on the SCP/J1850 data line
Poor or corroded connector or pin at instrument cluster, BCM, or sending modules
Faulty instrument cluster or body control module (BCM)
Low or unstable battery/charging system voltage during communication
Missing or corrupt module software (firmware) or configuration mismatch
Improper bus termination or grounding issue

Symptoms

Certain dash telltales (turn, ABS, airbag, check engine, etc.) not illuminated, stuck on, or behaving erratically
Instrument cluster displays incorrect or missing warning lights
Multiple network-related U-codes present
Intermittent or permanent loss of related vehicle functions controlled by modules on the SCP/J1850 bus

What to check

Verify battery voltage and charging system (battery fully charged, >12.4 V at key off; >13.5 V with engine running)
Scan all modules and record additional U-codes and freeze-frame data
Inspect connectors and wiring at instrument cluster, BCM and other modules for damage, corrosion, or loose pins
Check for poor or missing ground connections for BCM and instrument cluster
Look for signs of water intrusion or physical damage in affected harnesses
Compare module software/calibration levels with manufacturer specifications (TIS update may be required)

Signal parameters

Data bus should show regular message activity when key on/engine running (varies by vehicle and protocol)
Idle/bus voltage and dominant/recessive levels depend on protocol; look for clean, repeatable waveform without excessive noise or dropouts
Telltale messages are typically periodic status messages—absence or corrupted frames indicate a communication problem
Multiple nodes should not transmit identical message IDs simultaneously (bus arbitration issues indicate faulty module)

Diagnostic algorithm

Verify and record battery and charging voltages. Recharge battery or repair charging faults if needed, then retest.
Use a capable scan tool to read all U-codes and module status. Note any modules that fail to respond.
Visual inspection of connectors and wiring at instrument cluster, BCM and associated modules; repair damaged wires or pins and clean corroded connectors.
Wiggle-test the harness while monitoring the bus with a scan tool/oscilloscope to reproduce the fault (check for intermittent opens/shorts).
Back-probe the data line at the BCM and cluster; observe waveform and message traffic. Compare to known-good signals or specs.
If a single module is not responding or is transmitting corrupted data, try re-seating its connector and clearing codes. If persistent, consider module reflash or replacement per manufacturer procedures.
After repairs, clear codes and verify telltales function through all modes and that U1136 does not return. Road test and re-scan.

Likely causes

Damaged data bus wiring or connector between BCM and instrument cluster
Failed BCM or instrument cluster interrupting telltale messages
Battery voltage low or charging system problem causing communication errors
Corrosion at a pin/ground causing intermittent open/short on the bus

Fault status

⚠️ Status

SCP (J1850) — Invalid or missing telltale data reported on the vehicle network. Instrument cluster or BCM messages for telltales are absent or corrupt.

🟡 Repair difficulty: Medium

⏱️ Diagnostic time: 1.0 - 3.0 hours