P060E — Internal Control Module Throttle Position Performance #
Note: The code label may vary depending on the manufacturer. Always refer to your OEM (Original Equipment Manufacturer) documentation for the precise description.
- Internal Control Module Throttle Position Performance (Generic/OEMs)
- PCM Throttle Position Signal Performance (Ford)
- ECM Internal Throttle Position Error (GM)
- Throttle Position Sensor Learning/Performance (Toyota)
Summary of DTC P060E #
The P060E diagnostic trouble code (DTC) indicates that the vehicle’s Powertrain Control Module (PCM) or Engine Control Module (ECM) has detected a performance issue with the internal Throttle Position Sensor (TPS) circuit. This means the control module is not receiving consistent or rational signals from the throttle position data stored or transmitted internally. In practical terms, the computer is struggling to interpret how far open or closed your throttle is, which can impact driveability and engine response. While the root cause can vary, the code typically points to either electronic or internal communication problems within the control module. If this code appears, addressing it promptly is important for both performance and safety.
Common Symptoms for DTC P060E #
When P060E is set, you may notice changes in how your vehicle responds to throttle input or other electronic irregularities. Some of the most frequent signs include:
- Illuminated Check Engine Light (CEL): The most consistent symptom.
- Reduced engine power: The vehicle may enter “limp mode” with severely limited acceleration.
- Poor throttle response: Hesitation, surging, or delayed reaction when pressing the accelerator.
- Hard starting or stalling: Especially at idle or while coming to a stop.
- Other “communication” DTCs: Related codes for throttle, PCM, or sensor circuits may be present.
Most Likely Causes for DTC P060E #
This code is most often triggered by electronic or internal module malfunction rather than simple wiring faults. Here’s a ranked list from most to less common:
- Internal PCM/ECM failure: Faulty microprocessor or memory corruption affecting throttle position logic.
- Software issues: Outdated, corrupted, or incompatible PCM/ECM programming.
- Faulty Throttle Position Sensor (TPS): Especially if it’s integrated into the throttle body and feeds directly to the control module.
- Electrical interference or poor ground: Issues with module power supply, sensor ground, or voltage spikes.
- Shorted or open wiring: Rare, but possible in circuits related to the TPS or PCM/ECM connectors.
- Aftermarket tuning or non-OEM electronics: Incorrect calibrations or incompatible parts.
Step-by-Step Diagnostic for Code P060E #
Accurate diagnosis requires patience and the right approach—avoid jumping to conclusions. Here’s the recommended workflow:
- Scan for additional DTCs: Note any companion codes, especially those related to throttle, communication, or module faults.
- Check for technical service bulletins (TSBs): OEMs may have updates or recalls addressing this specific code.
- Inspect battery and charging system: Low voltage or voltage spikes can cause false module errors.
- Confirm all module grounds and power feeds: Clean, tight, and corrosion-free connections are essential.
- Check throttle body and TPS connector: Look for corrosion, bent pins, or loose connections.
- Test TPS operation (if accessible): Using a scan tool, verify live data shows smooth, rational throttle readings.
- Update or reflash PCM/ECM software: If available, use OEM tools to apply the latest calibration.
- If all else checks out, suspect PCM/ECM failure: Replacement or professional module testing may be needed.
Possible Repairs for DTC P060E #
Repairs depend on what you discover during diagnosis. Here are the most common solutions:
- PCM/ECM replacement or repair: If a confirmed internal failure is found.
- Module software update (reflash): To address programming bugs or compatibility issues.
- Throttle Position Sensor (TPS) replacement: If found defective, especially in integrated throttle body units.
- Repair wiring or connector faults: Fix damaged, corroded, or loose connections in the TPS or PCM/ECM circuits.
- Address poor ground or power supply issues: Clean or repair battery, ground straps, or fuse box connections.
- Remove or reprogram aftermarket devices: If they’re interfering with OEM module logic.
Can You Drive with Code P060E? #
Limited – Exercise caution! While the vehicle may still start and run, P060E often triggers “limp mode” or severely reduces throttle response, which can be hazardous in traffic or during overtaking. In rare cases, sudden stalling or inability to accelerate may occur. Driving should be limited to getting to a repair facility, and avoid highway speeds or heavy traffic if possible.
Vehicles Most Commonly Affected by DTC P060E #
This code can appear on a wide range of modern vehicles with electronic throttle control, but is most frequently reported on:
- Ford (Focus, Escape, Fusion, F-Series, Explorer)
- General Motors (Chevrolet Silverado, Malibu, GMC Sierra, Cadillac models)
- Toyota (Camry, Corolla, Tacoma, RAV4)
- Chrysler/Dodge/Jeep (Ram, Grand Cherokee, Charger)
- Honda (Civic, Accord, CR-V – less common, but possible on newer models)
Common Mistakes & Best Practices for P060E #
It’s easy to misdiagnose P060E due to its internal nature. Avoid these pitfalls:
- Replacing the throttle body or TPS without proper testing: The issue is often within the module, not the sensor.
- Ignoring TSBs or software updates: Many OEMs have released fixes for this code.
- Overlooking battery and ground problems: Even minor voltage issues can trigger module faults.
- Skipping a scan for related codes: Companion codes give valuable clues to root causes.
- Assuming aftermarket tuners or devices are innocent: These can often corrupt throttle logic.
Quick FAQ for P060E #
Here are answers to some of the most common questions about this trouble code:
-
Q: Can a dying battery cause P060E?
A: Yes! Low voltage or voltage drops during starting can lead to module memory errors and trigger this code. -
Q: Will clearing the code fix the problem?
A: No. While clearing may temporarily turn off the light, the underlying issue—often a module or sensor fault—will cause the code to return.




