SCP (J1850) Invalid or Missing Data for Primary Id
Your vehicle's main computer isn't receiving required data messages from other modules over the SCP (J1850) communication network. It's like a group chat where one person stopped responding, so the group can't function properly.
The ECM monitors incoming J1850 SCP bus messages from modules like the transmission control, ABS, and steering. It expects specific data packets at regular intervals with valid checksums and IDs. If primary ID packets fail to arrive within the timeout window or contain corrupted data, the fault is triggered.
| Parameter | Normal Range | Fault Condition |
|---|---|---|
| SCP Message Reception Timeout | Valid message received every 10-100ms | No message or invalid data for >500ms |
| Primary ID Data Checksum | Checksum valid and matches expected value | Checksum mismatch or corrupted packet data |
Code U1060 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.
Once the fault is repaired, U1060 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.