ECU module programming guide using FDRS

[BHunted1]

I’ll take a look at your vin and see what you are or what update you got. That sync version is old though.. the on in your picture

Can you double check mine to please In case I missed something? : 1FTFW1ED9MFA98104

Sponsored

 

[Lodans]

I finally took the plunge and did the updates. It was a little nerve racking at first but once I successfully completed the first module I was more confident. I want to thank everyone on this thread that has contributed as this made things much easier. I can report I am on the latest version on power up’s and sync based on the new features on Sync. I updated every module and some of them multiple times when they came back up. Some things to note:
1. Windows 11 did not work for me I had to get my other laptop which is windows 10.
2. For the USB I used a HP USB 3.0 128 gig and it was perfect.
3. My sync system never told me to remove the usb once everything was complete. I would get the updating system, then the restart to finish, then after restart I would not get anything. I put the USB back in my laptop and finished the process and it all passed. I did have to run the verification twice.
4. I still have the ABS and one other module like everyone else that still shows up as needing software updates. I may try later to see if they will clear.
If I can be of help to anyone please let me know.

 

[iceman77]

F*ck @Ford Motor Company for making this so infuriating. I went to get gas, turned my truck off and now I’m back to blanks and unable to turn on/off auto updates. I’m so over this BS

Damn, you just missed that short window of opportunity when your APIM/GWM exited the “limbo” mode. It was still on “old” version, but that’s when you were suppose to insert your FDRS update USB drive. I am positive you would have gotten your update prompt show up!

 

[speedracercjr]

Damn, you just missed that short window of opportunity when your APIM/GWM exited the “limbo” mode. It was still on “old” version, but that’s when you were suppose to insert your FDRS update USB drive. I am positive you would have gotten your update prompt show up!

Thats exactly what I thought, after I lost that window. FML

 

[iceman77]

Thats exactly what I thought, after I lost that window. FML

Don’t worry so much about it. There will be another opportunity, within days. Just keep an eye on this

 

[Airborne_Ape]

This is amazing

 

[MikeYQM]

Question for those who were stuck on 1.7.1:

I updated all modules the other day. However, when I look at OTA updates in the widget it tells me the servers still think I’m stuck on 1.7.1, with a fail date of 2021-12-24.

Has anyone that’s updated their vehicle with FdRS seen the OTA info update from being stuck on 1.7.1 to more correct info?

I’m concerned this might still block me from future OTA updates.
Thanks

 

[BHunted1]

Question for those who were stuck on 1.7.1:

I updated all modules the other day. However, when I look at OTA updates in the widget it tells me the servers still think I’m stuck on 1.7.1, with a fail date of 2021-12-24.

Has anyone that’s updated their vehicle with FdRS seen the OTA info update from being stuck on 1.7.1 to more correct info?

I’m concerned this might still block me from future OTA updates.
Thanks

Same here…. Its messed up. Been like that even after a new apim and fdrs updates.

 

[iceman77]

Question for those who were stuck on 1.7.1:

I updated all modules the other day. However, when I look at OTA updates in the widget it tells me the servers still think I’m stuck on 1.7.1, with a fail date of 2021-12-24.

Has anyone that’s updated their vehicle with FdRS seen the OTA info update from being stuck on 1.7.1 to more correct info?

I’m concerned this might still block me from future OTA updates.
Thanks

After I finished updating all modules via FDRS (including APIM) my OTA info did not change. It still reported failed 1.7.1 attempt just as before FDRS updates. A week later I have received the 2.3.0 OTA update. Like i mentioned in other posts many times before, the OTA status does not matter. its the node data stored in your As-Built that reports all your SW level info to Ford that matters. If your GWM is in good shape, that information gets updated automatically unless you disable vehicle connectivity in your truck.

 

[BHunted1]

After I finished updating all modules via FDRS (including APIM) my OTA info did not change. It still reported failed 1.7.1 attempt just as before FDRS updates. A week later I have received the 2.3.0 OTA update. Like i mentioned in other posts many times before, the OTA status does not matter. its the node data stored in your As-Built that reports all your SW level info to Ford that matters. If your GWM is in good shape, that information gets updated automatically unless you disable vehicle connectivity in your truck.

Going to go out and try the method you mentioned. Want to grab it before I change anything?

 

[iceman77]

NOTICE: Due to a suspected bug in the VCX Nano driver, I would recommend NOT TO RUN "Network Scan" when initiating session with FDRS for your truck. Doing so, your module information gets corrupted in your on-line As-Built dataset resulting in loss of certain functions (such as SecuriAlert and OTA). Instead, let the FDRS download the latest module config from the FORD server. Here is how to proceed:

1) Launch FDRS, but do not connect your VCX Nano to your truck (yet)

2) Enter VIN manually, or if you have saved an existing session, just click Go. You will be prompted with a message like this:

3) Click Continue and let the software to download all your truck related info from the cloud

4) Navigate to Toolbox tab and select SW updates. Note how I am being offered GWM SW update (which is part of Power-Up 2.4.1 OTA rollout), without doing any networks scan:

5) Connect VCX Nano, and proceed with SW update as usual. It will work just fine!

WARNING: Do not update the CCM module using the VCX Nano device. Doing so will brick the module that can be only recovered using the Mongoose-Plus (or official VCMII or VMC3) device


Some background on the Network Scan importance:

Network Scan is deemed important (as per Ford), as it reports the current state of module configuration to your As-Built dataset on Ford servers. These data are needed to reload configuration to the module after module SW update or PMI (Programmable Module Installation) function is executed. Note though, your truck performs and reports its own "Network Scan" periodically. However, it might happen that your configuration is not up to date, especially if there is a gap between the latest "self-report" and your module update. This can be easily mitigated by saving the module configuration via ForScan and reloading it after module SW update is completed. The module configuration does not change much, and I had to personally do this only once, when my FDRS based APIM update knocked out all of my ForScan changes.

 

[iceman77]

NOTICE: If you happen to lose certain "connected" functionalities (such as Horn & Light, SecuriAlert and OTA) after playing around with FDRS, here is how you fix it:

1) Connect your VCX Nano to your computer and your truck.

2) Open FDRS, and run a Network Scan. (Contrary to the above post, in this case this is a necessary step)

Once done, make sure your GWM module is showing a valid Software P/N (the field should not contain any spaces or special characters). Should be ML3T-14H021-XXX. See example below:

This usually fixes the SecuriAlert and Horn&Ligths issue. If not, restart FDRS (this step is important) and run another network scan. Repeat this until GWM Software P/N is shown in proper format

 

[BHunted1]

NOTICE: If you happen to lose certain "connected" functionalities (such as Horn & Light, SecuriAlert and OTA) after playing around with FDRS, here is how you fix it:

1) Connect your VCX Nano to your computer and your truck.

2) Open FDRS, and run a Network Scan. (Contrary to the above post, in this case this is a necessary step)

Once done, make sure your GWM module is showing a valid Software P/N (the field should not contain any spaces or special characters). Should be ML3T-14H021-XXX. See example below:

This usually fixes the SecuriAlert and Horn&Ligths issue. If not, restart FDRS (this step is important) and run another network scan. Repeat this until GWM Software P/N is shown in proper format

Your photos are not showing up btw.

 

[iceman77]

Your photos are not showing up btw.

Fixed!

 

[BHunted1]

So does that mean my gwm is still behind?

Sponsored