ECU module programming guide using FDRS

[JEB]

Transponder? You a pilot or something? Ya mean key fob?

Ford doesn’t call it a “key fob,” either. Their term is “remote control.” Cumbersome, so I just used the term Chevy uses. Same animal.

Sponsored

 

[DeltaDeuce]

Try battery disconnect. Reconnect, turn ignition ON, if you see SYNC message “restart required”, shut down open/close driver door. wait 30 mins. That’s what worked for me

Another alternative (as per @Snakebitten) is to remove the USB flash drive after vehicle has been shut down.

You just have to see what works out for you!

Ok so I let it run all night long and I don't know that it worked, also don't know that it did not work. Here is what I show this morning on FDRS: (meaning I can't download or run TCU anymore)

Hopefully now I can actually get an OTA, had the truck since May of 2021 and have yet to receive 1 OTA

 

[iceman77]

Ok so I let it run all night long and I don't know that it worked, also don't know that it did not work. Here is what I show this morning on FDRS: (meaning I can't download or run TCU anymore)

Hopefully now I can actually get an OTA, had the truck since May of 2021 and have yet to receive 1 OTA

What is the SW revision of your TCU ? If you PM me your VIN, I can check it for you

 

[iceman77]

Being a powerboost will disconnecting the battery really do anything?

My apologies! Being an EcoBoost owner I keep forgetting that battery disconnect won’t help for the hybrid models. You can still play with FORScan and try rebooting GWM/APIM from there and see if it helps with stuck 1.7.1 OTA

 

[Snakebitten]

If you ran a fresh scan and the TCU was available but no software update was available, THAT'S good news!

 

[DeltaDeuce]

If you ran a fresh scan and the TCU was available but no software update was available, THAT'S good news!

Thanks! That is the case.

 

[Snakebitten]

Kind of wish we had a method for reading each modules current revision.
You would think between FRDS or Forscan it could be revealed?

 

[Jesse-Infotainment]

There is a way to see the current files. Its a pain in the butt.

 

[iceman77]

Kind of wish we had a method for reading each modules current revision.
You would think between FRDS or Forscan it could be revealed?

You can in fact get that information from both FORScan as well as FDRS:

FORScan:

FDRS:

 

[iceman77]

It's the "Strategy" what you need to look for. That is what reflects your executable software level (or version) in your module:

 

[Snakebitten]

I love you guys!

I have in fact looked at the module/software-P/N grid in FRDS. But I remember thinking that I don't know how to map that to anything meaningful to me. Which is really me just being too lazy to build a spreadsheet myself and populate it with every data point possible.

 

[tkljr]

A huge THANK YOU to Iceman for starting this thread and to everyone else for contributing. I was one of the many stuck on a failed 1.7.1. I'm not sure what "Power Up" I'm on now but hopefully OTAs will start again. At least now I have a Sync version showing and CarPlay turn by turn and music thumbnails.

"Patience" may be a helpful note for others My first APIM USB update took a little longer than it should have because I expected the update to start pretty soon after seeing the "Inserted" and "Indexing" messages so I'd yank the USB to try again which seemed to corrupt the drive. Once I left it alone (probably only 3-4 minutes) I would see the "Updating" message.

Yesterday I did all the modules with updates shown in FDRS, this morning I had a GWM update and the TCU with forced APIM. I'm left with GSM which doesn't clear from the list after updating and an ACM update which aborts. It asks "Are you here for woofer install?", I select "No", the procedure starts and then aborts with an unsuccessful "GetFilesFromGivis". Tomorrow should be the last day of access (seems to be the day you purchase the license +2 days) so I'll see if I have any more pending updates.

 

[Snakebitten]

Good job!

 

[speedracercjr]

I'm a stubborn SOB, so I paid another $50 to get my FDRS license re-upped and found this waiting on me. Could this be why it's not kicking off the usb update for APIM? And if so what can I do?

 

[iceman77]

I'm a stubborn SOB, so I paid another $50 to get my FDRS license re-upped and found this waiting on me. Could this be why it's not kicking off the usb update for APIM? And if so what can I do?

Click on Toolbox, select APIM (its under HS3 section) and run Self-Test. See what's the issue and try to clear the fault.

Post a screenshot if you need further assistance

Sponsored