Comprehensive diagnostic guide for P2119 Throttle Actuator Control Range/Performance

Summary

• What the code means: P2119 is a throttle actuator control (TAC) related DTC signaling a range or performance problem with the throttle system. In OEM terminology this is typically described as TAC range or TAC performance. Open-source mappings show a throttle actuator control code describing range/performance behavior. This is consistent with the throttle body/actuator focus of P2119.
  • Source context: Open-source mappings label throttle actuator control/range or performance with related codes.
  • Context and classification: In OBD-II, P-codes are powertrain codes and P2119 falls under throttle actuator control concerns within the powertrain category.
• Symptom patterns observed in real-world complaints: NHTSA complaints frequently describe rough idle, check engine light, throttle response loss or surge, and idle instability associated with P2119 and throttle-body related faults. This reinforces a primary link to TAC/throttle body issues, with potential ancillary electrical concerns.
  • Complaint 1: rough idle, check engine light; throttle body fault P2119; idle surge; reduced throttle; light behavior may vary with temperature.
  • Complaint 2: multiple warnings including throttle system malfunction; rough idle/stall symptoms near throttle/takeoff.

What This Code Means

• P2119 maps to a TAC range/performance fault. From standard code naming conventions and open-source mappings, this code relates to the throttle actuator control system not staying within commanded range or not performing as expected.
  • Supporting context: Open-source mappings indicate throttle actuator control range/performance related codes; the general TAC terminology aligns with P2119 expectations.
  • Context within OBD-II: DTCs are used by the vehicle's PCM to indicate powertrain faults; P-codes are powertrain codes, including throttle control issues.

Probable Causes

Note: Only a small set of NHTSA complaints are provided here, so probabilities reflect observed patterns rather than large dataset statistics.

• Throttle body assembly or TAC motor issue (mechanical bind, carbon buildup, or faulty actuator) - around 70%

• TAC wiring, connectors, or harness deterioration (electrical fault in TAC circuit or poor communication) - around 20%

• Throttle position sensor (TPS) or accelerator pedal position sensor (APP) / pedal sensor correlation issue - around 5%

• PCM/ECU software calibration or sporadic fault (calibration, learn/adaptation needed, or software issue) - around 5%

Note: The above probabilities are anchored to the limited NHTSA complaint data (two cases both pointing to throttle body/TAC-related symptoms) and general TAC failure patterns in modern electronic throttle control systems.

Diagnostic Approach

Safety Considerations

1) Confirm the fault and gather context

• Use an advanced scan tool to confirm P2119 is current and not stored as a past code. Review freeze-frame data if available.
• Note any other codes that appear with P2119; sometimes multiple codes indicate related system faults (TPS/APP, MAF, ABS, etc.).
• Record observed symptoms: rough idle, idle surge or stalling at stop, throttle response issues, service light/wrench indicator status, and any temperature-related changes.

2) Safety and vehicle health prep

• Ensure battery and charging system are healthy (stable 12.6-14.5 V under load). A weak battery can cause ECU communication issues that mimic TAC problems.
• Visually inspect the TAC/throttle body area for obvious issues: dirty throttle body, loose or corroded connectors, damaged wiring harness, oil or coolant leaks, or intake vacuum leaks around the intake tubing.

3) Visual inspection and basic health checks

• Inspect throttle body and actuator connectors for corrosion, damaged pins, and secure fitment. Ensure the harness is routed correctly and not damaged by heat or moving components.
• Check for excessive carbon buildup on the throttle plate and bore. A sticky or dirty throttle plate can hinder proper movement and response.
• Inspect intake manifold and vacuum lines for leaks (especially around the throttle body mounting area). Use a smoke test or soapy water to surface-check for leaks if needed.
• Confirm there are no other obvious fault codes that would indicate related sensor or actuator issues (TPS, APP, MAF, etc.).

4) Electrical/system data checks (live data)

• With ignition on (engine off) and the vehicle in a safe state, monitor TAC commanded position vs. actual position, and the TAC current (demand) if the scanner supports live data.
• Compare the Throttle Position Sensor (TPS) reading to the Accelerator Pedal Position (APP) reading (or pedal position sensor). In a drive-by-wire system, commanded TAC position should align with pedal input; big discrepancies suggest TPS/APP or TAC issues.
• Look for intermittent or out-of-range TAC current/position values. If commanded vs. actual differ significantly or the TAC current is erratic, suspect TAC motor or control circuit.
• If available, check PCM fault code history and software version in the vehicle. Some TAC problems may be aggravated by calibration or software limits.

5) Functional checks and targeted testing

• If the throttle body is dirty or sticky:
  • Perform a careful throttle body cleaning per the service manual (do not forcefully scrape; use appropriate cleaners and follow OEM guidance).
  • After cleaning, perform any required idle relearn or TAC adaptation procedure per OEM guidelines.
• If wiring/connectors show corrosion or damage:
  • Repair or replace damaged wiring, connectors, or the TAC harness as needed. Re-seat connectors and clear any corrosion if possible.
• If a faulty TAC motor is suspected:
  • Replace the throttle body assembly or TAC motor as specified by the OEM. Some vehicles require a complete TAC-equipped throttle body unit.
  • After replacement, perform any required throttle relearn or adaptation procedure to establish proper idle and response characteristics.
• If a sensor problem is suspected (TPS/APP):
  • Test or replace the suspect sensor and re-calibrate the system. Recheck commanded vs actual TAC after replacement.

6) Post-maintenance verification

• Clear codes and perform a test drive to verify whether P2119 returns. Confirm that idle is stable, throttle response is normal, and there are no related symptoms.
• If available, re-check live data for consistency between commanded TAC and actual TAC across idle, light throttle, and full-throttle ranges.
• If P2119 reappears intermittently, consider pursuing a PCM/software update or calibration, or revisit the TAC wiring and sensor health in more detail. Some issues may be intermittent or require software re-flash per OEM guidelines.

Additional Notes

• Related symptoms from the NHTSA complaints emphasize rough idle and throttle-related faults associated with P2119; use these symptom patterns to inform your initial inspection focus toward TAC/throttle body components and their wiring.
• The TAC system relies on precise sensor inputs and a reliable ECU to command throttle movement; a mismatch or intermittent fault in sensors (TPS/APP), TAC hardware, or wiring can produce P2119 or similar throttle-related DTCs.
• The information from Wikipedia confirms the general structure of OBD-II DTCs (diagnostic trouble codes) and classifies P-codes as powertrain codes, which includes throttle control issues. This supports the diagnostic approach of focusing on the throttle actuator control system for P2119.
• Open-source mapping supports the interpretation that P2119 concerns throttle actuator control range/performance, aligning with a TAC/throttle body focus.

What to document when you finish

• Code status (current vs historical) and any freeze-frame data.
• Symptoms observed before, during, and after repair attempts.
• Visual inspection notes (throttle body cleanliness, connector condition, wiring integrity).
• Live data readings (TPS/APP, TAC commanded vs actual, TAC current) and any anomalies found.
• Maintenance performed (throttle body cleaning, TAC motor replacement, wiring repair, software updates) and re-learn/adaptation steps completed.
• Final test results (test drive outcomes, whether P2119 reappeared).

This diagnostic guide was generated using verified reference data:

• NHTSA Consumer Complaints: 2 real-world reports analyzed
• Wikipedia Technical Articles: OBD-II
• Open-Source OBD2 Data: N/A (MIT)

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

---