CSP 24B56 - Inoperative Front Parking Sensor(s) - IPMA Software Update for Certain 2022-24 F-150 Lightning Trucks

[CRAIGC540]

I had Ford home service pick up my lightning to apply the front sensor, frunk and the charge port recall. I told them maybe not do the front sensor because I was worried about having problems. He was fully aware of the long update and needing to have a battery tender for the 12 volt, so I told him to get all recalls done. They went well except he brought it back with the small 360 screen and no beeps when the camera pops up to see close objects., this after telling him to ask the tech to recalibrate the camera. To his credit he did tell both the tech and the porter to check for that problem and still didn't get done. They picked it up the next day and corrected the camera. Home service is the best and my dealer Raceway Ford seems to have a really good EV tech. Funny thing is I wasn't ever going to go to them for service because they were my original reservation dealer and found out I would be charged a markup so I changed to another dealer 29 miles away. I did try their service and didn't like it so decided to try Raceway Ford and have had nothing but great service. I ask Raceway to update my sync to 10.1 but since I wasn't having any problems the would charge $210 so I decided to wait for the OTA.

Sponsored

 

[LUXMAN]

This changed for me after a dealer update, I know have to turn it off when cruise is turned on. I'd rather turn it on when needed.

I agree. Now I have this on my pro and it’s annoying. I never use Lane centering unless I’m on a long trip.

 

[Mike G]

I had Ford home service pick up my lightning to apply the front sensor, frunk and the charge port recall. I told them maybe not do the front sensor because I was worried about having problems. He was fully aware of the long update and needing to have a battery tender for the 12 volt, so I told him to get all recalls done. They went well except he brought it back with the small 360 screen and no beeps when the camera pops up to see close objects., this after telling him to ask the tech to recalibrate the camera. To his credit he did tell both the tech and the porter to check for that problem and still didn't get done. They picked it up the next day and corrected the camera. Home service is the best and my dealer Raceway Ford seems to have a really good EV tech. Funny thing is I wasn't ever going to go to them for service because they were my original reservation dealer and found out I would be charged a markup so I changed to another dealer 29 miles away. I did try their service and didn't like it so decided to try Raceway Ford and have had nothing but great service. I ask Raceway to update my sync to 10.1 but since I wasn't having any problems the would charge $210 so I decided to wait for the OTA.

@Ford Motor Company

There's a "bug", or rather an "omission" in the latest IPMA scripted update (IPMA/PSCM coordinated updates).

I've experienced it personally, as have others on this forum who've done their own updates, and it goes unnoticed because the update appears to complete properly, but doesn't, and leaves clues behind.

When the IPMA update is downloaded and "Run" is selected, the scripted "block erase and replace" takes place fine. After the new software is loaded, the script should check and clear any DTCs that have ocurred as a result of the network interruption caused during programming, but this step never takes place. There are invariably DTCs that would need to be cleared at this juncture. Since the DTCs aren't cleared the script skips, or ignores the "Configuration" phase of the IPMA update and just concludes. Most techs start the IPMA update and since they know it can take quite a while they just hit the Run button and walk away to do something else. And when they get back they see that FDRS says "Application finished. Please press Ok to continue." and they have no clue that the configuration step of the IPMA actually failed because they weren't watching the screen to see it happen.

The coordinated update then steps into the PSCM portion of the process and that does the block erase and replace, followed by clearing the DTCs and then it applies the configuration as intended.

When the tech is returned to the "SW Updates" tab and the list refreshes....either the IPMA or the PSCM are still listed as available even though they supposedly got updated.
Just like in the below screenshot from @CRAIGC540 's available software list in FDRS from this morning:

That PSCM in the list is the clue that the IPMA Configuration didn't complete during the update.

If you ask a tech why the PSCM is still in the list after the IPMA/PSCM update...they won't know.

The fix for this A) Ford needs to either correct the script on the latest IPMA update, or B) post a message to OASIS telling techs that they need to perform this IPMA/PSCM coordinated update and then afterward separately clear all DTCs and then run the FDRS IPMA Configuration tool to correct this issue. That will force the configuration to be applied to the IPMA and then the PSCM (again) and then the PSCM shown in the available software list will drop off.

I'm posting this here so that forum members will know what the problem is with this update. The software is fine and is beneficial...it's the way the update was scripted that caused the issues people are seeing....and the fact that it's been going on for months now without Ford acknowledging that there's a problem that's the biggest issue.

To recap. For CSP 24B56. Perform IPMA/PSCM coordinated updates. When returned to the SW Updates tab and either IPMA or PSCM are still listed. Clear DTCs and run the IPMA Config tool:

Oh, and @Ford Motor Company ...if you don't believe me, have somebody look at the data for all the trucks that have had 24B56 performed...and still have either the IPMA or the PSCM still available in their software lists, even though as a 'coordinated' update you should never have one of those without the other in the list.

 

[TaxmanHog]

Oh, and @Ford Motor Company ...if you don't believe me, have somebody look at the data for all the trucks that have had 24B56 performed...and still have either the IPMA or the PSCM still available in their software lists, even though as a 'coordinated' update you should never have one of those without the other in the list.

@Gimme_my_MME please bump this up the chain for folks in the know !

 

[Pitbull2o08]

@Ford Motor Company

There's a "bug", or rather an "omission" in the latest IPMA scripted update (IPMA/PSCM coordinated updates).

I've experienced it personally, as have others on this forum who've done their own updates, and it goes unnoticed because the update appears to complete properly, but doesn't, and leaves clues behind.

When the IPMA update is downloaded and "Run" is selected, the scripted "block erase and replace" takes place fine. After the new software is loaded, the script should check and clear any DTCs that have ocurred as a result of the network interruption caused during programming, but this step never takes place. There are invariably DTCs that would need to be cleared at this juncture. Since the DTCs aren't cleared the script skips, or ignores the "Configuration" phase of the IPMA update and just concludes. Most techs start the IPMA update and since they know it can take quite a while they just hit the Run button and walk away to do something else. And when they get back they see that FDRS says "Application finished. Please press Ok to continue." and they have no clue that the configuration step of the IPMA actually failed because they weren't watching the screen to see it happen.

The coordinated update then steps into the PSCM portion of the process and that does the block erase and replace, followed by clearing the DTCs and then it applies the configuration as intended.

When the tech is returned to the "SW Updates" tab and the list refreshes....either the IPMA or the PSCM are still listed as available even though they supposedly got updated.
Just like in the below screenshot from @CRAIGC540 's available software list in FDRS from this morning:

That PSCM in the list is the clue that the IPMA Configuration didn't complete during the update.

If you ask a tech why the PSCM is still in the list after the IPMA/PSCM update...they won't know.

The fix for this A) Ford needs to either correct the script on the latest IPMA update, or B) post a message to OASIS telling techs that they need to perform this IPMA/PSCM coordinated update and then afterward separately clear all DTCs and then run the FDRS IPMA Configuration tool to correct this issue. That will force the configuration to be applied to the IPMA and then the PSCM (again) and then the PSCM shown in the available software list will drop off.

I'm posting this here so that forum members will know what the problem is with this update. The software is fine and is beneficial...it's the way the update was scripted that caused the issues people are seeing....and the fact that it's been going on for months now without Ford acknowledging that there's a problem that's the biggest issue.

To recap. For CSP 24B56. Perform IPMA/PSCM coordinated updates. When returned to the SW Updates tab and either IPMA or PSCM are still listed. Clear DTCs and run the IPMA Config tool:

Oh, and @Ford Motor Company ...if you don't believe me, have somebody look at the data for all the trucks that have had 24B56 performed...and still have either the IPMA or the PSCM still available in their software lists, even though as a 'coordinated' update you should never have one of those without the other in the list.

@Ford Motor Company We are messing up badly. And have dealerships that don't know what they're doing.

 

[Stalemate]

I had this update done today at Pierre Ford in Seattle and no issues so far (normal 360 camera size, etc.) Had to take it in because I ran over some debris on the highway the other night and it tore the active air dam off, so I figured I would let them take a shot at it. They also did the 24P24 update although I've never had any problems with the frunk.

*Update*
I am getting the "system off to save power" message when turning off the truck; will try some of the fixes reported in this thread and report back.

Another update; battery tested >12v with a multimeter so I unplugged the BMS for a few seconds, message seems to have gone away. Thanks everyone.

 

[Riverant]

Mentioned in another thread but I updated my IPMA in FDRS and the PSCM update was not clearing. Despite running the IPMA configuration and ensuring there were no DTCs, the PSCM still wouldn’t clear. Everything seems to be working…front parking sensors aren’t blocked randomly and BC is working fine.

 

[TaxmanHog]

Make plans to get this done BEFORE August 26th 2025 !

 

[Pitbull2o08]

I did it. Took 8 hours for me. The TPS was off when done but that was it.

 

[CRAIGC540]

My service guy told me this which is why I did it even though I had no problems. So if I ever had a problem with the sensor that I would be charged $210 for the update just like he wanted to charge me $210 to update my sync to 10.1..
Seems they would just update it for free since I will be getting it anyway.

 

[Lightning Rod]

The dealer tried to update mine last Thursday and apparently crashed the IPMA module, so now I'm paying for gas in a loaner until they can get a new one to replace it. They said mine is only the second one they've tried to update, and the same thing has happened both times. I don't know if that's due to an error with the update or something the dealer is doing wrong.

Has anyone heard of this update failing and bricking the hardware?

Ok. This very thing has happened to me this week because my dealer is also trying to install the CSP 24B56 IPMA/PSCM coordinated updates . I too have a loaner, 2024 F-150 ICE (I hate it) because they've had my 23 Lariat ER for the last 4 days. They kept getting the Update Failed message after several tries, and they finally called and said that they are going to have to replace the module (I'm assuming that they bricked it by not following the tech manual thoroughly as some have pointed out in this thread). He said that the module will be delivered monday morning and they will install it and retry the update and hopefully by Tuesday, my Lightning will be ready for pickup.

It seems clear that the technicians didn't follow the instructions that their manual says, and they probably started the update without a battery tender and wasn't present when alerts popped up because they started the install and walked away.

I was going to call them Monday morning before they install the new module and restart the update process. What should I tell them when I call them Monday about how they probably didn't follow the tech instructions to a Tee? After reading all 21 pages of this thread, there is a multitude of things that can go wrong with this update, and I would like to nip all of that in the bud, before any other failures happen.

With my phone call to them this coming Monday, I was going to probably start with forwarding them the @Mike G post about some technicians neglecting to follow proper procedures while performing this update with his post below....

@Ford Motor Company

There's a "bug", or rather an "omission" in the latest IPMA scripted update (IPMA/PSCM coordinated updates).

I've experienced it personally, as have others on this forum who've done their own updates, and it goes unnoticed because the update appears to complete properly, but doesn't, and leaves clues behind.

When the IPMA update is downloaded and "Run" is selected, the scripted "block erase and replace" takes place fine. After the new software is loaded, the script should check and clear any DTCs that have ocurred as a result of the network interruption caused during programming, but this step never takes place. There are invariably DTCs that would need to be cleared at this juncture. Since the DTCs aren't cleared the script skips, or ignores the "Configuration" phase of the IPMA update and just concludes. Most techs start the IPMA update and since they know it can take quite a while they just hit the Run button and walk away to do something else. And when they get back they see that FDRS says "Application finished. Please press Ok to continue." and they have no clue that the configuration step of the IPMA actually failed because they weren't watching the screen to see it happen.

The coordinated update then steps into the PSCM portion of the process and that does the block erase and replace, followed by clearing the DTCs and then it applies the configuration as intended.

When the tech is returned to the "SW Updates" tab and the list refreshes....either the IPMA or the PSCM are still listed as available even though they supposedly got updated.
Just like in the below screenshot from @CRAIGC540 's available software list in FDRS from this morning:

That PSCM in the list is the clue that the IPMA Configuration didn't complete during the update.

If you ask a tech why the PSCM is still in the list after the IPMA/PSCM update...they won't know.

The fix for this A) Ford needs to either correct the script on the latest IPMA update, or B) post a message to OASIS telling techs that they need to perform this IPMA/PSCM coordinated update and then afterward separately clear all DTCs and then run the FDRS IPMA Configuration tool to correct this issue. That will force the configuration to be applied to the IPMA and then the PSCM (again) and then the PSCM shown in the available software list will drop off.

I'm posting this here so that forum members will know what the problem is with this update. The software is fine and is beneficial...it's the way the update was scripted that caused the issues people are seeing....and the fact that it's been going on for months now without Ford acknowledging that there's a problem that's the biggest issue.

To recap. For CSP 24B56. Perform IPMA/PSCM coordinated updates. When returned to the SW Updates tab and either IPMA or PSCM are still listed. Clear DTCs and run the IPMA Config tool:

Oh, and @Ford Motor Company ...if you don't believe me, have somebody look at the data for all the trucks that have had 24B56 performed...and still have either the IPMA or the PSCM still available in their software lists, even though as a 'coordinated' update you should never have one of those without the other in the list.

What else should I tell the service Tech before he installs the brand new module and begins the update process? I don't want him to brick the new module again, and I would like to not have the tiny 360 view display, not having the front camera display after getting close to an object, and all of the other disasters that have happened trying to install this fix.

Thank you everyone in this thread... you guys have helped a lot of us out a lot with this nightmare of an issue!

 

[PJnc284]

What else should I tell the service Tech before he installs the brand new module and begins the update process? I don't want him to brick the new module again, and I would like to not have the tiny 360 view display, not having the front camera display after getting close to an object, and all of the other disasters that have happened trying to install this fix.

Looks like you have a 2023 based on your profile so you shouldn't have to worry about the small 360 camera as that seemed to be isolated to 22's.

 

[luebri]

Looks like you have a 2023 based on your profile so you shouldn't have to worry about the small 360 camera as that seemed to be isolated to 22's.

My dealer has been very good to deal with however not on this one.even after specifically warning them about the small 360 cam and not missing that step. The service person failed to properly relay that warning to the actual tech and I now have a small 360 camera as well Yay!

scheduled in two weeks to bring it back in

 

[Lightning Rod]

My dealer has been very good to deal with however not on this one.even after specifically warning them about the small 360 cam and not missing that step. The service person failed to properly relay that warning to the actual tech and I now have a small 360 camera as well Yay!

scheduled in two weeks to bring it back in

Do you have a 2022 lightning?

 

[luebri]

Do you have a 2022 lightning?

Yes, listed in my signature

Sponsored