npole
Well-Known Member
- Thread starter
- #1
EDIT: This assumption isn't every time accurate, see THIS post in the thread.
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).
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
Last edited: