- November 14: Dodge Durangos and Jeep Grand Cherokees Recalled Over ABS Modules recalls | 6 days ago
- November 12: Chrysler 300 and Dodge Charger Door Panels Warp: Lawsuit news | 8 days ago
- November 8: Dodge Class Action Lawsuit Dismissed news | 12 days ago
- November 7: Dodge Hornet Hybrid and Alfa Romeo Tonale Hybrid Recalled recalls | 13 days ago
- September 30: ZF-TRW Airbag Failure Investigation Closed investigations | 51 days ago
8.0
pretty bad- Typical Repair Cost:
- No data
- Average Mileage:
- 97,100 miles
- Total Complaints:
- 1 complaints
Most Common Solutions:
- not sure (1 reports)
electrical problem
Helpful websites
- No one has added a helpful site for this 2009 Caliber problem yet. Be the first!
A D V E R T I S E M E N T S
Problem appeared intermittent as early as 2016, but nothing that kept it off the road. Car has made a few trips between Michigan and Florida with no troubles. Back in 2010 I fitted fog lamp kit but removed around 2014, with proper fuse and relay for the lamps. Car continued to run well through early 2018.
In late Spring 2018, very strange electrical issue occurred, similar to one or two other descriptions I've read so far. Tachometer goes out, all trouble lights go on. Took to a local reputable shop, with early diagnostic codes such as Transmission Control, so various components related to transmission cooling were replaced, along with the alternator and battery. About the FOURTH trip back to this shop by late September 2018. They said problem went away when they drove it with front grille/clip removed. Just strange!
At this point we've put about $3000 in parts and labor. Suspecting computer control module at this point. Vehicle in storage so decided to start it up in November 2018 - add air to tires, etc, idled and drove short distance for 15 minutes, ran great, then resurfaced at this time after I parked it and tried to restart. Glad I'm no longer depending on this car!
Video attached of idle demo, followed by failure to restart. I disconnected the battery for a few hours at this point (11/18/18), no change in behavior after reconnecting.
- Peter V., Grand Rapids, MI, US