ECU module programming guide using FDRS

[JEB]

The changes I made in Forscan only two weeks ago are now showing up as my As-Built file. Does this mean if I updated, or restored any module using FDRS As-Built’s that my Forscan changes are now considered my new factory settings?

Yep. Now, every time you update a module with FORScan changes that populated to the server, that as-built data, including the changes, will be reloaded during the configuration stage.

Sponsored

 

[Jmeo]

Yep. Now, every time you update a module with FORScan changes that populated to the server, that as-built data, including the changes, will be reloaded during the configuration stage.

Excellent news. Yet another justification for using FDRS in my opinion. Once I am done making all my changes (adding projector LED, HSW, front parking sensors, ACC, and RSW), I will use FDRS to have my As-Built's updated with the changes. Now going forward, anytime I do module updates, I will not have failed updates do to inconsistent data in the As-Builts.

Assuming I am understanding this all correctly that is?

 

[JEB]

Excellent news. Yet another justification for using FDRS in my opinion. Once I am done making all my changes (adding projector LED, HSW, front parking sensors, ACC, and RSW), I will use FDRS to have my As-Built's updated with the changes. Now going forward, anytime I do module updates, I will not have failed updates do to inconsistent data in the As-Builts.

Assuming I am understanding this all correctly that is?

Not quite. You cannot manually trigger an upload of your truck’s configuration data to the server using FDRS or any other mechanism. It is automatic and nobody really knows when or how frequently the upload occurs. We only know that it will occur eventually. Some have seen the server updated quickly (e.g., you), for others it has taken quite a bit longer.

 

[Jmeo]

Not quite. You cannot manually trigger an upload of your truck’s configuration data to the server using FDRS or any other mechanism. It is automatic and nobody really knows when or how frequently the upload occurs. We only know that it will occur eventually. Some have seen the server updated quickly (e.g., you), for others it has taken quite a bit longer.

OK, thanks for the explanation.

 

[Bob_Mac]

I do not think it is necessary to revert anything before updates. about a year ago we had thought IPC changes were causing issues but we have since learned that was a red herring. depending on the state of sync between your truck and the mothership you may lose some
forscan changes and have to reapply them.

Not true. It wasn’t a red herring. It just turned out not to be widespread because not all FORScan changes caused problems—only certain changes to certain modules. I know @Bob_Mac had problems with some of the FORScan changes he made to the APIM and IPC causing FDRS updates to fail at the configuration stage and he had to revert the FORScan changes to complete the update. See Post #2628. So, although the problem was limited and it was easily fixed by reverting, completing the configuration, and then redoing the FORScan changes, it was real.

Ajzride, don't know how you came to that conclusion but it is incorrect, @Jesse-Infotainment was the one who pointed me in the right direction when an update failed.

 

[Ajzride]

Ajzride, don't know how you came to that conclusion but it is incorrect, @Jesse-Infotainment was the one who pointed me in the right direction when an update failed.

I was thinking specifically when a bunch of us had F120 fail to load on our IPC and got stuck in liMbo. We had initially thought forscan changes to IPC had caused that. later several with no changes got stuck the same way. Your situation had slipped my mind. I have corrected my post.

 

[roadPilot]

Not true. It wasn’t a red herring. It just turned out not to be widespread because not all FORScan changes caused problems—only certain changes to certain modules. I know @Bob_Mac had problems with some of the FORScan changes he made to the APIM and IPC causing FDRS updates to fail at the configuration stage and he had to revert the FORScan changes to complete the update. See Post #2628. So, although the problem was limited and it was easily fixed by reverting, completing the configuration, and then redoing the FORScan changes, it was real.

Mine was likely an isolated situation (success), but I had FORScan changes in both the IPC and BCM modules when I updated them (and others) with FDRS, and neither of those had issues being updated.

EDIT: After a quick review of my spreadsheet, only the BCM had changes @ that time, not the IPC. But no failure occurred when I updated it.

 

[Jesse-Infotainment]

They have updated the IPC update to a single step. They used to have two updates. For whatever reason. THey used to have a first half and then a second half. Made no sense. They have no eliminated that and there is a single IPC update directly the FDC/FCA

The original issues were more of the fact people were not getting the second half of the IPC update. That or they would get a mismatch of the two updates.

The AS BUild changes in Forscan would cause issues during the config portion of the update. The IPC update brings along a new AS build config. It would screw up the AS build update portion if you had changes. If your changes are common to the canadian truck like adding the digits below the temp then it knows how to deal with that.. if it is more then sometimes it would fail or screw it up and give a DTC of config mismatch

We know now. When @Bob_Mac originally did the updates he was one of the first and we were figuring it out as we went. Now we have the benefit of everything that has happened to know and learn from .

 

[roadPilot]

We know now. When @Bob_Mac originally did the updates he was one of the first and we were figuring it out as we went. Now we have the benefit of everything that has happened to know and learn from .

Which is as with most everything else we do on these trucks and dicuss here and on other forums.

Thanks for the 411.

 

[betathalguy]

I got my laptop and charger, but not receiving my Mongoose cable until Monday. I installed the Opus Driver from the link, which was an old version and proceeded to update to the latest. I then downloaded the FDRS software and installed, but it said that my VCI driver is an old version. Does anyone know what this is about? In the FDRS package there was also a 64 to 32 bit bridge. Is that something I have to download?

A little confused as to what exactly I need with this FDRS program. Thanks for any advice. I just wanted to have everything straight before I attempt these updates.

 

[Big Dog Daddy]

I got my laptop and charger, but not receiving my Mongoose cable until Monday. I installed the Opus Driver from the link, which was an old version and proceeded to update to the latest. I then downloaded the FDRS software and installed, but it said that my VCI driver is an old version. Does anyone know what this is about? In the FDRS package there was also a 64 to 32 bit bridge. Is that something I have to download?

A little confused as to what exactly I need with this FDRS program. Thanks for any advice. I just wanted to have everything straight before I attempt these updates.

The VCI driver is for Ford's VCM interface. You don't really need to install it, but I installed it just to make the software stop asking about it every time I load FDRS.

 

[betathalguy]

The VCI driver is for Ford's VCM interface. You don't really need to install it, but I installed it just to make the software stop asking about it every time I load FDRS.

Okay, good. I didn’t know if downloading it would screw anything else up. Ill just wait to get the cable and reinstall everything after I activate the cable..

 

[Tungy01]

Just picked up my truck from the dealer for warranty work. I had asked them to update 4 modules and they said it was completed, but i don't see the version 22293 - Revision 610. They were suppose to update the APIM/BCM/WACM/PCM

Can someone list the updates available for my truck, so i could see if they did the updates or not.

Much appreciated: 1FTFW1RG1NFC31153

 

[Shyrax]

Mongoose should be delivered in a couple days. Looking at my list, what is the suggested order to install these updates?

 

[TexasTruck]

I don't mean to be ding-a-ling here... I'm really trying to follow this... so instead of going to my local Ford dealer to enable all the things I did with FORScan, I can use this "FDRS" procedure/process/software/cable/licensing/juju/etc?

My truck is set for OTA updates but I thought that was only for Sync4 updates?

How do owners get the OTA flash updates? Is this the same as going to a dealer and them flashing you?

Sorry for not knowing this stuff, I'm trying to keep up ?‍

Sponsored