The key fob for my 1997 Expedition stopped working suddenly. I replaced it's batteries, but still no response. I tried to reprogram the fob using the instructions I found on this forum, but I couldn't get the RAP module to go into it's programming mode (5 key cycles within 10 seconds, doors lock and unlock three times). Thinking it may be a RAP module issue, I removed the module for visual inspection. It didn't show any obvious sign of failure, but I was wondering if there are any tests I could perform on the module before replacing it. I have a multi meter, but do not have access to the Ford Star diagnostic tool called for in the service manual. Thanks

 

Easiest way to diagnose this is to get another FOB off eBay. That way if your FOB is bad you've got a new one, but if the FOB isn't bad you have a spare.

 

The problem is, as I see it, that the RAP module doesn't go into it's programming mode. That would prevent me from programming a new fob if I did get one, and it leads me to believe that the problem is not the fob, but rather the module itself or its peripheral wiring.

 

Did you check for any blown fuses?

 

I checked fuse #4 and #8, both testing good. I found an inexpensive, used RAP module on Ebay with the same part number as the one I'm replacing, so I took a chance and bought it. I hope it's the answer. I'll post the results when it arrives. Thanks for your help.

 

Did you ever hook up a scantool and check for codes?

 

I have a generic scan tool (ODBII), but not the Star tool referred to in the workshop manual. The star tool is a little too pricey for me. The scan tool I use shows no codes.

 

If its a scantool that works with a PC or mobile device, try to use it with the app FORScan, it shows codes from all modules.

 

My scan tool only has an OBDII connector and doesn't work with a PC or laptop.
Thanks for the suggestion though. I'll look into a scan tool which works with a laptop, and using that app. Maybe its something I should be using, going forward.

 

I recommend OBDLink MX Bluetooth, as it supports all the network protocols including both HS and MS Can out of the box, and its very fast in polling times. Its 99 bucks on amazon or ebay

 

I just ordered a scan interface (ELM327) to use with my laptop. The thought of being able to read individual module codes is intriguing. Wish I had looked into this earlier. Thanks
Skauber!

 

Skauber
In a "cabled" scan interface, I looked for something that could be used with the FORScan app and worked with Windows 10. In a BT, I would want something ios compatible.

 

ODBLink does offer a wifi module instead of bluetooth, which would work with iOS. iOS is unfortunately too closed in order to work with bluetooth devices like these... The generic ELM327 interfaces are a bit hit and miss, and might also require some mild modification in order to access MS Can network protocols. But that might not be an issue on a 1. gen '97 Expy, I don't think they used CAN network on the early model years.

 

From my reading, the CAN bus exists on all post 96 vehicles with OBDII. If this is true, my 97 Expedition has to have it. But to a larger issue, upon my first "read through" of all the information I came across, I became intimidated. I have a large learning curve ahead. I hope there's a "CAN bus for Dummies" book out there.

 

It could be, I haven't been digging around in the networks of the 1. gen much yet, so I can't say for sure. I thought the CAN bus protocol came in the 2. gen and the earlier used a different network protocol, but I can't be sure and I can't be bothered to dig out the factory workshop manual...

Anyway, it's not so difficult, mostly plug and play, but if you need MS CAN, you may have to add a switch to your ELM327 interface.