P2164 – Throttle/Pedal Position Sensor “B” Maximum Stop Performance

DTC P2164 is a powertrain fault that points to an implausible relationship in the throttle/pedal input signal data the Powertrain Control Module (PCM) uses to calculate driver demand. SAE J2012 defines the DTC structure, but the exact sensor or circuit involved can vary by make, model, and year, so you should confirm the affected input(s) with scan data and basic electrical testing. In practice, P2164 often shows up when the PCM sees input signals that don’t correlate under certain operating conditions.

What Does P2164 Mean?

In SAE J2012-style wording, P2164 indicates a throttle/pedal input plausibility problem: the PCM is receiving input information that doesn’t agree with expected values or with other related inputs. Depending on the vehicle, those inputs may come from commonly associated circuits like Accelerator Pedal Position Sensor (APP) signals, Throttle Position Sensor (TPS) signals, or their shared reference/ground paths.

This follows SAE J2012 formatting, and standardized DTC descriptions are published in the SAE J2012-DA digital annex. P2164 is shown here without a hyphen suffix, meaning no Failure Type Byte (FTB) is provided. If an FTB were present (for example, “-xx”), it would further classify the failure mode (such as signal range/performance, plausibility, or other subtypes) without changing the base code’s system-level meaning. What makes P2164 distinct is that it’s about correlation/plausibility rather than a simple “high” or “low” voltage condition.

Quick Reference

• System: Powertrain (driver demand / electronic throttle input processing)
• What it means: PCM sees throttle/pedal input signals that are not plausible or don’t correlate as expected
• Commonly associated with: APP/TPS signal circuits, 5-volt reference, sensor ground, connector integrity, throttle body contamination (vehicle-dependent)
• Likely driver symptoms: Reduced power, poor throttle response, warning light, intermittent hesitation
• Best first checks: Scan live data correlation, verify 5V reference and sensor ground stability, wiggle-test harness/connectors

Real-World Example / Field Notes

In the shop, P2164 often behaves like an “it comes and goes” complaint: the vehicle may drive normally until a bump, heat soak, or heavy rain changes connector resistance just enough to push correlation out of tolerance. One common pattern is stable idle but erratic response on tip-in, where APP and TPS (commonly associated inputs, depending on the platform) briefly disagree in live data. Another pattern is a weak 5-volt reference that looks fine with a meter at rest, but drops under load or during a wiggle test, making the PCM flag plausibility. When you see this, don’t jump straight to a throttle body or pedal assembly—confirm with scan data snapshots, verify power/ground integrity, and reproduce the fault before replacing anything.

Symptoms of P2164

• Check Engine Light: Malfunction Indicator Lamp (MIL) on, sometimes after a cold start, a refuel event, or a hard acceleration where sensor signals change quickly.
• Driveability change: Hesitation, stumble, or uneven power delivery if the control module substitutes a default value when it sees an implausible sensor signal.
• Reduced power: Limp-in or limited throttle response on some vehicles when the Powertrain Control Module (PCM) can’t trust a key input signal.
• Poor fuel economy: Noticeable drop in miles per gallon when fueling is commanded conservatively due to a signal plausibility issue.
• Rough idle: Idle instability if the affected input is used for airflow/fueling/load calculations (exact strategy varies by make/model/year).
• Intermittent symptom: Condition comes and goes with vibration, heat soak, moisture, or harness movement (classic for a connection or wiring integrity problem).
• Hard start or extended crank: Possible on some applications if the questionable input is required for accurate starting fuel and spark decisions.

Common Causes of P2164

Most Common Causes

• Connector/terminal issues (spread pins, corrosion, water intrusion, poor pin fit) causing voltage drop or intermittent signal disruption.
• Harness damage (chafed insulation, rub-through, pinch points, previous repair splices) creating signal distortion rather than a clean open/short.
• Power or ground integrity problem to the sensor circuit (high resistance in ground, weak reference feed, shared ground splice issues) leading to implausible readings under load.
• Sensor signal out of expected range/performance due to contamination, mechanical influence, or response lag (the exact sensor involved can vary by vehicle; confirm with scan data and circuit tests).

Less Common Causes

• Aftermarket part mismatch (wrong sensor type/curve) or incorrect installation causing plausibility failures even though the circuit “looks” connected.
• Electromagnetic interference or poor shielding/grounding on sensitive signal wiring (more likely if symptoms appear with certain electrical loads on).
• PCM software/calibration sensitivity (some vehicles are more prone to setting a range/performance fault when thresholds are tight; verify basics before considering software).
• Possible PCM internal processing or input-stage issue, but only after the sensor, wiring, power, ground, and signal integrity tests pass.

Diagnosis: Step-by-Step Guide

Tools you’ll use: scan tool with live data and freeze-frame, digital multimeter (DMM), back-probe pins or piercing probes, wiring diagram/service information, oscilloscope (helpful for intermittent dropouts), test light, battery/charging system tester, and basic hand tools for harness/connector inspection.

1. Confirm P2164 is current or history. Record freeze-frame data (RPM, load, temperature, voltage). This tells you when the PCM judged the signal “out of performance,” which is a plausibility/behavior fault, not automatically an open/short.
2. Check for obvious electrical issues first: battery state of charge, charging voltage, and main engine grounds. Low system voltage can skew sensor references and trip range/performance logic.
3. Use the scan tool to identify which input the PCM is flagging on your specific vehicle. SAE J2012-DA defines DTC structure, but the exact component tied to P2164 can vary by make/model/year, so you must confirm by data PIDs and service information.
4. On live data, watch the suspect sensor value for plausibility: does it move smoothly, match engine conditions, and avoid sudden spikes/dropouts? Compare to a related parameter (for example, commanded vs. actual behavior) without assuming a specific sensor type.
5. Perform a visual inspection of the sensor and harness routing. Look for oil saturation, coolant intrusion, exhaust heat damage, abrasion, and connector lock issues.
6. Key on/engine off, verify reference voltage (commonly 5 V on many sensors, but not always) and verify ground quality with a voltage-drop test (load the circuit if possible). A “good” ground should show very low drop under load.
7. Check signal integrity: with a DMM for steady sensors or an oscilloscope for dynamic signals. Look for noise, intermittent flatlines, or dropouts that correlate with the fault event.
8. Wiggle test the harness and connector while monitoring the signal on the scope/live data. If the reading glitches, you’ve found a direction: terminal tension, broken conductor, or internal sensor fault.
9. If wiring tests good, confirm the sensor’s response against a known input change (temperature, vacuum/pressure, throttle movement, etc., depending on application) and verify it returns to baseline quickly and repeatably.
10. Only after external checks pass, evaluate PCM involvement: verify PCM powers/grounds with voltage-drop tests and confirm the signal arriving at the PCM matches what you see at the sensor connector. A mismatch points to harness/connector; a match with persistent fault points toward a possible internal processing/input-stage issue.

Professional tip: For range/performance faults, don’t stop at “has 5V and ground.” Use a scope or at least min/max capture on the DMM during a wiggle test and during the operating condition shown in freeze-frame—many P2164 cases are momentary signal dropouts or noise that only appear under vibration, heat soak, or high electrical load.

Possible Fixes & Repair Costs

Repair decisions for P2164 should follow test results, because the exact monitored signal can vary by make/model/year even though SAE J2012 defines the DTC format and classes. Your goal is to correct the underlying plausibility issue (an input that doesn’t make sense compared to expected values or related signals), not to “replace a part.”

• Low cost ($0–$60): Clean/tighten battery terminals and main grounds, repair minor connector issues, reseat terminals, fix obvious harness rub-through only if voltage drop or wiggle testing shows the fault appears/disappears with movement.
• Typical ($80–$350): Repair/replace a damaged section of wiring, replace a sensor or switch only after confirming proper power/ground/reference and finding an out-of-spec signal (wrong voltage/frequency/resistance) or a failing plausibility check under the same conditions that set the code.
• High ($400–$1,500+): Replace a throttle body/sensor assembly or a control module only after all external inputs, wiring integrity, powers/grounds, and signal integrity tests pass and you can reproduce the implausible reading at the module pin or via scan data, suggesting a possible internal processing or input-stage issue.

Costs vary with access time, whether the fault is intermittent, and whether component calibration/learn procedures are required after replacement (vehicle-dependent).

Can I Still Drive With P2164?

Sometimes you can, but you should treat P2164 as a “driveability-risk” code until proven otherwise. Because it indicates a powertrain signal plausibility problem, the vehicle may enter a reduced-power strategy, change shift behavior, or limit throttle response to protect the engine and transmission. If you have hesitation, surging, stalling, harsh shifting, or a flashing malfunction indicator, avoid driving and diagnose it. If it drives normally, keep trips short and avoid heavy loads until you confirm stable sensor data and electrical integrity.

What Happens If You Ignore P2164?

Ignoring P2164 can turn an intermittent plausibility issue into a recurring no-start, limp mode, poor fuel economy, or catalyst-damaging misbehavior depending on which input the vehicle is questioning. It can also mask new problems because the control strategy may substitute default values and reduce diagnostics while the fault is active.

Last updated: February 13, 2026

Vehicles Commonly Affected by P2164

P2164 is commonly seen across many OBD-II vehicles rather than being exclusive to one brand, but it’s often reported on vehicles with complex electronic throttle control and multiple plausibility cross-checks. Some technicians frequently associate it with Ford, Volkswagen/Audi, and General Motors products, as well as high-mileage trucks/SUVs where harness routing and vibration can stress wiring. The common thread is architecture: more sensors, more correlation logic, and more opportunities for voltage drop, connector resistance, or noisy signals to look “implausible.”