Error Code P061A is defined as Internal Control Module Torque Performance. This code is a generic trouble code, meaning it applies to all vehicles equipped with the OBD-II system, especially those made since 1996 up to present. It’s particularly common among Chrysler, Dodge, Ford (Powerstroke), Land Rover, Mercedes Benz, Ram (Cummins), etc. Specifications on the definition, troubleshooting, and repairs, of course, vary from one make and model to another.

The job of the Internal Control Module processor is to monitor various controller self-test duties and overall internal control module accountability. The engine torque calculation system input and output signals are subject to self-test, and continuously monitored by the PCM and other controllers. The TCM (transmission control module), TCSM (traction control module), and other controllers are bound by the interaction with engine torque monitoring system.

When this code is stored, that means the PCM has seen an internal performance error in the engine torque monitoring system. Other controllers can also detect an internal error in the PCM (powertrain control module, also known as ECM or engine control module in other vehicle makes) with the engine torque monitoring system, which may contribute to the Error Code P061A.

The engine torque is monitored by the PCM and other controllers using input signals from MAF (Mass Air Flow) sensor and APP (Accelerator Pedal Position, also referred to as the Pedal Position Sensor). Desired or approximate required engine torque is calculated by the APP sensor, while actual engine torque is calculated through data from the MAF sensor.

These self-tests are automatically initiated when the ignition is turned on, and the PCM receives power. Aside from running internal controller self-tests, CAN also automatically compares signals from each individual module, ensuring controllers are working properly. These tests are performed simultaneously.

If the PCM sees a discrepancy in the desired torque and actual torque (more than 50-newton meters for more than 1 second) for the engine RPM of above 5,000 RPM and volumetric efficiency greater than 16%, then this error code will be stored, and simultaneously illuminating the Check Engine light. Depending on the severity of the condition, it may take multiple drive cycles before the Check Engine light lights up.

Common Symptoms

  • Hesitation upon acceleration
  • Unresponsive acceleration
  • Increase in fuel consumption
  • MAF or throttle actuator codes may be present

Possible Causes

There are many causes for this code to appear, such as:

  • Damaged throttle valve control servo
  • Open or shorted circuit in the throttle valve control servo
  • Open or shorted circuit between APP/MAF sensor and PCM
  • Open or shorted circuit in CAN harness
  • Clogged air filter element
  • Defective APP/MAF sensor
  • Debris on MAF sensor hot wire
  • Defective PCM
  • PCM programming error
  • Insufficient control module ground

How to Check

This code is quite a challenging problem to diagnose, and many times, it involves reprogramming issues. Thus, without the right tools and reprogramming equipment, it will be impossible to replace a defective controller and complete the repair.

If the ECM/PCM power supply codes are present, then obviously, they don’t need to be rectified before attempting to diagnose this code.

Many preliminary tests can be performed to make sure a controller is defective. A diagnostic scanner, DVOM (digital volt/ohmmeter), and reliable vehicle information is needed for diagnosis of this code.

The first step is to connect the scanner to the vehicle diagnostic port and retrieve all stored codes, including their freeze frame data. You need to write down this information, just in case the problem proves to be intermittent. After writing down all pertinent information, clear the codes and then take the vehicle for a test drive to see if the code resets, or if the PCM enters readiness mode. If the PCM does the latter, then you have an intermittent problem, which is more difficult to diagnose, as it means you would have to wait for the problem to develop more before you can successfully diagnose.

If the code resets, however, then continue with your preliminary diagnosis.

When trying to diagnose this code, refer to your information source or TSB (technical service bulletin); looks for signs and symptoms parallel to the stored code. Search for the year, make, model, and engine of your vehicle. If you are able to find the right TSB, then you may get the best diagnostic information for your problem.

Use vehicle information source to obtain component locations, connector face views, connector pin-out charts, wiring diagram, and diagnostic flow chart related to your vehicle’s error code.

Then, use the DVOM to the test controller power supply fuses and relays. Next, test and replace any blown fuses as necessary. Fuses must be tested with circuit loaded.

If all fuses and relays are running well, check whether the controller related wiring and harness are in order. You may also want to check chassis and engine ground junctions. Again, use your vehicle information source to obtain ground locations as related circuits. Test ground integrity using the DVOM.

Then, check the system controllers for any signs of water, heat, or collision damage. Any controller that is damaged, especially by water, is considered defective and must be replaced.

If controller power and ground circuits are intact, then there’s a good chance the controller is defective, or there’s a programming error in the controller. Thus, controller replacement requires reprogramming. In some cases, you may want to get aftermarket reprogrammed controllers. Some vehicles and controllers require on-board reprogramming that may be done only through the dealership or a qualified shop.

How to Fix

Depending on your diagnosis, possible repairs include:

  • Replacement of blown fuses
  • Replacement and reprogramming of defective controller

Unlike most codes, this code is likely caused by a defective controller or a programming error in the controller.

Test the integrity of the system ground by connecting the negative test lead of DVOM to the ground, and the positive test lead to battery voltage.