SCP (J1850) Invalid or Missing Data for Engine Torque
The engine control unit isn't receiving valid torque demand information from the transmission control module over the J1850 communication bus. Think of it like a radio station broadcasting on the wrong frequency—the message exists but the receiver can't decode it.
The ECM monitors CAN/J1850 bus traffic for torque demand signals from the TCM, which coordinate engine output with transmission behavior. The ECM expects periodic valid messages within a defined time window; missing or corrupted data triggers this fault. Communication timeouts or bus errors prevent proper engine-to-transmission torque coordination.
| Parameter | Normal Range | Fault Condition |
|---|---|---|
| Message Reception Timeout | Valid torque data every 10-100ms | No valid message received for >200ms |
| Data Validity Check | Checksum and CRC pass validation | Checksum mismatch or corrupted payload |
Code U1009 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, U1009 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.