TSB 22-2117 - Fix for Stuck Power-Up 1.7.1 Update

[ProximusAl]

In the UK there is no APIM update available in FDRS (aka OTA 2.3.0). I have a failed OTA 2.3.0 which has never retried since February, but I don’t even have the option to manually update it using FDRS. I don’t have a stuck 1.7.1 as I did it manually with FDRS before.

Sponsored

 

[ZuleMME]

Work like this is just quite foreign to mechanics. They really should consider enlisting the dealerships IT guys to do FDRS work on the EV's...

 

[ZuleMME]

In the UK there is no APIM update available in FDRS (aka OTA 2.3.0). I have a failed OTA 2.3.0 which has never retried since February, but I don’t even have the option to manually update it using FDRS. I don’t have a stuck 1.7.1 as I did it manually with FDRS before.

Check under bezel diagnostics if you have the serial number for your APIM. If not; you have the same problem just different software load.

 

[Illinibird]

I preformed this fix on @Shaggyrn car yesterday. It was very straight forward.

Pull the plastic molding, disconnect the USB hub, Start the "Module Repair" in FDRS, it does a few quick operations, then installs the windows drivers for the Sync system. Then you plug in the USB cable to the APIM from the laptop, and it does a few more quick things, then you switch to the ethernet connection. At this point, it went through a series of steps, Resetting the APIM, and then the TCU. Then It went through a rewrite of the data base on the APIM and then the TCU. And then it was done. Takes about 10 minutes total.

As soon as it was done, checking the about sync page, and the version number was back, and the automatic updates could be turned on and off again.

After that APIM and TCU updates applied successfully.

After that I went through all the updates I could, and ended up taking almost 10 hours to get through all of them. The longest being the IPMA of course.

After applying a few of the updates, several more popped up. Seems like some of the updates trigger others to show up on the list. After the 1.7.1 fix an APIM version showed up. Updated that. Then did a few other modules, then another APIM version came up.

Thank you for explaining what you did. This really helps me to understand what is going on and what steps it takes to do it. I know they will not take the time you did to install all the updates if it took 10 hours so I wonder if they'll come OTA or not.

 

[benk016]

Thank you for explaining what you did. This really helps me to understand what is going on and what steps it takes to do it. I know they will not take the time you did to install all the updates if it took 10 hours so I wonder if they'll come OTA or not.

They should come OTA, just don't know when they'll start releasing them again to cars that had this issue.

All the updates I did were not required to be done after the fix. The only one that I needed to do was the APIM update which basically just installed the 1.7.1 version again since it didn't actually install the first time. There was not a TCU update to apply after the fix was done.

A few other updates I did prompted another TCU update, and then the APIM update to 2.3.0 also showed up.

 

[ProximusAl]

Check under bezel diagnostics if you have the serial number for your APIM. If not; you have the same problem just different software load.

Well I’ll be. My serial number is — only in bezel diagnostic. Sync version shows fine in normal about
So if I perform the procedure it should fix it?

 

[Illinibird]

They should come OTA, just don't know when they'll start releasing them again to cars that had this issue.

All the updates I did were not required to be done after the fix. The only one that I needed to do was the APIM update which basically just installed the 1.7.1 version again since it didn't actually install the first time. There was not a TCU update to apply after the fix was done.

A few other updates I did prompted another TCU update, and then the APIM update to 2.3.0 also showed up.

Well I hope they know to do the APIM update when they're through then. I agree with what was said earlier, Ford needs to have IT people to work on these cars as it takes that type of knowledge to be able to do it.

 

[benk016]

Well I hope they know to do the APIM update when they're through then. I agree with what was said earlier, Ford needs to have IT people to work on these cars as it takes that type of knowledge to be able to do it.

Well as long as they follow the TSB, it will tell them to apply AIPM/TCU updates after if they are available.

Also, at the end of the Module update repair process, the last prompt it tells the tech is " The Module Update Repair procedure was successful! Perform any software updates on the TCU and APIM as required. "

 

[ProximusAl]

 

[dml105]

Well, that's concerning....

 

[benk016]

I suspect they have this setup to look for a stuck 1.7.1 update. Since you mention you got stuck on 2.3.0, it may not detect needing done.

 

[Gimme_my_MME]

Well, that's concerning....

 

[Logal727]

This is actually pretty accurate. It seems like most dealers just don't want to touch this car.

They can see their future. Ford just needs to open company owned shops already. You can’t get cooperation for an industry as it’s being lead to its demise.

 

[Gimme_my_MME]

I suspect they have this setup to look for a stuck 1.7.1 update. Since you mention you got stuck on 2.3.0, it may not detect needing done.

Oh yeah that's 100% what it is. This will ONLY work for stuck 1.7.1

 

[ProximusAl]

Oh yeah that's 100% what it is. This will ONLY work for stuck 1.7.1

Great.

Sponsored