badassjeep wrote:
geordi wrote:
Do you have a ScanGauge connected, or any other type of scan tool feeding on the OBD port?
If so, that is the reason. The CRD doesnt like playing nice with other computers, the data bus is already overcrowded badly.
I do have my Scanguage connected, all three times. I will try to disconnect it and see if it happens. I will report back.
DING DING DING, we have a winnah! The Scangauge is not a "passive" participant on the data bus in this vehicle, and because of the screwy way that Mopar decided to design the computers, bad things happen when another player joins the system.
The ECM and TCM speaks DRB, the ABS and BCM speak another protocol... Who knows for the SKIM and airbag computers. What you experience is the conflict that happens when too many controllers are trying to take control and speak, and the ECM "gets annoyed" and kicks the offender off the system entirely. That is what happens when your Scangauge locks up, it has been ejected from the system. If the Scangauge is not the victim of that, but the TCM is the one that gets kicked... The transmission will be thrown out of gear violently. This is what you have experienced.
Take the scangauge off, and your problems will vanish. The SAME THING will happen with just about any of the inexpensive scanners. The only one that I haven't had this problem with, other than a DRB3 (which I don't own yet) is the super-expensive AutoEnginuity scanner. Before you buy one of those, contact me. I have one that I might be willing to sell.