ECU module programming guide using FDRS

[Bob_Mac]

That was something I was thinking about as well. Has anyone who performed a manual module update gotten an OTA (any OTA) after the update? I haven’t and I know 2.4.1 came out well after my first tour through FDRS in January.

Nothing yet and I did my updates after the 2.3.0 OTA failed so I'm not sure if Ford saw that failed OTA and may not be pushing 2.4.1 to my truck or if the corrupted data or even both is stopping it. I'm hoping to see another FDRS update within the next few days and if it happens, I'll be jumping right in to see if it fixes the issue.

Sponsored

 

[iceman77]

I don't think it's affecting the modules but, the AsBuilt shows the same issues and would probably prevent any OTA's being pushed to us due to the corruption.

Only if your F188 (Strategy) information is affected. Other fields does not seem to affect OTA.

 

[Snakebitten]

Amazing how far everyone has come.

I don't know why you would be surprised. Fixing your own truck sitting in the captains chair with nothing more than a cup of coffee and a laptop? It's like heroin.
And YOU were the kingpin dealer. ???

 

[speedracercjr]

That was something I was thinking about as well. Has anyone who performed a manual module update gotten an OTA (any OTA) after the update? I haven’t and I know 2.4.1 came out well after my first tour through FDRS in January.

Once I got past the stuck 1.7.1 Ford tried to push 2.3 to my truck (it failed, shocker) so I think manually updating isn't affecting OTA's being pushed.

 

[Jesse-Infotainment]

I don't know why you would be surprised. Fixing your own truck sitting in the captains chair with nothing more than a cup of coffee and a laptop? It's like heroin.
And YOU were the kingpin dealer. ???

Ha, yeah it is very empowering. I remember a lot of hesitation. I remember a lot of texts with Iceman.. Walking through it all. Now he is doing a great job along with you, JEB and several others helping and working through issues and continuing the education and helping others. That is all I wanted . My initial problem was the cost of the VCM 3 but now the unit has been found to work at a more affordable price makes it a must have.

I am happy to have helped some get their trucks up to date and getting some issues resolved. Its very important to not need dealer intervention for everything.

I am glad to see so many taking it on. I am also happy I dont have to answer all the questions anymore . Its amazing just how many great and really smart people are involved with this forum. Makes this a very good tool and resource for owners and potential owners.

 

[Bob_Mac]

Once I got past the stuck 1.7.1 Ford tried to push 2.3 to my truck (it failed, shocker) so I think manually updating isn't affecting OTA's being pushed.

That just means they are disregarding the last failed OTA but the corruption issue may affect the OTA's and until someone with the corrupted data gets an OTA it's a wait and see game.

 

[Jesse-Infotainment]

Once I got past the stuck 1.7.1 Ford tried to push 2.3 to my truck (it failed, shocker) so I think manually updating isn't affecting OTA's being pushed.

No, I have gotten OTAs, the manual is just an option. I always made the suggestion in the beginning to manually update due to the cancelled updates and for some future update they have the previous update. If you didnt get the previous update then the updates stop since the requirement hasn't been met. Anyone that has done the FDRS route can see the way they work. You finish an update and then another one becomes available. The same applies to OTAs.

 

[iceman77]

That just means they are disregarding the last failed OTA but the corruption issue may affect the OTA's and until someone with the corrupted data gets an OTA it's a wait and see game.

I have a 22 F-150 and the only OTA for these new truck is the BlueCruise OTA pushed out as GWM update. I happened to notice this update via FDRS and update my truck myself. The OTA then subsequently failed with a "cancelled" status. This is expected as my truck was already up to date when the OTA tried to push down to my truck.

 

[Bob_Mac]

Only if your F188 (Strategy) information is affected. Other fields does not seem to affect OTA.

Good to know!

 

[BlackSheep]

Looks like I have several modules impacted. It is also interesting that a couple of them were not updated but are now corrupt.

Does anyone know if this long field (F106) is corruption too? (Bottom Screenshot).

 

[iceman77]

Here's a complete breakdown of fields you see in As-Built dataset for the GWM module:

<NODEID>
   716
   <F10A>ML3T-14J009-EKB</F10A>
   <F110>DSMU5T-14G650-ED</F110>
   <F111>MU5T-14H026-AH</F111>
   <F113>MU5T-14G650-ABX</F113>
   <F16C>ML3T-14J007-EKB</F16C>
   <F17F>1EG110L5</F17F>
   <F188>ML3T-14H021-EKB</F188>
   <F18C>FUBCH20339031102</F18C>
   <F190>1FTFW1E85MFAxxxxx</F190>
</NODEID>

F10A        ECU_CONFIGURATION
F110        PART_II_SPECIFICATION (ASSEMBLY)
F111        CORE_ASSEMBLY_PART
F113        ASSEMBLY
F16C        ECU_CONFIGURATION
F17F        SERIAL_NUMBER
F188        STRATEGY (SW VERSION)
F18C        SERIAL_NUMBER
F190        VIN

When you skip FDRS NetworkScan and you opt for "cloud" based vehicle info download, that info is stored in JSON format here:

C:\ProgramData\Ford Motor Company\FDRS\fdrs\data\vehicle\{your_vin}_en_US.json

It contains all your vehicle information, including module version, configuration as well as your AB data. You can use this file to figure out what different "F" fields mean. If someone would be willing to write a parser for the publicly available AB data (downloadable via MotorCraft) that would be great. Perhaps @tonesto7 would be up for a challenge, and add this to his widget tool ?

 

[antho]

Looks like I have several modules impacted. It is also interesting that a couple of them were not updated but are now corrupt.

Does anyone know if this long field (F106) is corruption too? (Bottom Screenshot).

View attachment 41016

I have these issues also. Comparing my original data, This is something new and wasnt in my original data.

 

[BlackSheep]

I have these issues also. Comparing my original data, This is something new and wasnt in my original data.

Thanks for confirming. Hopefully, someone finds a fix soon.

 

[22Platinum]

If someone would be willing to write a parser for the publicly available AB data (downloadable via MotorCraft) that would be great.

Can you elaborate on this request?

 

[iceman77]

Here is detailed breakdown of AB fields for APIM:

<NODEID>
   7D0
   <F10A>MU5T-14G680-AA</F10A>
   <F110>DSMU5T-14G670-EG</F110>
   <F111>MU5T-14G681-KF</F111>
   <F113>MU5T-14G670-PNL</F113>
   <F124>MU5T-14G677-ABA</F124>
   <F129>ML3T-18K811-AA</F129>
   <F12B>ML3T-18B955-BE</F12B>
   <F12C>FFF1-14F180-FE</F12C>
   <F142>MLBE04324F</F142>
   <F143>20201102212414</F143>
   <F144>AKC0NDHG</F144>
   <F16B>MU5T-14J003-AF</F16B>
   <F17F>1SN11346</F17F>
   <F188>MU5T-14G676-EG</F188>
   <F18C>FUBCH20333050605</F18C>
   <F190>1FTFW1E85MFAxxxxx</F190>
</NODEID>

F10A        ECU_CONFIGURATION
F110        PART_II_SPECIFICATION (ASSEMBLY)
F111        CORE_ASSEMBLY_PART
F113        ASSEMBLY
F124        CALIBRATION
F129        OTHER
F12B        OTHER
F12C        OTHER
F142        SERIAL_NUMBER
F143        SERIAL_NUMBER
F144        SERIAL_NUMBER
F16B        ECU_CONFIGURATION
F17F        SERIAL_NUMBER
F188        STRATEGY (SW VERSION)
F18C        SERIAL_NUMBER
F190        VIN

Looking closer at the F12C (OTHER) field, my old truck self-reported FFF1-14F180-FE. This might be either a valid value or a result of something else as Network Scan via J2534 pass-through in FDRS. So, @tonesto7, you are in my opition in good shape as far as AB data integrity on Ford servers

Sponsored