@Livnitup the dealer tells me those updates are for if I had an optionally installed subwoofer (which I don't). Does this sound plausible to you? Thanks

 

No, not at all. The subwoofer is configured in the asbuilt values of the ACM but it wouldn't show a software update for your VIN unless it was applicable to your VIN. The GWM has absolutely nothing to do with a subwoofer. Like I said before though....it appears as they were successful updating the GWM & ACM yesterday so the fact that they're still showing as available for your VIN means one of two things in my opinion:
1. Either Ford's database wasn't updated correctly after they did this and that's why they're still showing
2. There are additional GWM & ACM updates available

Note: when I suggest Ford's database maybe wasn't updated correctly I'm not suggesting the dealership did anything wrong here; it's an automatic process that happens in FDRS upon successful completion of a module update that clears the selected module from the list.

Edit: the ACM update may address an issue with the subwoofer (if you had one) but the GWM is entirely separate from that

 

@Livnitup Thank you for this. In your past experience, typically how long does it take for a completed update to drop off of FDRS once completed? Is it possible that it takes 24 hours or more for that to happen or is it more or less immediately after being applied? They aren't bringing my truck back until Thursday, If it's not too much of a problem for you, would you be willing to check my VIN again tomorrow morning to see if those updates have dropped off of FDRS? If they are still there tomorrow morning I think I will call them back and have them try to apply them.1FTFW1E89MFB00484 Once again thank you so much for your help.

 

The updates drop off the list immediately upon completion when Ford's servers record your module's firmware information. I would only be concerned about the GWM update because if there is an additional one for that to be done then it should be done since this will aid with the OTA update process.

 

Yes, but keep in mind only DTCs in the intended target will cause OTA updates to fail. For example, a U code in the IPC would prevent an update from being applied to the IPC, but not the APIM.

OTA updates seem to get issued in consecutive order though, so if OTA update X is an update for something specific and you have a DTC preventing it from installing, than it is unlikely you will get OTA update Y and Z for other modules in the meantime.

It wouldnt be so bad if OTA updates didnt cause DTCs. So far, Id estimate half of the OTA updates I received caused some sort of communication loss error as things reboot after an update. Without ForScan to clear away OTA generated DTCs Id probably still be on 2.1.0.

One thing Ford could do which they might have already is change the tolerance for network communication timeout faults between modules. Theres been 3 GWM updates so far but no release notes.

Every F150 owner should just be issued a copy of ForScan and a 10mm socket with their vehicle.

 

I think it's that DTCs in the target module might cause an OTA issue. If OTAs are failed by DTCs, it has to be about specific ones. I have had an IPC DTC for months, and received two OTA updates targeting the IPC in that time.

The June 15th OTA I got was 2.7.4 and that targeted the IPC, but the DTC was there before and after.

I just mention it because I see enough of people in this thread getting worked up on stuff and going to their dealer or whatever, and I don't think having a DTC is immediately a cause for concern over getting an OTA update. But if you start to see failed OTA updates, it may be worth reviewing.

 

In the help section of the Ford Pass app there is a live chat feature from 8-5 weekdays that is somewhat useful for some owners. It you are convincing, the Ford representatives there will escalate your case and create a ticket.

In your situation, at this stage, you are better to keep it with a Ford dealer for service. I would suggest considering changing to another Ford dealership if possible because unfortunately you may be in a shop full of mechanical experts who are not necessarily I.T. experts.

Depending where you are some independent shops such as Ford fleet providers have all the skills and tools to perform the service. You would have to ask in advance to have the labour credited by Ford though if you get warranty work performed outside of the dealership network. I know it is possible, but dont know the exact process.

 

Interesting points by both of you. All this just leads me to believe I'm right about my theory on my particular truck. I had 2.7.3 "try" to install on 6/9, again on 6/13 and again on 6/21. My OTA dashboard says the update failed all three times, yet when I go into my touchscreen, my truck says it's running on 2.7.3. As you can see in my history below, I had no IPC DTCs any of those days. On the 20th and the 23rd, my truck reported low voltage DTC's which I know can cause the update to fail. However, when I click "update status" to see why the update failed, it says "ecuId:1824utcTime:1655842108". I think my truck is stuck in a loop trying to install an update onto itself that it already has because Ford's OTA servers think the initial update failed. It still states the OTA retry is pending, and there is no campaign expiration date. It hasn't tried to install the update again since 6/21, but when it does, I think the same thing is going to happen.

The good news is, on 6/9, it also sent a TRM module update via OTA. While my dashboard says that update also failed, I did take out my boat Sunday and I got no annoying messages on my dash while driving, so I am guessing the TRM update also went through successfully.

 

I have the impression the OTA failure rate is more associated with persistent DTCs. Opposed to historical DTCs which are stored and preserved as a snap shop but do not affect the outcome of an attempted install. That might be what you were seeing in the OTA Dashboard.The WSM suggests OTA updates should fail if continuous DTCs are present in the intended target, but maybe the team creating OTA updates changed the process to deliver better solutions.

 

I had the same problem a month ago. The new software installed but the success confirmation failed to upload back to the server. I posted my solution several pages ago and will try and add a link. The solution was to essentially just reset all the main modules with ForScan and do a Sync 4 master reset. You can also reset everything manually by disconnecting the vehicle battery / batteries (if you have a PowerBoost).