SCP (J1850) Invalid or Missing Data for Primary Id
Your vehicle's communication network isn't receiving critical data from a module on the J1850 bus—think of it like a team member who stopped answering radio calls during a group project. The ECU can't complete its tasks without this missing information.
The ECU monitors the J1850 serial data bus for valid messages from modules like the PCM, TCM, and ABS. When expected data frames fail to arrive or contain invalid checksums within a specific time window, the fault is triggered. The ECU relies on these periodic handshakes to coordinate engine, transmission, and safety functions.
| Parameter | Normal Range | Fault Condition |
|---|---|---|
| J1850 Message Arrival Time | Data received every 10-100ms | No valid data for >200ms or checksum failure |
| Primary Module ID Response | Valid ID with correct checksum present | Missing, corrupted, or unrecognized module ID |
Code U1035 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, U1035 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.