ECU module programming guide using FDRS

[lojoma]

Now up to 22087, and my Additional Updates list shows a whole slew of them coming up. I did a GWM update before an APIM update today.

I started to update IPC next, as it says I need to that and TCU next, but it said it would take 3 hours so I will need to do that another day.

Did the IPC update and it took 4 hours, but seems to have gone fine. TCU next.

Sponsored

 

[rugedraw]

I think you’re overstating what that tool does. First, I’m not sure it’s available for all modules or only certain ones. Second, for the modules for which it is available it doesn’t repopulate all of the local as-built data—only certain parts. If it uploaded everything, the tool could be used to immediately upload FORScan changes to the cloud instead of having to wait for the vehicle to self-report. As far as I know, there is no way to force up FORScan configuration changes.

I've noticed the same thing. I've tried running that script on my truck several times and my a/b data on the truck still differs from what Ford shows.

 

[Mike G]

I think you’re overstating what that tool does. First, I’m not sure it’s available for all modules or only certain ones. Second, for the modules for which it is available it doesn’t repopulate all of the local as-built data—only certain parts. If it uploaded everything, the tool could be used to immediately upload FORScan changes to the cloud instead of having to wait for the vehicle to self-report. As far as I know, there is no way to force up FORScan configuration changes.

Understood. And it did just that. I had numerous GVMS data errors in FDRS immediately after doing the glare-free headlights FORSCAN changes (but that's all I've done using FORSCAN).

And it looked like this:

I did report the GVMS errors and check PTS afterward, and nothing had happened after three days. So after reading about what the "Read Configuration Data" tool does..I tried that and immediately after it completed, and I was returned to the SW Updates tab, the GVMS blocks were gone. But you're right...you do have the ability to read the data for all the modules or just the ones you pick. In fact, that's part of Ford's "FSA Software Verification" process to ensure the tech actually updated the modules they were supposed to.

 

[JEB]

Understood. And it did just that. I had numerous GVMS data errors in FDRS immediately after doing the glare-free headlights FORSCAN changes (but that's all I've done using FORSCAN).

And it looked like this:

I did report the GVMS errors and check PTS afterward, and nothing had happened after three days. So after reading about what the "Read Configuration Data" tool does..I tried that and immediately after it completed, and I was returned to the SW Updates tab, the GVMS blocks were gone. But you're right...you do have the ability to read the data for all the modules or just the ones you pick. In fact, that's part of Ford's "FSA Software Verification" process to ensure the tech actually updated the modules they were supposed to.

You mean GIVIS blocks? I am aware of using the Read Config tool to remove GIVIS-type blocks. See SSM 51407, for example, below. But that’s not the same thing as actually rebuilding the cloud data. As I understand it, this tool is more of a force reporting to get FDRS to grab data that is already there but it isn’t automatically retrieving like it should. @UNCGrad was reporting a different kind of error that suggested that the configuration data she needed to complete the procedure wasn’t there at all. It wasn’t a GIVIS error.

SSM 51407 2021-2022 Various Vehicles - SYNC 4 - Procedure Unsuccessful - GetConfigDataFromGIVIS Error Message

Some 2021-2022 Ford and Lincoln vehicles equipped with SYNC 4 may experience an error message during the gateway module (GWM) software update application which states Procedure Unsuccessful- GetConfigDataFromGIVIS. This may be the result of a server related concern. To correct the condition, download and run the Ford Diagnosis and Repair System (FDRS) application GWM-Read the Gateway Module A (GWM) Configuration Data application. When the application completes, refresh and re-attempt the GWM-Gateway Module A (GWM) Software Update application. For claiming, use causal part 14G229 and applicable labor operations in Section 10 of the Service Labor Time Standards (SLTS) Manual.

 

[rugedraw]

You mean GIVIS blocks? I am aware of using the Read Config tool to remove GIVIS-type blocks. See SSM 51407, for example, below. But that’s not the same thing as actually rebuilding the cloud data. As I understand it, this tool is more of a force reporting to get FDRS to grab data that is already there but it isn’t automatically retrieving like it should. @UNCGrad was reporting a different kind of error that suggested that the configuration data she needed to complete the procedure wasn’t there at all. It wasn’t a GIVIS error.

I think I see where the disconnect is here. The GVMS warnings are something relatively new that was introduced with one of the latter FDRS releases. When you see one of these, you have to submit an a/b assistance request from engineering before the update(s) will be released for you to install. The problem is that it can take a few days or even longer for Ford to get to it and fix the issue. This was not the problem for UNCGrad; I'm just trying to shed some light on what Mike was referring to.

 

[JEB]

I think I see where the disconnect is here. The GVMS warnings are something relatively new that was introduced with one of the latter FDRS releases. When you see one of these, you have to submit an a/b assistance request from engineering before the update(s) will be released for you to install. The problem is that it can take a few days or even longer for Ford to get to it and fix the issue. This was not the problem for UNCGrad; I'm just trying to shed some light on what Mike was referring to.

Yeah, I see that. But that just confirms that it really has nothing to do with the problem we were dealing with. I think it’s also further corroboration that we, as end users, can’t repair as-built data stored on the cloud without help from Ford engineering.

 

[rugedraw]

Yeah, I see that. But that just confirms that it really has nothing to do with the problem we were dealing with. I think it’s also further corroboration that we, as end users, can’t repair as-built data stored on the cloud without help from Ford engineering.

Well, not any more. There was a way for the gurus to manipulate data on the server in the past, but from my understanding of things, Ford closed the loophole that was used to do so.

 

[Bowtye8]

Been checking my truck on updates and its been a while. Mine is a early build 2021(March 2021) but I did the FDRS updates and all has been fine(it performed OTA updates for a few years. even the one that whipped out my tune and wrote my truck back to stock).

This is what I have been showing for some months now.
Not completed ??
Should I load up FDRS again? Its been over 2 -3 yrs ago since I did the manual updates so I would have to reread "How to" and also have a different laptop so start from scratch with the software again

 

[rugedraw]

Been checking my truck on updates and its been a while. Mine is a early build 2021(March 2021) but I did the FDRS updates and all has been fine(it performed OTA updates for a few years. even the one that whipped out my tune and wrote my truck back to stock).

This is what I have been showing for some months now.
Not completed ??
Should I load up FDRS again? Its been over 2 -3 yrs ago since I did the manual updates so I would have to reread "How to" and also have a different laptop so start from scratch with the software again

23291 is only one version behind the latest one. You do show a GWM pending which once done, will release the APIM update to bring you up to 24127 which is the latest version. Your IPMA is also on an old version, so updating that will give you the improved lane centering and driver assist features, too.

 

[Bowtye8]

23291 is only one version behind the latest one. You do show a GWM pending which once done, will release the APIM update to bring you up to 24127 which is the latest version. Your IPMA is also on an old version, so updating that will give you the improved lane centering and driver assist features, too.

Thanks for the quick response.
Any reason why that one has been showing Not completed for a while?

 

[rugedraw]

Thanks for the quick response.
Any reason why that one has been showing Not completed for a while?

That screen will always show whatever happened the last time an OTA attempt was made. Until you get another update, that will be the status you see when you check that screen.

 

[americanuck]

Hello all. I'm sure this is somewhere, I even think I remember reading it, but I can't find it. I have a Job 1 '21 f150 that hates updates.

I bought the mongoose cable, 30 day FDRS, and I'm out here doing updates. I realized after I started that I did them out of order... I didn't have a GWM update to do, but I did the IPC update before the APIM. It finished successfully, but now when I put in the USB for the APIM, nothing happens. The first time, I got an error about the USB, so I grabbed a different one. Now it says indexing, it goes away as if it read it properly, and then nothing happens.

How long should I wait with the USB in the truck before it says Do Not Remove? It seems for most people, and according to FDRS, it should only be a couple of minutes... Did I break something? Is there anything I can do to help myself?

I waited about 20 minutes last night for something to happen, then today I drove around for a bit, nothing happening so far.

 

[Gord0]

Hello all. I'm sure this is somewhere, I even think I remember reading it, but I can't find it. I have a Job 1 '21 f150 that hates updates.

I bought the mongoose cable, 30 day FDRS, and I'm out here doing updates. I realized after I started that I did them out of order... I didn't have a GWM update to do, but I did the IPC update before the APIM. It finished successfully, but now when I put in the USB for the APIM, nothing happens. The first time, I got an error about the USB, so I grabbed a different one. Now it says indexing, it goes away as if it read it properly, and then nothing happens.

How long should I wait with the USB in the truck before it says Do Not Remove? It seems for most people, and according to FDRS, it should only be a couple of minutes... Did I break something? Is there anything I can do to help myself?

I waited about 20 minutes last night for something to happen, then today I drove around for a bit, nothing happening so far.

What version does your "about sync" page say in the truck?

 

[rugedraw]

Try rebooting the GWM module with FDRS or FORScan.

What Sync version is your truck on right now? It is a 5 digit number that starts with a 2.

 

[americanuck]

In my truck, it’s blank.
@rugedraw looked up for me the other day and confirmed it was 20301.
Rebooting the GWM, didn’t try that. I plan on hooking everything back up tonight as soon as kids go to bed.
Thank you for the recommendation!!

Sponsored