ECU module programming guide using FDRS

[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

 

[iceman77]

From my observations, for OTA to work, F188 (STRAGETY) field must be intact. Especially on GWM.

Other fields such as F124 (CALIBRATION) and F10A (ECU_CONFIGURATION) might play a crucial role as well, but it is unconfirmed at this time.

 

[iceman77]

Can you elaborate on this request?

You can publicly download AB data for any truck here. Data in this file is a minimized (unformatted) XML, with fields coded as "Fxxx", unreadable at first glance. It is PIA to modify this file to a readable format each time you download it and use a cheatsheet to determine what each "F" field means. Would be nice to have a tool that would automatically convert this file into a more readable format.

 

[iceman77]

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

No need for a fix. Your truck will send its own version of "network scan" that will correct all issues you see currently in your AB file. All you need to pay attention that your GWM data are in good shape

 

[BHunted1]

You can publicly download AB data for any truck here. Data in this file is a minimized (unformatted) XML, with fields coded as "Fxxx", unreadable at first glance. It is PIA to modify this file to a readable format each time you download it and use a cheatsheet to determine what each "F" field means. Would be nice to have a tool that would automatically convert this file into a more readable format.

I posted it above: Winmerge works great. Compares the files too and highlights differences.
ECU module programming guide using FDRS | Page 43 | F150gen14.com -- 2021+ Ford F-150, Lightning EV, Raptor Forum (14th Gen) | Owners, News, Discussions

 

[nicholsbradley]

Took my truck to dealership today for some recalls and said hey can you catch me up on all the updates "FDRS". They stated they only do updates if something is wrong. I mean wow, how can it update itself if its so far behind on everything. Ford services has gone to shit.

 

[tonesto7]

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

Thanks for that... I had the address breakdown at one time but lost it.

 

[tonesto7]

You can publicly download AB data for any truck here. Data in this file is a minimized (unformatted) XML, with fields coded as "Fxxx", unreadable at first glance. It is PIA to modify this file to a readable format each time you download it and use a cheatsheet to determine what each "F" field means. Would be nice to have a tool that would automatically convert this file into a more readable format.

I seriously want to build a whole platform that allows us to decipher all of the asbuilt and modules.
I want a web portal that will show us which asbuilt options are available for our vehicle and firmware.
I was going to start with creating a web-based version of using Livinitups spreadsheet and allowing descriptions and more.
There are just so many variables that need to be considered to make something like these useful and maintainable. I will definitely need multiple in on a project like this.

In the meantime, I think I can make an electron app that does what you are asking. I just need some time to finish up some projects that I'm working on

 

[RellIk&5]

Does anyone have any errors toward the bottom of their AB file? I downloaded mine from the Motorcraft site and have this as the very bottom:

<ERROR>
<ERRORCODE>612</ERRORCODE>
<ERRORMSG>PCM DATA NOT FOUND</ERRORMSG>
</ERROR>
<ERROR>
<ERRORCODE>614</ERRORCODE>
<ERRORMSG>CCC DATA NOT FOUND</ERRORMSG>
</ERROR>

 

[BlackSheep]

No need for a fix. Your truck will send its own version of "network scan" that will correct all issues you see currently in your AB file. All you need to pay attention that your GWM data are in good shape

Thanks for that info! I was concerned. Appreciate all you have done in this thread!

 

[Bob_Mac]

Can you elaborate on this request?

PowerShell is one option.

 

[Bob_Mac]

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.

Thx for this!

 

[iceman77]

Does anyone have any errors toward the bottom of their AB file? I downloaded mine from the Motorcraft site and have this as the very bottom:

<ERROR>
<ERRORCODE>612</ERRORCODE>
<ERRORMSG>PCM DATA NOT FOUND</ERRORMSG>
</ERROR>
<ERROR>
<ERRORCODE>614</ERRORCODE>
<ERRORMSG>CCC DATA NOT FOUND</ERRORMSG>
</ERROR>

My old Job 1 truck has the same error code so does my new 22 F-150. I would not worry about those much though.

 

[22Platinum]

It is PIA to modify this file to a readable format each time you download it and use a cheatsheet to determine what each "F" field means.

Where does the cheatsheet come from?

 

[iceman77]

Where does the cheatsheet come from?

I just shared them here and here. I created them (only for GWM and APIM) based on the vehicle info JSON file downloaded by FDRS tool from cloud. I have shared the location of the JSON file here.

Sponsored