Lightning Software Updates using FDRS

[Mike G]

19 Aug 23 and there's a new OBCC update this morning for my '22. A check of one '23 model also turned up an OBCC update. And over on the Mach-E side this OBCC also showed up this morning.

Sponsored

 

[MickeyAO]

That was not there yesterday when I checked

 

[Mike G]

I recommend holding off on updating FDRS until they fix the session log issue that started with 37.4.3, and wasn't fixed by the panic release of 37.4.4 the next day (yesterday).

It makes your session logs look like this:

Stay on 36.4.8 until the all clear is sounded.

 

[Zzebro]

@Mike G are you able to check my vin? I just bought a used 2022 Lightning Lariat and it appears to be missing quite a few updates. Not quite sure what to do to get them to come through.
VIN: 1FT6W1EV2NWG04401

Pics of current Software:

 

[MickeyAO]

Lots of updates...could not fit them on one screen (13 in total).

 

[Zzebro]

Wow. Thanks for running that.
Not sure what to do to push them through. I tried the drive around, set it to update in 15 mins, e brake, and light off method…nothing. Tomorrow morning I’m going to set the update during my morning commute.
I’ve called the Ford OTA line with no resolution other than go to the dealer. The dealers around me that I have called are clueless.

 

[#1 Scuba]

Wow. Thanks for running that.
Not sure what to do to push them through. I tried the drive around, set it to update in 15 mins, e brake, and light off method…nothing. Tomorrow morning I’m going to set the update during my morning commute.
I’ve called the Ford OTA line with no resolution other than go to the dealer. The dealers around me that I have called are clueless.

I had a 2022 Platinum with the same issues. I had the OTA update group assign a Case number (twice) but it took 2 months and a lot of special help from Mike and others from Ford who watch this forum. My Platinum works great now and has the new User Interface.

 

[Zzebro]

I had a 2022 Platinum with the same issues. I had the OTA update group assign a Case number (twice) but it took 2 months and a lot of special help from Mike and others from Ford who watch this forum. My Platinum works great now and has the new User Interface.

glad to hear a success story. Did you ever end up working with a dealer?

 

[#1 Scuba]

glad to hear a success story. Did you ever end up working with a dealer?

Yes, I was very fortunate to have a technician and his manager at the dealership involved from day one. They followed the instructions from a member on this site exactly and made the necessary updates. My issue was the truck was originally a mannequin but only had 300 miles on it. It originally needed to be removed from the Ford Telematics program. Then Ford need to get the software updates on the vehicle in sinc so the OTA updates would work.
My dealership was VERY impressed with the help I received from members on this forum.

 

[Mike G]

Wow. Thanks for running that.
Not sure what to do to push them through. I tried the drive around, set it to update in 15 mins, e brake, and light off method…nothing. Tomorrow morning I’m going to set the update during my morning commute.
I’ve called the Ford OTA line with no resolution other than go to the dealer. The dealers around me that I have called are clueless.

Call your service advisor this morning and ask them to check your OTA dashboard and read out to you the history that they see for the last 60 days. If there is no history, that's your first clue that you have a problem that needs further diagnosis (by a tech in person). If there is a history of any sort and it says that OTAs have been attempted but failed, ask the service advisor what the reasons were for the failures are/were according to what the system reported. That will also be a clue as to what might be holding you back.

You do have an APIM update showing as available but I'm not sure what would happen if the tech attempted it using FDRS. There may be something else at work here like what happened to @#1 Scuba . But it's not clear yet that this is the case.

 

[Mike G]

Good morning all 29 Aug '23 and a new APIM (Sync) update popped up this morning for my '22 (alongside the OBCC I've been too lazy to apply).

Now that I have more than one update in my list, and the outdoor temps have dropped to below mid-90s, and there's no rain forecast for today, I think I'll get the kit out and knock both of those out.

 

[Mike G]

Good morning all 29 Aug '23 and a new APIM (Sync) update popped up this morning for my '22 (alongside the OBCC I've been too lazy to apply).

Now that I have more than one update in my list, and the outdoor temps have dropped to below mid-90s, and there's no rain forecast for today, I think I'll get the kit out and knock both of those out.

And then this happened....

I hit the remote start button around 0830 because I know my truck is set to check for updates at 0900. I figured I'd get the 12V LVB charged back up with a remote start + a 15 min extension just to avoid having to charge the LVB up before starting to do the two updates.

Well after the 30 min remote "warmup", when I went to start the truck and move it over to the workspace to do the updates I checked the updates page and found this:

Seeing as how I planned on doing updates today and didn't want to wait for the OTA to actually do the update tomorrow morning at 0900, I closed that dialog and just hit the button to do the update now instead:

So it's probably finished by now (supposed to take 10 minutes), and now I'll go back out with my laptop and USB drive and forgo the powersupply completely, becasue the remaining APIM update is a USB update and we know that those are all done with the truck fully running and keeping the 12V LVB charged while that process is going on.

 

[GDN]

I got the notification in the truck this morning when I ran a quick errand, but was busy and forgot to hit the button when I got back home. Must go do that now.

 

[bmwhitetx]

And then this happened....

I hit the remote start button around 0830 because I know my truck is set to check for updates at 0900. I figured I'd get the 12V LVB charged back up with a remote start + a 15 min extension just to avoid having to charge the LVB up before starting to do the two updates.

It may have tried to update you this morning at 9am but the requirements weren't met (namely you had the truck on). If so, you would have a message in Fordpass that an update failed. I'm an expert on those.

 

[Mike G]

So Part Deux of this morning's entertainment:

I went back out with the laptop, mongoose, and thumb drive and started back up.

So this is the starting point. Sync 713 and a software rev. (in FDRS) of "-EC".

DL the update to the USB drive (a small update..only 1 GB ).

When directed, stick the drive in the console USB port and after about a minute:

Then after about two minutes:

Made more coffee, and then went back out and turned back on. After about a minute:

After advising FDRS that the update was successful and spamming the re-scan network button to remove the APIM from the software list (sometimes it takes a minute for the server to acknowledge that you already have that update done), I checked the About page and was kinda surprised to see that I was now at Sync 915. That's a bit of a jump, from 713 to 915!

Now...the F188 DID did not change, it's still rev. "-EC". But there were a bunch of small software tweaks that happened. I didn't see any updates to any of the apps though so I'm thinking this is a step toward BC 1.3.

Baby steps...I guess we're gonna sneak up on BC 1.3 rather than have one big update dump that enables it for everybody.