ECU module programming guide using FDRS

[m_bt54]

I'm not even mad at him. I still find trucks stuck on Sync 20301 on an almost daily basis. To my knowledge, Ford has never acknowledged the issue or provided any real fix for this even for trucks still under warranty. If I was stuck on Sync 20301, I would sign up.

The whole thing seems a little suspicious to me, especially where this is his first post ever on here…

Sponsored

 

[nkyhunter]

he's fishing for some business most likely!

 

[DK4]

I’d just be curious what the grounds would be for such litigation. What sort of law Ford is breaking by not providing a software update. Does the stuck update keep the truck from operating? Honest question. Or maybe a promised feature by a certain date is still missing?

 

[Eric55AMG]

Ran the latest BCM update tonight without issues ... but did notice something strange on the overall software versions.

I've tracked all my updates since 9/2/22 by copying the Engineering Assembly P/N & Software P/N displayed on the FDRS vehicle information page.

In doing a comparison, I'm finding inconsistencies with what's reported under the software P/N.

Sometimes it's only a partial version. Sometimes it's the same P/N from two sessions ago, but not the previous session.

I'm assuming this is a bug in FDRS (I've stayed fairly current on the released version (currently 38.5.7) as I haven't noticed any challenges using the most recently released version.

To drive better consistency and accuracy .... what DID number should I look for in the Module Details to gather the correct Software version in hopes of avoiding any FDRS bugs?

I'm also wondering if these inconsistencies could be contributing to why I've not seen some of the module updates (such as APIM or IPC) that others have received. Maybe it's not reporting the correct versions back to the mother ship.

I've also not received an OTA update since April.

 

[Jesse-Infotainment]

Ran the latest BCM update tonight without issues ... but did notice something strange on the overall software versions.

I've tracked all my updates since 9/2/22 by copying the Engineering Assembly P/N & Software P/N displayed on the FDRS vehicle information page.

In doing a comparison, I'm finding inconsistencies with what's reported under the software P/N.

Sometimes it's only a partial version. Sometimes it's the same P/N from two sessions ago, but not the previous session.

I'm assuming this is a bug in FDRS (I've stayed fairly current on the released version (currently 38.5.7) as I haven't noticed any challenges using the most recently released version.

To drive better consistency and accuracy .... what DID number should I look for in the Module Details to gather the correct Software version in hopes of avoiding any FDRS bugs?

I'm also wondering if these inconsistencies could be contributing to why I've not seen some of the module updates (such as APIM or IPC) that others have received. Maybe it's not reporting the correct versions back to the mother ship.

I've also not received an OTA update since April.

BCM has several locations of software that Update.

188 is the strategy. It went from AAJ TO AAM

But there are 8 I think locations.

Not all of the locations are updated.

The other fields vary from truck to truck

 

[Eric55AMG]

BCM has several locations of software that Update.

188 is the strategy. It went from AAJ TO AAM

But there are 8 I think locations.

Not all of the locations are updated.

The other fields vary from truck to truck

Thx for the response Jesse. Always appreciate your insight.

Sorry I wasn't clearer.
I wasn't referencing inconsistencies within the BCM ... or more generically within any of the specific module details ... unfortunately I wasn't tracking to that level.

I was only tracking the "top portion" of the Vehicle information screen where it reports a single Engineering Assembly P/N & Software P/N .

Those single Software P/Ns are what I was noticing were at times, inconsistent between sessions (session = module update activities).

 

[fordtruckman2003]

I intend to file a class action suit. I am the owner of a 2021 Bloc 1 F-150 which has hung up on an update and I'm not buying a mongoose or voiding my warranty trying self-repair. If you would like to join call me at 850-739-6970 or via email at [email protected]

Maybe stick to bankruptcy law?
You'll lose and put all of us at risk of not being able to perform our own updates if you irritate Ford enough.

 

[MoodyLaw]

I’ll be rooting for you but don’t expect you to get very far. Borrowing a cable and spending $50 and a few hours seems like much less of a hassle and you won’t void your warranty.

That actually does void the warranty and I've been practicing complex litigation for 15 years, including the largest cases in products liability. I do expect to get very far.

 

[Ajzride]

@MoodyLaw Please start a dedicated thread for this topic. It is already difficult enough to find the information needed in this one without a tangent topic muddying things up

 

[MoodyLaw]

Maybe stick to bankruptcy law?
You'll lose and put all of us at risk of not being able to perform our own updates if you irritate Ford enough.

Would be the first case I have lost in 15 years. Not very likely. Ford is assured to be infuriated. As we all are or should be.

 

[JEB]

Ran the latest BCM update tonight without issues ... but did notice something strange on the overall software versions.

I've tracked all my updates since 9/2/22 by copying the Engineering Assembly P/N & Software P/N displayed on the FDRS vehicle information page.

In doing a comparison, I'm finding inconsistencies with what's reported under the software P/N.

Sometimes it's only a partial version. Sometimes it's the same P/N from two sessions ago, but not the previous session.

I'm assuming this is a bug in FDRS (I've stayed fairly current on the released version (currently 38.5.7) as I haven't noticed any challenges using the most recently released version.

To drive better consistency and accuracy .... what DID number should I look for in the Module Details to gather the correct Software version in hopes of avoiding any FDRS bugs?

I'm also wondering if these inconsistencies could be contributing to why I've not seen some of the module updates (such as APIM or IPC) that others have received. Maybe it's not reporting the correct versions back to the mother ship.

I've also not received an OTA update since April.

I am not certain about what you are asking, but here is my as-built data for the BCM after the last update. The bolded software versions are changes:

<NODEID>726
<F10A>ML3T-14C636-BDC</F10A>
<F10E>ML3T-14G570-AAD</F10E>
<F110>DSMU5T-14B476-AAL</F110>
<F111>MU5T-14F141-KAB</F111>
<F113>MU5T-14B476-KAD</F113>
<F16B>MU5T-14F391-BAA</F16B>
<F16C>ML3T-14F390-CAR</F16C>
<F16D>ML3T-14F389-AFA</F16D>
<F16E>ML3T-14G163-CAC</F16E>
<F17D>MU5T-14G162-KAE</F17D>
<F17F>1BR16YY0</F17F>
<F188>MU5T-14C184-AAM</F188>
<F18C>21181191872</F18C>
<F190>XXXXXXXXXXXXXXXXX</F190>
</NODEID>

In general, FDRS reports on the vehicle identification page the software version at F188 as THE software version of the module, suggesting (to me) that F188 is the DID to be considered when determining whether the module is up to date.

There is an inconsistency in FDRS with regard to the APIM, which appears to vary the DIDs used to report the software version on the vehicle identification page. But as far as I can tell, only the APIM has that irregularity.

 

[fordtruckman2003]

Would be the first case I have lost in 15 years. Not very likely. Ford is assured to be infuriated. As we all are or should be.

As said above, best to start a dedicated thread for this topic and leave this one to those of us using FDRS to update our trucks.

 

[MoodyLaw]

As said above, best to start a dedicated thread for this topic and leave this one to those of us using FDRS to update our trucks.

Understood, will work on trying to do so. All my best, - Mike

 

[Eric55AMG]

I am not certain about what you are asking, but here is my as-built data for the BCM after the last update. The bolded software versions are changes:

<NODEID>726
<F10A>ML3T-14C636-BDC</F10A>
<F10E>ML3T-14G570-AAD</F10E>
<F110>DSMU5T-14B476-AAL</F110>
<F111>MU5T-14F141-KAB</F111>
<F113>MU5T-14B476-KAD</F113>
<F16B>MU5T-14F391-BAA</F16B>
<F16C>ML3T-14F390-CAR</F16C>
<F16D>ML3T-14F389-AFA</F16D>
<F16E>ML3T-14G163-CAC</F16E>
<F17D>MU5T-14G162-KAE</F17D>
<F17F>1BR16YY0</F17F>
<F188>MU5T-14C184-AAM</F188>
<F18C>21181191872</F18C>
<F190>XXXXXXXXXXXXXXXXX</F190>
</NODEID>

In general, FDRS reports on the vehicle identification page the software version at F188 as THE software version of the module, suggesting (to me) that F188 is the DID to be considered when determining whether the module is up to date.

Awesome ... Thank You JEB.
this is the info I was looking for. Will copy DID F188 going forward vs relying on the sometimes-inconsistent Software P/N displayed on the top half of the Vehicle info page.

Here's an example of what I see ...

ECU: Description: Engineering Assembly P/N: Software P/N:
APIM: Accessory Protocol Interface Module: DSNU5T-14G670-EC: NL1T-14D358-FB:

However F188 in the module details shows: NU5T-14G676-EC

Going forward I'll record the F188 value and see if that drives better consistency for me in my tracking.

 

[JEB]

Awesome ... Thank You JEB.
this is the info I was looking for. Will copy DID F188 going forward vs relying on the sometimes-inconsistent Software P/N displayed on the top half of the Vehicle info page.

Here's an example of what I see ...

ECU: Description: Engineering Assembly P/N: Software P/N:
APIM: Accessory Protocol Interface Module: DSNU5T-14G670-EC: NL1T-14D358-FB:

However F188 in the module details shows: NU5T-14G676-EC

Going forward I'll record the F188 value and see if that drives better consistency for me in my tracking.

Yeah, I added an edit to my post above. I think the APIM is kind of an FDRS glitch—certainly an irregularity. I think if you track F188 you should be fine.

Sponsored