SCP (J1850) Invalid or Missing Data for Primary Id
Your vehicle's main computer isn't receiving proper data messages on the J1850 communication network, like a radio that can't hear its station. This prevents modules from talking to each other correctly.
The ECM monitors the J1850 bus for valid data packets from the transmission control module, body control module, and other networked units. It expects periodic messages with valid checksums and identifiers within specific timing windows. If primary ID messages fail to arrive or contain corrupted data, the ECM flags this as a network failure.
| Parameter | Normal Range | Fault Condition |
|---|---|---|
| J1850 Message Arrival Time | Within 10-50ms intervals | Missing or delayed >100ms |
| Message Checksum Validity | Checksum matches expected value | Checksum mismatch or corrupted data |
Code U1066 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, U1066 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.