*** Restricting New Posts to SD Premium Members ONLY *** (09 May 2025)

Just made a new account? Can't post? Click above.

Help us help you. By posting the year, make, model and engine near the beginning of your help request, followed by the symptoms (no start, high idle, misfire etc.) Along with any prevalent Diagnostic Trouble Codes, aka DTCs, other forum members will be able to help you get to a solution more quickly and easily!

2010 GMC Canyon (Chevy Colorado) 2.9 L3 p0017

  • GeekPriest
  • GeekPriest's Avatar Topic Author
  • Offline
  • New Member
  • New Member
More
3 years 4 weeks ago #58211 by GeekPriest
Troubleshooting a 2010 GMC Canyon with the 2.9 inline 4. P0017 code, incorrect cam/crank correlation. The cam solenoid tested bad and was replaced a few months ago, which reduced the problem.

Of note, the problem is INTERMITTENT, and the code will go away for 300-500 miles at a time. (This suggests I can rule out a stretched timing chain for now.)

Does anyone have a known good (I have a 2200 series Pico, so no access to their library) for the cam and crank WITH THE 3-Wire HALL EFFECT CRANK SENSOR? I've found some others but they all show a 2-wire sensor for the CKP.

Thanks for any tips or a known good.

Please Log in or Create an account to join the conversation.

  • Tyler
  • Tyler's Avatar
  • Offline
  • Moderator
  • Moderator
  • Full time HACK since 2012
More
3 years 4 weeks ago #58226 by Tyler
I've got a capture for the two wire CKP, but none for the three wire. :(

Do you have the Freeze Frame data for your P0017 when it resets? The conditions under which it resets may tell you something.

Before you go too much deeper into diagnostics, you might check for crankshaft end play. PIP3694F details the specifications:

static.nhtsa.gov/odi/tsbs/2015/MC-10139336-9999.pdf

The two Canyon/Colorado trucks I've seen with VVT problems were both out of specification according to the TSB, but still got fixed with phasers and chains. In other words, the crank end play needs to be WHOA and not 'meh' to be causing this fault, IMO.

Please Log in or Create an account to join the conversation.

Time to create page: 0.285 seconds