FORScan forum

I tried updating the tire size on my 2002 F-150 using a Chinese VCM3 clone and a cracked version of IDS. It did not go well, and the truck isn't running at all anymore. It looks like just to update the tire size of this vehicle, IDS tries to completely rewrite the firmware on the PCM, which failed. Now I've got a PCM that IDS says is "blank" and every time I try to reprogram it, IDS fails out.

So I tried the FORScan beta, and it looks like maybe it doesn't support reprogramming this model year vehicle. I have tried both a OBDLink EX and an OPUS Mongoose (the Toyota-branded one, but J2534 should still work on it with Ford, and has in the past). It doesn't look like I can get the module programming screen of FORScan to come up using either of them. Does anyone know if there is some way to check the firmware database to see if this model year is supported?

iamgeek wrote: Fri Jul 11, 2025 10:12 pm I tried updating the tire size on my 2002 F-150 using a Chinese VCM3 clone and a cracked version of IDS. It did not go well, and the truck isn't running at all anymore. It looks like just to update the tire size of this vehicle, IDS tries to completely rewrite the firmware on the PCM, which failed. Now I've got a PCM that IDS says is "blank" and every time I try to reprogram it, IDS fails out.

So I tried the FORScan beta, and it looks like maybe it doesn't support reprogramming this model year vehicle. I have tried both a OBDLink EX and an OPUS Mongoose (the Toyota-branded one, but J2534 should still work on it with Ford, and has in the past). It doesn't look like I can get the module programming screen of FORScan to come up using either of them. Does anyone know if there is some way to check the firmware database to see if this model year is supported?

I'm not familiar with this vehicle. If FORScan 2.4.18beta can program this PCM, it's likely that you need a cable with 18v FEPS support eg vLinker FS. The clone VCM3 should support 18v FEPS. Have you tried using it with FORScan?

I have not, but that is a good idea. I'll give it a shot and report back.

iamgeek wrote: Fri Jul 11, 2025 10:12 pm I tried updating the tire size on my 2002 F-150 using a Chinese VCM3 clone and a cracked version of IDS. It did not go well, and the truck isn't running at all anymore. It looks like just to update the tire size of this vehicle, IDS tries to completely rewrite the firmware on the PCM, which failed. Now I've got a PCM that IDS says is "blank" and every time I try to reprogram it, IDS fails out.

So I tried the FORScan beta, and it looks like maybe it doesn't support reprogramming this model year vehicle. I have tried both a OBDLink EX and an OPUS Mongoose (the Toyota-branded one, but J2534 should still work on it with Ford, and has in the past). It doesn't look like I can get the module programming screen of FORScan to come up using either of them. Does anyone know if there is some way to check the firmware database to see if this model year is supported?

FORScan is unable to do these as of yet as the PCM is on a network call PWM(Ford Calls it SCP) and so far the team has had little luck getting PWM firmware programming to work in FORScan(I was told way back at 2.3.09 and 2.4.02 that it was being worked on)!
Firmware Programming is available in FORScan for 2005 and later with the PCM on the HSCAN network(.phf firmware files and have bricked and recovered one with both IDS 86 and FORScan 2.4.12 and VCM2 clone) ! These HSCAN PCM's require FEPS up to about 2011 MY!

The OBDlink EX adapter does not have FEPS capability, if your mongoose is for Toyota I would also rather think not, it would have to put out an 18 volt signal on DLC pin 13!

And Yes any VIN ID block programming on these FEPS type PCM modules requires the 18 VOLT signal from the Adapter to open the PCM for programming (VCM2 and the clones and the vLinker FS are capable). The VCM3 clone you have must be FEPS Capable or you would not have got to point of the erase phase(not familiar enough with the VCM3 clones, VCM2 Clone I have works well with FORSCan). Without the 18 volt FEPS signal the process should have failed at the FEPS voltage apply stage, before it even got to the erase phase!

VIN ID block changes on these PCM's(such as Tire size and Gear ratio) do require a complete erase and reprogram with the desired changes included!

If IDS had Problems usually it is because a Calibration file got corrupted/unreadable during the Download phase(you did have a good internet/wifi connection and a Charger or power supply on the battery?). Or you have a corrupted file in the FORD calibration files Folder in the FORD Motor company program folder!

If the PCM is now reporting as blank then try recovering it using the "Blank/used PCM IDS PMI process described in this YouTube video: https://www.youtube.com/watch?v=Hhk7Wg0i3KE

Been though this with a 2003 Expedition 5.4(With IDS 86) and a 2005 F150(With Both)!

Thanks, lots of good info here. I can confirm that even with getting the VCM3 clone working with FORScan, the application itself does not have the ability to reprogram the module.

I have tried multiple copies of the calibration file to try to make sure it wasn't corrupt itself but have had no luck.

I'll loop through the video and see what it recommends. Thanks again.