nicholsbradley
Well-known member
Thank you
Sponsored
Sponsored
sailorz
Active member
Unfortunately, I suspect the dealership will probably be in the same situation. They will stick the USB in and wait. Maybe it kicks off, may not. I doubt you want them holding onto your truck for a week trying to get the dumb thing to take an update.
MikeYQM
Well-known member
- First Name
- Mike
- Joined
- Jul 3, 2021
- Threads
- 4
- Messages
- 117
- Reaction score
- 59
- Location
- Moncton NB Canada
- Vehicles
- 2021 F-150 Platinum Powerboost | 2013 BMW M3 Comp
I’m growing concerned, that even after updating with FDRS, the OTA will not be fixed. There have been several OTA since my 2.4.1 equivalent manual update and I have yet to receive any. Widget still says I’m stuck on 1.7.1.
I wonder if there’s something on Ford’s end that needs to reset the OTA update “push” after a failure.
I wonder if there’s something on Ford’s end that needs to reset the OTA update “push” after a failure.
PadU235
Member
Never thought of that. It would explain why ford says they can't update it and then someone doing a manuel update is able to wait it out and get the update to take.
Never thought of that. It would explain why ford says they can't update it and then someone doing a manual update is able to wait it out and get the update to take.
Sponsored
BHunted1
Well-known member
- First Name
- John
- Joined
- Mar 17, 2021
- Threads
- 2
- Messages
- 400
- Reaction score
- 104
- Location
- Sumner County TN
- Vehicles
- 2021 Ford-150 Platinum Hybrid
- Occupation
- Retired
After many dealership failures, they got the go ahead to replace the apim. They did some updates and I did the rest. Been holding off for a bit but have a question.
I know some of you had new apims too. After doing updates via fdrs, have any of yaz received any otas at all? I have received nada. Don't think the mothership contacted my truck since months ago after failing 1.7.1 and jamming it up which led to the new apim.
I’m kinda pist because was hoping things would start by themselves like need be. Over 12k on truck and not even a year and what a pain it has been. So anyone?
I know some of you had new apims too. After doing updates via fdrs, have any of yaz received any otas at all? I have received nada. Don't think the mothership contacted my truck since months ago after failing 1.7.1 and jamming it up which led to the new apim.
I’m kinda pist because was hoping things would start by themselves like need be. Over 12k on truck and not even a year and what a pain it has been. So anyone?
Snakebitten
Well-known member
- First Name
- Bruce
- Joined
- Jun 19, 2021
- Threads
- 3
- Messages
- 1,521
- Reaction score
- 923
- Location
- Coastal Texas
- Vehicles
- 2021 F150 Powerboost Platinum
Here you go sir:
It could be that TCU update that is holding you up on getting further update availability?
I could be wrong but the Telematic Control Unit is "the embedded system onboard the vehicle that wirelessly connects to cloud services"
That was a quote from Google.
If it's even remotely accurate, having an update created by Ford is them saying we need to update the module on the truck that plays a role in us using OTA.
Perhaps others here with a better understanding will correct me where I'm wrong.
Having said all that, your historical data shows that you did a ton of updates just a few days ago, and even included a TCU update. But it shows "unsuccessful"
RapidRedRick
Active member
- First Name
- Rick
- Joined
- Jan 19, 2022
- Threads
- 0
- Messages
- 29
- Reaction score
- 6
- Location
- Northern Virginia
- Vehicles
- Ford F150 Platinum Powerboost
I did some digital surgery on my truck 7 days ago with a 2 day FDRS license and a Nano. Took a few steps forward, got Sync 4 software version to go from 20312 - 243 to 21281 – 244, and a few steps the other way, lost heated steering wheel and heated seats functionality. I’m getting ready to place another order for an FDRS license, so I thought I would check a few things first.
Using the FordPass - Scriptable Widget – I went and took a look at the Vehicle Module Info. Pretty cool feature of this widget, and as I understand it the data comes directly from Ford’s server. In this server data I found 8 different modules that had one or two lines of code with spaces,, ugh. I hadn’t run Forscan in a while, so I ran it and saved the Module Configuration log to compare Strategy lines in the Forscan module data with the Strategy lines from the Fordpass Widget. About an hour later I updated my module data in the Fordpass Widget. The first thing I noticed was there were now only 3 modules instead of 8 modules with spaces in code. Guessing that going into Forscan triggered the module updates from the truck to the server. What I can’t understand is why are the Strategy lines from my Trucks data (Forscan) different than the data from the Ford Server (Widget)? Shouldn't they be the same? Does this indicate that the updates made to the truck modules are not going to the Server?
Using the FordPass - Scriptable Widget – I went and took a look at the Vehicle Module Info. Pretty cool feature of this widget, and as I understand it the data comes directly from Ford’s server. In this server data I found 8 different modules that had one or two lines of code with spaces,, ugh. I hadn’t run Forscan in a while, so I ran it and saved the Module Configuration log to compare Strategy lines in the Forscan module data with the Strategy lines from the Fordpass Widget. About an hour later I updated my module data in the Fordpass Widget. The first thing I noticed was there were now only 3 modules instead of 8 modules with spaces in code. Guessing that going into Forscan triggered the module updates from the truck to the server. What I can’t understand is why are the Strategy lines from my Trucks data (Forscan) different than the data from the Ford Server (Widget)? Shouldn't they be the same? Does this indicate that the updates made to the truck modules are not going to the Server?
| FORSCAN DATA | FORD SERVER (Widget data). |
| PCM - Powertrain Control Module Strategy : ML3A-14C204-NEG | Strategy : ML3A-14C204-NEH |
| GWM - Gateway Module A Strategy : ML3T-14H021-ALE | Strategy : ML3T-14H021-EKK |
| APIM - Access. Protocol Interface Module: Strategy :MU5T-14G676-CA | Strategy : MU5T-14G676-EG |
nicholsbradley
Well-known member
Yea I did do a ton. Almost 12 hours worth. I did try the
Here you go sir:
It could be that TCU update that is holding you up on getting further update availability?
I could be wrong but the Telematic Control Unit is "the embedded system onboard the vehicle that wirelessly connects to cloud services"
That was a quote from Google.
If it's even remotely accurate, having an update created by Ford is them saying we need to update the module on the truck that plays a role in us using OTA.
Perhaps others here with a better understanding will correct me where I'm wrong.
Having said all that, your historical data shows that you did a ton of updates just a few days ago, and even included a TCU update. But it shows "unsuccessful"
I did do allot almost 12 hours worth. I tried the TCU a couple of times but was unsuccessful. Might try again this weekend maybe it was a bad update.Here you go sir:
It could be that TCU update that is holding you up on getting further update availability?
I could be wrong but the Telematic Control Unit is "the embedded system onboard the vehicle that wirelessly connects to cloud services"
That was a quote from Google.
If it's even remotely accurate, having an update created by Ford is them saying we need to update the module on the truck that plays a role in us using OTA.
Perhaps others here with a better understanding will correct me where I'm wrong.
Having said all that, your historical data shows that you did a ton of updates just a few days ago, and even included a TCU update. But it shows "unsuccessful"
JEB
Well-known member
- Joined
- Aug 15, 2021
- Threads
- 0
- Messages
- 576
- Reaction score
- 393
- Location
- Northern Illinois
- Vehicles
- 2021 F-150 Lariat Powerboost
Two things could be at work here.
First, you used a Nano. It is corrupting the as-built data. Because of the corruption, there could be differences between the local data (retrieved by FORScan) and the as-built data (retrieved by the widget) in the short term until the truck self-reports its local data and corrects the as-built data.
Second, FORScan sometimes holds onto old data if you stored a profile from a prior scan. Delete the existing stored profile and try scanning again. See if you see different strategies reported.
Sponsored
imnuts
Well-known member
- First Name
- Mark
- Joined
- Mar 1, 2021
- Threads
- 7
- Messages
- 657
- Reaction score
- 127
- Location
- Dirty Jerz
- Vehicles
- '21 502A Powerboost 4Ă—4
- Occupation
- Facilities Engineer
Is there a confirmed way to get the cloud AsBuilt days updated properly without one of the more expensive adapters? I have spaces and garbage data in the XML download from Motorcraft and I'd like to fix it if I can.
speedracercjr
Well-known member
Most people....stupid ass truck and the stupid ass restart loop.
Thekameleon
Active member
I not one of those people. I'm stuck on 1.7.1. I have a Platinum Hybrid and I just keep the USB in the port hoping that one day it will kick off.
Last edited:
speedracercjr
Well-known member
I was there, for a very long time and then randomly one day it kicked over and I got past 1.7.1. That's gotta be the hardest part, once you get updated to 2.1 you'll probably be able to update easily from there on out. I'm stuck getting to 2.3, my usb start consistently but I get stuck in "restart truck to finish" loop.
