[kerpyw]

My Jeep died as I was driving in to town yesterday


The odometer had just reached 500 miles and the engine suddenly stopped running while I was driving. I was able to coast into a parking lot and when I tried to restart it the motor would turn over briefly then stop cranking. It was displaying every fault message possible. They took it to the dealer but they have not figured it out yet.


Anyone else hear of such a problem? I couldn't find it among any of the posts here. I am also worried since I see so many problems among the posts

 

[Thorpeland]

Yikes, scary! I haven't had any issues. A couple others had something which sounded similar. I think they had to replace the on board computer on one... maybe? Hope they get you fixed up and it's your last bad experience.

 

[kerpyw]

Well I guess we dodged a bullet there. Apparently there was an electrical connection on the fuel injection harness and another on the main CPU harness that were not completely locked together. It appears that all is well now and we will pick up the car this afternoon.

Seems like bad connections are a rather common theme among the service complaints. Perhaps they need some additional training at the factory over in Italy?

 

[Thorpeland]

Whats the build date on your Jeep? Earlier builds had more of these issues which seemed to be credited to the training process on the assembly line.

 

[26921]

Was it 500 or 5,000 miles?

 

[The Trailhawk]

Well I guess we dodged a bullet there. Apparently there was an electrical connection on the fuel injection harness and another on the main CPU harness that were not completely locked together. It appears that all is well now and we will pick up the car this afternoon.

Seems like bad connections are a rather common theme among the service complaints. Perhaps they need some additional training at the factory over in Italy?

I am glad to hear everything is okay and it was a simple fix!! Keep us updated.

 

[raz-0]

Check your build date. check wires on the firewall behind the intake manifold for damage.

Earlier build dates can have the issue with the crushed BCM wiring harness by the firewall. It causes shorts. This can garble can-bus communication which can throw tons of errors. Eventually the shorting will destroy the BCM which can cause any kind of weirdness up to total unresponsiveness.