Drove again today with new scanner hooked up. Sitting at stop lights my tach is pegged at zero and scanner is reading 530-550RPM at warm running temp. The rest of my instrument cluster is working correctly, is there something else that can recalibrate the tach?
2006 Yukon XL 2500 6.0L dies/stutters at cruising speed randomly
- Thread starter jmlhd7
- Start date
Disclaimer: Links on this page pointing to Amazon, eBay and other sites may include affiliate code. If you click them and make a purchase, we may earn a small commission.
Scottydoggs
Full Access Member
pretty common for the stepper motors in the cluster to fail. that would be my guess. scanners dont lie, that info comes right from the PCM.
Another update: while driving this weekend, it finally died on me again while sitting at a stoplight and then would crank and not start. Took about 6-7 tries and finally got it to start. Had the scanner in the car and hooked up real quick and read the pending codes, lo and behold, P0335 - Crankshaft Position Sensor A Circuit code. I suspected it was the crank sensor but glad to have confirmation. Ordered one off RockAuto yesterday and will install after it comes in and hopefully it solves my issues.
Hopefully that's all it is -- the sensor itself. After you change it do yourself a favor and do a CASE relearn so the new crank sensor knows where the cam sensor is. That will help avoid possible long crank times and random misfires.
thats the plan. i've got a buddy who is a mechanic who has a scanner tool capable of doing that, so I plan on going over there after I swap it out. It should be at least driveable after changing before the relearn, right?
If it starts, yes. We hear about the occasional no-start after changing a crank sensor, but it's rare. Don't sweat it.
Got it swapped and started driving it today. on the way to work the CEL started flashing on and off intermittently and had a code of p0300 random cylinder misfire. But after about 5 min of driving it went off. Still haven't done a re learn yet and wonder if those two are related. Called the dealer in town and they wanted $155 to do a relearn (one hour of labor). Have a guy who worked on my acura who is a family friend who said I could use his scanner to do a relearn so plan on taking it over there sometime soon to do a relearn.
The P0300 could absolutely be related to a discrepancy between the two sensors. Let us know how the relearn goes, and if you experience any issues afterward.
Went and did a relearn over lunch at my buddy's house. Drove it pretty ******* the way back to work and didn't get a flashing CEL or any pending codes. Driving home will be the true test as I get up to 70mph and set the cruise and it has happened each of the 3 times I've done that so far.
On a different note, my tach is still off, to where when sitting at Idle it is reading 0RPM, so off like 500rpm. Do you suspect this is more just coincidental that my Dash cluster started acting up (on only my tach) at the same time at this Crank sensor issue, or is there something else I can do to get my Tach working again?
Compare the rpm value that a scanner reports, to the analog tach reading; if they're significantly different you likely have your answer. This gen of clusters (2003-2006) suffers from failed or inaccurate stepper motors (there is one for each gauge). You can always temporarily substitute a cluster with known good gauges for validation.
