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

[R3tro GT]

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.

I just got ABS-24.12.0 yesterday

Sponsored

 

[npole]

Continuing on this thread. WAL settings (activated via ForScan) wouldn't sent back to the servers for months (I was monitoring AsBuilt remote data), until I've got a new update few days ago (PT-25.11.1) and then the remote server got updated, so (as mentioned in the first post) the remote server updates are happening right before (or around) a new update is pushed (that makes sense to preserve your current settings before they get overwritten). I'm not sure why it didn't happened with a specific update mentioned in the previous posts (also experienced by others), as with that update I "lost" WAL and had to enable it back.

 

[rugedraw]

When an vehicle receives an OTA, the server interrogator polls the module and reports the config back to the mothership. However, I don't think the interrogator will poll the enite module network......only the module(s) that is being updated with the OTA packet.

So if you make changes to the APIM and get and OTA for the BCM, the config may not change on Ford's side to reflect what you did in the APIM.

This is just my theory, but it is the only way I have been able to explain why the config only sometimes and not always get updated after an OTA.

 

[npole]

It shouldn't be, because the change that got reverted last time (and with a specific update) were contained in the same module of other changes that didn't got reverted. I didn't found a valid explanation, although there must be one. Not critical as mine got reverted only one time across ten updates or such.

Sponsored