U1170

SCP (J1850) Invalid or Missing Data for Cellular Phone / Paging System

Network / Communication Network/Communication Body/Telematics Communication 🟡 Moderate — Fix within a week ⚠️ Drive with Care
💬

What This Actually Means

In plain language — no jargon

Your vehicle's computer can't receive or understand data from the cellular/paging system module—like a phone that won't connect to the network. This is a communication error between the body control module and the telematics/cellular system.

Symptoms You May Notice

3 known symptoms for this code
OnStar or cellular service not functioning
No fault indicator light (typically network-related)
Emergency call system unresponsive
🔬

How Your ECU Detects This

Technical sensor logic and voltage thresholds

The body control module monitors incoming SCP (J1850) bus messages from the cellular/paging module at regular intervals. It checks for valid data packets with correct checksums and timing. If messages are missing, corrupted, or fail integrity checks for a set duration, the fault is logged.

Voltage & Parameter Thresholds

ParameterNormal RangeFault Condition
SCP Message Reception Rate Valid messages received every 100-500 ms No valid message for >1-2 seconds
Data Checksum Validation Checksum matches expected value Checksum mismatch or corrupted payload
🔧

Diagnostic & DIY Fix Guide

Check these in order — from cheapest to most complex
1
OBD-II scanner
Clear the code and retest to confirm if it's intermittent or persistent communication noise.
2
J1850 bus connectors and wiring
Inspect all body control module and cellular module connectors for corrosion, loose pins, or damage.
3
Cellular/telematics module
Perform a module reset or reflash using manufacturer diagnostics; if unresponsive, replacement may be needed.
⚠️

When to See a Professional Mechanic

Not all fault codes are safe to DIY

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

What happens after you fix the fault

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