Originally Posted by
wsmolich1
I’m not sure if someone else has found a long term “solution” for this ridiculous issue, but just got off the phone with Justin from MDP, and they stopped playing in this space about 4 years ago when they could no longer get parts for it from Chrysler.
I came to this forum a while ago, but actively returned to reading when my Crossfire started having SKREEM issues. I accidentally stumbled upon a guy, a Mercedes wiz, whose shop is literally 1.5 miles away from me. Twice now (in a 3 year span), my car has experienced the whole SKREEM immobilisation nightmare. It always starts because I use my key to unlock the car when the fob fails to open unlock anything. ,...........
thank you
1) That is easy, the lock cylinder is not grounding the "unlock" line as you rotate the key in the lock, so of course the alarm goes off. Why are you taking the car to someone who does not understand basic troubleshooting? (I can tell you why, because electronic troubleshooting is not being taught ANYWHERE In the USA anymore!)
2) Just call the MSS. Josh and James will get you fixed up in a mater of days.
As to the entire mess....... the complexity is DESIGNED IN. Back around 2000 or so, cars were disappering off European streets at an awful rate. The industry responded with, in our cars, an integrated handshake that the PTCM and SKREEM do to insure the person starting the car is authorized to do so. Once the Diamler/Chrysler divorce happened, tech support disappeared, there is no easy way to talk to those in the know about how the system works.
Guys like Josh dug in and learned on their own. But this takes TREMENDOUS component-level and software level knowledge, those two skills in ONE PERSON are RARE.
There is NO easy fix for this, as the coding in the PTCM expects a response from the SKREEM in the short time allowed by the code. If the SKREEM is dead or if the FOB does not reply to the SKREEM properly, the SKREEM is not going to tell the PTCM to start the car. PERIOD.