ECU module programming guide using FDRS

[sailorz]

Can’t tell you guys how much I appreciate all the advice. Almost makes me hope ford doesn’t fix it so I can take a shot. I keep a battery tender connected to my truck (I’m old and don’t drive as much as I use to) and have everything necessary except the Nano or Mongoose and the software.

Unfortunately, I suspect the dealership will probably be in the same situation. They will stick the USB in and wait. Maybe it kicks off, may not. I doubt you want them holding onto your truck for a week trying to get the dumb thing to take an update.

Sponsored

 

[MikeYQM]

I’m growing concerned, that even after updating with FDRS, the OTA will not be fixed. There have been several OTA since my 2.4.1 equivalent manual update and I have yet to receive any. Widget still says I’m stuck on 1.7.1.

I wonder if there’s something on Ford’s end that needs to reset the OTA update “push” after a failure.

 

[Jaug]

I’m growing concerned, that even after updating with FDRS, the OTA will not be fixed. There have been several OTA since my 2.4.1 equivalent manual update and I have yet to receive any. Widget still says I’m stuck on 1.7.1.

I wonder if there’s something on Ford’s end that needs to reset the OTA update “push” after a failure.

I wouldn’t worry yet. Anything past 2.4.1 is in theory only being sent to a very small select group for BC purposes.

 

[PadU235]

Never thought of that. It would explain why ford says they can't update it and then someone doing a manuel update is able to wait it out and get the update to take.

Unfortunately, I suspect the dealership will probably be in the same situation. They will stick the USB in and wait. Maybe it kicks off, may not. I doubt you want them holding onto your truck for a week trying to get the dumb thing to take an update.

Never thought of that. It would explain why ford says they can't update it and then someone doing a manual update is able to wait it out and get the update to take.

 

[BHunted1]

After many dealership failures, they got the go ahead to replace the apim. They did some updates and I did the rest. Been holding off for a bit but have a question.
I know some of you had new apims too. After doing updates via fdrs, have any of yaz received any otas at all? I have received nada. Don't think the mothership contacted my truck since months ago after failing 1.7.1 and jamming it up which led to the new apim.
I’m kinda pist because was hoping things would start by themselves like need be. Over 12k on truck and not even a year and what a pain it has been. So anyone?

 

[Snakebitten]

I was able to update all modules available but can’t seem to get mine past the 2.1.1 . But maybe that’s the newest for mine currently. 1FTFW1E89MFA46118

Here you go sir:

It could be that TCU update that is holding you up on getting further update availability?

I could be wrong but the Telematic Control Unit is "the embedded system onboard the vehicle that wirelessly connects to cloud services"

That was a quote from Google.
If it's even remotely accurate, having an update created by Ford is them saying we need to update the module on the truck that plays a role in us using OTA.

Perhaps others here with a better understanding will correct me where I'm wrong.

Having said all that, your historical data shows that you did a ton of updates just a few days ago, and even included a TCU update. But it shows "unsuccessful"

 

[RapidRedRick]

I did some digital surgery on my truck 7 days ago with a 2 day FDRS license and a Nano. Took a few steps forward, got Sync 4 software version to go from 20312 - 243 to 21281 – 244, and a few steps the other way, lost heated steering wheel and heated seats functionality. I’m getting ready to place another order for an FDRS license, so I thought I would check a few things first.
Using the FordPass - Scriptable Widget – I went and took a look at the Vehicle Module Info. Pretty cool feature of this widget, and as I understand it the data comes directly from Ford’s server. In this server data I found 8 different modules that had one or two lines of code with spaces,, ugh. I hadn’t run Forscan in a while, so I ran it and saved the Module Configuration log to compare Strategy lines in the Forscan module data with the Strategy lines from the Fordpass Widget. About an hour later I updated my module data in the Fordpass Widget. The first thing I noticed was there were now only 3 modules instead of 8 modules with spaces in code. Guessing that going into Forscan triggered the module updates from the truck to the server. What I can’t understand is why are the Strategy lines from my Trucks data (Forscan) different than the data from the Ford Server (Widget)? Shouldn't they be the same? Does this indicate that the updates made to the truck modules are not going to the Server?

FORSCAN DATA	FORD SERVER (Widget data).
PCM - Powertrain Control Module Strategy : ML3A-14C204-NEG	Strategy : ML3A-14C204-NEH
GWM - Gateway Module A Strategy : ML3T-14H021-ALE	Strategy : ML3T-14H021-EKK
APIM - Access. Protocol Interface Module: Strategy :MU5T-14G676-CA	Strategy : MU5T-14G676-EG

 

[nicholsbradley]

Yea I did do a ton. Almost 12 hours worth. I did try the

Here you go sir:

It could be that TCU update that is holding you up on getting further update availability?

I could be wrong but the Telematic Control Unit is "the embedded system onboard the vehicle that wirelessly connects to cloud services"

That was a quote from Google.
If it's even remotely accurate, having an update created by Ford is them saying we need to update the module on the truck that plays a role in us using OTA.

Perhaps others here with a better understanding will correct me where I'm wrong.

Having said all that, your historical data shows that you did a ton of updates just a few days ago, and even included a TCU update. But it shows "unsuccessful"

Here you go sir:

It could be that TCU update that is holding you up on getting further update availability?

I could be wrong but the Telematic Control Unit is "the embedded system onboard the vehicle that wirelessly connects to cloud services"

That was a quote from Google.
If it's even remotely accurate, having an update created by Ford is them saying we need to update the module on the truck that plays a role in us using OTA.

Perhaps others here with a better understanding will correct me where I'm wrong.

Having said all that, your historical data shows that you did a ton of updates just a few days ago, and even included a TCU update. But it shows "unsuccessful"

I did do allot almost 12 hours worth. I tried the TCU a couple of times but was unsuccessful. Might try again this weekend maybe it was a bad update.

 

[JEB]

I did some digital surgery on my truck 7 days ago with a 2 day FDRS license and a Nano. Took a few steps forward, got Sync 4 software version to go from 20312 - 243 to 21281 – 244, and a few steps the other way, lost heated steering wheel and heated seats functionality. I’m getting ready to place another order for an FDRS license, so I thought I would check a few things first.
Using the FordPass - Scriptable Widget – I went and took a look at the Vehicle Module Info. Pretty cool feature of this widget, and as I understand it the data comes directly from Ford’s server. In this server data I found 8 different modules that had one or two lines of code with spaces,, ugh. I hadn’t run Forscan in a while, so I ran it and saved the Module Configuration log to compare Strategy lines in the Forscan module data with the Strategy lines from the Fordpass Widget. About an hour later I updated my module data in the Fordpass Widget. The first thing I noticed was there were now only 3 modules instead of 8 modules with spaces in code. Guessing that going into Forscan triggered the module updates from the truck to the server. What I can’t understand is why are the Strategy lines from my Trucks data (Forscan) different than the data from the Ford Server (Widget)? Shouldn't they be the same? Does this indicate that the updates made to the truck modules are not going to the Server?

FORSCAN DATA	FORD SERVER (Widget data).
PCM - Powertrain Control Module Strategy : ML3A-14C204-NEG	Strategy : ML3A-14C204-NEH
GWM - Gateway Module A Strategy : ML3T-14H021-ALE	Strategy : ML3T-14H021-EKK
APIM - Access. Protocol Interface Module: Strategy :MU5T-14G676-CA	Strategy : MU5T-14G676-EG

Two things could be at work here.

First, you used a Nano. It is corrupting the as-built data. Because of the corruption, there could be differences between the local data (retrieved by FORScan) and the as-built data (retrieved by the widget) in the short term until the truck self-reports its local data and corrects the as-built data.

Second, FORScan sometimes holds onto old data if you stored a profile from a prior scan. Delete the existing stored profile and try scanning again. See if you see different strategies reported.

 

[imnuts]

Is there a confirmed way to get the cloud AsBuilt days updated properly without one of the more expensive adapters? I have spaces and garbage data in the XML download from Motorcraft and I'd like to fix it if I can.

 

[speedracercjr]

There are many that have gotten past the stuck 1.7.1 Ota failure to include myself. I am now on the latest that is out there all by following this thread and working things out with people on here. I would say most people that came here to get unstuck are now in the front when it comes to the latest and greatest updates.

Most people....stupid ass truck and the stupid ass restart loop.

 

[Thekameleon]

Most people....stupid ass truck and the stupid ass restart loop.

I not one of those people. I'm stuck on 1.7.1. I have a Platinum Hybrid and I just keep the USB in the port hoping that one day it will kick off.

 

[speedracercjr]

I not one of those people. I'm stuck on 1.7.1. I have a Platinum Hybrid and it just keep the USB in the port hoping that one day it will kick off.

I was there, for a very long time and then randomly one day it kicked over and I got past 1.7.1. That's gotta be the hardest part, once you get updated to 2.1 you'll probably be able to update easily from there on out. I'm stuck getting to 2.3, my usb start consistently but I get stuck in "restart truck to finish" loop.

 

[Jaug]

Most people....stupid ass truck and the stupid ass restart loop.

Sorry about that, very insensitive of me to be so nonchalant about my update status

 

[JEB]

Is there a confirmed way to get the cloud AsBuilt days updated properly without one of the more expensive adapters? I have spaces and garbage data in the XML download from Motorcraft and I'd like to fix it if I can.

No, not on demand. You will need to wait until the truck self-reports its data. Time frame for that is unknown. Mine never self-reported. I had corrupted data for at least a couple of weeks before I decided to spring for the Mongoose. Others reported at least a partial correction within a few days. Unfortunately, nobody has figured out a way to trigger a self-report. @iceman77 wrote that he tried but was unable to do so.

Sponsored