Lightning Software Updates using FDRS

[GDN]

Where you live there are a bunch of folks who do this routinely. I'm sure you could work something out.

True - I know one of the most advanced is here and several others too. I'm thinking every 6 months if Ford doesn't push these out I can foot beer and pizza one afternoon and get updates.

The problem is when Ford doesn't trigger some of these immediately or they take hours to apply.

Sponsored

 

[Mike G]

True - I know one of the most advanced is here and several others too. I'm thinking every 6 months if Ford doesn't push these out I can foot beer and pizza and and afternoon and get updates.

The problem is when Ford doesn't trigger some of these immediately or they take hours to apply.

Well I figured you knew which "module whisperer" I was talking about.

 

[Mike G]

25 July and new updates for the Lightning:

I don't know if this is related to the OTA 3.1.0 that at least one owner received over the weekend. I don't have any VINs of vehicles that got that OTA to be able to figure out what updates it processed.

This will very likely program just like it does on the Mach-E, meaning select the PCM and it will 'chain' all the other updates in sequence without having to individually select them.


EDIT/UPDATE:

As expected FDRS started with the PCM module first and advised that other modules would be updated as well. If you pick any of the other modules first (BECM, SOBDMB, SOBDMC) it will start with the PCM anyway. Even though they are chained in sequence by FDRS you still have to stay with the truck to turn on/off the ignition button when prompted etc.

After the PCM, FDRS selected the SOBDMB, SOBDMC, and finally the BECM. (Why? Cause that's the way FDRS likes it!)

Here's the version info for those keeping track with the updated version shown first:
PCM NL3A-14C204-BCK (was NL3A-14C204-BBJ)
SOBDMB NL38-14H297-CH (was NL38-14H297-CG)
SOBDMC NL38-14G069-AYJ (was NL38-14G069-AXH)
BECM NL38-14C197-AH (was NL38-14C197-AG)

Total time on the laptop was 61 minutes start to finish.

And again, I had to put a brief charge on the LVB before starting as it was showing 60% when I hooked up the powersupply.

Mike

 

[GDN]

Is it correct that without FDRS the only version information I have is on the "About Sync" screen?

Just a reference I've had not updates and I show Sync 4 Software Version: 22082_PRODUCT Revision:411.

If I were to get any OTA updates would these numbers change?

 

[FlasherZ]

Mike, do you have FDRS access as a dealer or did you go down the DIY path for FDRS? I read through a few posts elsewhere and it left me feeling like I should be the usual OTA customer until someone here posts that FDRS fix XYZ ifxed the problem with ABC, then I go pester my buddy up at the dealer to plug it in and update it.

 

[Mike G]

Is it correct that without FDRS the only version information I have is on the "About Sync" screen?

Just a reference I've had not updates and I show Sync 4 Software Version: 22082_PRODUCT Revision:411.

If I were to get any OTA updates would these numbers change?

So the list of software updates that I see in FDRS...none of that is reflected in anything you see in your Sync screens.

If you get an OTA...then the OTA is updating one or more of the modules listed in FDRS of the previously available software updates, and they would then drop from the list.

If you get an OTA for the APIM (Sync module), that one will change the "About Sync" page and show the updated version.

I still show the same Sync version that you see on your screen in your truck. The actual software version in FDRS is "MU5T-14G676-HB"...and for comparison the version on my Mach-E is"MU5T-14G676-EJ"...so similar but not exactly the same.

Mike

 

[Mike G]

Mike, do you have FDRS access as a dealer or did you go down the DIY path for FDRS? I read through a few posts elsewhere and it left me feeling like I should be the usual OTA customer until someone here posts that FDRS fix XYZ ifxed the problem with ABC, then I go pester my buddy up at the dealer to plug it in and update it.

Yeah, I'm DIY. I post updates here so people know they're available. On the ICE and Mach-E forums there are lots of people doing their own updates.

Mike

 

[RickLightning]

Is it correct that without FDRS the only version information I have is on the "About Sync" screen?

Just a reference I've had not updates and I show Sync 4 Software Version: 22082_PRODUCT Revision:411.

If I were to get any OTA updates would these numbers change?

If an OTA update is completed, you will get a message in FordPass and you will be able to see it on the Sync screen where you check for updates. There will be information about the update, as much, or as little, as they put in the notes. You will see an update number, like "PowerUp 2.8.2".

However,...

- That isn't a "version".
- That tells you about the last update applied, but doesn't tell you that you are "current".
- The updates don't necessarily hit your car in order. Mach-E owners documented getting them out of sequence.
- The update last applied, and its notes, will go away, and then it will just say "Up to Date".
- "Up To Date" doesn't mean what you think it means. It means there are no more updates queued up by Ford for your vehicle. Mine says "Up to Date" right now, but I don't have the recall update yet.

 

[Mike G]

Yeah...so if anybody has received the 3.1.0 OTA and wants to send me their VIN to lookup, I'll tell you what modules got updated and then we'll all know.

 

[GDN]

I sent you my VIN - I'm OK if the results and VIN are published here. I didn't get the OTA so it might be nice to see what is needing to be updated and what gets updated assuming I'll get it in the next week.

This might need a different thread, but I also signed up for Early Access yesterday. Will see if this helps in the future.
https://www.earlyaccess.ford.com/

 

[Mike G]

I sent you my VIN - I'm OK if the results and VIN are published here. I didn't get the OTA so it might be nice to see what is needing to be updated and what gets updated assuming I'll get it in the next week.

This might need a different thread, but I also signed up for Early Access yesterday. Will see if this helps in the future.
https://www.earlyaccess.ford.com/

Well you may be luckier than I am with EA. I suspect I've not been included due to the fact I live in a 1 1/2-2bar AT&T coverage area. I signed up last year sometime and recently checked in again and am still not one of the anointed ones. Doesn't matter in most respects if you've got FDRS anyway. You can do the updates as they roll in.

And you have all the currently available updates that I would guess most folks have at this point. BECM, GWM, PCM, OBCC, SOBDMB, and SOBDMC.

 

[GDN]

I don't want to hijack this thread with Early Access - might try over here if others want to discuss this - https://www.f150lightningforum.com/forum/threads/early-access-to-sw.11346/post-235350

 

[Mike G]

Okay, new day new update!

Checked FDRS today and found a BCM (Body Controller Module) update.

BCM version before update was NU5T-14C184-AAJ and afterwards is NU5T-14C184-AAK.

Took about 10 minutes to do. In most cases after programming a module FDRS then configures that module with info in your asbuilt configuration. This was no different. So besides updating the BCM to accommodate whatever new functionality it will provide (or an issue that was corrected?) during the config sequence it updated the asbuilt data from the Ford-cloud into my BCM, - which would include the recent recall-related data about the TPMS tire low warning threshold.

Here's the screengrab showing the update in FDRS:

Mike

 

[Mike G]

And this morning, 7 Aug, two surprises.

First I checked FDRS and found an OBCC update. The second was the 3.3.1 Mystery PowerUp that hints at bits and bobs, and this and that being updated. You know...like fairy dust being sprinkled.

So for a little bit of background, as a Mach-E owner as well, I checked FDRS yesterday and noticed an OBCC update which I applied (3 minutes on the computer) but what was a bit controversial was the fact that the version number seemed to revert to a previous version. Well it did and it didn't. Some of the packages in the version did change so it wasn't a wholesale reversion to a previous iteration.

And so I did some before and after comparisons on the version I had this morning on the Lightning "-AN" and the version it updated to "-AM", and yes it would also appear that the Lightning OBCC update "looks" like it's going backwards but all is not as it seems.

The "original" LJ98-14G684-AM software version the trucks rolled out of the plant with got updated (as seen in this thread previously) to the "-AN" version.

But that original -AM version is not the same as the new and slightly modified -AM version I updated to this morning.

I created a side by side comparison of the DIDs that includes my dealer's mannequin for reference since I know that hasn't been updated at all.

You'll notice that some of the newer software packages do seem to have reverted back to previous versions but some haven't. So there were tweaks.

Mike

 

[Mike G]

Checked FDRS today while running some VINs and noticed that the APIM for my Lightning had a different engineering part number as well as a change in the software version. This may have been a result of the 3.2.0/3.3.1 OTA, But I haven't checked my "About Sync" screen yet.

Anyway the engineering part number used to be DSMU5T-14G670-HB, but is DSMU5T-14G670-DT
as of today.

And the software version that I had before the OTA was MU5T-14G676-HB but it's now MU5T-14G676-DT.

So it goes from a "-HB" version on both the engineering part number and software version "backwards" (revision-wise) to "-DT" on both.

Does anybody else think the DT might stand for "Dual Telephone"?

Mike

Sponsored