ECU module programming guide using FDRS

[Mike G]

I tried this morning, and reapplied the PSCM update, no change. the PSCM update is still in the SW updates list.

I could not reapply IPMI update as its not there anymore.

Any suggestions? I assume the PSCM update is important with the new IPMI update.

Thanks,

Sorry I didn't see this post earlier...I guess I need to check my forum settings for notifications.

IPMA and PSCM are scripted to be done together. You should get a message about multiple modules being programmed when you hit the "Run" button to start programming on either of those two.

The IPMA part of the two-part scripted update is a bit wonky. What should have happened when you did the IPMA was it should have done the block erase and replace, and then it should have checked and cleared DTCs before stepping into the "configuration" phase of the IPMA update. It didn't do the clearing of the DTCs for me, and it hasn't for several others. The end result was that the configuration step for the IPMA failed (due to DTCs that are present)...but the script went on into the PSCM update and did that. You'd actually have to be paying close attention to the messages flashing by to catch it.

So after it says the IPMA is completed, it then goes right into the PSCM part of the update. Same thing, block erase and replace, etc., but on the PSCM part of the scripted update it does actually check and clear DTCs before doing the configuration of the module.

I don't think you need to try the IPMA update again...there is a way to do it if you wanted to though (more on that below).

To fix the problem from where you are now in the process, I'd log into FDRS and clear all DTCs. Then go over to the toolbox tab and under the "All" section, scroll down until you find the "IPMA- Image Processing Module A (IPMA) Configuration" tool and download that and run it.

You will get a notification that multiple modules will be programmed.

FDRS will then get your configuration info from the cloud and put it back into your IPMA module, and then move on to the PSCM.

If it says the process is successful, then the PSCM should also drop off of the list.

If for some reason that fails, the fix would be to do a PMI on the IPMA module. (IPMA - Programmable Module Installation tool in FDRS). And when you run the PMI tool, and you're asked in the dialogs if the original module is still installed you make sure you say "No". Doing that will re-download and install the IPMA software again, and then apply the configuration settings from the cloud. It could also say afterward that it's going to re-do the PSCM update again, but once it checks and finds the software is current, it will simply reapply the same configuration settings you already have and the process should end successfully.

Sponsored

 

[Mike G]

Bottom line...the current (as well as the previous) IPMA/PSCM software update combo has a script problem.

During the IPMA update after software is burned, the script never clears the DTCs caused by normal network interruptions during programming, and so the IPMA configuration step fails. The script moves into the PSCM update and that normally completes fine.

So yes, you may have the current IPMA software, but it's possible that your IPMA module didn't get it's configuration info restored after the new software was burned.

So the fix is to go back in and do the standalone IPMA Configuration to put the settings back in.

I wonder how many owners have gone in to have 24B56 done and have ended up getting sent home with issues relating to their IPMA configuration?

 

[21st Century Truck]

Bottom line...the current (as well as the previous) IPMA/PSCM software update combo has a script problem.

During the IPMA update after software is burned, the script never clears the DTCs caused by normal network interruptions during programming, and so the IPMA configuration step fails. The script moves into the PSCM update and that normally completes fine.

So yes, you may have the current IPMA software, but it's possible that your IPMA module didn't get it's configuration info restored after the new software was burned.

So the fix is to go back in and do the standalone IPMA Configuration to put the settings back in.

I wonder how many owners have gone in to have 24B56 done and have ended up getting sent home with issues relating to their IPMA configuration?

Hmmm... I wonder how many of the dealer techs know these ins & outs?

 

[rugedraw]

Bottom line...the current (as well as the previous) IPMA/PSCM software update combo has a script problem.

During the IPMA update after software is burned, the script never clears the DTCs caused by normal network interruptions during programming, and so the IPMA configuration step fails. The script moves into the PSCM update and that normally completes fine.

So yes, you may have the current IPMA software, but it's possible that your IPMA module didn't get it's configuration info restored after the new software was burned.

So the fix is to go back in and do the standalone IPMA Configuration to put the settings back in.

I wonder how many owners have gone in to have 24B56 done and have ended up getting sent home with issues relating to their IPMA configuration?

Interesting. I didn't know this either. My truck has an iron-clad IPMA. It takes updates like a champ. I never have any issues with mine.

 

[ChrisCon]

Interesting. I didn't know this either. My truck has an iron-clad IPMA. It takes updates like a champ. I never have any issues with mine.

Just throwing this out there that I had all of the exact same issues @Mike G did with that particular update. I followed all of his directions here to get the update to clear. Maybe 2022 lightning specific if the IPMA update cleared for you @rugedraw without these issues.

 

[ytwytw]

Sorry I didn't see this post earlier...I guess I need to check my forum settings for notifications.

IPMA and PSCM are scripted to be done together. You should get a message about multiple modules being programmed when you hit the "Run" button to start programming on either of those two.

The IPMA part of the two-part scripted update is a bit wonky. What should have happened when you did the IPMA was it should have done the block erase and replace, and then it should have checked and cleared DTCs before stepping into the "configuration" phase of the IPMA update. It didn't do the clearing of the DTCs for me, and it hasn't for several others. The end result was that the configuration step for the IPMA failed (due to DTCs that are present)...but the script went on into the PSCM update and did that. You'd actually have to be paying close attention to the messages flashing by to catch it.

So after it says the IPMA is completed, it then goes right into the PSCM part of the update. Same thing, block erase and replace, etc., but on the PSCM part of the scripted update it does actually check and clear DTCs before doing the configuration of the module.

I don't think you need to try the IPMA update again...there is a way to do it if you wanted to though (more on that below).

To fix the problem from where you are now in the process, I'd log into FDRS and clear all DTCs. Then go over to the toolbox tab and under the "All" section, scroll down until you find the "IPMA- Image Processing Module A (IPMA) Configuration" tool and download that and run it.

You will get a notification that multiple modules will be programmed.

FDRS will then get your configuration info from the cloud and put it back into your IPMA module, and then move on to the PSCM.

If it says the process is successful, then the PSCM should also drop off of the list.

If for some reason that fails, the fix would be to do a PMI on the IPMA module. (IPMA - Programmable Module Installation tool in FDRS). And when you run the PMI tool, and you're asked in the dialogs if the original module is still installed you make sure you say "No". Doing that will re-download and install the IPMA software again, and then apply the configuration settings from the cloud. It could also say afterward that it's going to re-do the PSCM update again, but once it checks and finds the software is current, it will simply reapply the same configuration settings you already have and the process should end successfully.

It works!!! Now the PSCM update is gone from the list

Since PMI can reinstall the software on the module, would it work for BCM so i can avoid dealer visit to get software updated?
im not dared enough to try as BCM update can brick the truck rendering inoperable...

Thanks,

 

[Mike G]

It works!!! Now the PSCM update is gone from the list

Since PMI can reinstall the software on the module, would it work for BCM so i can avoid dealer visit to get software updated?
im not dared enough to try as BCM update can brick the truck rendering inoperable...

Thanks,

Nope. The BCM would still have a 'permissions' requirement hurdle even if done as a PMI.

 

[Riverant]

Regarding power supplies… has anyone had any experience with the power max pmbc 75?

it seems to meet the specs but is much cheaper than the pl6100 or Schumacher units. It also has a 100a version but I think 75a should be plenty?

 

[PJnc284]

Regarding power supplies… has anyone had any experience with the power max pmbc 75?

it seems to meet the specs but is much cheaper than the pl6100 or Schumacher units. It also has a 100a version but I think 75a should be plenty?

I have the 75. Only used it once but no issues after about 6 hours of updates

 

[rugedraw]

Regarding power supplies… has anyone had any experience with the power max pmbc 75?

it seems to meet the specs but is much cheaper than the pl6100 or Schumacher units. It also has a 100a version but I think 75a should be plenty?

Messaged you on the ICE forum. You're up on the Mongoose loaner list.

Yes, 75amp will work.

 

[chillaban]

I haven't applied any updated since September and spent an afternoon updating the whole kitchen sink (including APIM/TCU, BECM, PSCM+IPMA, etc).

The updates themselves all went very smoothly. I did have the whole Christmas tree of errors during one of the updates, which is the first time I've seen a Lightning do it (Mach-E's seem to do this with every update) but FDRS's automatic DTC clearing took care of it. I did not run into the issue with the IPMA+PSCM update erroring out.

I have noticed some behavior changes that I attribute to the above updates, most notably:

• 100% charge showed 347 miles on the guess-o-meter. Not sure if that's because of the BECM update or just coincidence but it's the first time I've seen it show over 320.
• APIM/TCU update seemed to help with CarPlay and AA stability -- I was able to do a 3 hour road trip without a single disconnect, which is honestly the first time that's happened since the Spring APIM updates. I do note that there's some stuttering once in a while where it drops a frame of audio and video before picking up again, but that's far less annoying than a total disconnect.
• APIM update also added Android Auto EV routing for me for the first time. Holy crap it's so much better than CarPlay, the Google Maps range predictions actually seem to be accurate within a percent or two, while Apple Maps has been off by a laughable 10+ percent especially when going up and down mountains.
• I already had the previous IPMA update and Forscan BC 1.2/1.3 enablement, but I do notice some small enhancements:
  • The road geometry ACC slowdown behavior has changed. It is a lot milder than before, which is an improvement. On some of the gentle curves it slows down from 75 to 72 instead of to 60, which was way too dramatic
  • In BC Hands On (grey steering wheel mode), I no longer see road geometry slowdowns happening at all. It still happens in hands-free mode.
  • When a slower car cuts in ahead of you, the slowdown feels much more gentle without an abrupt brake slamming.
  • Other than that, it doesn't feel dramatically different. 1.0 to 1.2 was a huge step up but 1.2 to 1.3 feels like a small modest bug fix.
• It seems like all of my Forscan modifications survived.

Sponsored