FORScan v2.4.1 release notes

Car configuration discussions and experience sharing
User avatar
ddg71
Posts: 21
Joined: Sat Jun 27, 2020 10:54 am
Vehicle: Ford Mondeo 2.0 TDCI Powershift, 180 HP, mk5, 2016

Re: FORScan v2.4.1 release notes

Post by ddg71 » Sun Sep 06, 2020 6:43 am

Thanks 8-)
Forscan 2.4.2 , Obdlink EX

Vento
Posts: 4
Joined: Thu Aug 13, 2020 4:03 pm
Vehicle: Ford Mondeo Hybrid 2018

Re: FORScan v2.4.1 release notes

Post by Vento » Mon Sep 07, 2020 9:30 am

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.
I have a Ford Mondeo Hybrid (MY 2018) do I still need to connect a charger do the 12V battery or since I have also the main one (and when is near empty the engine starts automatically to recharge it) I can simply update modules without it?

Also:

I'm a software dev but does not know a lot about cars (this is my first car actually)... be understanding if I'm asking stupid question, but please talk freely about stuffs like binary dumps / external flashers / and things like that... I understand "zeros and ones" I have problems with "gears and oil"

I would like to update just the APIM fw... BUT!:
  • 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?

RyanE
Posts: 8
Joined: Thu May 25, 2017 12:46 am
Vehicle: 2017 Ford Fusion Sport 2.7 Ecoboost

Re: FORScan v2.4.1 release notes

Post by RyanE » Mon Sep 07, 2020 6:29 pm

Hello developer folks,

I understand that you are aware of the issue of not being able to update the APIM firmware on Sync 3 systems if the Sync software has been updated to 3.4 using the hacked/cracked updater.

I was wondering, as I am experiencing this issue, if I can provide any information to help with the resolution of this bug? I have a 2017 US model Ford Fusion Sport, with Sync 3 and the Sony audio package, but without navigation. I have the EX OBD2 adapter, as well as a J2354 pass through adapter.

Thanks for all your hard work on this release!

Airborne_Ape
Posts: 33
Joined: Thu Sep 08, 2016 11:18 pm
Vehicle: F150, 3.5 Eco, 2017
Location: Edmonton, Alberta

Re: FORScan v2.4.1 release notes

Post by Airborne_Ape » Mon Sep 07, 2020 7:15 pm

Thanks for this release! I feel bad that you aren't generating the income from your products you deserve. If you ever launch an online fundraiser campaign, for example a special color OBD Link EX, I'd be glad to make such a purchase. However you manage to serve a community this large and still have time to put food on your table is incredible.

Airborne_Ape
Posts: 33
Joined: Thu Sep 08, 2016 11:18 pm
Vehicle: F150, 3.5 Eco, 2017
Location: Edmonton, Alberta

Re: FORScan v2.4.1 release notes

Post by Airborne_Ape » 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

rich935
Posts: 70
Joined: Sat Oct 12, 2019 11:45 pm
Vehicle: Ford Focus SE 2.0

Re: FORScan v2.4.1 release notes

Post by rich935 » Mon Sep 07, 2020 9:26 pm

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
You seem to be one of the people that knows the most about updating modules. Would you happen to know if you update the TCM does this have any dependencies on the PCM. Well if you update the TCM and don't update the PCM is there going to be any problems that you know of. I have a 2013 Ford Focus SE with an ELS27 adapter and it might be different for this vehicle but if you know anything please let me know. Hope this makes sense. Thanks.

Dirk_Pitt
Posts: 1
Joined: Thu Aug 06, 2020 10:28 pm
Vehicle: 2019 Ford F-250 Lariat

Re: FORScan v2.4.1 release notes

Post by Dirk_Pitt » Tue Sep 08, 2020 1:07 am

oldtinfords wrote:
Thu Sep 03, 2020 8:02 am
Has the Tatrix OpenPort 2.0 been tested with v2.4.1?
I would love to know this as well.

FARES2002M
Posts: 11
Joined: Sat Aug 01, 2020 5:42 pm
Vehicle: 2017 Ford Expolrer 3.5

Re: FORScan v2.4.1 release notes

Post by FARES2002M » Fri Sep 11, 2020 6:13 pm

Thanks so much FORScan Team for your tremendous efforts to release FORScan v2.4.2 :idea: 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 :geek:

nabilultranet
Posts: 6
Joined: Thu May 30, 2019 1:03 pm
Vehicle: FORD FOCUS MK3 1.6L TDCI 115 2012

Re: FORScan v2.4.1 release notes

Post by nabilultranet » Mon Sep 14, 2020 6:57 pm

FARES2002M wrote:
Fri Sep 11, 2020 6:13 pm
Thanks so much FORScan Team for your tremendous efforts to release FORScan v2.4.2 :idea: 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 :geek:
Hello and think you for sharing your experience.
Can you tel us how much time take every firmware update and what adapter did you use ?

Thinks and sorry for my bad english.

rich935
Posts: 70
Joined: Sat Oct 12, 2019 11:45 pm
Vehicle: Ford Focus SE 2.0

Re: FORScan v2.4.1 release notes

Post by rich935 » Tue Sep 15, 2020 5:51 am

Does any know what the "Stop activity on buses" check box option does on the "module firmware update screen" you any advantages and disadvantages of this?

Post Reply