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

[Mike G]

When I called Ford they told me it hasn't been updated since December of 2021 ?.

Ford said it should definitely be updated so I have an appointment scheduled with my dealer for Friday. How should I go about telling them to do the module repair in FDRS? I worry the dealer is not very experienced with this and will check FDRS and say there is no update pending and not do anything.

Should I tell them to run TSB 22-2150?

That TSB has been superseded by the later TSB 22-2404 but essentially that is what we're talking about.

You should relate to the service advisor (and the tech if possible) your discussion with Ford and the fact that they agree that your car needs to be updated as it had a pre-exisiting condition that has prevented any updates from getting applied as OTAs since essentially October of '21 when 1.7.1 started this issue,

Some dealerships service departments did go out and buy the necessary additional USB cables and adapters to perform the steps in 22-2404...but some didn't. For the tech...the fastest alternative to having to perform the procedure (which can be a PITA to get right) would be to simply order and replace the APIM. But we will leave that up to the tech and service department to decide. Remember to request that the tech involve engineering support to get this resolved if required (more so that they know that you know about this option as an 'informed customer' than anything else).

Sponsored

 

[PianoDan0]

That TSB has been superseded by the later TSB 22-2404 but essentially that is what we're talking about.

You should relate to the service advisor (and the tech if possible) your discussion with Ford and the fact that they agree that your car needs to be updated as it had a pre-exisiting condition that has prevented any updates from getting applied as OTAs since essentially October of '21 when 1.7.1 started this issue,

Some dealerships service departments did go out and buy the necessary additional USB cables and adapters to perform the steps in 22-2404...but some didn't. For the tech...the fastest alternative to having to perform the procedure (which can be a PITA to get right) would be to simply order and replace the APIM. But we will leave that up to the tech and service department to decide. Remember to request that the tech involve engineering support to get this resolved if required (more so that they know that you know about this option as an 'informed customer' than anything else).

Thank you, I will make sure to do that. Having something to reference is good because I'm not sure the dealer would even be convinced anything was wrong otherwise. I might even print out 22-2404 and bring it with me.

That TSB has been updated a few times it seems (started out as 22-2117), so must be difficult to do!

This whole experience has really opened up my eyes on how out of date my software actually is. Looking up all the features after 1.7.1 has gotten me a little excited for all the new stuff. There's really nothing "wrong" with how my car drives, operates, etc. but would be nice to get the latest updates and improvements. The one thing that does bother me is FordPass. It essentially doesn't work unless connected via Bluetooth. I can't lock/unlock, start, charge to 100%, set departure times, refresh status, get charging data, etc. unless I'm connected to the car via Bluetooth. It makes the app virtually useless. I am hoping the update to the APIM will fix it or trigger other updates to fix it. I found another thread on this forum about someone experiencing similar issues and it was fixed with an IPC update apparently.

 

[Mike G]

Thank you, I will make sure to do that. Having something to reference is good because I'm not sure the dealer would even be convinced anything was wrong otherwise. I might even print out 22-2404 and bring it with me.

That TSB has been updated a few times it seems (started out as 22-2117), so must be difficult to do!

This whole experience has really opened up my eyes on how out of date my software actually is. Looking up all the features after 1.7.1 has gotten me a little excited for all the new stuff. There's really nothing "wrong" with how my car drives, operates, etc. but would be nice to get the latest updates and improvements. The one thing that does bother me is FordPass. It essentially doesn't work unless connected via Bluetooth. I can't lock/unlock, start, charge to 100%, set departure times, refresh status, get charging data, etc. unless I'm connected to the car via Bluetooth. It makes the app virtually useless. I am hoping the update to the APIM will fix it or trigger other updates to fix it. I found another thread on this forum about someone experiencing similar issues and it was fixed with an IPC update apparently.

Well TBH you are so far behind and there have been so many updates to the APIM, GWM and TCU...not to mention the RFA (Bluetooth), that once updated, will likely completely change the character of your car (for the better).

 

[PianoDan0]

Well TBH you are so far behind and there have been so many updates to the APIM, GWM and TCU...not to mention the RFA (Bluetooth), that once updated, will likely completely change the character of your car (for the better).

Certainly seems that way! I'm wondering if there's some incompatibility between the latest FP and the versions of SW that are on my car that's causing issues. Wouldn't surprise me one bit!

I really hope the process with the dealer goes smoothly. I haven't had much experience with EVs at dealers yet but in the past I asked about performing a TSB and they pretty much totally ignored me and did something else, but maybe I'll get someone who is more interested in helping this time.

 

[rugedraw]

Certainly seems that way! I'm wondering if there's some incompatibility between the latest FP and the versions of SW that are on my car that's causing issues. Wouldn't surprise me one bit!

I really hope the process with the dealer goes smoothly. I haven't had much experience with EVs at dealers yet but in the past I asked about performing a TSB and they pretty much totally ignored me and did something else, but maybe I'll get someone who is more interested in helping this time.

Fortunately, I have never had to perform TSB 22-2404 myself. I've read the TSB and followed along with other members on the F150 FDRS thread have done it and posted questions to get help with the process and it does not look like a good time. My job 1 truck made it past the broken APIM software on it's own and got stuck a bit further down the line. Therefore, I cannot speak with full intelligence on it. However, it is done with FDRS and if FDRS is not showing an APIM update for you, I don't see how 22-2404 can help. However, if that gets you in the door so they can start to diagnose the issue and order a new APIM, then use it. It sucks to be welcomed into the forum and your ownership experience with such a cluster-fudge. Be patient as this is not going to be resolved overnight.

 

[PianoDan0]

Fortunately, I have never had to perform TSB 22-2404 myself. I've read the TSB and followed along with other members on the F150 FDRS thread have done it and posted questions to get help with the process and it does not look like a good time. My job 1 truck made it past the broken APIM software on it's own and got stuck a bit further down the line. Therefore, I cannot speak with full intelligence on it. However, it is done with FDRS and if FDRS is not showing an APIM update for you, I don't see how 22-2404 can help. However, if that gets you in the door so they can start to diagnose the issue and order a new APIM, then use it. It sucks to be welcomed into the forum and your ownership experience with such a cluster-fudge. Be patient as this is not going to be resolved overnight.

The way that I understand it is that this procedure essentially sideloads the APIM software and it's not something that can just be done with FDRS alone (you need special hardware to bypass a few things to get it to work).
I don't really know how FDRS works, but from what Mike said yesterday there's a "Module Update Repair" that needs to be run - I'm not sure if that's something that would show up automatically, or if that is a manual process that needs to be done to get unstuck.

Worth a shot and hopefully they read the "The PTS – OTA Dashboard on vehicles with this condition may also display multiple APIM and/or TCU updates have failed, and/or a no OTA history message." In particular, the no OTA history part since that's what has happened to me.

It's frustrating because I *think* I know what needs to be done, but I'm at the mercy of the dealer and whether or not they determine that is the best path forward.

 

[rugedraw]

The way that I understand it is that this procedure essentially sideloads the APIM software and it's not something that can just be done with FDRS alone (you need special hardware to bypass a few things to get it to work).
I don't really know how FDRS works, but from what Mike said yesterday there's a "Module Update Repair" that needs to be run - I'm not sure if that's something that would show up automatically, or if that is a manual process that needs to be done to get unstuck.

Worth a shot and hopefully they read the "The PTS – OTA Dashboard on vehicles with this condition may also display multiple APIM and/or TCU updates have failed, and/or a no OTA history message." In particular, the no OTA history part since that's what has happened to me.

It's frustrating because I *think* I know what needs to be done, but I'm at the mercy of the dealer and whether or not they determine that is the best path forward.

If I remember correctly, you cannot side-load anything on the APIM. It does not communicate via the CAN process. It has to be updated via USB or plugged into directly with the ethernet port. A module update repair procedure may do the trick, or after a few failed ones, it will lock out the APIM preventing it from being updated. Should that happen, FDRS would generate a repair validation code which is what your dealer would need to get you new APIM under warranty. I think that is the best way out for you and based on a offline convo I had with Mike about your case, he agrees a new APIM is the way to go for you.

 

[PianoDan0]

If I remember correctly, you cannot side-load anything on the APIM. It does not communicate via the CAN process. It has to be updated via USB or plugged into directly with the ethernet port. A module update repair procedure may do the trick, or after a few failed ones, it will lock out the APIM preventing it from being updated. Should that happen, FDRS would generate a repair validation code which is what your dealer would need to get you new APIM under warranty. I think that is the best way out for you and based on a offline convo I had with Mike about your case, he agrees a new APIM is the way to go for you.

Ah, got it. Maybe I misunderstood then.

Yeah, I wish I could just walk in the door and say "I need a new APIM" but I understand there's a process for it. Who knows, maybe a repair would work and that would save the hassle of replacing the part.

 

[CarGuy11]

So is Ford still on Holiday break? No new updates in FDRS or OTAs this week?

 

[Mike G]

So is Ford still on Holiday break? No new updates in FDRS or OTAs this week?

Well I'm doing an IPMA and PSCM that showed up this morning on my Lightning...just after the Voldemort GWM update appeared when I hit the check updates button beforehand...so yeah I think things are rolling again. I've heard that some OTAs are going out to MMEs as well but since I have a '23 I'm not really in the "priority group" at the minute.

 

[rugedraw]

The IPMA and PSCM updates showed up to 2023 ICE trucks a few days ago and the Lightning yesterday or possibly sooner. As of today, the IPMA and PSCM files are showing in FDRS for 2022 ICE trucks, too.

On vehicle with BC 1.0, these files are not activating BC 1.4.....something is still missing. I am guessing an APIM update is still needed to add the toggle switches for lane change assist, predictive speed, etc. It is possible that vehicles that already have BC 1.2 or 1.3 will automatically go to BC 1.4. However, on the ICE trucks, the IPMA update is writing all zeros to the file locations where BC goodies are supposed to go.

@Mike G Does your Lightning have BC 1.0 or higher?

 

[Mike G]

The IPMA and PSCM updates showed up to 2023 ICE trucks a few days ago and the Lightning yesterday or possibly sooner. As of today, the IPMA and PSCM files are showing in FDRS for 2022 ICE trucks, too.

On vehicle with BC 1.0, these files are not activating BC 1.4.....something is still missing. I am guessing an APIM update is still needed to add the toggle switches for lane change assist, predictive speed, etc. It is possible that vehicles that already have BC 1.2 or 1.3 will automatically go to BC 1.4. However, on the ICE trucks, the IPMA update is writing all zeros to the file locations where BC goodies are supposed to go.

@Mike G Does your Lightning have BC 1.0 or higher?

It does...all 22 Lariat and higher trims came with it from the plant. Same for 23s.

It will be 1.0 to 1.4 whenever it happens.

 

[PianoDan0]

Should that happen, FDRS would generate a repair validation code which is what your dealer would need to get you new APIM under warranty. I think that is the best way out for you and based on a offline convo I had with Mike about your case, he agrees a new APIM is the way to go for you.

After some more digging on this forum, it seems like if the dealer attempted 21G01 (which they did) and it failed (it clearly did if I'm still stuck, plus I don't have BC) then it's likely my APIM is locked because 21G01 directs you to run 22-2117 which runs the module recovery and starts the 20 day lockout window (if it fails) and after that the APIM doesn't receive updates.

I guess we'll find out!

 

[rugedraw]

After some more digging on this forum, it seems like if the dealer attempted 21G01 (which they did) and it failed (it clearly did if I'm still stuck, plus I don't have BC) then it's likely my APIM is locked because 21G01 directs you to run 22-2117 which runs the module recovery and starts the 20 day lockout window (if it fails) and after that the APIM doesn't receive updates.

I guess we'll find out!

Your warranty history in PTS says the dealer tried 21G01 several times with a flash drive and it failed and they had to hardwire to the car to do it and then it went through, But, vehicle history does not show any indication that 21G01 was ever attempted. None of the tech notes that day makes any sense to me for several reasons; the fact that you don't have BC is only one reason.

All that was done to your car in August was an IPC update that failed via USB and had to be CAN'd in and it took 5.5 hours, but they did it. Between October and November, some module updates were done spread out through a few days.

 

[PianoDan0]

Your warranty history in PTS says the dealer tried 21G01 several times with a flash drive and it failed and they had to hardwire to the car to do it and then it went through, But, vehicle history does not show any indication that 21G01 was ever attempted. None of the tech notes that day makes any sense to me for several reasons; the fact that you don't have BC is only one reason.

All that was done to your car in August was an IPC update that failed via USB and had to be CAN'd in and it took 5.5 hours, but they did it. Between October and November, some module updates were done spread out through a few days.

What is PTS vs. vehicle history? Are they two different systems that report what updates have been performed?

Interesting though, that second to last one was before I bought the car but I took my car in to my local dealer for the same issues about a month or so later so whatever they did didn't fix it. My local dealer wasn't able to find any issues and it's just been something I've been dealing with. Usually I drive for a few mins, restart the car, and the faults go away. I thought it was a 12V battery issue which led me down this whole path - someone suggested I go on this forum and ask about the updates I need and here we are.

Could still be a problem with my 12V battery but I want to get all these SW updates figured out first since it could potentially be resolved with more up to date software.

Sponsored