On the road in Oregon today and out of the "blue" my 2012 F350 6.7 through Trouble Code P0196 today while cruising along at slow 60 on the Freeway. Went about 15 miles to Baker Oregon and hit the O' Reilly Auto Parts. The great guy at the counter was happy to check what Code and what it was for. Came out to be Oil Temperature Sensor. While driving to Baker I checked the on Screen Oil Temperature Gauge and it was running 170 to 174 degrees. Pretty cool I thought.....

Bottom line..... I reset the Code and drove another 250 miles today without a re-occurrence. I have no idea what caused the Code and if I never see it again I'll be happy. 15,000 miles plus and this is the first HICCUP to date.

GARY

 

Yeah thats pretty cool temp.I think my oil temp is around 190 when up to temp..In winter it may take a good 45 minutes to get there but thats where i level off when unloaded winter or summer.

Just thinking out loud here,were you only driving for a short periodof time?Just wondering if the sensor is actually bad since Im usually 190 ish..If you were only driving fior a short while then thats pretty normal.

 

Rob,
When she through the Code I had been driving for about 30 minutes on Interstate 84 on moderate hills with Truck Camper and Harley Hauler Trailer on behind. Ambient temp was in the mid 30's. Seemed like pretty cool Temp to me too. However, after resetting the Code in Baker Oregon I watched the Oil Temperature for another 30-40 miles and it never went above 178 degrees in the Blue Mountains. Maybe its running too cool!?!?!?!?

GARY

 

Yeah Idk.I would think you would be above that but Idk.Im driving mostly flat on the interstate around here and same temps.Im always 190 after driving for a while.But who knows.A lot of different variables here,but I would think going up mountains towing you would get up to temp fairly quickly.Im just wondering if you are really at about 190 and the sensor IS bad and is giving you an erroneous reading?Im not exactly sure how the sensor works but maybe it sent the wrong voltage output or something and tripped the CEL?
Im sure some smarter members here will answer this for you.