U1122

SCP (J1850) Invalid or Missing Data for Odometer

Network / Communication Network/Communication SCP Bus Communication 🟡 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 valid odometer data from the powertrain control module over the SCP communication bus. Think of it like a phone that can't receive text messages from one specific contact.

Symptoms You May Notice

3 known symptoms for this code
Odometer display shows zero or doesn't increment
Instrument cluster warning lights or erratic displays
Dashboard communication errors or slow response
🔬

How Your ECU Detects This

Technical sensor logic and voltage thresholds

The ECM continuously transmits odometer distance data via the J1850 SCP (SAE J1850 Standard Corporate Protocol) serial communication bus to the instrument cluster. The cluster expects valid odometer updates at regular intervals with proper data checksums. If data is missing, corrupted, or fails validation checks for a threshold time period, this fault code sets.

Voltage & Parameter Thresholds

ParameterNormal RangeFault Condition
SCP Message Validity Valid odometer data received every 100-500ms with correct checksum Missing or invalid odometer message for >2 seconds or checksum failure
Data Range Check Odometer increments logically within vehicle speed parameters Data missing entirely or implausible values detected
🔧

Diagnostic & DIY Fix Guide

Check these in order — from cheapest to most complex
1
Battery terminals and connections
Clean corrosion from battery terminals and ensure all ground connections are tight, as loose grounds disrupt SCP communication.
2
OBD-II connector and wiring harness
Inspect the OBD-II port and dashboard harness connectors for bent pins, corrosion, or loose seats and reseat firmly.
3
Instrument cluster or PCM replacement
If communication still fails, the cluster or PCM module may need reprogramming or replacement by a dealer.
⚠️

When to See a Professional Mechanic

Not all fault codes are safe to DIY

Code U1122 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 U1122

What happens after you fix the fault

Once the fault is repaired, U1122 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.