Pulling Codes: The Importance Of Communication – No Code Analysis
For this month’s Pulling Codes case, we will attempt to provide a plan of attack for communication issues on General Motors products with the Class 2 Protocol. Our diagnostic journey begins with a 2004 Chevrolet Tahoe. This vehicle was tested at the EPA test facility in our area and it was determined that there is no communication with the PCM.
Pulling Codes: The Variables Of Cam Timing – No Code Analysis
Carlton Banks investigates a no-code analysis for a variable cam timing (VCT) system issue involving multiple misfires. The subject vehicle is a 2005 Ford F-150 Super Duty and has a 5.4L engine with three valves per cylinder. The engine starts and runs; the idle quality is very poor; and cylinders 2, 3 and 4 have misfire activity.
Pulling Codes: This One Didn’t Go ‘Zoom Zoom’! The Story Of P1345
Top EPA Codes: Carlton Banks investigates a P1345 code – CMP Sensor Circuit Malfunction – in a 2000 Mazda Protege. This is a code that involves the cam sensor input to the PCM. In many situations, one may be tempted to replace the cam sensor right away. This article will attempt to provide a possible plan of attack.
Pulling Codes: What Is Our Position On This? The Story of P1512
P1512 is a code that involves electronic throttle control (ETC), or throttle actuator control (TAC), and in many situations, a technician may be tempted to replace the throttle body assembly right away. This article will attempt to provide a better plan of attack.
Pulling Codes: The Story of Code P0456
The Smallest of Details? This month’s Pulling Codes documents the infamous P0456 code — 0.20 leak detected. A small leak code can be the most challenging for any technician, so Carlton Banks gives his suggested plan of attack.
Pulling Codes: Rough Road Data Not Available?
A 1998 Chevrolet Blazer is looked at by the state to determine if the cost to repair this vehicle may exceed what many may deem reasonable. The owner of the vehicle has suffered some financial hardships and we have been asked to take a look at the vehicle.
Pulling Codes: Mean and Lean with Shades of Gray
This article will document the infamous P0171 code – Lean Condition. A fuel system lean condition can be broken down into three subsections, namely, fuel pump performance, fuel quality and injectors. Keep in mind this is only a starting point, but it is a good place to start.
Pulling Codes: Hit or Miss? Part III
In the first two articles, we looked at cranking compression and tailpipe analysis. We will now explore in-cylinder analysis. In order to have an understanding of this concept, one must envision the four-stroke cycle at the time the plug fires as a reference. This denotes the end of our compression stroke, and the beginning of the power stroke for that cylinder.
Pulling Codes: Hit or Miss? Part II
This article will continue the work we started in the June 2011 Pulling Codes article. Part I outlined how we used relative compression to find a fault mechanically. In this article, we will focus on exhaust waveforms (tailpipe analysis) to gather data. In order to have an understanding of this concept, one must envision the four-stroke cycle at the time the plug fires as a reference.
Pulling Codes: The Story of Codes P1128 and P1129
It was Saturday, June 11, 2011, at 8:30 in the morning. I had just arrived at an automotive repair facility located in Merriville, IN, owned by a very good friend of mine. The reason for my visit that morning was the challenge of a 2008 Chrysler 300 VIN Code R with a 2.7L engine. This vehicle appeared to operate properly until it reached cruising speed, and then once cruising speed was obtained, the vehicle would actually hiccup and set a pending code for P1128 and P1129. This hiccup could more accurately be defined as a “fishbite” reaction that was felt at cruising speed.
Pulling Codes: The Story of U1016
This Pulling Codes article will center on issues involving the powertrain control module (PCM) talking to your scan tool. In many states, this is the controller our scan tool needs to talk to in order to determine if the correct number of monitors has run and passed. It’s interesting to note that there appears to be two modes of failure in terms of communication.
Pulling Codes: Hit or Miss? The Story of P0302
It is unfortunate that today misfire analysis can be a hit-or-miss concept on many of today’s engine families. If one views several misfire failures, and documents the behavior of fuel trims, it is reasonable to state that ignition misfires do not have a significant impact on them, whereas fuel-related issues create a significant impact.