FORScan forum

Thanks for the update.

Ford4Life wrote: Thu Sep 10, 2020 2:18 pm The procedure said "successfully programmed" but it also said the module was bricked.

This problem was fixed in version 2.4.2 released several days ago.

FORScan wrote: Sun Sep 13, 2020 5:21 am

Ford4Life wrote: Thu Sep 10, 2020 2:18 pm The procedure said "successfully programmed" but it also said the module was bricked.

This problem was fixed in version 2.4.2 released several days ago.

Right, I thought I upgraded ForScan but apparently I never did, I was on version 2.4.1. Thanks for clarifying.

Hi would like to ask how you went as im having the same problem

I don't remember but I had my car saved in forscan so I selected that and it found the info it needed on its own,I think. So I could just do a reprogram of the IPC.

Hopefully someone will learn from this incident
Look at this link:
https://forscan.org/forum/viewtopic.php?f=16&t=24637

1) A power supply is required, not a battery charger
The battery charger has too much AC ripple when charging (high noise frequency on the battery connection)
The output is either too high or too low! 2) A floating power supply should maintain the correct amperage supply and battery voltage (Min 12.5v to 13.5v).
3) A floating power supply will keep the vehicle alive as long as required and not overcharge the battery.
4) The laptop needs to be on it own power supply and not running on its battery.
5) WiFi is a good connection but a LAN is safer and faster.
6) Any programming should be done with a USB J2534-2 device or tools such as vLinker FS that supports FEPS.
7) What is FEPS (read it, do not share it yet)!
8) What to do with a bricked module A) Cry B) replace it C) try the next solution below.
Kindly take a number if the thought process requires an argument.