100% Free

No Scanner Needed

Carly logo

Carly Community

jonasbaumann1

Crankshaft Camshaft Reference Value Error

I'm having trouble with my 2010 Ford F diesel. The check engine light is on, and I've noticed reduced engine power, poor engine response, and higher fuel consumption. I ran a scan and got a 'Crankshaft to Camshaft Reference Value' error. I'm suspecting it might be a defective crankshaft sensor. Has anyone else experienced something similar?

4 comment(s)

michaelhoffmann8

Greetings! I had a similar issue with my 2014 Opel Astra, albeit with a petrol engine. The symptoms you describe – engine light, reduced power, poor response – mirror my experience. The error code pointed towards a timing issue, possibly a misfire. Did you check the camshaft position sensor in addition to the crankshaft sensor?

jonasbaumann1 (Author)

Thanks for the insight! I haven't checked the camshaft position sensor yet. Where exactly is it located, and is it easy to test? Could a faulty timing chain also cause this crankshaft to camshaft reference value error?

michaelhoffmann8

The camshaft position sensor is typically located near the camshaft, often on the cylinder head. Its accessibility varies depending on the engine configuration. While a defective sensor is a likely cause, a stretched timing chain could indeed throw off the crankshaft-camshaft synchronization, leading to that error. Given the potential complexity, I'd recommend consulting a qualified mechanic to diagnose it properly before replacing parts indiscriminately. This will also rule out any ECU issues, although it is unlikely. Better safe than sorry, since the cost of a timing chain replacement can be significantly higher than the cost of a sensor replacement.

jonasbaumann1 (Author)

Thanks a lot for the detailed advice! I appreciate you sharing your experience with the Astra. I'll take it to a workshop to have them diagnose the issue properly. Turns out it was the crankshaft sensor that was defective. The repair cost me 340€, but at least the Ford is running smoothly again!

Join the discussion now: