That tsb was pulled by Ford a long time ago because it didn't work. You just have to leave the USB in there. Countless people here have done it. Make sure it is formatted to exFAT, name the usb something simple like sync, and leave it in there until it decides to kick off.
/
You might want to take the wife out for coffee or a drive to see the sites or ice cream a few evenings a week just until the update kicks off.
Yep I just bought that at $102 so yes that is a good price, darn!
Sweet! Was the PMI quick or did it take hours?Posting this about my trials tonight with the IPC update, in case it helps someone else.
I bought a 1 month subscription to FDRS a few weeks ago. A couple days left as of today, had checked that I had an IPC software update showing so I thought I'd do it. All started well, the USB stick ran as it should, and said updated successful and to remove the stick and clicked that the install was good. Thought "that was easy", but then...
The install continued post USB removal (verification step I think?), saying something like "shut and lock all doors with key and wait 10 minutes for modules to sleep". So I did that, but I did leave the hood open with the PS running on the battery. After waiting 15 minutes, came back and told it to finish. It really went to crap from there. The instrument cluster went black, started clicking, the FDRS said fail to load update, and then said to shut the doors and wait 10 minutes like before. I figured, oh, it wants to try again. This time I shut the hood too. Waited 20 minutes. FDRS update failed again, and then gave me some option like to reload software or exit, and exit was default so I did that. This message showed up at some point during all of this:
Figured no big deal, I'll run a self test: A message with a whole bunch of gobbly goop showed up. Tried clearing the CMDTCs and that didn't work. Figured no-big deal, I'll run PMI and say "no" to the module being the original, that didn't work as it didn't recognize the module. IPC is purple now and I can't communicate with it. I can hear clicking behind the instrument panel under the steering wheel, about 1 click per second. So, I figure I would disconnect the battery for ten minutes. Reconnected the battery, the clicking stopped, the instrument panel came to life about like normal. Tried to clear CMDTCs again and got this:
Looked up the SSM on the right side, which didn't really help. Finally, ran PMI and it updated correctly and cleared all the DTC. So, I'm not sure if by not closing the hood I messed up, or if it just messed up on its own. Computer and PS and all that were good, so was voltage (over 13). But the clicking noise which prompted me to disconnect the battery seemed to be the key and allowed PMI to do its thing, and then of course running PMI to bring the IPC back to life fully and update the software that way worked.
I thought for a moment I was going to have to PM rugedraw or JEB or Jessie etc. Thanks to them, and all the others on here who know this stuff cold, I didn't go into a sheer state of panic, but I was getting a bit nervous.
The PMI took not even 2 minutes total and it said updating software for only several seconds. I think the software download and update had already happened via USB, but something messed up during validation that fubar-ed it all up. So I don’t think the PMI had to do much other than “get things in order”. I don’t have any software updates showing now.
I just updated to FDRS 45.5.1 with an active subscription from previous version and updated one of my vehicle modules. Download and Login was fine, no issues. It gave a couple of VCI and J2534 interface error messages upon reboot with just the Mongoose connected to the USB but not the vehicle. I was afraid the Mongoose wasn't going to work since it said things like “can’t recognize J2534 adapter” etc. When I connected Mongoose to the vehicle and hit ok on the adapter selection screen it worked fine and updated a module on my Escape.
