ECU module programming guide using FDRS

[Snakebitten]

Interesting, can you Message me the exact process so I can test and update the doc?

Edit: Don't you mean the BCM (BodyCM)?

Yes, BCM

What's with my dyslexia today? ??

Sorry about that.

Sponsored

 

[Bob_Mac]

Well making headway now. Got some updates done but of course can't get rid of the GSM update and the APIM won't kick start from USB.
Now I need to work on my TRM DTC. My truck didn't come with the controller but I added it and had Ford program it - well thought they did. It has a DTC and I'm attaching some screen shots. I have the PDF with the steps to program it through FDRS but that didn't take care of the DTC.
Any Advice on which ones to proceed with?

While in the toolbox click the All tab then click on TDM on the left side you should see a new tab show with TRM as it's label now click on TRM - Programmable Module Installation (PMI) then Download and run. Go through the prompts as if you already installed a new module and report back if that cleared your DTC

The GSM will not go away... disregard it as it appears to be a bug

 

[windowsmedia10]

Alright you fellow ECU module programming nerds, I had a few hours today and got around to updating my Feb/21 build Lariat 502A 4x4 SCREW 2.7L.

Some notes:

• I'm in Canada and the suggested battery charger/conditioner was expensive up here. I used this guy from Canadian Tire and it worked great. The procedure to hook it up was red to the battery terminal, and then black to the elevated bolt thing shown in a few pictures in this thread. I got my VXDIAG from this site for $120 CAD with free shipping.
• Although my truck was a Job 1 build, I only had a handful of updates available. My truck has not been into the dealer. I had PCM, the digital dashboard, both door modules, and a few others like the steering module.
• The update procedures listed here were spot on. The trickiest part was to remember to leave the USB key in after one of those updates, open the driver door, and then let the truck power down before clicking it back on and waiting for the remove USB message.

Some questions:

• Now that my PCM has been updated, would it make sense to run any of the routines like the transmission adaptive tables? What about just disconnecting the battery for a while so the truck can relearn its idle strategy etc?
• I updated everything that was available and I'm still on 2.3 instead of 2.4.1. Is that normal?
• Has anyone actually noticed a difference in functionality, stability, or performance after updating a module?
• Is Ford planning to do this module update business OTA at some point?
• Ford recently announced that they are moving away from their in-house developed Sync software in 2023 for an Android OS based infotainment. Their CIO was recently quoted as saying "We were spending hundreds and hundreds and hundreds of millions every year, keeping up with basically a generic experience that was not competitive to your cellphone.". Any sense if whether or not our trucks will be updatable to that Android platform if come MY23 or if we're going to be permanently a generation behind?

Thanks!

 

[daemonic3]

Hey team!

I have to take my truck in (job1 - Feb'21) this week to get a proximity sensor replaced. I asked the service manager if they can update my truck with all available modules while its in if I leave it for the day. He doesn't know the modules by name, and I do not yet know the savviness of the techs there, but I asked if I walk in with a list of the bare minimum modules to update if they can hand it to the tech.

For sure when they run FDRS they will find several updates available. Do you guys know the bare minimum required to enabled cameras in motion? I already did the required Forscan changes like for the bed camera card to be prepared. I know I need the IPMA for sure, any others? Any kind souls want to run my VIN so I can make a list of updates to request?

If I find my local dealer is not savvy enough or not willing to do these updates, I will have to join the FDRS team.

 

[iceman77]

Hey team!

I have to take my truck in (job1 - Feb'21) this week to get a proximity sensor replaced. I asked the service manager if they can update my truck with all available modules while its in if I leave it for the day. He doesn't know the modules by name, and I do not yet know the savviness of the techs there, but I asked if I walk in with a list of the bare minimum modules to update if they can hand it to the tech.

For sure when they run FDRS they will find several updates available. Do you guys know the bare minimum required to enabled cameras in motion? I already did the required Forscan changes like for the bed camera card to be prepared. I know I need the IPMA for sure, any others? Any kind souls want to run my VIN so I can make a list of updates to request?

If I find my local dealer is not savvy enough or not willing to do these updates, I will have to join the FDRS team.

PM me your VIN and I can run a scan for you

 

[Jesse-Infotainment]

Appears that as long as your apim is 21146 or higher the Forscan changes for cams in motion will work. I had originally believed the ipma needed to updated that has been shown not to be the case.

 

[daemonic3]

Appears that as long as your apim is 21146 or higher the Forscan changes for cams in motion will work. I had originally believed the ipma needed to updated that has been shown not to be the case.

Ah, thanks Jesse! I think I did get that info from you before, so this is fantastic to know.

PM'ing VIN to @iceman77, thanks in advance!

 

[Snakebitten]

I guess I won't be updating the IPC tonight. It keeps erroring out in the beginning when it starts to download update software. Tried multiple times still a no go. Guess I won't be fully updating tonight.

Jaug,
Never heard back from you regarding your IPC update. Get it done?

 

[Snakebitten]

Anyone feeling like they have no choice but to update the IPC using the bus instead of the USB should try ONE other thing first.

The USB routine is much like the other USB updates and will begin by FDRS downloading the necessary update files to the USB stick. Then you are prompted with the SAME FDRS USB screen prompt that FDRS always prompts with :

I believe that for this particular IPC USB update, that screen is possibly an inaccurate depiction of the proper routine. I say that because I believe that the screen above can only be accurate if the truck performs the entire update process on its own with no assistance from FDRS.

In other words, the USB stick will be inserted, the onboard system trigger and will copy those files. Then the files will be acted upon (executed) by the onboard system independent of FDRS. In fact, notice that the FDRS prompt above ends with a question of whether the update was successful or not. That implies that YOU will know whether it was or not based on the Sync screen informing you that it was.

However, the IPC files on the USB stick trigger the onboard system to copy the files (exactly like the APIM and TCU) and the progress bar on the Sync screen shows that it completes. But that's it. Nothing else ever happens. No "restart truck"..... Nothing.

If you leave the USB stick in and restart the truck just because you think maybe it will do something (because other updates included that routine) you will find that nothing happens except the ordinary detection and indexing of the USB stick.

But, if you return to FDRS and click "Yes" on the standard instruction screen, FDRS immediately runs a verification of the files that are related to the IPC update and then EXECUTES the writing to blocks on the module.
In other words, unlike what that instruction prompt states, the truck does not prompt you to do anything, and certainly not say yes to FDRS to complete the update.

I suspect this is why some have answered NO and then chose to update via canbus because they think the update failed.

I think there is a considerable lack of consistency between how each update is constructed. Or at least FDRS doesn't have accurate screen prompts to accommodate subtle differences between updates that are not identical in necessary routine.

Having said all this, maybe I just got lucky again? This is twice now that I didn't get stuck in a loop or dead end by deviating from FDRS or Sync screen prompts that resulted in failure

 

[Jaug]

Jaug,
Never heard back from you regarding your IPC update. Get it done?

Never did get it to work. It would error out right away when it tried to download the update software. My license expired so haven't gotten to try again. Waiting for bluecruise update to maybe be available to make it worth purchasing the license again.

 

[Snakebitten]

Never did get it to work. It would error out right away when it tried to download the update software. My license expired so haven't gotten to try again. Waiting for bluecruise update to maybe be available to make it worth purchasing the license again.

Did you see this fresh BlueCruise email thread?
If true, then my Job1 BC pessimism just might prove folly.

 

[Jaug]

Did you see this fresh BlueCruise email thread?
If true, then my Job1 BC pessimism just might prove folly.

I did and have been refreshing it in hopes someone reports that it they finally got it!

 

[Bob_Mac]

I decided to get the Mongoose and it'll be here on Wednesday, I am not going to touch the truck or use FDRS until then and hope that the corruption clears up when the truck phones home to the servers. I have until 3/20 to return the Nano since I purchased it from Amazon so there will be time to do some testing between the devices.

 

[JEB]

I agree. I think it's more related to the speed of the VCX Nano. My UCDS adapter hasn't had the corruption others have. I only have the ML3T- the part number in the Sync Module.
My data is back to looking good again. My truck must have sent in the latest data.

I just tried out your new widget to check my “as-built” data. Thanks for this valuable update. But it raises even more questions. Are you sure your data is now uncorrupted, even for the APIM? It looks good as far as it goes. But my APIM data is showing, among other things, an “unknown node” at (F12A) and missing parts of the strategy code: ML3T- 6-BJ. You have no (F12A) node at all. There might be other differences as well—I still have corruptions so it’s hard to parse.

 

[Bob_Mac]

FYI

SSM 50383 - 10 Jan 2022 - 2021 F-150/Mustang Mach-E - Over-The-Air (OTA) Failed Message In The Center Touchscreen / SYNC Software Does Not Download From The USB

Some 2021 F-150/Mustang Mach-E vehicles may display OTA Update Not Successful messages on the vehicle’s center touchscreen. Also, when a software update is being performed on the accessory protocol interface module (APIM) using the FDRS, the center touchscreen may not indicate the APIM software is downloading when plugging a USB drive into the vehicle. This may be due to an APIM software concern.Inform customers that Ford is currently working on a solution for this condition that is to be released via the Ford Diagnosis and Repair System (FDRS) in February 2022. Inform the customer that they can continue to drive the vehicle and only need to schedule a follow-up appointment if they are still experiencing the OTA Update Not Successful message in March 2022 or if the APIM is not able to be updated via the FDRS. Monitor OASIS for updates.

Sponsored