Maybe this can help:

 

Thanks for the info but I have read it from a 15 RAM fine. Just getting an error on the 21 Cherokee. I have seen some posts here about reading the PIN and programing a remote but it was on earlier models.

 

Hi @kent0 ,

See full step-by-step instructions here: https://www.jeepcherokeeclub.com/th...reads/programming-extra-key-fobs-using-alfaobd-step-by-step.250206/post-3035701

 

I just noticed your image with the security issue.... The 8+2 Security Gateway Bypass cable is just a passive cable to eliminate the SGW module from the chain and shouldn't be the cause yet that error does sound like it could be involved....

Question... What OBD2 adapter do you have? The vLinker MC+ or the OBDLink MX+ ? Or do you have some other adapter? Note, the adapter must be able to speak to the Medium Speed (MS) CAN as well as the standard high speed CANBUS. If you're using a generic adapter or similar, I'd look possibly there. The time-out message may be the adapter timing out on the buss. (in AlfaOBD, what's your timeout value set to and your baud rate?)

 

I just noticed your image with the security issue.... The 8+2 Security Gateway Bypass cable is just a passive cable to eliminate the SGW module from the chain and shouldn't be the cause yet that error does sound like it could be involved....

Question... What OBD2 adapter do you have? The vLinker MC+ or the OBDLink MX+ ? Or do you have some other adapter? Note, the adapter must be able to speak to the Medium Speed (MS) CAN as well as the standard high speed CANBUS. If you're using a generic adapter or similar, I'd look possibly there. The time-out message may be the adapter timing out on the buss. (in AlfaOBD, what's your timeout value set to and your baud rate?)

I said I have a security bypass, but it is not the bypass cable. I actually have a connection to the star connector, basically hopping on the CANBUS after the security gateway. I have seen some Youtube locksmith videos successfully program Cherokee remotes through the star connector but they already had the PIN. I can connect to the RF Hub, read system ID, read system status, and tell it to Locate Learned Keys, so communication seems to work, just not read the PIN.

As for my adapter, it is a bluetooth OBDLINK MX(Older, not the MX+) I didn't realize AlfaOBD had settings for communications, I never had to adjust them before but it is set at the default 115200 / 100ms. I will try changing the timeout to see if that does anything. You mention it needs to read Medium and High speed bus. Is that over the same wire? The star connector adapter is just 2 wires.

 

At that point, you are only on one bus, for a lot of OBDii functions you need to be able to hop between the CAN and the MS-CAN busses, the MX can do this just fine, but only with the proper Security Bypass Cable. The Security Gateway didn't exist before 2019 MY KLs...

 

Reporting back, I was able to read the PIN with AlfaOBD and the star connector cable!

I ended up attempting to program the FOB and entering a made up PIN. I had a 1 in 100,000 chance of getting it correct and of course that failed with invalid PIN. Then I attempted to read the PIN and it worked showing me the PIN!

Just for fun, I disconnected/reconnected and tried reading the PIN again and received the same error about the time delay not expired. I then tried to program with a made up PIN, got an error about an invalid PIN again. Tried to read the PIN and it worked again.

I did it twice to make sure the PIN it gave me was not the made up one I entered and it wasn't. I'm not sure why, but trying to program it must open it up so the PIN can be read.

Anyway, after getting the PIN I was successfully able to program my new FOB.