2021+ F-150 FORScan List / Database / Spreadsheet ?

[uavmx]

Hi, I will try and get them off of mine but there has been a total of 2 IPMA updates. he first IPMA update resolved a clarity/Resolution issue with the camera system. The second was not specific to the camera in motion but that was included. Also if you have the latest update and still do not have motion you will need to adjust as built in the APIM as well. I used a 21.5 as a guide. You could maybe use the forscan dropdown style configuration also to adjust yours to remove the speed limits. I just found it easier the way I went with it since I knew the speed restrictions were resolved in those truck.

Unfortunately the IPMA will likely not get OTA for these updates as they are so large and can cause too many issues if they do not complete. Since the IPMA controls so much of the vehicle. It is one of the most important modules in the Truck. If you look at the operation charts for the 2021 almost all runs through it. If it were to fail during an update it would be a big problem for ford and this update is huge. I do understand a portion of the time required for the update is due to the Canbus data speed limitations but the update took me 6 hours or so on a 360 cam IPMA. Could be less for the rear cam.

My understanding(Could be wrong) The ethernet is only for OTA, the gateway downloads the update(8GB limit) and then transfers the update through ethernet to the module. Modules with Ethernet. APIM, TCU, IPMA(If Update is Small enough), Gateway(Some that have an early build that have not received OTAs as of now need to have the dealer manually update their Gateway as it was the issues causing OTAs to not work), IPC, B&O Amp. Again I could be wrong but its what I understand since the ethernet has a much higher data transfer speed.

I have received all the power up updates including the latest 2.1.1 and prior the 2.1.0 and neither address the IPMA. The 1.7 was an APIM update to 21146. I did that one manually though, I was to anxious to wait.

The 1.7 power up was to get the APIM to build 21146 for 21 builds. The 1.6 was a gateway update. I cant say what the prior one was. I believe it was a TCU(Telematic Module) update to improve responsiveness.

There are several updates available for early 21 builds that are dealer visit required. I would suggest to those of you that have not gone to a dealer or have FDRS access to log in and get all of those done and I believe that will help with those of you not receiving OTA. I am receiving OTAs and my truck is so far from stock its hilarious when I get in and see a successful update.

One Note to those with a APIM build previous to 21146. 21146 will not even show in FDRS until the Gateway update is completed, If you have a truck that has not received any updates I would suggest strongly you be the ones to go get your truck fully updated. A lot of the updates depend upon other updates being there.

Sorry if this is a bit of a rambling post, I just got on and am going freestyle. I am trying to help as best I can. I know it can be frustrating to not have updates others are getting but I really suggest you follow the advice I gave to get the updates done. I think once you do that you'll be ready to start receiving updates.

Also be careful when comparing to 21.5 trucks for as build date. They are different and some do not have the start stop they removed it so they can ship them faster.

Side note any of those with a July build that can not activate Fordpass you need to go to the dealer for a gateway reconfigure. There is a TSB/SSM/GSM about it.

A) how the heck do you know all of this...great info

B) what you're describing really feels like why the older trucks aren't getting bluecruise. They shipped them with APIMs that can't do it, and they're struggling to get OTA updates to work on the older APIMs....

Sponsored

 

[Jesse-Infotainment]

A) how the heck do you know all of this...great info

B) what you're describing really feels like why the older trucks aren't getting bluecruise. They shipped them with APIMs that can't do it, and they're struggling to get OTA updates to work on the older APIMs....

A - Its just me having a job that allows me to spend all day with these trucks and Ford Products. Plus I have a 2021 STX that is now a lariat. I have done everything you can imagine. I did the 8" to 12" upgrade, I even made it passive entry with push to start, Fixed DSS LED headlamps(Fully Functioning) upgrading to the Adaptive DSS LED soon(Waiting on the height sensors), Wireless charging, rain sensing wipers, 360 Cam, Digital Cluster, Rear Brake assist, Bliss, Power Fold mirrors, Will be adding Adaptive cruise with the hopes of getting Blue Cruise added also. Ive aded the auto dim rear view and side view. Will be adding B&O system and power running boards. I would have added power tailgate but it requires new tailgate. That will be last If I do it.

B - Your Apim is identical to the ones being shipped now. I can confirm this to be true. THe software build 21146 is limited to 21 trucks and 21223 is 21.5 trucks. The modules are different starting in July. The Apim is not one of those that is different though. I have confirmed I can install the 21.5 software on a APIM from early builds.

I believe the blue cruise will be sent out but I do want everyone that has not had any updates to please heed my warning to go get the dealer to update your truck ASAP. A lot of these updates that are rolling out have a prerequisite of the previous updates being installed.

The best thing you can do is get your truck fully updated now. There were MANY updates for early build trucks for modules that I believe to be not OTA capable.

These updates are very clear for the dealer in FDRS> There is a tab after they hook up that will list all the modules that need to be updated. It is clear for them. The IDS way required them to go into every module and see if an update was available.

 

[abd79]

A - Its just me having a job that allows me to spend all day with these trucks and Ford Products. Plus I have a 2021 STX that is now a lariat. I have done everything you can imagine. I did the 8" to 12" upgrade, I even made it passive entry with push to start, Fixed DSS LED headlamps(Fully Functioning) upgrading to the Adaptive DSS LED soon(Waiting on the height sensors), Wireless charging, rain sensing wipers, 360 Cam, Digital Cluster, Rear Brake assist, Bliss, Power Fold mirrors, Will be adding Adaptive cruise with the hopes of getting Blue Cruise added also. Ive aded the auto dim rear view and side view. Will be adding B&O system and power running boards. I would have added power tailgate but it requires new tailgate. That will be last If I do it.

B - Your Apim is identical to the ones being shipped now. I can confirm this to be true. THe software build 21146 is limited to 21 trucks and 21223 is 21.5 trucks. The modules are different starting in July. The Apim is not one of those that is different though. I have confirmed I can install the 21.5 software on a APIM from early builds.

I believe the blue cruise will be sent out but I do want everyone that has not had any updates to please heed my warning to go get the dealer to update your truck ASAP. A lot of these updates that are rolling out have a prerequisite of the previous updates being installed.

The best thing you can do is get your truck fully updated now. There were MANY updates for early build trucks for modules that I believe to be not OTA capable.

These updates are very clear for the dealer in FDRS> There is a tab after they hook up that will list all the modules that need to be updated. It is clear for them. The IDS way required them to go into every module and see if an update was available.

You sir are amazing! Most people wouldn’t go through the trouble of adding all the items you have. Nice to know there are still a lot of tinkerers out there.

Are you able to check a VIN and see if there are any issues with the OTA status or module versions/calibrations? Mine I believe is stuck on an update after 1.6 and FORD has been no help when trying to understand the issues.

My VIN is: 1FTFW1ED0MFB66211

 

[Jesse-Infotainment]

You sir are amazing! Most people wouldn’t go through the trouble of adding all the items you have. Nice to know there are still a lot of tinkerers out there.

Are you able to check a VIN and see if there are any issues with the OTA status or module versions/calibrations? Mine I believe is stuck on an update after 1.6 and FORD has been no help when trying to understand the issues.

My VIN is: 1FTFW1ED0MFB66211

I am going to try and be more active this coming year. I havent been because of different things. Unfortunately the only real way to know is if they plug in. It polls the modules plus if I pull your vin on my bench it will show in the history. Anything done if I were to pull your vin in Oasis or in FDRS would be reflected in the vehicle history. I try not to pull a vin unless absolutely necessary with the newer stuff.

The best and most accurate would be to plug in and open FDRS. Do you know when yours was built?

 

[mhoffman54]

Hey everyone. Like most of us, I have made a handful of changes via Forscan, both from the common list, as well as testing a few things. On 12/13, my truck received PowerUp 2.1.0 via an automatic OTA update. Since the update, it has not had cellular connectivity. FordPass doesn't work, Oasis shows the last status update as 12/13, 5 minutes before the PowerUp. Without that connectivity, my maps don't update, traffic doesn't work, weather doesn't work, the in-vehicle Ford Assistant doesn't seem to be able to understand my commands half the time, and of course I can't start my vehicle from my phone.
I work at a dealership and spoke with service, who told me they could get me in sometime next week, but in the meantime I was wondering if there is anything that you could think of in Forscan that could've caused this, or any ideas on how I could fix it with Forscan before I have to take it in. I've noticed a handful of values that I never touched that reference connectivity. The one thing that I did change a week or so ago was I enabled HD radio. Didn't do anything for me, as I don't have the HD receiver, but I'm wondering if changing that back may fix my issue. I'm not opposed to restoring my default values either, if need be. I would imagine that I'd need to restore APIM, maybe IPC as well? If anybody has any insight, I would greatly appreciate it!

 

[abd79]

You sir are amazing! Most people wouldn’t go through the trouble of adding all the items you have. Nice to know there are still a lot of tinkerers out there.

Are you able to check a VIN and see if there are any issues with the OTA status or module versions/calibrations? Mine I believe is stuck on an update after 1.6 and FORD has been no help when trying to understand the issues.

My VIN is: 1FTFW1ED0MFB66211

My build date was 04/21.

playing around with the FordPass API the following OTA info is available. Seems like for me 1.7.1 was cancelled for some reason. See below;


OTA Info
{
"displayOTAStatusReport": "UserAllowed",
"ccsStatus": {
"ccsConnectivity": "On",
"ccsVehicleData": "On"
},
"error": null,
"fuseResponse": {
"fuseResponseList": [
{
"vin": "1FTFW1ED0MFB66211",
"oemCorrelationId": "FLARE-PRD-SOFTWARE-FNV2-458591-457085",
"deploymentId": "c4a641d2-781d-4611-9a4b-733b3bb6a391",
"deploymentCreationDate": "2021-12-08T19:33:10.892+0000",
"deploymentExpirationTime": "2021-12-15T19:33:10.892+0000",
"otaTriggerExpirationTime": "2021-12-16T20:03:05.793+0000",
"communicationPriority": "High",
"type": "NEW_FEATURE",
"triggerType": "SOFTWARE",
"inhibitRequired": false,
"additionalConsentLevel": 1,
"tmcEnvironment": "PRD",
"latestStatus": {
"aggregateStatus": "cancelled",
"detailedStatus": "OTAM_S1011",
"dateTimestamp": "2021-12-11T23:51:06.987+0000"
},
"packageUpdateDetails": {
"releaseNotesUrl": "https://mmota.autonomic.ai/1/bytest...98222423-189e6aa7-5d14-4800-92a3-0418d9d85e2f",
"updateDisplayTime": 0,
"wifiRequired": false,
"packagePriority": 1,
"failedOnResponse": "none",
"cdnreleaseNotesUrl": "http://vehicleupdates.files.ford.co...98222423-189e6aa7-5d14-4800-92a3-0418d9d85e2f"
},
"deploymentFinalConsumerAction": "Cancelled"
}
],
"languageText": {
"Language": "English (US/NA)",
"LanguageCode": "ENU",
"LanguageCodeMobileApp": "en-US",
"Text": "FordPower-Up 1.7.1\n\nNavigation, other enhancements\n\nNavigation will automatically make helpful destination suggestions (but you can turn that off if you like), plus new cloud connectivity combines conversational voice command recognition with internet-based search, so you get the latest info with almost every request.\n\nApple CarPlay® compatibility will display on-screen turn-by-turn navigation in your instrument cluster.\n\nThe user-profile icons on your SiriusXM® with 360L radio are a bit bigger, and there were a couple of bug fixes.\n\nOngoing updates like these help ensure that you’re always driving the best possible version of your F-150. Keep in mind that update availability varies by model."
}
},
"tappsResponse": {
"vin": "1FTFW1ED0MFB66211",
"status": 200,
"vehicleInhibitStatus": null,
"lifeCycleModeStatus": {
"lifeCycleMode": "TRANSPORT",
"oemCorrelationId": "0",
"vehicleDateTime": "2021-07-28T18:56:21Z",
"tappsDateTime": "2021-11-24T21:04:49.246Z"
},
"asuActivationSchedule": {
"scheduleType": "",
"dayOfWeekAndTime": null,
"activationScheduleDaysOfWeek": [],
"activationScheduleTimeOfDay": null,
"oemCorrelationId": "",
"vehicleDateTime": "",
"tappsDateTime": ""
},
"asuSettingsStatus": null,
"version": "2.0.0"
},
"updatePendingState": null,
"otaAlertStatus": "YOU ARE ALL SET"

 

[Jesse-Infotainment]

Hey everyone. Like most of us, I have made a handful of changes via Forscan, both from the common list, as well as testing a few things. On 12/13, my truck received PowerUp 2.1.0 via an automatic OTA update. Since the update, it has not had cellular connectivity. FordPass doesn't work, Oasis shows the last status update as 12/13, 5 minutes before the PowerUp. Without that connectivity, my maps don't update, traffic doesn't work, weather doesn't work, the in-vehicle Ford Assistant doesn't seem to be able to understand my commands half the time, and of course I can't start my vehicle from my phone.
I work at a dealership and spoke with service, who told me they could get me in sometime next week, but in the meantime I was wondering if there is anything that you could think of in Forscan that could've caused this, or any ideas on how I could fix it with Forscan before I have to take it in. I've noticed a handful of values that I never touched that reference connectivity. The one thing that I did change a week or so ago was I enabled HD radio. Didn't do anything for me, as I don't have the HD receiver, but I'm wondering if changing that back may fix my issue. I'm not opposed to restoring my default values either, if need be. I would imagine that I'd need to restore APIM, maybe IPC as well? If anybody has any insight, I would greatly appreciate it!

I had this happen. I had to remove my truck from my account in the ford pass app and then re add it

 

[Jesse-Infotainment]

My build date was 04/21.

playing around with the FordPass API the following OTA info is available. Seems like for me 1.7.1 was cancelled for some reason. See below;


OTA Info
{
"displayOTAStatusReport": "UserAllowed",
"ccsStatus": {
"ccsConnectivity": "On",
"ccsVehicleData": "On"
},
"error": null,
"fuseResponse": {
"fuseResponseList": [
{
"vin": "1FTFW1ED0MFB66211",
"oemCorrelationId": "FLARE-PRD-SOFTWARE-FNV2-458591-457085",
"deploymentId": "c4a641d2-781d-4611-9a4b-733b3bb6a391",
"deploymentCreationDate": "2021-12-08T19:33:10.892+0000",
"deploymentExpirationTime": "2021-12-15T19:33:10.892+0000",
"otaTriggerExpirationTime": "2021-12-16T20:03:05.793+0000",
"communicationPriority": "High",
"type": "NEW_FEATURE",
"triggerType": "SOFTWARE",
"inhibitRequired": false,
"additionalConsentLevel": 1,
"tmcEnvironment": "PRD",
"latestStatus": {
"aggregateStatus": "cancelled",
"detailedStatus": "OTAM_S1011",
"dateTimestamp": "2021-12-11T23:51:06.987+0000"
},
"packageUpdateDetails": {
"releaseNotesUrl": "https://mmota.autonomic.ai/1/bytest...98222423-189e6aa7-5d14-4800-92a3-0418d9d85e2f",
"updateDisplayTime": 0,
"wifiRequired": false,
"packagePriority": 1,
"failedOnResponse": "none",
"cdnreleaseNotesUrl": "http://vehicleupdates.files.ford.co...98222423-189e6aa7-5d14-4800-92a3-0418d9d85e2f"
},
"deploymentFinalConsumerAction": "Cancelled"
}
],
"languageText": {
"Language": "English (US/NA)",
"LanguageCode": "ENU",
"LanguageCodeMobileApp": "en-US",
"Text": "FordPower-Up 1.7.1\n\nNavigation, other enhancements\n\nNavigation will automatically make helpful destination suggestions (but you can turn that off if you like), plus new cloud connectivity combines conversational voice command recognition with internet-based search, so you get the latest info with almost every request.\n\nApple CarPlay® compatibility will display on-screen turn-by-turn navigation in your instrument cluster.\n\nThe user-profile icons on your SiriusXM® with 360L radio are a bit bigger, and there were a couple of bug fixes.\n\nOngoing updates like these help ensure that you’re always driving the best possible version of your F-150. Keep in mind that update availability varies by model."
}
},
"tappsResponse": {
"vin": "1FTFW1ED0MFB66211",
"status": 200,
"vehicleInhibitStatus": null,
"lifeCycleModeStatus": {
"lifeCycleMode": "TRANSPORT",
"oemCorrelationId": "0",
"vehicleDateTime": "2021-07-28T18:56:21Z",
"tappsDateTime": "2021-11-24T21:04:49.246Z"
},
"asuActivationSchedule": {
"scheduleType": "",
"dayOfWeekAndTime": null,
"activationScheduleDaysOfWeek": [],
"activationScheduleTimeOfDay": null,
"oemCorrelationId": "",
"vehicleDateTime": "",
"tappsDateTime": ""
},
"asuSettingsStatus": null,
"version": "2.0.0"
},
"updatePendingState": null,
"otaAlertStatus": "YOU ARE ALL SET"

Yeah, I believe that to be the 21146 APIM update. If you are an April build I would say you have plenty of updates available. The caellation COULD be related to the gateway module not being up to date. THe APIM update to 21146 is only available to trucks with the gateway fully updated.

Just my thoughts.

 

[abd79]

Yeah, I believe that to be the 21146 APIM update. If you are an April build I would say you have plenty of updates available. The caellation COULD be related to the gateway module not being up to date. THe APIM update to 21146 is only available to trucks with the gateway fully updated.

Just my thoughts.

Sounds like a trip to the dealer to get all these modules updated.

I don’t have FDRS although wouldn’t be against purchasing it and the adaptor if the cost isn’t equal to buying a new truck… ?

 

[Jesse-Infotainment]

Sounds like a trip to the dealer to get all these modules updated.

I don’t have FDRS although wouldn’t be against purchasing it and the adaptor if the cost isn’t equal to buying a new truck… ?

Yeah, I understand. It is expensive after the license and VCM 3.

 

[mhoffman54]

I had this happen. I had to remove my truck from my account in the ford pass app and then re add it

Removing your truck from FordPass and re-adding it corrected ALL the connectivity issues? Even ones that are not related to FordPass at all?

 

[Jesse-Infotainment]

Removing your truck from FordPass and re-adding it corrected ALL the connectivity issues? Even ones that are not related to FordPass at all?

Yes.. because its all related. I forget what I was doing but I did something and lost it all and just removed and added it was back.

Just what I did. You can always wait for service.

 

[mhoffman54]

Yes.. because its all related. I forget what I was doing but I did something and lost it all and just removed and added it was back.

Just what I did. You can always wait for service.

Well, I just tried that. Can't re-activate it at all now.
When I enable debugging it shows a cellular connection too. Doesn't make sense, and confirms to me that it's software related, not hardware.

 

[abd79]

Well, I just tried that. Can't re-activate it at all now.
When I enable debugging it shows a cellular connection too. Doesn't make sense, and confirms to me that it's software related, not hardware.

How do you get the debug data on the screen?

 

[mhoffman54]

How do you get the debug data on the screen?

Hold right skip on both the steering wheel and console for a few seconds. A speaker test will come up. You can either let it go through all your speakers (I did the first time. Had a couple speakers I didn't know I had!), or hit end test. It'll bring up a whole list of debug menus. Hit connectivity to view what is connected and what is disconnected. You can also hit "Test Settings" and turn on Connectivity View or something like that to show the icons I have on my screen there. Green shows it's connected. The icon will be red if it's disconnected.
There's a bunch of things in there that you can play with. The one thing that freaked me out was when I adjusted the screen scaling and it blew it up so big I couldn't change it back. If something like that happens, hold power and forward skip to reboot and you'll be back to normal.

Sponsored