Diagnostic Guide for OBD-II Code P2113

Throttle Actuator Control System - Throttle Position Sensor B Circuit Range/Performance

What This Code Means

• P2113 is a powertrain/OBD-II code used to indicate an issue with the Throttle Actuator Control (TAC) system specifically tied to the Throttle Position Sensor "B" circuit, with a range or performance problem.
• In open-source mappings, P2113 is described as the Throttle Position Sensor B
• OBD-II uses diagnostic trouble codes to monitor and report faults in powertrain systems, including throttle/ TAC-related issues. While the general explanation is broad, it supports the concept that TAC-related codes are part of Powertrain Codes under OBD-II.

Symptoms

• Engine light on with P2113 stored, often accompanied by intermittent or persistent reduced engine power or limp-mode behavior.
• Sluggish or delayed acceleration response; pedal input does not always correlate with engine speed or throttle opening.
• Idle instability or rough idle when TAC position readings are out of spec.
• Occasional surges or bucking as the TAC/ TPS B signal fluctuates outside expected range.
• In some cases, no obvious driveability symptom yet the MIL (Check Engine Light) is on and freeze-frame data show TAC/B sensor anomalies.

Important Notes

• These symptoms can overlap with related TAC/TP sensors (A vs B) and with other throttle-related DTCs. A systematic diagnostic approach is required to isolate P2113 from other possible TAC or TPS faults. Sources emphasize the TAC/TPS family of issues as the root domain for this code.

Probable Causes

• Faulty Throttle Position Sensor B (TPS B) or defective TAC position sensor module (B channel) - ~40%
• Wiring harness/connectors to TPS B or TAC (damaged wires, poor ground, corroded or loose pins) - ~30%
• Throttle Actuator Control (TAC) motor or throttle body assembly mechanical issue or binding - ~15%
• ECU/PCM calibration, software/adaptation issue, or need for TAC relearn after replacement - ~10%
• Secondary factors such as intake/vacuum leaks or dirty throttle body contributing to misreadings (less direct cause, but can exacerbate symptoms) - ~5%

Diagnostic Approach

1) Confirm the fault and gather context

• Use a reputable OBD-II scan tool to confirm P2113 is present and review freeze-frame data: engine speed, pedal position, TAC duty cycle, intake airflow, and any related sensor readings at the moment the code was set.
• Note any other related codes that may be present (e.g., generic throttle position sensor codes or TAC-related codes). This helps determine if the problem is isolated to TPS B or part of a broader TAC issue.

2) Visual and connector inspection

• Inspect the TAC/trottle body area and the TPS B sensor connectors for signs of corrosion, moisture, bent/pinched wires, loose pins, or damaged harnesses.
• Wiggle test the connectors and nearby wiring while monitoring live data to see if readings change or if the code triggers during movement of the harness.
• Check grounding points and the power supply to the TAC/control module circuit. A poor ground or supply can cause symptoms similar to a sensor fault.

3) Electrical testing of the TPS B circuit

• With ignition on (engine off) or running as appropriate for the vehicle, measure the TPS B circuit voltage signal(s) for expected behavior (typical modern TPS signals are in the 0-5 V range; however, exact specs vary by vehicle-consult the service information for your application).
• Compare TPS B readings to TPS A readings and to the pedal position input to ensure the B sensor is moving through the expected range and is not stuck or erratic.
• Look for a smooth, monotonic response of the TPS B signal across the pedal travel; abrupt jumps, dead zones, or flat spots indicate a sensor or TAC problem.

4) Mechanical inspection of the TAC/throttle body

• Check the throttle body for sticking or binding of the throttle plate, carbon buildup, or foreign debris that could impede movement.
• Verify that the throttle plate closes fully and returns to idle with no binding when the TAC is commanded to idle by the ECU.
• If the throttle body is dirty or binding, cleaning might improve readings; however, if there's underlying TAC sensor or actuator failure, cleaning won't fix the fault and replacement may be required.

5) Correlate sensor data with actuator behavior

• Use live data to observe how the TAC responds to pedal input and how the throttle plate responds (position vs. commanded position or pedal position vs. actual throttle angle).
• If the TPS B signal is within range and changes properly, yet the TAC does not move correspondingly, suspect TAC actuator/ motor or an ECU-side control issue.
• If the TPS B signal is out of range, intermittent, or does not change with pedal travel, suspect the TPS B sensor or its circuit (wiring/connectors) first.

6) Relearn/ recalibration steps when appropriate

• Many TAC-related repairs require an engine relearn or throttle adaptation procedure after the sensor or TAC unit is replaced. This ensures the PCM correctly maps sensor readings to actual throttle positions during normal operation.
• If replacement of TAC or TPS B is performed, perform the manufacturer-recommended relearn procedure and then verify via a road test and data monitoring. (General TAC service practices; detailed steps depend on the vehicle)

7) Road test and verification

• After addressing suspected causes, perform a controlled road test to evaluate throttle response, torque delivery, idle behavior, and any reoccurrence of P2113.
• Re-scan to ensure the code does not return and verify that live data show consistent TPS B readings across pedal travel and proper TAC actuation.

If the code remains after the above steps

• Consider substituting a known-good TPS B sensor or TAC unit as a diagnostic trial to determine if the fault is sensor/actuator hardware vs. wiring/ECU control.
• Check for and install any available manufacturer service bulletins or updates related to TAC/ TPS B issues for the specific vehicle, as software/firmware can influence throttle control behavior.
• If persistent, escalate to dealer-level diagnostics or more advanced teardown/repair to inspect the TAC module and related control circuitry.

What to document and record during diagnostics

• Freeze-frame data at the time of P2113 occurrence: engine rpm, pedal position, TAC position, throttle angle, intake manifold pressure, mass airflow (if available), and ambient conditions.
• Wiring/connector inspection results, including photos if possible.
• Sensor voltage readings and ranges across the pedal travel for TPS B (and TPS A for comparison, if accessible).
• Relearn/adaptation procedure performed and the vehicle's response during/after the relearn.
• Road-test observations, including any intermittent customer-reported symptoms that were reproduced.

Safety Considerations

• Use proper PPE and avoid contact with moving parts during any inspection of throttle components.

• If you suspect a TAC or throttle-body mechanical failure, avoid aggressive driving until the issue is confirmed to be repairable, as a sudden loss of throttle control can be dangerous.

• Disconnecting the battery or performing certain procedures may require safety precautions and/or a relearn procedure; follow manufacturer guidance for your vehicle.

• Treat P2113 as a TAC TPS B circuit range/performance issue until proven otherwise by testing.

• Start with wiring/connectors and sensor readings (cheap and quick) before moving to actuator/mechanical tests (more involved and costly).

• Use a structured, data-driven approach: rely on live data and freeze-frame data to guide which path to take next.

• After any repair, verify by clearing the code and performing a road test to ensure the fault does not reappear and the TAC system operates as intended.

• Open Source mapping of OBD-II codes - )

• OBD-II overview and diagnostic trouble codes: General statements about how DTCs are used to monitor powertrain systems and how TAC/TPS are part of OBD-II powertrain codes.

• The TAC/TPS relationship is part of the broader OBD-II Powertrain Codes concept described in the Powertrain Codes section.

• The general framework of using DTCs to guide diagnosis, including the importance of sensor data, wiring integrity, and ECU calibration considerations, is described in the OBD-II background materials.

This diagnostic guide was generated using verified reference data:

• Wikipedia Technical Articles: OBD-II
• Open-Source OBD2 Data: N/A (MIT)

Content synthesized from these sources to provide accurate, real-world diagnostic guidance.

---