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

[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?

Sponsored

 

[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.

 

[mhoffman54]

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;

Yup. Your 1.7.1 is stuck. Shows as "Pending". Have you tried manually updating it in Sync 4?

The same update was successfully downloaded and then cancelled on 12/11.

 

[abd79]

Yup. Your 1.7.1 is stuck. Shows as "Pending". Have you tried manually updating it in Sync 4?

The same update was successfully downloaded and then cancelled on 12/11.

I’ve done a master reset and basically started from scratch. My auto update and notifications can’t be enabled, the schedule can be set but then reverts back to undefined on its own and when I click on update status it says it’s checking for an update but then comes back saying I’m up to date.

 

[heffer86]

Yup. Your 1.7.1 is stuck. Shows as "Pending". Have you tried manually updating it in Sync 4?

The same update was successfully downloaded and then cancelled on 12/11.

Are these screen just dealers can see? I'd be willing to pay for a subscription to see this data.