P060E Code: Throttle Position Monitor Performance
P060E: Verify Throttle Inputs Before the PCM
Save throttle, power and network faults together with all available failure records.
DIAGNOSTIC FOCUS
- FAULT TYPE
- Internal throttle-position monitoring
- FIRST CHECKS
- Power integrity, TPS evidence and calibration
Internal monitoring performance does not by itself condemn PCM hardware.
P060E means Internal Control Module Throttle Position Performance. Internal monitoring performance does not by itself condemn PCM hardware. Identify the vehicle-specific monitored system and test the relevant branch before replacing parts.
Preserve the original scan and freeze frame. Identify the actual circuit or monitored system before selecting a repair; the named component is not automatically defective.
What Does the P060E Code Mean?
Internal Control Module Throttle Position Performance identifies a monitored concern, not a guaranteed failed component. Preserve the reporting module, complete suffix and current/history status before selecting the OEM procedure.
The manufacturer examples below explain the relevant system and diagnostic distinctions. Their applicability and test limits remain vehicle-specific.
No universal voltage, resistance, current, pressure, waveform or drive cycle follows from this code. The exact VIN procedure controls the measurements.
P060E concerns the controller's internal monitoring of throttle-position information. FCA describes its cited implementation as a Level 2 TPS coherency-check failure; this finding does not by itself identify defective PCM hardware.
Internal monitoring performance does not by itself condemn PCM hardware.
The code does not establish these conclusions: PCM hardware is defective; Throttle body alone is defective; Accelerator pedal and throttle position are the same sensor; FCA 18-035-15 Rev. B proves a flash will cure this code. These are questions to resolve with evidence, not reasons to skip the named circuit.
P060E Symptoms, Severity, and Driving Safety
Reduced power, limited throttle response, unstable idle or MIL may occur according to the failsafe strategy; no statement guarantees the vehicle is drivable.
Record when this actually occurs and whether the warning appears at the same time.
This possibility is not a diagnosis; distinguish it from companion faults.
Preserve the exact message and operating state before clearing anything.
Compare normal and failing conditions without deliberately repeating a hazardous event.
Check companion records and their timing before assuming a shared cause.
Reduced power, limited throttle response, unstable idle or MIL may occur according to the failsafe strategy; no statement guarantees the vehicle is drivable. Follow the owner's manual and assess the actual symptoms. No universal safe mileage follows from this code. Arrange professional transport when safe response or reliable engagement cannot be established.
P060E Causes and the Evidence That Separates Them
These are six possibilities to distinguish, not a frequency ranking. Use the recorded conditions to select a test that separates one branch from another.
Unstable controller supply
Low voltage or poor grounding can undermine a valid coherency comparison.
How to prove it: Check battery capability and PCM power/ground before interpreting internal-monitor results.
Check firstThrottle signal disagreement
The monitored inputs may fail their expected relationship.
How to prove it: Compare supported TPS channels and command/actual evidence using the exact OEM criteria.
Check firstConnector or reference fault
External circuit damage can contaminate the data reaching the controller.
How to prove it: Inspect the relevant throttle and PCM connections, references and signal paths.
Verify directlyThrottle response problem
The assembly may not follow a valid request, but the code alone does not establish a physical failure.
How to prove it: Separate sensor feedback from actual controlled response without forcing an energized plate.
Verify directlyConfiguration or software context
A calibration or configuration issue can affect diagnostics and available failure records.
How to prove it: Verify the exact software and current bulletin scope; do not assume any update is curative.
Verify directlyInternal controller defect
Controller hardware remains a final branch when external information and support circuits are proved.
How to prove it: Follow the OEM internal-monitor test before programming or replacing the PCM.
Final branchConfirm each finding with a controlled retest before replacing parts.
Using MA900 During P060E Diagnosis
The iCARZONE MA900 OBD2 Scanner and Battery Tester supports accessible generic engine codes, freeze frame, live data and readiness, plus 12V/24V battery tests.
MA900 does not guarantee full-system access. Dedicated modules, enhanced records, active tests, coding and relearns require separately confirmed equipment coverage.
Battery tests support a relevant supply-voltage branch. They do not prove sensor waveforms, actuator response, hydraulic pressure or controller failure. Use the independent OEM-required equipment.
iCARZONE MA900 2-in-1 OBD2 Diagnostic Scanner & 12V/24V Battery Tester
Save accessible engine evidence for P060E; use an OEM-capable tool when the relevant module or function is not supported.
Checked September 7, 2026: $69.99 USD, compared with $99.99 on the official page. Stock was not confirmed; recheck price, availability and required vehicle/function coverage.
How to Diagnose P060E in 6 Steps
Use these six steps with the exact manufacturer procedure. Confirm equipment coverage and safe test conditions before using any active command; a visible menu item does not establish applicability.
P060E Quick Diagnostic Path
-
1
Save throttle and failure records
- Save the complete TPS/throttle/power/network DTC set and available failure records before clearing.
- Retain original codes and conditions before disconnections or erasure.
-
2
Verify battery and PCM support circuits
- Verify battery and controller power/ground integrity, especially after low voltage or previous service work.
- Match the VIN, connector view and required test state.
-
3
Compare throttle-position and response evidence
- Compare supported throttle-position signals, commanded angle and actual response; distinguish sensor-circuit faults from an internal coherency flag.
- Document findings, then make one controlled correction at a time.
-
4
Inspect throttle and PCM signal paths
- Inspect the correct throttle/PCM connectors and reference/signal paths using OEM information; do not force the plate or apply battery voltage.
- Unavailable scan data is not a zero reading.
-
5
Confirm configuration and bulletin scope
- Verify module configuration, software and current bulletin applicability. The cited FCA update enables failure-record storage and must not be described as a guaranteed cure.
- Use approved isolation and equipment; never power an unknown circuit.
-
6
Complete OEM controller tests and verification
- Only after external inputs, supplies and configuration pass can the exact OEM test lead to controller diagnosis or replacement. Verify throttle response and monitor outcome after repair.
- Confirm the relevant monitor ran after the proven repair.
How to Fix P060E and Verify the Repair
Unstable controller supply repair
Check battery capability and PCM power/ground before interpreting internal-monitor results. Repair only the proven fault and retain the after-repair test result.
Throttle signal disagreement repair
Compare supported TPS channels and command/actual evidence using the exact OEM criteria. Repair only the proven fault and retain the after-repair test result.
Connector or reference fault repair
Inspect the relevant throttle and PCM connections, references and signal paths. Repair only the proven fault and retain the after-repair test result.
Throttle response problem repair
Separate sensor feedback from actual controlled response without forcing an energized plate. Repair only the proven fault and retain the after-repair test result.
Diagnostic time
VIN-specific quoteRequest safe fault reproduction and the correct tests, not merely a generic code read.
Wiring or supporting-system work
VIN-specific quoteItemize connector, harness, ground or prerequisite work with the measurement supporting it.
Proven component or assembly
VIN-specific quoteConfirm the VIN-specific part, labor, taxes and warranty in a current local quote.
Setup and verification
VIN-specific quoteInclude only required learning, calibration and verification. These are alternative paths, not four mandatory repairs.
Get a current VIN-specific estimate showing the failed test, proposed repair and verification. A code alone does not justify an assembly replacement.
Only after external inputs, supplies and configuration pass can the exact OEM test lead to controller diagnosis or replacement. Verify throttle response and monitor outcome after repair. If the event returns, investigate the unresolved branch rather than repeating a clear-and-drive cycle.
P060E OEM Differences and DIY Limits
FCA Bulletin 18-035-15 Rev. B describes a Level 2 throttle-position coherency check and enables additional diagnostic recording for specified 6.2L vehicles. Its diagnostic improvement must be distinguished from a proven cure, and throttle-position information must be separated from accelerator-pedal information.
Internal monitoring performance does not by itself condemn PCM hardware.
Match the VIN, equipment, code suffix and failure conditions before applying a bulletin. A similar symptom is insufficient.
MA900 supports accessible generic engine information and battery testing. Dedicated modules, waveforms, active tests and programming require separately confirmed equipment.
Confirm current VIN, equipment, calibration and suffix applicability. A historical bulletin is not a warranty promise or a procedure for another application.
- Save codes and freeze frame before erasing.
- Record VIN, symptoms and recent repair history.
- Inspect only safely accessible, de-energized areas.
- Request the documented failed test and estimate.
- Never bypass safety interlocks or bridge unknown circuits.
- Do not guess pinouts or transfer another engine’s limits.
- Do not reproduce unsafe symptoms on the road.
- Leave invasive testing and programming to equipped professionals.
Frequently Asked Questions About P060E
What does P060E mean?
Does the FCA update guarantee a repair?
What should I check first for P060E?
Can I keep driving with P060E?
Why can P060E return after a part was replaced?
Can MA900 complete the entire P060E diagnosis?
Will clearing P060E prove that it is fixed?
What should a P060E repair estimate include?
Sources and Technical Review Notes
- FCA Service Bulletin 18-035-15 Rev. B: Flash: 6.2L / 6.4L Diagnostic and System Improvements — Application-specific manufacturer evidence discussed above. Verify current VIN applicability before using its tests or remedies.
- Snap-on Diagnostic Trouble Codes (DTC) List — Current diagnostic-equipment manufacturer terminology cross-check; vehicle-specific testing still requires OEM service information.
- California Bureau of Automotive Repair — On-Board Diagnostic Test Reference — Explains emissions readiness and permanent-DTC verification; applicable emissions rules and vehicle behavior must be considered.
0 comments