Well, at 6250 miles, I have joined the (not so exclusive) brotherhood of RAM CTD owner who are driving around with their check engine lights on. I had my 2008 RAM 2500 CTD on vacation in Oregon when it happened. Called the local Dodge dealer to get it looked at. He said it would be two weeks before he could get me in! I told him I was leaving for home the next day. He said "if it was running ok, it was probably nothing and it should go out in 2-3 days". Ten days and 1000 miles later, it's still on.

Is there a way to access the error codes on the 2008 model truck? I tried the "ignition on-off-on-off-on" trick for older years, but got no results.

Thinking about buying an Equus 3100 Innova CanOBD2 Diagnostic Tool from Amazon to get the codes myself before deciding how necessary it is to see the dealer. Anyone have suggestions/recommendation on code readers?

From what I read about cel problems before, and since, my purchase, I am not enthusiastic about wearing a path to the dealer for BS cel warnings!

Thanks for the input!

 

I would drive to the dealer and have them hook up the starscan or witec and ck just for codes. That way you will know if you need to leave the truck.

 

If you at least get the code, it'll narrow it down.

You can either go to the dealer for it, or just hit an Autozone, Advance, etc., and get the code.

I almost guarantee it's gonna be the variable nozzle failed to achieve 100% range of motion. That's the common one.

That means bringing it in and they pull the turbo and clean it and then they tell you to drive it with the exhaust brake on all the time.

Being that it's under warranty, I suggest bringing it in.

 

Had it in to the Dealer today to get the codes checked. Advisor reported that there were several codes (and a couple that they couldn't read?). Said I needed "two O2 sensors, a filter cleaning, and some other stuff". He didn't show any urgency, just told me to make an appointment to bring it is when I have time. It continues to amaze me how casual everyone it about the cel on these trucks. I think I am going to invest in a code reader, though, so nothing serious slips into the equation.