Post here if you have an active FDRS account and are willing to look up info for others

[justalfe]

Well you can try to update the APIM using FDRS...but the problem was that the data corruption on the APIMs that got borked actually prevented the techs from doing it using FDRS the normal way.

So they were supposed to buy a selection of special USB and network adapters to kind of 'side-load' into the APIM to clear out the corrupted data. It's time-consuming and many techs just ended up replacing the APIM to fix the problem (the returned APIMs go back for lowlevel reprogramming that fixes the issue, and then they're put back into spares circulation).

Attached is the latest TSB that addresses this issue....but it's now no longer in effect and techs have been told within the last year to just follow the workshop guidance ...which generally ends with the APIM being replaced (RVC code issued).

that tsb doesn't seem to bad.. I'm a IT guy by trade

Sponsored

 

[Snakebitten]

Well you can try to update the APIM using FDRS...but the problem was that the data corruption on the APIMs that got borked actually prevented the techs from doing it using FDRS the normal way.

So they were supposed to buy a selection of special USB and network adapters to kind of 'side-load' into the APIM to clear out the corrupted data. It's time-consuming and many techs just ended up replacing the APIM to fix the problem (the returned APIMs go back for lowlevel reprogramming that fixes the issue, and then they're put back into spares circulation).

Attached is the latest TSB that addresses this issue....but it's now no longer in effect and techs have been told within the last year to just follow the workshop guidance ...which generally ends with the APIM being replaced (RVC code issued).

I haven't been around here long enough to know for sure, but the same exact issue affects 2021 F150 with Sync4. (No doubt Mike is aware)

Lots, and I mean lots of fellas with the issue were able to get out of APIM Purgatory by creating the USB memory stick using FDRS, and then leaving the stick in the trucks USB hub until the update finally kicked off and completed. It could take 2 days, or 2 weeks. A few took even longer. But the vast majority did in fact succeed, and from that moment on, their APIM has been just as reliable as a replacement APIM is. And that means they could continue to update their trucks using FDRS, all the way until their trucks were current. It also solves the issue with Auto Update scheduling no longer being greyed out and not functioning.

 

[TNG_Guy]

Hello,

Can someone please check my car?

VIN: 3FMTK3SU5MMA03225

The last update I received was on June 7th for 24-PU0301-BLM-PE. I’m not sure if I should just continue to wait as updates are being rolled out to the 21 models or if my updates are stuck because of an issue with the IPMA.

Thanks

 

[jmgreen]

Lots, and I mean lots of fellas with the issue were able to get out of APIM Purgatory by creating the USB memory stick using FDRS, and then leaving the stick in the trucks USB hub until the update finally kicked off and completed. It could take 2 days, or 2 weeks. A few took even longer.

I am curious: Does this mean that the update then starts out of the sudden and uncontrolled, e.g. during the night, and w/o any required interaction from an "operator" (e.g. put the car into "Key On, Engine Off", ...). But then you also will never have an external power supply attached to the LV battery. So this is not dangerous, i.e. the APIM update does not require that much amps, and the LBV can support this alone w/o external help?

 

[Nugatti]

Could anyone check my VIN? And perhaps see why my lane keep assist isn’t working? WF0TK3SU5MMA23992

 

[Mike G]

Hello,

Can someone please check my car?

VIN: 3FMTK3SU5MMA03225

The last update I received was on June 7th for 24-PU0301-BLM-PE. I’m not sure if I should just continue to wait as updates are being rolled out to the 21 models or if my updates are stuck because of an issue with the IPMA.

Thanks

I see a DTC that has an associated TSB that says your powertrain modules need to be updated. I would also call the BEV team and ask them when you'll be getting the BC 1.3 update that you need to take advantage of your paid subscription (800-392-3673) and ask them to open a case for you to sort that out.

Here's the list of available software updates in FDRS for your VIN (powertrain and IPMA updates are included):

 

[Mike G]

Could anyone check my VIN? And perhaps see why my lane keep assist isn’t working? WF0TK3SU5MMA23992

I'm unable to see any vehicle health info about your car.

Are you the original owner?

You may need to perform a 'Factory Reset" in Sync and delete the car from your FordPass app and add it back and then enable the settings so that your car can report to the cloud it's status.

Should look like this.

Here's the list of available software updates today for your VIN in FDRS:

 

[XeonBAMF]

You have an available update for the IPMA and PSCM which should address those issues.

Do you see anything that would prevent the car from doing these updates? I have auto-update on and its on wifi at home and work.

 

[Mike G]

Do you see anything that would prevent the car from doing these updates? I have auto-update on and its on wifi at home and work.

I don't really see anything out of the ordinary. You may want to call the BEV team and ask them why you haven't been updated. 800-392-3673

 

[kdonnel]

Wondering if the block on my TCU has been removed.

3FMTK2R73NMA04935

I saw some posts where you mentioned the possible need to run the Read the Configuration Data routine to another forum member. I wonder if my manual changes to turn on BC 1.3 might have tripped up the process, though I didn't make changes to the TCU.

 

[Snakebitten]

I am curious: Does this mean that the update then starts out of the sudden and uncontrolled, e.g. during the night, and w/o any required interaction from an "operator" (e.g. put the car into "Key On, Engine Off", ...). But then you also will never have an external power supply attached to the LV battery. So this is not dangerous, i.e. the APIM update does not require that much amps, and the LBV can support this alone w/o external help?

The update in question is an APIM update that is loaded on a USB stick. That kind of update requires Key-on/Engine-on anyway.

So the procedure described was one where the owner of the vehicle in APIM Purgatory (the infamous 2021 corrupt version) would just use the vehicle daily until the Sync screen would suddenly report "Software Update in progress"

Nobody has ever been able to explain why the corrupted APIM will suddenly/finally recognize the update available and then apply it. We just know that it's an alternative to swapping APIM modules, and/or performing the TSB.

 

[Drkvampire2001]

Could someone please check my VIN again, Its at the dealer for some little things and they are telling me it has 77 codes and lots of things, they have contacted ford to help with fixing whatever these issues are but they did not get specific with me what the issues they are seeing are, and im wondering if the codes are for some programming things I did with Forscan

VIn: 3FMTK4SX7PMA38613

 

[jcb003]

Hi everyone,

Would someone be able to check my VIN: 3FMTK1SSXMMMA42122? The last update I received was 24-PU0301-BLM-PE. Currently, I have the BlueCruise 1.3 update in the queue, but it has been stuck in "Not Completed" for a few weeks. From what I understand, if that happens, there's not much you can do until Ford pushes another update.

Any insights would be appreciated thanks!

 

[Mike G]

Hi everyone,

Would someone be able to check my VIN: 3FMTK1SSXMMMA42122? The last update I received was 24-PU0301-BLM-PE. Currently, I have the BlueCruise 1.3 update in the queue, but it has been stuck in "Not Completed" for a few weeks. From what I understand, if that happens, there's not much you can do until Ford pushes another update.

Any insights would be appreciated thanks!

DM sent.

 

[Mike G]

Could someone please check my VIN again, Its at the dealer for some little things and they are telling me it has 77 codes and lots of things, they have contacted ford to help with fixing whatever these issues are but they did not get specific with me what the issues they are seeing are, and im wondering if the codes are for some programming things I did with Forscan

VIn: 3FMTK4SX7PMA38613

You didn't mention FORSCAN did you?

I'm thinking it's 12V battery related...but I could be wrong.

It looks like they cleared the DTCs around 0820 this morning. So not sure what they're doing now.

Sponsored