It took them multiple tries, but they were able to successfully update your APIM and get your truck unstuck yesterday. Yes, you are still not fully up to date. However, when your trucks VIN is due for an update, now you will actually get it sent as your truck is no longer stuck with the broken software that would not accept OTA's. It is just a matter of waiting for them to get sent to you. There is noting you can do to trigger an update being sent to your truck.

 

Hey guys,
Can someone please look up my VIN and let me know what is going on? I still do not have full-screen CarPlay
Current Sync Version: SYNC 4, Software Version: 22177_PRODUCT Revision 473
Build Date: May 10, 2021
VIN: 1FTFW1E55MFB61255
I tried FDRS today, and I did not have any APIM updates available.
But I did see this error:
IPC - U0554 : 00 : 08
U0554 = Invalid Data Received From Accessory Protocol Interface Module
FT : 00 = No Sub-Type Information
ST : 08 = Not a Current DTC Fault previously detected, not currently present
This module uses GGDS Format 00 DTC descriptions.
CW: INVALID DATA RECEIVED CW: INVALID DATA RECEIVED

 

Thanks for that @rugedraw I greatly appreciate you doing that.

 

There is nothing wrong with your truck. Ford is just slow pushing out updates.

I am surprised FDRS did not show any updates, though. I see the network scan performed. Where there any updates at all? Sometimes, you have to perform update to get other updates to show up.

 

Hello rugedraw,
I have a Audio Update which asks about a Subwoofer, then does nothing.
This morning I updated the BCM and I also have an available Instrument Cluster Panel update but it looks like it will take 3-4 hours.
Other than that, nothing else.
That APIM update error, nothing to be alarmed about?
Anything else I can do with FDRS?
BTW appreciate the info!
--Vinny

 

You probably should not have done the BCM update. It may be that faulty update that Ford hasn't removed from FDRS that has caused trucks with the quad headlight to burn the lights out. Too late now, though.

If you are showing an IPC update, then yes, you need to take the time to do it. Once you do it, it is very possible that several other module updates will pop up. Without the IPC up to date, it will not allow to you to perform certain updates that require the updated IPC to be there first. It's a PITA, but a necessary PITA. If you have trouble getting the IPC to install, lmk. It is possible that you have over-updated your truck to a point where the IPC update will have to be can bus'd in which will take even longer. If you install certain updates without doing the IPC first, it can cause problem updating the IPC later on down the line.

I would not concern myself with the APIM DTC until you after you perform the IPC update. If then, you still don't see an APIM update pop up when you do another network scan, then you might have to get it looked at or try running the module repair process on it with FDRS.

 

DOH on the BCM - It did mention it was for the tailgate module, who knows really.

I tried once for the IPC last weekend, and it was approx 3.5 hours, then after all that, it failed. The truck rebooted as normal and was fine, even though it went through almost 90k blocks or something along those lines. Also, it did it through the Mongoose cable, not a USB. Can it be done with USB or only the cable? I can start this process tomorrow evening when I get home.

 

Oh, sh*t. Lmk if it fails again. I am not knowledgeable enough to tell you how to fix it, but I can direct you to someone that is. I am not sure if in your case it can be can bus'd in at this point. Just in case it cannot, do you have your as-built data backed up in case you need to go backwards?

Sync 4 can only be updated via the Mongoose cable. Some modules (like the APIM & TCU) need to be done via USB, but the only way to get the files on the USB is to perform a network scan with FDRS and then FDRS will tell to you insert the USB and download the files directly on it.

 

I have not had any update attempt in the last 90 days.

Update History:
Sent 2.7.3 on Jun 26 2022 - Failed
Received Recall 22S17 on Jun 11 2022 - successful
Received 2.7.1 on Jun 6 2022 - successful
Received 2.6.0 on Jun 2 2022 - successful
Received 2.1.1 on May 17 2022 - successful
Received 1.7.1 on May 5 2022 - successful

At this point should I continue to be patient or should I chase a manual update from a dealer?

 

Ford does not pay dealers to update modules. it will be very pricey to pay them to do it as these updates take hours. It is cheaper to buy a Mongoose OBDII tool and do it yourself. Up to you.