Would be nice if the SKIM feature could be completely removed.
Or at least bypassed.
Somehow the bad guys are able to do it when stealing cars.

What about the 2005 gateway module?
Any hope in repairing those or bypassing them?
(When I dug through the FCM it appears that the SKIM connects through the gateway)

That's good information to know! Keep up the good work.

Any advice from any of you IT experts on what can be done for the poor souls who are having issues with the Front Control Module that seems so far to be no longer available anywhere?
Are there any bench fixes or bypasses available for them?
GDE, Sir Sam, anybody?

My comment in the other thread is that I was planning to grab a FCM from a durango or something similar, which appears to be on the outside the exact same hardware, and then open it up and see if there is anything we can read from it. My hope is that we could get a generic module and then clone it to what our FCM does.

That's good information to know! Keep up the good work.

Any advice from any of you IT experts on what can be done for the poor souls who are having issues with the Front Control Module that seems so far to be no longer available anywhere?
Are there any bench fixes or bypasses available for them?
GDE, Sir Sam, anybody?

Something I've been trying to get around to for awhile, messing with the SKIM. I grabbed a used one from a junkyard and set about reading the memory from it. After much research and experimentation I have found that the eeprom can be desoldered, read, and then the VIN and PIN read in the file.

In the absence of any better ideas, I'd suggest finding a known-good unit or two and using those to build an emulation of the original unit on an FPGA. That's not likely to happen quickly, though, and someone would have to be really motivated to do it. It could also potentially involve the destruction of the good units as part of the process.

Interesting... So does this mean that the VIN and PIN are stored in the EEPROM unencrypted?

I'm wondering what other hardware in the vehicle may take a similar approach.

Something I've been trying to get around to for awhile, messing with the SKIM. I grabbed a used one from a junkyard and set about reading the memory from it. After much research and experimentation I have found that the eeprom can be desoldered, read, and then the VIN and PIN read in the file.

I have also found the factory fresh eeprom file, next step is to load the factory fresh eeprom hex back to the used eeprom, resolder it, and then attempt to program the SKIM to an ECU as if it were a new in box SKIM.

This way a cheap skim from the junkyard can be programmed to work with any Jeep I need it to. If I can figure out the eeprom coding I could even program a used skim to a jeep and then install it and go, but at the very least I should be able to clone a SKIM.

In theory a cloned skim should work with your existing keys.

What did you use to read and reprogram the eeprom? Back when those chips were current technology, the equipment for RW eeprom chips were $400 to $1400 plus the software to run it.

Green Diesel can turn off the skim in the ecm tuning upon request.

When you turn it off upon request, does the keyless entry still work? Or no because the SKIM module is on the WCM there in the column and has to be unplugged before installation?