The Complete DIY Guide to Updating Your Mach-E with FDRS

[Robob]

I made sure I re-ran a network test while still plugged in, so it updated with the master server. So now when I check without it plugged into VCI it all matches up.

Sponsored

 

[KevinS]

?

If you mean that there's no date showing...that's the new "normal" going forward after Sync 1049. Just a map version number now. No expiration date.

I’m referring to the actual map version number that is installed.

 

[Mike G]

I made sure I re-ran a network test while still plugged in, so it updated with the master server. So now when I check without it plugged into VCI it all matches up.

Understood...but maybe in two weeks from now it won't.

 

[Robob]

Oh so it doesn’t save the manifest server side at last time of sync and compare to the new versions as they release? I figured once a modules software revision code was stored it would know at the server what you had last time plugged in.
Ty for info though

 

[Mike G]

Oh so it doesn’t save the manifest server side at last time of sync and compare to the new versions as they release? I figured once a modules software revision code was stored it would know at the server what you had last time plugged in.
Ty for info though

Well yes, it does...but with the passage of time it can easily get a little out of sync again if your car isn't reporting it's software status each time you use it. So you could have a software update showing in PTS (as @rugedraw shows for VINs he looks up) but it might not show when you look up your VIN in FDRS without being connected to the car at the time you do the check. Makes sense?

 

[rugedraw]

Well yes, it does...but with the passage of time it can easily get a little out of sync again if your car isn't reporting it's software status each time you use it. So you could have a software update showing in PTS (as @rugedraw shows for VINs he looks up) but it might not show when you look up your VIN in FDRS without being connected to the car at the time you do the check. Makes sense?

@Robob Correct. I have seen vehicle go months before they sync up with the server. When an OTA trigger is sent to a vehicle and it activates, the interrogator will sync the vehicle with the server and provide an updated manifest at that time. At that point, the vehicle verifies the files that the mothership wants to send before they are downloaded. If the files don't match, the OTA trigger will failed with a "manifest mismatch" or "software mismatch" error that can be seen in PTS.

What I am not sure of, is if the interrogator polls all the modules at that time, or only the module(s) associated with the OTA.

 

[Robob]

Makes sense, I will make sure I check with it plugged in every time I renew license to check updates. Thanks again to MikeG and Rugedraw for the info.

 

[Eric_C_Boston]

What exact "stability changes" would this be? If it means less frequent deactivation and fixes the "hug the right lane marker" issue, it would be worth applying. I've got some long trips starting next week and not looking forward to doing them with BC 1.0.

While I have not officially gotten BC 1.4, the updates I applied through FDRS so far has given my car some of the BC 1.4 features. I had problems previously with BC nagging about watching the road when I was watching the road. I also noticed slightly different graphics. I do not know if this is a new action, but when I put on the blinker BC will turn off and will turn on again when I turn off the blinker. I did not really test to see if the "hug the right lane marker" went away, but it seemed to mostly be in a good lane position. I only got nervous and took over when trucks tended to start straying over the lane marker into my lane. I used BC more on a recent roadtrip because it became less annoying.

Another reason not to force enable BC 1.4 with FORScan is the various software pieces needed might not be present and some new features may not work correctly. All the modules involved need to have the updates to fully support BC 1.4.

 

[kennelh]

I've got about 6 hours left on my two-day license, so checked this morning and see there a new GWM and HVAC update available. I received 24-PUD102-SDV-FX via OTA a week ago. Anyone have an idea what this GWM might be for?

 

[737flyer]

I've got about 6 hours left on my two-day license, so checked this morning and see there a new GWM and HVAC update available. I received 24-PUD102-SDV-FX via OTA a week ago. Anyone have an idea what this GWM might be for?

https://github.com/elmedico27/fordpowerup

 

[kennelh]

https://github.com/elmedico27/fordpowerup

Thanks, but I'm wondering what this new GWM update might be for.

 

[benk016]

Thanks, but I'm wondering what this new GWM update might be for.

If you got that OTA, it may just not have updated on the back-end its completed to drop off your FDRS list. Mine got that OTA, but still shows the GWM available too.

 

[kennelh]

If you got that OTA, it may just not have updated on the back-end its completed to drop off your FDRS list. Mine got that OTA, but still shows the GWM available too.

Would this be true if I got it OTA on 2/13 and it wasn't showing up via FDRS on 2/19 (and is now)?

 

[benk016]

Would this be true if I got it OTA on 2/13 and it wasn't showing up via FDRS on 2/19 (and is now)?

Best way to know is to just do a network scan and it will fall off then if it was the same update.

 

[kennelh]

Best way to know is to just do a network scan and it will fall off then if it was the same update.

Yep, it fell off. ?

Sponsored