mrhemi wrote:
Well this may be a bit of a long post, but I am looking for ideas from those who have gone down this rabbit hole before.
History: 2006 Liberty CRD, a couple of times while I was out of the country, it quit on the wife and left her stranded (in her words, all the lights on the dash lit up). Fortunately, both times she was able to get it started and home after sitting for a bit. At this point I have no idea if it threw any codes, I am still trying to diagnose this over the phone. Ordered a Crankshaft Position Sensor as these symptoms would point to that. Also, I managed to talk my wife through (over the phone) bleeding the air out of the fuel filter just in case. Neither of my CRD's have lift pumps (on the list) but do not suffer from air ingress. After that ordeal, she when for a test drive and it quit once or twice again, but she managed to limp it home and in the garage, where it would not even crank. At this point it had to wait until I got home.
First observation, with ignition on, waiting for glow plug sequence, I notice a couple of many unusual warning warning lights. The ESP light remains on, as well as the traction control disabled (which would not change state when the button is toggled). Also, the security system warning lamp stays lit solid. The engine will not crank from the ignition switch. The only code present was P0725 which indicates a type of RPM error, which I attributed to (maybe in error) to the last time it ran badly, limping home. I cleared that code and it did not return.
The starter relay was by-passed and the starter cranks fine, but no start. It appears the ECM is not satisfied for a run command.
I have inspected the wire harness in all the usual places and all of the grounds that I can find and found no issues. For good measure, I replaced the ignition switch and actuator mechanism as I had them on hand. Still no change.
At this point I rechecked for codes and none were present. Of note though, when I select live data, I do get an RPM value of zero, as expected, and a TPS position of 25%. The TPS tracks to 100% when the go pedal is depressed.
Then, curious about the ESP and Traction Control lights, I checked for ABS codes and found the following: U0100 (loss of comm), U0401 (invalid data), U140E (improper configuration), C2202 (VIN mismatch) & C2100 (low voltage). The final low voltage code was probably due to the battery being low by this point. I cleared all the codes, charged the battery fully and rechecked for codes. They all returned except for the C2100. It seems to me, although this may be an incorrect assumption that this is displaying loss of communication between various modules, however the fact that the code reader can connect successfully indicates the CanBus link is valid.
In following through the FSM procedures for many, but not all of these indicators, it is appearing as a failed ECM module. Unfortunately both of my CRD's have GDE tunes, so if I have to replace an ECM I am not sure if I can get that replaced due to the current EPA over reaching over sight. Although both vehicles are registered in Ontario. More complications to the issue at hand.
Now this is what I propose as my next step. Since I have two CRD's, I can swap the questionable ECM into the CRD that runs and see if it will start (I know, for only a few seconds due to the VIN / Key mismatch), and pull the codes. I do not want to swap the functional ECM into the broken Jeep for fear of frosting the good ECM. Update: I swapped the ECM from the problem Liberty into the other functional Liberty. Good news, it started and ran for a few seconds before the security feature shut it down due to VIN mismatch. No codes were present other than the VIN mismatch. So, it appears my ECM, with a GDE tune is good, although now the search continues for the comm error.
I will reach out to Keith at GDE for his suggestions as well.
Any comments and suggestions from the board are welcomed. Thanks in advance.
Login
Register
FAQ
Search
