ECU module programming guide using FDRS

[abd79]

I had the TRM recall done yesterday but had updated the TRM module when it was available in FDRS weeks ago. Comparing the module information currently in FDRS after the recall was done to that from weeks prior there is no change to the software or calibration that I can see. All Asbuilt info is also unchanged.

Not sure how long it takes once the dealer says it’s done for it to clear but I still show the recall in the ford app.

Sponsored

 

[Shoebox72069]

I had the TRM recall done yesterday but had updated the TRM module when it was available in FDRS weeks ago. Comparing the module information currently in FDRS after the recall was done to that from weeks prior there is no change to the software or calibration that I can see. All Asbuilt info is also unchanged.

Not sure how long it takes once the dealer says it’s done for it to clear but I still show the recall in the ford app.

Based on the driveshaft recall with the insulation.. it was at least a few days for the bang light to clear.

 

[JEB]

I had the TRM recall done yesterday but had updated the TRM module when it was available in FDRS weeks ago. Comparing the module information currently in FDRS after the recall was done to that from weeks prior there is no change to the software or calibration that I can see. All Asbuilt info is also unchanged.

Not sure how long it takes once the dealer says it’s done for it to clear but I still show the recall in the ford app.

Software isn’t out yet. That’s why there was no change. You’ll need to go back sometime after the 18th when the software is expected to be out.

 

[Snakebitten]

I have been thinking the same things. But "get it to the trucks now" has OTA written all over it. Service departments around Austin have multi-week waits. Clearly there is something not disclosed here as the Ford savings for an OTA update are huge. They WOULD NOT PASS ON THOSE $$$ unless more $$$$$$$ are at risk by using OTA.

And we may never know what those risks were. But their actuaries have done the math.. be certain of that.

OTA isn't exactly working right now, so how can Ford leverage it, especially with the pressure of a recall behind the update.

If they could deliver it OTA, I believe that their strategy would be to.

Someday OTA will be awesome. But it ain't currently.

 

[BHunted1]

The TRM was allegedly not available yet. Been checking FDRS every day since TSB was released. As far as OTA or updating and clearing a recall, I believe it doesn’t.

I had a recall for the wiper motor. That recall vanished from my FP and Ford Dashboard. Was replaced with the TRM recall. I stopped by my dealer yesterday to look up any recalls left on my truck. They told me I still had the wiper motor recall, I was also listed for BC and the TRM recall. They were updating another while I was there and said they couldnt after all said and done, because the TRM was not avail in FDRS yet. But they had a newer update to the TSB with info for them to perform it
In my case, BC has been done by me with the help of Jesse and others and only thing left is the wiper motor. Told them I’ll do the TRM if it becomes avail. As for as the wiper, none are in stock from Ford and the dealer is waiting for Ford to ship them. Crazy stuff! Again, they leave a trail of confusion for everyone.

 

[Bigwillokc]

Damn so should I return it?

 

[JEB]

Damn so should I return it?

I don’t know of anyone who has tested the Pro with the newest Ford vehicles. It might work with all of the modules, it might not. I have no information either way.

 

[ClayBell]

Hi peeps, just to clear up some technology FUD; If your vehicle is taking days or “a month” to update via USB, you have some other problem that needs to be addressed. Either there is a badly run and/or connected canbus, bad memory, bad configuration, corrupt code, or some other issue. “Let it sit overnight” Is not a fix, it’s a workaround AND CAN VERY LIKELY RESULT IN CORRUPTION. If this happens; you have something that needs to be fixed. It’s not magic, it’s just inconsistent mfr installs/builds and a data network that can’t diagnose itself

 

[Snakebitten]

There's many examples of those that had that issue with a specific APIM update, waited however long it took to kick off, and then went on to do all other updates without the problem repeating or replacing parts.

 

[Autofill]

Anyone know if the xlt 302a with 8” cluster can update to the latest APIM yet? I’m hoping to get the cameras in motion working. I’m also curious if anyone can look up my VIN to see what updates are available.

 

[FordConvert]

There's many examples of those that had that issue with a specific APIM update, waited however long it took to kick off, and then went on to do all other updates without the problem repeating or replacing parts.

My situation exactly.

 

[Jesse-Infotainment]

Hi peeps, just to clear up some technology FUD; If your vehicle is taking days or “a month” to update via USB, you have some other problem that needs to be addressed. Either there is a badly run and/or connected canbus, bad memory, bad configuration, corrupt code, or some other issue. “Let it sit overnight” Is not a fix, it’s a workaround AND CAN VERY LIKELY RESULT IN CORRUPTION. If this happens; you have something that needs to be fixed. It’s not magic, it’s just inconsistent mfr installs/builds and a data network that can’t diagnose itself

Wrong

 

[jordandev]

Anyone know if the xlt 302a with 8” cluster can update to the latest APIM yet? I’m hoping to get the cameras in motion working. I’m also curious if anyone can look up my VIN to see what updates are available.

Nope. 302A with here stuck on 21281 revision 244.

Never got an IPMA update at all.

However I do have cameras in motion enabled through forscan changes. But the bed camera side card won’t work without an IPMA update.

However @JaHoova is on the same with a 302A and DID get an IPMA updateand has the bed camera side card working after forscan changes.

We are unsure why this is different between two 302A trucks (both with 360 and no adaptive cruise). Went through both our as built data and all forscan chabges were the same but different IPMA strategy/calibration numbers (because he got an update and I didn’t).

 

[JaHoova]

Hi peeps, just to clear up some technology FUD; If your vehicle is taking days or “a month” to update via USB, you have some other problem that needs to be addressed. Either there is a badly run and/or connected canbus, bad memory, bad configuration, corrupt code, or some other issue. “Let it sit overnight” Is not a fix, it’s a workaround AND CAN VERY LIKELY RESULT IN CORRUPTION. If this happens; you have something that needs to be fixed. It’s not magic, it’s just inconsistent mfr installs/builds and a data network that can’t diagnose itself

There's a specific issue with 1.7.1 that caused some form of error where the APIM would no longer update. Some unknown set of circumstances would get it out of that loop hence the "wait a month". TSB 22-2117 solves this issue by re-flashing part of the APIM. Sometimes sitting it overnight does fix issues as well because it ensures all modules in the truck shut down.

 

[TowRig]

I have never posted on here but just wanted to post to say THANK YOU to all of you that have put work into this thread!

I have a Job 1 truck and have been following this thread waiting to see another Job 1 truck use this method to get BlueCruise. When I saw it worked I went on the search for the mongoose tool.

That tool came in last night. At 8PM last night I started updating the truck. I had almost 20 updates that were needed. I finished around 4AM. No major issues. After all that I decided to take a "nap" for a few hours.

Once I got up I took it for a drive

8AM this morning I was driving down the highway using BlueCruise!

I did try calling some dealerships to do this before I decided to take it on. No one said they could. After how much babysitting I had to do with my truck I can understand the hurdles.

Note: this may have already been said but the one shortcut I was able to make is when you are updating via USB and it asks to restart I did the following.

Shut truck off
Opened door
Waited for light around USB port to go off (less then 10 mins)
Shut door
Turned on truck.

Was successful for me everytime. I did try starting the truck once before the light went out and it was unsuccessful.

So again THANK YOU!

Sponsored