what is the meaning of this data... cam phaser

[budwich]

This was taken from an old post and I was wondering about what it is saying. In particular what the "cam phaser sol" is trying to indicate? I have seen a p0014 on my truck on occasion but have never seen any freeze frames associated with it. I think I have found that the launch reader has some of the pids (still under investigation). The other thing, somewhat related to coding, is the code potentially related to how fast the desired and actual happen or how much difference might be occurring in the "final event"? The CPAS (I think that what it was... the fitting beside the power steering pump which has to be removed to get at... but maybe I am confused... maybe that's the actual actuator and not the sensor) has been replaced a while back (4-5 years ago, I think). The original wasn't coding, it was more of maintenance check "effort" while doing the water pump since I had things apart at the time. I still have the original as a spare.
Other possible options are electrical as the area has been "touched" from other work dealing with power steering hosing replacement and such a long while back so the connection might have been "beat on" during that effort to make it less than stable connection.

Anyway, this is more of a "request for comment / knowledge" than a must have at this point. I don't I will think I will be doing much in the domain, outside of monitoring any pids that I find, until the spring as the truck will see limited use until then and my work space isn't heated.

Indeed!!

When I first acquired my 2002 back in 2010 it would occasionally set the P0340 as well as a P0014. I learned what they were and how the system operated. Cleared the codes a few times and did my usual oil changes using full synthetic oil. Never removed the CPAS or the position sensor. The CPAS had oil on it and the connector spins. After some time both codes stopped returning as the synthetic oil did its' thing. I have often monitored and recorded the operation of the system. Works fine.

Just sayin'. Others experiences may vary.

View attachment 106002

 

[Mooseman]

Cam Sol Act % is probably the PWM duty cycle of the CPAS to get to the Desired Cam angle. It probably knows or learned what % duty it needs to achieve the desired angle. Probably as long as the Desired and Actual angles are close, depending on the tolerance, it shouldn't trigger a code for over or under advanced cam angle.

Might not hurt to clean the cam sensor. I've seen that happen.

 

[mrrsm]

FWIW... I have your Vehicle programmed into the Snap-On Vantage Pro and can provide the Data as discreet Screen Images of the "Guided Component Descriptions" and ALL Diagnostic Procedures ...if seeing these 29 Images would interest you...

 

[TJBaker57]

Cam Sol Act % is probably the PWM duty cycle of the CPAS to get to the Desired Cam angle.

Exactly. The PID and terminology are as displayed by a Tech II (clone).

I know it works for a 2002 to 2005 P10 PCM. Would need to check my records to see if the same PID applies to later models with different PCMs.

In my own case the duty cycle is high at first then drops back. I assume this behaviour is intended to get the actual angle to the desired position as rapidly as possible.

 

[TJBaker57]

Here is a link to a 2008 4.2L service manual description of P0014.

P0014 — 2008 Chevrolet TrailBlazer 4WD L6-4.2L Service Manual | Operation CHARM

Detailed repair manual for the 2008 Chevrolet TrailBlazer 4WD L6-4.2L.

charm.li

And here is a screenshot of the conditions for setting the code. As seen here it takes a decent amount of time for the code to set. A type B code needs to happen twice in consecutive ignition cycles before the CEL\MIL is illuminated, if memory serves.

 

[TJBaker57]

Here is an image of the relevant screen on a Tech II.

 

[budwich]

I am wondering if there is some limits on the "SOL" in terms of "out of spec"... meaning I wonder if the "extra percentages" to cause the operation is what could trigger the code even though the actual and desired are OK but it took more than "expected" to cause the response. In the graph, if that "spike" shown is say 25% higher (or some limit) than the "hold value" then its codes. That could be because of "inertia" in the actuator (as in poor pressure / mechanical resistance) or electrical (as in poor connection).

ADDED: oops there was a time lag in my viewing / posting.

Interesting so there is both a time and value component to the event, I didn't see that in the GM SI but was fighting a PC update at the same time which was causing / needing restarts. I wonder why there is no freeze frame data captured.

Further, guess if the cmp sensor is poorly reporting the actual angle then that could be another source and as Mooseman suggested, cleaning it could help.