Confirmation: AsBuilt data is uploaded to the remote servers right before an update

[npole]

To contextualize what's this about. Ford has a database of our cars settings named "AsBuilt", accessible here: https://www.motorcraftservice.com/AsBuilt/
As mentioned already in other thread, the name suggest that those values are "As Built", so the factory settings, static and useful to revert them in case you have changed something: THEY ARE NOT.

That database is the repository of the current settings (right before a new update), so in case of a OTA (network update), those settings (even those modified/added via ForScan) are preserved and applied to the new software.

We were debating how often those settings are uploaded to the remote server and now I have an answer: the settings are uploaded right before an update is delivered. It works like this: an update is available > the current settings are uploaded to the servers > the upload is sent to the vehicle (and eventually installed). Even if you don't install the update (manual installation) the settings are already stored remotely.

How do I know: I had the changes I did before sent to the server, but then I did more changes after an update and they didn't get updated on the server. I monitored the changes on the website, they never hit the server, until today: I got the notification about a new update and the settings on the remote servers have been updated (until yesterday they were not).

To resume: the "AsBuilt" data on the server is the car settings right before a new update is sent out. It's neither the "stock" settings, nor the current settings (if you changed anything after an update).

Sponsored

 

[npole]

Oh and if anyone is curious about what update I just received, It's this: ABS-24.12.0

https://static.nhtsa.gov/odi/tsbs/2024/MC-11006019-0001.pdf

apparently a almost year old update, I don't know why I got it only now.. maybe because of the EU market.

 

[roadpilot]

I've both received OTA updates and applied many myself via FDRS/Mongoose (S650 and F150), and I can assure you that the AsBuilt data is not ALWAYS updated immediately before these events.

 

[npole]

I've both received OTA updates and applied many myself via FDRS/Mongoose (S650 and F150), and I can assure you that the AsBuilt data is not ALWAYS updated immediately before these events.

If you receive a new OTA update, the current settings are sent to the server (no matter if the update is applied to the vehicle or not).
Did you experienced the website to not reflect the current settings right after an OTA update has been received?

 

[roadpilot]

If you receive a new OTA update, the current settings are sent to the server (no matter if the update is applied to the vehicle or not).
Did you experienced the website to not reflect the current settings right after an OTA update has been received?

Correct. But that was at least a couple of years back (F150), so who know if/what has changed.

 

[npole]

It may have changed, as of now I've found some of my mods there (because I had few updates between), then made some changes recently (weeks ago) and they didn't hit the server until today (as I mentioned in the first post), so I'm pretty confident that that's how it works, and it makes sense: the settings stored on the server have to reflect the current settings before applying the update, otherwise those settings won't be preserved.

 

[roadpilot]

... and it makes sense: the settings stored on the server have to reflect the current settings before applying the update, otherwise those settings won't be preserved.

Many settings AREN'T preserved. That's well documented across this and the F150 forums.

 

[npole]

Many settings AREN'T preserved. That's well documented across this and the F150 forums.

I guess it happened when the current settings aren't being uploaded remotely. So far (as of me) they are all preserved (I mean the ForScan mods) except for the color settings (dashboard), do you have any example of which one aren't preserved?

 

[roket]

this is why i have two read-only copies of my factory as-built data, before i even did the BCM update

 

[smurfslayer]

Good information, thanks for posting!

 

[roadpilot]

I guess it happened when the current settings aren't being uploaded remotely. So far (as of me) they are all preserved (I mean the ForScan mods) except for the color settings (dashboard), do you have any example of which one aren't preserved?

Again, see the F150 forums and here. Tons of posts about people losing thier mods after updates.

 

[npole]

Again, see the F150 forums and here. Tons of posts about people losing thier mods after updates.

But this forum (and post) is about the S650 Mustangs. Do we have anyone who have lost their ForScan (mods) after an update or anyone who didn't found their settings uploaded to the server right before an update?

 

[smurfslayer]

The two things can and probably are true.
1) there is a pre-upload to asbuilt db with changes in the OTA update
2) not everything is copied or triggers a pre OTA update change to the as built db.

That’s why we back up our modules in FORSCAN with the best of intentions.

 

[npole]

It's always good to do backups, however neither ForScan backups, nor saving the AsBuilt tables would be the definitive solution: ForScan backups will preserve the current state (to revert everything you need to go step by step backward and do it manually, remembering what you changed); AsBuilt data will contain your modifications... you say: I can save the initial AsBuilt data so I can always revert everything to stock, that's not true because the official OTA updates could change the stock settings sometime and can use the unused addresses for additional features/settings.

Sponsored