Firmware update failed used PCM 2007 Navigator

[FixrUpr]

Hi all,

I have a 2007 Lincoln Navigator. It had been throwing codes in multiple modules for communication problems, so followed shop manual diagnostic procedures, kept coming up replace pcm.

Got a used pcm, and on the advice from some experienced users on here, picked up vlinker fs, got the paid extended license, and modified an HP1200 server power supply to output 13.7v while programming so battery stays charged.

I first reprogrammed the vin on the used module, went well. Erased and reprogrammed both pats keys(wasn't sure i had to do this as they are stored in the IC, but figured I would just incase). I initialized the pcm, reset parameters, and tried to update firmware.

The first update failed at 94%, so I disconnected from vehicle, and to see if the keys worked, I cycled the ignition, theft light went out, started the vehicle and it fired up, but ran very rough. After clearing dtcs and rescanning, it came up with p2104, and p0600.

Was thinking either the used pcm is bad or the failed firmware update was the issue. Saw in the troubleshooting section to change ISO15765 from auto to "in application" and retry update. Did that and it still fails at the same 94%.

Any other ideas on something i should try? I love this program and the users on this forum are amazing. I still have the original pcm, and I knew there was a chance this wouldn't work, but if anyone has any ideas, that would be awesome. Sorry for the long post!

[tractmec]

Hi all,

I have a 2007 Lincoln Navigator. It had been throwing codes in multiple modules for communication problems, so followed shop manual diagnostic procedures, kept coming up replace pcm.

Got a used pcm, and on the advice from some experienced users on here, picked up vlinker fs, got the paid extended license, and modified an HP1200 server power supply to output 13.7v while programming so battery stays charged.

I first reprogrammed the vin on the used module, went well. Erased and reprogrammed both pats keys(wasn't sure i had to do this as they are stored in the IC, but figured I would just incase). I initialized the pcm, reset parameters, and tried to update firmware.

The first update failed at 94%, so I disconnected from vehicle, and to see if the keys worked, I cycled the ignition, theft light went out, started the vehicle and it fired up, but ran very rough. After clearing dtcs and rescanning, it came up with p2104, and p0600.

Was thinking either the used pcm is bad or the failed firmware update was the issue. Saw in the troubleshooting section to change ISO15765 from auto to "in application" and retry update. Did that and it still fails at the same 94%.

Any other ideas on something i should try? I love this program and the users on this forum are amazing. I still have the original pcm, and I knew there was a chance this wouldn't work, but if anyone has any ideas, that would be awesome. Sorry for the long post!

Long posts give the the most information! I am guilty of that myself!

I assume when you changed the VIN and other Parameters in the VID block it referred you over to the firmware update section? And also assume the erase of all blocks and the reload with the VID block changes started?

The fact that engine actually starts and runs poorly means that some of the calibration files installed! Failures like this can mean the PCM took a long time to respond during the calibration write and FORScan timed the process out before the write was finished!

It may mean the team will need to increase the wait time for this particular PCM series assuming this is a similar error!
Instruction on how to contact support below!

That was my experience back using 2.4.09 on 2005 F150 except that the write failed before the process really even got started and I had a PCM that would crank but not fire!
I was so discouraged that I did not report the error for quite some time and when i finality did, the Team was a little miffed at me as they could have resolved this error much sooner if i had reported it immediately!
In the mean time some one else had the same experience and did report it immediately during 2.4.11/12 development

That particular error was resolved in 2.4.12 and I have since changed parameters in this F150 several times since(Drive line mismatch and and tire size by My stupidity mostly)!

You would not have had to erase Keys with PATS control in the IPC but a PATS initialization would have been required

Best Advice I can give is send your Debug files(dump.bin) and Log files in to the team using the instructions after the Heading "Providing FORScan Debug Information" here: https://forscan.org/contactus.html