FORScan v2.4.1 release notes

[FORScan]

Update 2020-09-23: v2.4 is temporarily removed from the site because of number of people that don't really understand what they do and brick their modules or even cars, then paniking and attack our support and paralize our normal work. So new roadmap is:

1. Create a comprehensive programming guide (manual)

2. Make any china ELM327 disabled for programming function by default. User will be able to explicitly enable it, though. Unfortunately, experience shows that using these adapters for MFU is a kind of playing russian roulette.

3. Make v2.4 available, but not from the Products page. The idea is to make it available to the users that have read the programming guide.

We are sorry for the trouble.

1. General

Version 2.4.1 includes all the functionality of v2.3.35 (last version of 2.3 branch), plus implements module firmware update functions.

This document covers only certain issues with programming. In the nearest days we will create article about module programming in FORScan.

Version 2.4.1 is addressed to advanced users who understand the module firmware update (MFU) functionality. MFU is more dangerous than any other FORScan programming function, so it is not recommended to use it just for fun.

2. Not implemented

Unfortunately a lot of MFU features are still not implemented and be a subject of the future releases. Here are some of them: update for older ECU (200x MY), update for Mazda ECU, update wizard etc.

3. Firmware files

FORScan downloads firmware files from this page:

https://www.fordtechservice.dealerconne ... rogram.asp

Unfortunately this site doesn’t contain all the files, also old files seem to be removed. If file is missing here, FORScan requests the file from an independent storage. Access to the storage is only available for users who have paid Extended License.

The independent storage may also have no some files. In this case please contact us and we will try to find it. No guarantee we will be able to do it, though.

4. Adapters

This version only allows wired adapters to be used with MFU. For J2534 PassThru adapters there are no other limitations. ELM327 adapters must have increased baud rate (>38400) and minimum response time <20ms. It is not recommended to use any china ELM327 for MFU. It is recommended to use either J2534 PassThru or OBDLink EX (see note below).

It is strongly recommended to upgrade OBDLink EX firmware up to the latest one available on official site (5.5.3). FORScan can do it for you on connect .

OBDLink MX+ is the only wireless adapter that is allowed for firmware update. It shows very good results in MFU tests and it was decided to add it. It must be upgraded to the latest firmware. FORScan can do it for you on connect. We still recommend to use wired adapter, though, as it is more reliable and fast.

Automated check & update adapter’s firmware function is implemented only for OBDLink EX and MX+. If something went wrong with the update, you will need to download official ScanTool firmware updater (https://www.scantool.net/scantool/downloads/updates/) and recover it manually. Note: after firmware update of OBDLink MX+ it may require some significant time to be available for connection, so FORScan may be unable to connect automatically right after the update. In this case just please connect manually.

5. Programming time

Performance of the programming process depends on a lot of factors. But first of all, it depends on adapter’s performance and functionality. Critical parameter is support of ISO15765 in the adapter. If adapters implements full ISO15765 support (we call it hardware ISO15765), it is 4-5 times faster than the adapter that has no such function (we call it software ISO15765). Here are some reference points for HS-CAN:

Ford VCMII genuine with hardware ISO15765 – 1000Kb/min

OBDLink EX with hardware ISO15765 – 700-900Kb/min

Ford VCMII genuine with software ISO15765 – 200-300 Kb/min

ELS27 with software ISO15765 -200-300 Kb/min (on 2-8 Mbps baud rate)

OBDLink EX with software ISO15765 – 200 Kb/min (on 2Mbps baud rate)

ELM327 with software ISO15765 – 100 Kb/min (on 500 Kbps baud rate).

(Timings for MS-CAN may be up to 4x times slower )

So you can see why we do not recommend to use ELM327 for firmware update, and why we require OBDLink be upgraded to the latest fw that supports hardware ISO15765.

Unfortunately, there are no firmware with stable hardware ISO15765 support for ELS27 yet This is not a fault of ELS27 team but chip developer (ScanTool).

6. Preparations

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.

Firmware update process may take up to several hours (depends on adapter performance, firmware size, vehicle bus speed etc). So we also recommend to connect a charger to the laptop (or at least keep it in mind). Please note that 12V chargers connected to the car power point are not safe and not recommended.

It is very important to connect adapter to the OBDII port in a reliable way that excludes a possibility to disturb the adapter during the programming process. It may cause very unpleasant sequences even if you use good quality adapter.

7. Other notes
Please note this is not a test version. The function has been tested for more than two years (since November 2017). This release was thoroughly tested on many real cars of 2012-2018MY. It has a beta quality. It means that some problems are possible, but it must be not easy to brick the module if you follow all recommendations (on adpater, battery charger etc). Please address any issues found to our Support Team (don't forget to provide debug information), thanks.

[Paul_13]

Hi, not sure if this is the correct place to post this, but I've just upgraded the HVAC module firm ware on my 2014 smax 2.0 tdci.
Everything was going OK, but then it displayed a fault of "the module seems to be bricked"
However it still functions as it should afterwards
The same fault also occurred on the abs module. Programming was complete, but ECU seems to be bricked error code.
When I rescan the module, the correct firm ware has been loaded

[fordsmax471]

Hi !

Restore the AB factory configuration, reset the module and always use a new car profile

[rich935]

Will this show any time remaining estimate for the module update? If not that would be a good feature update if possible.

[rich935]

If anyone has any videos of module firmware update (MFU) for a 2013 Ford Focus SE or similar year please post a link. Just to double check the procedure. Thanks.

[ks_aus_jucunda]

Guys from Forscan team,

first of all congrats for the new release! Something I was waiting for a long time now.

Question 1 - Free extended licence is good enough to update firmware of modules if available via the ford servers?
Question 2 - Do you know a better source of a retailer selling the OBDlink EX than Amazon?
Queston 3 - is this adapter a working clone of the OBDlink EX? https://www.amazon.de/bbfly-FORScan-OBD ... in_1_title

Thanks for following up on my questions.

CU soon!

[FORScan]

The same fault also occurred on the abs module. Programming was complete, but ECU seems to be bricked error code.

Interesting, never experienced this in our tests. Secondary Boot Loader (SBL) has a special
function to check if the module has a proper executable. The error you see means that SBL returned some
wrong code or the function is not really supported in this module. Please email us debug information from
your session (instruction: https://forscan.org/contactus.html#debug_info), we will analyse it and make necessary
corrections.

Will this show any time remaining estimate for the module update? If not that would be a good feature update if possible.

WIll implement it in the future releases. FORScan provides a estimate right before the procedure, but it is not possible to estimate precisely as some parameters are unknown (module performance, size of blocks transferred etc). So it shows it in range. ex "5..10 mins". Remaining time could be calculated precisely. Please note that current progress indicator is quite accurate and have to be used to estimate the progress and remaning time.

[FORScan]

Question 1 - Free extended licence is good enough to update firmware of modules if available via the ford servers?

Yes it is.

Question 2 - Do you know a better source of a retailer selling the OBDlink EX than Amazon?

It can be also purchased from the manufacturer's site:

https://www.scantool.net/obdlink-ex/

We guess (but don't know) if you order it there, they will send it from their office/stock. Anyway, ScanTool has great support team, we suggest to address this type of questions to them directly.

Queston 3 - is this adapter a working clone of the OBDlink EX? https://www.amazon.de/bbfly-FORScan-OBD ... in_1_title

We had no chance to try it (honestly, had no idea about this adapter before), but we don't believe it is a clone of EX. We suspect (but not sure) it is regular ELM327 with MS-CAN available through RTS relay and has no any of EX features.

[rich935]

Thanks for the reply. Hope to see this in the future if possible.

[oldtinfords]

Has the Tatrix OpenPort 2.0 been tested with v2.4.1?