U1137

SCP (J1850) Invalid or Missing Data for Telltales

Network / Communication Network/Communication SCP Bus Fault 🟡 Moderate — Fix within a week ⚠️ Drive with Care
💬

What This Actually Means

In plain language — no jargon

Your vehicle's instrument cluster isn't receiving proper communication signals from the engine control unit, like a radio losing its station signal. The ECU can't reliably send telltale (warning light) data over the SCP bus network.

Symptoms You May Notice

3 known symptoms for this code
Dashboard warning lights fail to illuminate or stay on constantly
Instrument cluster displays are dim, flickering, or non-responsive
Loss of gauge readings (speedometer, fuel gauge, temperature gauge)
🔬

How Your ECU Detects This

Technical sensor logic and voltage thresholds

The ECU monitors the SCP (SAE J1850) serial communication bus that transmits telltale status and diagnostic data to the instrument cluster. It validates message timing, data integrity, and signal presence on the network. When valid data frames fail to transmit or receive within expected intervals, the fault is logged.

Voltage & Parameter Thresholds

ParameterNormal RangeFault Condition
SCP Bus Message Frequency Valid frames received every 10-100ms Missing or delayed frames exceeding timeout threshold
Data Checksum Validity Checksum matches transmitted data Checksum mismatch or corrupted payload detected
🔧

Diagnostic & DIY Fix Guide

Check these in order — from cheapest to most complex
1
OBD-II connector pins and socket
Clean corrosion from pins 6 and 14 (SCP bus lines) with contact cleaner and inspect for loose connections.
2
SCP bus wiring harness
Visually inspect wiring between ECU and instrument cluster for damaged insulation, pinches, or loose connectors.
3
Instrument cluster module
If wiring is intact, the cluster module may need replacement or reprogramming by a dealer.
⚠️

When to See a Professional Mechanic

Not all fault codes are safe to DIY

Code U1137 is a moderate fault. You can generally drive to a workshop, but avoid long trips or high-load driving (motorway, uphill towing) until it is diagnosed. If the code keeps returning after clearing, or if you notice the symptoms listed above worsening, do not delay professional diagnosis. Many moderate codes have multiple possible root causes — a mechanic with live OBD data can identify the exact fault more efficiently than part-by-part trial and error.

Safety note: OBD-II codes identify the system or circuit where a fault was detected — they do not always identify the exact failed component. A professional mechanic using live sensor data will diagnose the root cause more accurately than replacing parts based on the code alone.
🔄

How to Clear Code U1137

What happens after you fix the fault

Once the fault is repaired, U1137 can be cleared using any OBD-II scanner. Connect the scanner, navigate to "Clear Codes" or "Erase DTCs," and confirm. The check engine light turns off immediately.

The code will return if the root cause was not actually fixed. The ECM re-detects the fault within 1–3 drive cycles and sets the code again.

✅ Safe to Clear When
  • Fault has been diagnosed and repaired
  • You want to confirm the repair worked
  • Code appeared after a sensor was cleaned
⚠️ Do Not Clear When
  • Preparing for an emissions/PUC test
  • Root cause is still undiagnosed
  • Check engine light is flashing
Emissions test note: Clearing codes resets OBD readiness monitors. Most vehicles need 50–100 km of mixed driving before monitors complete. Do not clear codes immediately before an emissions or PUC inspection.