Lightning Software Updates using FDRS

[ziptbm]

Well that "in-process" OTA is likely gonna be on your Check Updates page for a while if you've already done all the updates with FDRS.

I'd call the service advisor and find out what module(s) that OTA was supposed to be updating (have them look at your OTA dashboard). If you updated that same module during your FDRS session...problem solved. It does mean that it will probably show that OTA in the same status on your Check Updates page in Sync until it "expires" from your OTA Dashboard list though.

The naming designation on these OTAs now is making it harder to figure out just what it updated.

What specifically have you asked your Server Advisor to get this kind of information? I just called my dealer and the SA first told me they couldn't get this information and wanted to relay me to BEV support (also worthless), but after pushing to ask around for anyone else there that may know, the SA came back with info from an "OTA Dashboard" that just showed a bunch of numbers and dates that updates were pushed. While the numbers didn't match up to the Priority Update giving me trouble, what's interesting is there was nothing on the date that this update first showed up in their system. And the SA didn't really have any other guidance or information other than to bring in the vehicle.

@Mike G you not only have the magic touch for FDRS, but also for the SAs apparently!

Sponsored

 

[Mike G]

What specifically have you asked your Server Advisor to get this kind of information? I just called my dealer and the SA first told me they couldn't get this information and wanted to relay me to BEV support (also worthless), but after pushing to ask around for anyone else there that may know, the SA came back with info from an "OTA Dashboard" that just showed a bunch of numbers and dates that updates were pushed. While the numbers didn't match up to the Priority Update giving me trouble, what's interesting is there was nothing on the date that this update first showed up in their system. And the SA didn't really have any other guidance or information other than to bring in the vehicle.

@Mike G you not only have the magic touch for FDRS, but also for the SAs apparently!

I'm sorry I didn't see this post sooner and respond.

Service Advisors sit behind a computer all day with PTS on the screen in front of them. All day. So they have all the OASIS messages (Ford releases messages everyday about different problems with vehicles, sometimes with a solution, other times they say they're working on it or the parts aren't unavailable, etc). From this screen they can pull up the Connected Vehicle page to view all the DTCs that have happened in a calendar type format and when they were reported by your vehicle (it reports when you are driving). And there's a page called the OTA Dashboard that will list OTAs and their status going back 60 days prior to today's date. So it will show successes, failures, the modules that were involved, the update notes that the customer sees in Sync, all that. This is an example showing the notes for a recent gateway OTA update, with the dates and times shown for three other previously received updates as well.

Your SA sees all of this (techs can see this too). It sounds to me like you ran into someone who just didn't want to make time for you or didn't know what they were doing.

 

[Mike G]

As happens quite often, new updates seem to be released on Wednesdays for Lightnings (seems to be Friday afternoon for Mustang Mach-Es).

So this morning I checked to find a new IPC (instrument panel) update for the Lightning. That same old broke DSP update is still in the list, but at least something got updated this month. And not to get anybody's hopes up, but an IPC update (along with an IPMA, and an APIM, at the very least) would be a necessary updates to have on the way to getting BlueCruise 1.2 activated. Just sayin'. I don't know that the reason for this particular update is to enable some of that functionality, but I don't know that it isn't either.

EDIT: Given the news this morning I guess I should have said "...on the way to BlueCruise 1.3" instead of 1.2. I guess they are going to skip straight to updating our trucks to the new and improved 1.3 version when ever that rolls out later in the year.

 

[chillaban]

Sounds like this might be the “louder frunk chime plus battery percentage shows on screen” update?

 

[MickeyAO]

Sounds like this might be the “louder frunk chime plus battery percentage shows on screen” update?

It is. When I got home, Sync showed an update. I looked at FDRS before it finished.

 

[Mike G]

It is. When I got home, Sync showed an update. I looked at FDRS before it finished.

So you got this IPC update as an OTA?

I stopped by my dealer yesterday around lunch and had them pull up my OTA dashboard and I had nothing in the queue for downloads. Last OTA for my truck was early June.

 

[Mike G]

So, was out and about this afternoon and when I stopped the truck I got the notification that I was gonna get an update tomorrow morning at my normal 0900 time, and did I want to reschedule?

I was thinking it was time for a burger and fries anyway so I stopped in at my local Whataburger, and after shutting off, the countdown clock started backwards from 120 seconds...

Lunch over and back to the truck (over the required 15 minutes had elapsed by that point).

Well that's another one I didn't need FDRS for. I'm glad they are sending these out. I just wish they'd do the fixes and send them out more frequently.

 

[MickeyAO]

So you got this IPC update as an OTA?

I stopped by my dealer yesterday around lunch and had them pull up my OTA dashboard and I had nothing in the queue for downloads. Last OTA for my truck was early June.

Yes. And when I checked FDRS today, the IPC update is no longer there.

 

[Mike G]

Yes. And when I checked FDRS today, the IPC update is no longer there.

It was gone from my list this morning as well.

BTW there's a new FDRS update to version 36.4.8

Supposedly when you get DTCs on a selftest it should show links to any relevant TSBs or SSMs.

EDIT: I don't know if that means you'd also need a PTS account to see the TSBs and SSMs though. That would make this less useful for independents and DIY'ers.

 

[Mike G]

So this morning the 20th of July the DSP update that was the cause of the popping sound in the truck, that wouldn't clear from the available software list...is now gone.

So hopefully a revised and corrected package will appear soon.

 

[Mike G]

So for those considering getting into doing updates with FDRS I thought I'd post a small update that might help. I was under the impression that one of the firm requirements for running FDRS was the use of a laptop or tablet running Windows 10, as listed in the requirements.

Now, I completely understand that like Windows 10 being partially based on Windows 7...Windows 11 is also based on Windows 10. So you would have thought it was a given. But several months ago there was a Mach-E forum member from the EU who was unable to get FDRS to work on Windows 11, forcing him to wipe and reload Windows 10. Based on that report, I believed at that time that it was not possible, until the subject came up in the VIN check thread over on the MME site.

So several members there posted that they were in fact running FDRS on Win 11 with no problems at all.

So I guess Win 11 is a go. (I'm still on Win 10 with my rig).

 

[mattskr]

So for those considering getting into doing updates with FDRS I thought I'd post a small update that might help. I was under the impression that one of the firm requirements for running FDRS was the use of a laptop or tablet running Windows 10, as listed in the requirements.

Now, I completely understand that like Windows 10 being partially based on Windows 7...Windows 11 is also based on Windows 10. So you would have thought it was a given. But several months ago there was a Mach-E forum member from the EU who was unable to get FDRS to work on Windows 11, forcing him to wipe and reload Windows 10. Based on that report, I believed at that time that it was not possible, until the subject came up in the VIN check thread over on the MME site.

So several members there posted that they were in fact running FDRS on Win 11 with no problems at all.

So I guess Win 11 is a go. (I'm still on Win 10 with my rig).

Yea I’ve been using Windows 11 the whole time. Although - note that if you are using Windows 11 and need to call for support TELL THEM YOU ARE USING WIN 10. They will refuse to help you at all if you mention Windows 11, despite it not having anything to do with my issue. So stupid.

 

[MickeyAO]

Turns out the cheap laptop I have been using for FDRS is Windows 11 Home.

 

[Mike G]

I was assisting a forum member who is doing FDRS updates for the first time. It's all going very well but there was a moment or two of uncertainty after the updates were done caused by the frunk not wanting to close when commanded.

Let me post this so everybody knows. When you have the frunk open to connect the powersupply during updates, there are interruptions to the network during programming that basically make the system forget what position the frunk is in. So after all the programming is done and you're cleaning up and putting things away don't be surprised if your frunk just beeps at you when you press the button to get it to close. Don't panic, you didn't break it. You just have to close it one time manually and then it will "sync back up" and work properly from then on (assuming no other issues).

 

[GDN]

I was assisting a forum member who is doing FDRS updates for the first time. It's all going very well but there was a moment or two of uncertainty after the updates were done caused by the frunk not wanting to close when commanded.

Let me post this so everybody knows. When you have the frunk open to connect the powersupply during updates, there are interruptions to the network during programming that basically make the system forget what position the frunk is in. So after all the programming is done and you're cleaning up and putting things away don't be surprised if your frunk just beeps at you when you press the button the get it to close. Don't panic, you didn't break it. You just have to close it one time manually and then it will "sync back up" and work properly from then on (assuming no other issues).

Good PSA, this is also true if you simply have disconnected the 12v battery. The frunk just doesn't take a chance, it won't budge. So a simple gentle manual close typically gets you back in business.

Sponsored