What does it mean?
This generic powertrain diagnostic trouble code (DTC) generally applies to many OBD-II vehicles. This may include, but is not limited to, vehicles from Ford, Dodge, Duramax, GMC, Chevrolet, Isuzu, Ram, etc.
When a P060B code is stored, it means that the Powertrain Control Module (PCM) has detected an internal processor error from a specific set of processors (designated as A/D). Other controllers may also detect a PCM processor performance error and cause the storage of such a code.
The internal control module monitoring processors are responsible for various controller self-test tasks and the overall responsibility of the internal control module. The internal controller temperature (especially PCM), as well as multiple input and output signals, are constantly monitored by specific controller processors.
Whenever the ignition is turned on and the PCM is powered up, many internal controller processing self-tests are initiated. In addition to running internal controller self-tests, the Controller Area Network (CAN) also compares signals from each individual module to ensure each controller is functioning correctly. These tests are performed simultaneously.
If the PCM detects a discrepancy between any of the onboard controllers, which would indicate an internal processor error, a P060B code will be stored and a Malfunction Indicator Lamp (MIL) may be illuminated. Multiple failure cycles may be required for MIL illumination, depending on the perceived severity of the malfunction.
Photo of a PCM with the cover removed:
Powertrain Control Module PCM
How severe is this DTC?
Internal control module processor codes should be classified as severe. A stored P060B code could result in a no-start condition or severe driving problems, suddenly and without warning.
What are some of the symptoms of the code?
Symptoms of a P060B trouble code may include:
- Multiple driving issues
- Harsh or erratic automatic transmission shifting
- Reduced fuel efficiency
- Irregular idle or stalling
- Hesitation during acceleration
What are some common causes of the code?
Causes of this code may include:
- Faulty controller or programming error
- Bad controller fuse or power relay
- Open or shorted circuit or connectors in the CAN harness
- Insufficient control module ground
What are the troubleshooting steps for P060B?
Even for the most experienced and well-equipped professional technician, diagnosing a P060B code can prove very challenging. There is also the issue of reprogramming. Without the necessary reprogramming equipment, it will be impossible to replace a faulty controller and perform a successful repair.
If ECM/PCM power codes are present, they will obviously need to be corrected before attempting to diagnose a P060B.
Several preliminary tests can be performed before declaring an individual controller faulty. A diagnostic scanner, a digital volt/ohmmeter (DVOM), and a reliable vehicle information source will be required.
Connect the scanner to the vehicle’s diagnostic port and retrieve all stored codes and freeze frame data. You’ll want to note this information, just in case the code proves to be intermittent. After recording all relevant information, clear the codes and test the vehicle until the code resets or the PCM enters readiness mode. If the PCM enters readiness mode, the code is intermittent and will be more difficult to diagnose. The condition that caused the P060B to be stored may even need to worsen before a diagnosis can be made. If the code resets, continue with this short list of preliminary tests.
When trying to diagnose a P060B, information can be your best tool. Search your vehicle information source for Technical Service Bulletins (TSBs) that match the stored code, the vehicle (year, make, model, and engine), and the symptoms presented. If you find the right TSB, it can provide diagnostic information that will help you significantly.
Use your vehicle information source to obtain connector face views, connector pinout diagrams, component locators, wiring schematics, and diagnostic flowcharts related to the code and vehicle in question.
Use the DVOM to test the controller power fuses and relays. Test and replace blown fuses as needed. Fuses should be tested with the circuit loaded.
If all fuses and relays appear to be functioning as expected, a visual inspection of the wiring and harnesses related to the controller is necessary. You’ll also want to check chassis and engine ground junctions. Use your vehicle information source to obtain ground locations for related circuits. Use the DVOM to test ground integrity.
Visually inspect system controllers for signs of water, heat, or collision damage. Any damaged controller, especially by water, should be considered faulty.
If the controller power and ground circuits are intact, suspect a faulty controller or controller programming error. Controller replacement will require reprogramming. In some cases, you can purchase pre-programmed controllers through aftermarket sources. Other vehicles/controllers will require onboard reprogramming that can only be performed by a dealer or other qualified source.
Unlike most other codes, P060B is likely caused by a faulty controller or controller programming error
Test system ground integrity by connecting the DVOM negative test lead to ground and the positive test lead to battery voltage