PCM programs OK but is still in the SW Update list

[PatchManager]

I had four modules in my SW Updates list including the PCM update. All of the update seemed to work successfully including the PCM update, but the PCM update continues to show up in the SW Update list. I've clicked "Run" on the PCM update four times. The first time took some time to complete and also updated the ABS module. After it reported that is completed, I ran the update again since it was still in the list, and that appeared to successfully complete as well. However, the second and subsequent updates were much short and seemed to all do the same thing and it still shows in the list. The other modules I updated tonight all run flawlessly and are no longer in the list. Has anyone else run into this issue and how did you solve it? For now, I going to let it sit overnight and check tomorrow.

I hit the refresh icon on the Run button, which didn't help and ran the "Rerun Network Test" as well.

Sponsored

 

[Jesse-Infotainment]

It probably installed. Send me your vin. This has happened before wih upodates.

 

[JEB]

I had four modules in my SW Updates list including the PCM update. All of the update seemed to work successfully including the PCM update, but the PCM update continues to show up in the SW Update list. I've clicked "Run" on the PCM update four times. The first time took some time to complete and also updated the ABS module. After it reported that is completed, I ran the update again since it was still in the list, and that appeared to successfully complete as well. However, the second and subsequent updates were much short and seemed to all do the same thing and it still shows in the list. The other modules I updated tonight all run flawlessly and are no longer in the list. Has anyone else run into this issue and how did you solve it? For now, I going to let it sit overnight and check tomorrow.

I hit the refresh icon on the Run button, which didn't help and ran the "Rerun Network Test" as well.

Assuming it installed correctly, @HammaMan found an interesting tool to correct a very similar problem with a different module. Try flushing and refreshing the vehicle cache in FDRS. The tool is under the envelope menu in the upper left corner. https://www.f150gen14.com/forum/threads/ecu-module-programming-guide-using-fdrs.8249/post-324069

 

[PatchManager]

Assuming it installed correctly, @HammaMan found an interesting tool to correct a very similar problem with a different module. Try flushing and refreshing the vehicle cache in FDRS. The tool is under the envelope menu in the upper left corner. https://www.f150gen14.com/forum/threads/ecu-module-programming-guide-using-fdrs.8249/post-324069

I did try that a couple of times and it didn't help, but that was a good thought. The next morning the update list was empty, so it just needed some time to register on the server or Jesse corrected it.

 

[JEB]

I did try that a couple of times and it didn't help, but that was a good thought. The next morning the update list was empty, so it just needed some time to register on the server or Jesse corrected it.

It probably was the former. After you updated the APIM, did you transfer the usb back to the laptop and do the post-install validation? If not that might explain the short lag time before the server updated.

 

[PatchManager]

I did not have an APIM update. The updates were all fairly simple and didn't require a USB stick.

 

[Jesse-Infotainment]

USB doesnt need to be inserted back into the computer. The validation is done by communicating with the APIM not the USB anyways

 

[JEB]

I did not have an APIM update. The updates were all fairly simple and didn't require a USB stick.

Right. Sorry, got off track.

 

[JEB]

USB doesnt need to be inserted back into the computer. The validation is done by communicating with the APIM not the USB anyways

Doesn’t have to be. But it’s still good to see the post-validation comparison where FDRS compares the nodes line by line to make sure what’s written to the APIM matches what’s on the USB. I have had the APIM update not immediately clear when it doesn’t.

 

[Jesse-Infotainment]

Doesn’t have to be. But it’s still good to see the post-validation comparison where FDRS compares the nodes line by line to make sure what’s written to the APIM matches what’s on the USB. I have had the APIM update not immediately clear when it doesn’t.

It doesn’t do anything with the usb !

 

[JEB]

Then what is FDRS reading for comparison when it lists the software node by node and issues a pass/fail for each node?

EDIT: ANd blocking me so I can’t respond? What a baby.

 

[PatchManager]

I can't speak to Jesse's patience level, but he is considered somewhat of a folk hero on this board for good reason as you probably know. Except for a few Ford firmware engineers and technicians, nobody likely knows this system like he does.

Keep in mind that there is a difference between updating module firmware with FDRS and updating the configuration with FORScan. For a few modules, a USB stick is required to update the firmware using FDRS. Most of the updates are downloaded by FDRS over your computer's WIFI or network connection directly to the computer running FDRS and FDRS uses those files for the update. In those cases, there is no USB involved and there is no option to use a USB stick that I am aware of.

 

[JEB]

I can't speak to Jesse's patience level, but he is considered somewhat of a folk hero on this board for good reason as you probably know. Except for a few Ford firmware engineers and technicians, nobody likely knows this system like he does.

Keep in mind that there is a difference between updating module firmware with FDRS and updating the configuration with FORScan. For a few modules, a USB stick is required to update the firmware using FDRS. Most of the updates are downloaded by FDRS over your computer's WIFI or network connection directly to the computer running FDRS and FDRS uses those files for the update. In those cases, there is no USB involved and there is no option to use a USB stick that I am aware of.

I actually am pretty familiar with the process, after having been at this for over a year now and know how FDRS and FORScan work. I had forgotten you were talking about the PCM, which updates via canbus, and somehow had gotten off track. With the exception of the GWM last year, which had a bug, I had only seen a successful module update fail to clear the FDRS queue when I had failed to do the APIM post install validation properly and it was re-presented to me for a second try. My mistake in transposing your experience with that one.

As for @Jesse-Infotainment , I am aware of his reputation and know (or knew) him pretty well both on and off the forum. I stand by my comment. He is without doubt the most knowledgeable person actively participating on the forum. But don’t disagree with him. He can’t handle it. I had forgotten to genuflect when he spoke.

 

[JEB]

Although not relevant to your current situation, in the event you do have to update the APIM (or another module that uses USB instead of canbus) Ford’s procedure as of last summer was to transfer the USB drive to the PC for a final post-install validation procedure. See TSB 22-2256, p. 2, para. 5 (bottom of page) (06/28/2022). https://static.nhtsa.gov/odi/tsbs/2022/MC-10214881-0001.pdf. I don’t know if the procedure has changed since I last followed it. You might want to ask @Jesse-Infotainment , but only do it from a kneeling position.

 

[imnuts]

Although not relevant to your current situation, in the event you do have to update the APIM (or another module that uses USB instead of canbus) Ford’s procedure as of last summer was to transfer the USB drive to the PC for a final post-install validation procedure. See TSB 22-2256, p. 2, para. 5 (bottom of page) (06/28/2022). https://static.nhtsa.gov/odi/tsbs/2022/MC-10214881-0001.pdf. I don’t know if the procedure has changed since I last followed it. You might want to ask @Jesse-Infotainment , but only do it from a kneeling position.

I've never put the USB drive back in my computer. FDRS always verifies USB updates via the cable after it's finished.

Sponsored