ECU module programming guide using FDRS

[Big Dog Daddy]

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.

How in the world would updating your software using Ford's own software and a Ford VCM void your warranty? Your using there exact prescribed products and procedures to do the exact same thing that most dealers are incapable of doing due to poor training of there own technicians. Most dealerships will not update software because they claim they "don't get paid to do it" and will not update software even if you offer to pay them to do this work. Most dealers are reluctant to touch any vehicle software due to lack of knowledge they need technicians not mechanics for software work and simply don't have them. If you really want to go after Ford, go after getting all U.S dealers to be required to update software under warranty, the same way any mechanical thing on a new vehicle would be warranted.

Sponsored

 

[fordtruckman2003]

How in the world would updating your software using Ford's own software and a Ford VCM void your warranty? Your using there exact prescribed products and procedures to do the exact same thing that most dealers are incapable of doing due to poor training of there own technicians. Most dealerships will not update software because they claim they "don't get paid to do it" and will not update software even if you offer to pay them to do this work. Most dealers are reluctant to touch any vehicle software due to lack of knowledge they need technicians not mechanics for software work and simply don't have them. If you really want to go after Ford, go after getting all U.S dealers to be required to update software under warranty, the same way any mechanical thing on a new vehicle would be warranted.

I think that is his intention, to get Ford to fix software under warranty. They do somewhat, with the procedures to fix old broken APIM updates. Still many fall behind on updates for no logical reason.

I also think in all the legal speak we all agree to with using these trucks they have something in there about software updates are not guaranteed.

 

[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.

A couple of other things I forgot to mention. Since the APIM is an anomaly in the way FDRS reports it, you might want to consider not tracking F188 at all for that module. The "About Sync" page on the Sync screen provides the Sync version and might serve as a better tracker. It's easily accessible to everyone and in that sense provides a better (or at least more common) frame of reference to compare where you are to where others are in terms of updatedness.

You also referenced above a part number for the APIM that starts with "DS." That is a totally different animal. That is found at F110 and from what I can tell is not actually a loaded piece of software. I've seen it described in the FORScan Beta materials as a "virtual" assembly number or a "calibration level" and it's derived from the software levels in the other DIDs. I don't know how Ford uses it so I can't say if it would be useful to track it. But it isn't a piece of software in the way F188, for example, is. You won't see it anywhere among the software and calibration items downloaded to your hard drive for installation.

 

[Eric55AMG]

Appreciate the additional insight / information.
Basic sync versions / revs are much easier to follow.

What I was wondering (maybe hoping) is if some of the underpinning files were getting updated without actually changing the full sync version.

By tracking the inconsistent data points, I was suspecting this may be the case ... but now I'm thinking the "bug" in FDRS was simply reporting different DIDs in the "Software P/N" in the top section of FDRS.

Specific to the sync version, I've been stuck on 23159 Rev:915 for many months.

First world "problems" for sure - LOL

 

[JEB]

Appreciate the additional insight / information.
Basic sync versions / revs are much easier to follow.

What I was wondering (maybe hoping) is if some of the underpinning files were getting updated without actually changing the full sync version.

By tracking the inconsistent data points, I was suspecting this may be the case ... but now I'm thinking the "bug" in FDRS was simply reporting different DIDs in the "Software P/N" in the top section of FDRS.

Specific to the sync version, I've been stuck on 23159 Rev:915 for many months.

First world "problems" for sure - LOL

The software reported for the APIM in FDRS is different just about every time I log in, even when I know there's been no APIM update activity. I disregard it.

As for the Sync version, I can't say with certainty that there's never been an occasion where a software or calibration file was updated without the Sync version changing. But I don't remember it ever happening, either. So, Sync version is what I tend to rely on. Another check I use is to periodically download the as-built data from Motorcraft and save it on my hard drive. Then I can compare more recent as-builts to older ones to see if there are any changes.

 

[M.R.F.O.R.D.]

Looks like the SOLAR PL2320 Pro Logix Battery Charger 20 Amp is on sale/discounted at Amazon right now. I was cheaper for me to order from Amazon in the USA than Amazon in Canada.

 

[johnsond98]

Hey there, first time trying to connect to FDRS and getting this error. I have internet connection but its not allowing me to log in. I purchased the 2 day license this morning. any insight would be appreciated.

 

[Big Dog Daddy]

Hey there, first time trying to connect to FDRS and getting this error. I have internet connection but its not allowing me to log in. I purchased the 2 day license this morning. any insight would be appreciated.

Sunday mornings can be problematic trying to login to FDRS. This is when they update there servers. Usually by early afternoon you can get in.

 

[johnsond98]

Sunday mornings can be problematic trying to login to FDRS. This is when they update there servers. Usually by early afternoon you can get in.

Thanks for your response. Im about ready to pull my hair out lol. Will try it this afternoon. Thanks

 

[nitrobass24]

might also want to try 37.4.7 if you are on windows 11.

 

[RickBullotta]

Thanks for your response. Im about ready to pull my hair out lol. Will try it this afternoon. Thanks

My advice is to wait until Tuesday. The last thing you want is an FDRS glitch partway through 11 hours of updates....

 

[adt1982]

My advice is to wait until Tuesday. The last thing you want is an FDRS glitch partway through 11 hours of updates....

Unfortunately, waiting until Tuesday would mean he's looking at spending another $50...

 

[superfordman]

Hey there, first time trying to connect to FDRS and getting this error. I have internet connection but its not allowing me to log in. I purchased the 2 day license this morning. any insight would be appreciated.

You are using the wrong login option, need to select independent operator/non dealer.

 

[johnsond98]

You are using the wrong login option, need to select independent operator/non dealer.

Selecting that option comes up with this screen, only allowing me to put in a 8 digit user ID?

 

[superfordman]

Selecting that option comes up with this screen, only allowing me to put in a 8 digit user ID?

Just FDRS being FDRS (on a Sunday mainly). Try again later. Make sure now firewalls or anything are in the way. I had the same issue with my old laptop the other week so just kept using my newer one that works just fine with it.

Sponsored