(RESOLVED) FordPass - SecuriAlert, OTA Updates dissappeared

[iceman77]

Just as the title says, SecuriAlert as well as OTA Updates disappeared from my FordPass application about 2 days ago. I did a manual GWM update to "EKB" revision via FDRS which was successful. Not sure if that caused it, or there is a glitch at Fords "mothership" servers:

What's even more concerning is that @tonesto7 "hidden" OTA message shows following:

Truck does not show any DTCs to any modules related to OTA and SecuriAlert. Anyone experiencing same/similar issues. Especially those who performed manual GWM update ?

Sponsored

 

[iceman77]

I fixed it this morning. Seems FDRS uploads and modifies your As-Built after your initial Network Scan. It uploads changes made to module configurations as well as SW revisions of your modules. In my case, the GWM SW revision got corrupted during scan (or upload):

All I needed was to launch FDRS and re-run network scan and that corrected my As-Built SW revision info for GWM:

And voila! OTA and SecuriAlert is back in business!

 

[heffer86]

I fixed it this morning. Seems FDRS uploads and modifies your As-Built after your initial Network Scan. It uploads changes made to module configurations as well as SW revisions of your modules. In my case, the GWM SW revision got corrupted during scan (or upload):

All I needed was to launch FDRS and re-run network scan and that corrected my As-Built SW revision info for GWM:

And voila! OTA and SecuriAlert is back in business!

Great you got it working. Where did you pull those config files from on your PC?

 

[iceman77]

Great you got it working. Where did you pull those config files from on your PC?

You can pull your As-Built either from PTS (if you have access to it) or motorcraft website here. I managed to save a copy before GWM update so I had data to compare against. Took me a good while to figure this out...

 

[JEB]

I fixed it this morning. Seems FDRS uploads and modifies your As-Built after your initial Network Scan. It uploads changes made to module configurations as well as SW revisions of your modules. In my case, the GWM SW revision got corrupted during scan (or upload):

All I needed was to launch FDRS and re-run network scan and that corrected my As-Built SW revision info for GWM:

And voila! OTA and SecuriAlert is back in business!

Does this suggest that you should always do a follow-up network scan after every module update to make sure nothing in your As-Built data got corrupted?

 

[iceman77]

Does this suggest that you should always do a follow-up network scan after every module update to make sure nothing in your As-Built data got corrupted?

i think this was an isolated case caused perhaps by network disturbance (by weak wifi signal to my laptop) or a bug in FDRS software. Don’t know for sure. Should you get such issue as described in OP, a simple network scan would fix it

 

[JEB]

i think this was an isolated case caused perhaps by network disturbance (by weak wifi signal to my laptop) or a bug in FDRS software. Don’t know for sure. Should you get such issue as described in OP, a simple network scan would fix it

Got it. Thanks. Good catch on your end.

 

[DeltaDeuce]

i think this was an isolated case caused perhaps by network disturbance (by weak wifi signal to my laptop) or a bug in FDRS software. Don’t know for sure. Should you get such issue as described in OP, a simple network scan would fix it

So if I download that as built file how do I upload it into FDRS?

 

[iceman77]

So if I download that as built file how do I upload it into FDRS?

You can’t! FDRS submits all HW/SW revision info automatically at the end of network scan

 

[BHunted1]

I fixed it this morning. Seems FDRS uploads and modifies your As-Built after your initial Network Scan. It uploads changes made to module configurations as well as SW revisions of your modules. In my case, the GWM SW revision got corrupted during scan (or upload):

All I needed was to launch FDRS and re-run network scan and that corrected my As-Built SW revision info for GWM:

And voila! OTA and SecuriAlert is back in business!

As mentioned in other thread, both of mine are gone now too. I’m pretty sure I reran net scan again. Just happened to notice exactly what you mentioned here. Ugh.

 

[BHunted1]

Reran the test several times this morn. No joy. FP still missing security and update screen.

 

[MikeYQM]

In my last scan, I had the blank APIM version in FDRS, but still have FP updates & Security.

 

[iceman77]

Reran the test several times this morn. No joy. FP still missing security and update screen.

Whats important, that you shut down FDRS between individual Network Scan sessions. It seems only the intial Network Scan result is reported to Ford servers. Any subsequent scan does not. At least this was my observation

 

[BHunted1]

Whats important, that you shut down FDRS between individual Network Scan sessions. It seems only the intial Network Scan result is reported to Ford servers. Any subsequent scan does not. At least this was my observation

First I heard that. Pretty sure I tried that but I have one more day. So will try first thing in morn. My brain hurts.

 

[BHunted1]

Following icemans procedure above resolved my missing headlight, securealert stuff missing. Also gave back the data to the widget ap.
Thanks Pete!

Sponsored