FORScan forum

It is strongly recommended to connect a battery charger to the vehicle battery. It may be not necessary for small firmware, so if you are experienced user and know for sure the battery will be enough, you may not do it. Otherwise, we recommend to connect the charger as a rule.

• Is updating other module fw recommended/needed?
• Are there dependencies between other modules/fw?
• Are there update sequences that should be followed (like before update module X update Y and Z and after go with X)?
• Are there "relearning"/"reset" phase/action that I have to do after/before a fw update? How to I make my car relearn parameters? (I'm asking because I've helped my dad fixing some stuffs on his motorbike and after some modification I had to press a "Reset/Relearn parameters", and test the motorbike for few kilometers to completely make the car adapt to the new changes, is there a similar button in ForScan? A "general" one or is module-by-module basis?)
• Is "having always the last version" a good thing/mindset? Seeing that I can update most modules, should I simply do it?
• Do I lose module configuration?
• After the update can I load an "factory configuration" that 99.9%% sure will work? Does the fw update does this by itself?
• Can I backup my current version + configuration and roll back if necessary? If yes how? Do I need other hw other than the Obdlink EX?
• What can/should i do if the update fails?
• From https://community.cyanlabs.net/t/updati ... n-files/17 (specific to update APIM fw but my question is about any module) is see that the process should be "Find the module to update" > "Download" > "Test run SBL" > "Program". Is this the best practice?

Vento wrote: Mon Sep 07, 2020 9:30 am
I would like to update just the APIM fw... BUT!:

• Is updating other module fw recommended/needed? No
• Are there dependencies between other modules/fw? Yes
• Are there update sequences that should be followed (like before update module X update Y and Z and after go with X)? No
• Are there "relearning"/"reset" phase/action that I have to do after/before a fw update? How to I make my car relearn parameters? Not necessarily for the APIM but at the very least you should master reset it afterwards.
• Is "having always the last version" a good mindset? Seeing that I can update most modules, should I simply do it? No
• Do I lose module configuration? No, but you should master reset it
• After the update can I load an "factory configuration" that 99.9%% sure will work? Does the fw update does this by itself? No & No
• Can I backup my current version + configuration and roll back if necessary? If yes how? Do I need other hw other than the Obdlink EX? Screenshot your calibration before attempting the update, the firmware flash is probably going to fail so don't worry about it because you likely won't able to restore the original files at that point
• What can/should i do if the update fails? It will probably will fail first try, you can force other firmware onto it to bring it back to life and sometimes it takes a lot of attempts.
• From https://community.cyanlabs.net/t/updati ... n-files/17 (specific to update APIM fw but my question is about any module) is see that the process should be "Find the module to update" > "Download" > "Test run SBL" > "Program". Is this the best practice? Never used it. i assume it is not the best practice for the same reason ForScan & UCDSYS is not the best practice: best practice would be to use dealership tools

Airborne_Ape wrote: Mon Sep 07, 2020 7:35 pm

Vento wrote: Mon Sep 07, 2020 9:30 am
I would like to update just the APIM fw... BUT!:

• Is updating other module fw recommended/needed? No
• Are there dependencies between other modules/fw? Yes
• Are there update sequences that should be followed (like before update module X update Y and Z and after go with X)? No
• Are there "relearning"/"reset" phase/action that I have to do after/before a fw update? How to I make my car relearn parameters? Not necessarily for the APIM but at the very least you should master reset it afterwards.
• Is "having always the last version" a good mindset? Seeing that I can update most modules, should I simply do it? No
• Do I lose module configuration? No, but you should master reset it
• After the update can I load an "factory configuration" that 99.9%% sure will work? Does the fw update does this by itself? No & No
• Can I backup my current version + configuration and roll back if necessary? If yes how? Do I need other hw other than the Obdlink EX? Screenshot your calibration before attempting the update, the firmware flash is probably going to fail so don't worry about it because you likely won't able to restore the original files at that point
• What can/should i do if the update fails? It will probably will fail first try, you can force other firmware onto it to bring it back to life and sometimes it takes a lot of attempts.
• From https://community.cyanlabs.net/t/updati ... n-files/17 (specific to update APIM fw but my question is about any module) is see that the process should be "Find the module to update" > "Download" > "Test run SBL" > "Program". Is this the best practice? Never used it. i assume it is not the best practice for the same reason ForScan & UCDSYS is not the best practice: best practice would be to use dealership tools

I've flashed several APIM's with ForScan 2.4.0. I think your post is in the wrong thread and answered your questions in bold text. For your APIM you don't need to worry about the battery. With the OBD Link EX the APIM takes about 16 to 30 minutes to flash depending on which generation hardware it is. I would estimate there's about an 75% chance it will fail first try; they often do, when they fail you can't revert back to the original firmware and you need to try other calibration files from other vehicles to restore it. I wrote a much longer post on the subject in the thread linked below.

Read post #2 here:

https://www.f150forum.com/f118/upgrade- ... ost6356291

oldtinfords wrote: Thu Sep 03, 2020 8:02 am Has the Tatrix OpenPort 2.0 been tested with v2.4.1?

FARES2002M wrote: Fri Sep 11, 2020 6:13 pm Thanks so much FORScan Team for your tremendous efforts to release FORScan v2.4.2 after 7 days only of releasing FORScan v2.4.1 to fix the APIM Firmware update issue. I used both version to update almost all Modules in my 2017 Explorer, but unfortunately the APIM update issue which is the main concern for most of people here have not been solved yet. Thanks again and hope to see a solution for this issue soon