laurasmith3
Fiat Bravo Crankshaft Sensor Issue
Summary of the thread
A 2012 Fiat Bravo with a diesel engine is experiencing issues such as a check engine light, reduced engine power, and increased fuel consumption. An OBD reader indicates an error related to the crankshaft to camshaft reference value. The problem is likely due to a faulty crankshaft sensor, a common issue with this model. The recommended solution is to have the sensor diagnosed and replaced by a professional workshop, which resolved the issue effectively.
Did this summary help you solve your problem?
4 comment(s)
laurasmith3 (community.author)
I was reading online that the crankshaft sensor could be the cause. How difficult was it to diagnose definitively, and what was the fix?
charles_steel6
To be honest, I didn't mess about trying to diagnose it myself. I'm no mechanic, so I took it straight to a workshop. They hooked it up to their proper diagnostics kit and confirmed it was the crankshaft sensor pretty quickly. Apparently, it's a common issue. They replaced the sensor, cleared the code, and it's been running sweet as a nut since. Just go to the workshop and let them have a look.
laurasmith3 (community.author)
I took it to a local garage, and you were spot on. It was the crankshaft sensor. The reference value was off, and they replaced it. Cost me about 340€, but the car is running like new again. Thanks again!
rmh_community_comment_box_header
community_crosslink_scanner_headline
community_crosslink_scanner_intro
community_crosslink_scanner_title
community_crosslink_scanner_price
community_crosslink_rmh_headline
community_crosslink_rmh_intro
community_crosslink_rmh_title
community_crosslink_rmh_subtitle
community_crosslink_rmh_brand
FIAT
community_crosslink_rmh_model
BRAVO
charles_steel6
That sounds suspiciously like what happened with my Bravo. I didn't get the exact same error code, but the symptoms are bang on – engine light, felt like I was driving through treacle, and the fuel consumption went mental. Have you checked the crankshaft sensor? That was the culprit in my case.