MicroHacker Forum

FORScanSetup2.4.0.test20200114_no_stpx
This function is in testing stage. There are problems, known ones and may be not known ones. Please note you use it "AS IS". In no event shall FORScan team be liable for any direct or indirect damage, caused by use of this function. We strongly recommend to foresee an option to recover "bricked" module with another equipment (like IDS).

Short instruction:

The function is called "Module firmware update" and available in Configuration and Programming section. Content
consists of 2 columns: current assembly/calibration and available for programming. All the firmware files that included into
the assembly are displayed.

There are 2 filter checkbox on the top (enabled by default):
Only official branch - only firmware from official branch, this is what available in IDS. If this filter box is unchecked, all
possible builds will be displayed, but only compatible with current hardware
Only newer than current - this shows only builds that are newer than current. If you need older ones, uncheck this box.

Every firmware file has status indicator on the right:
- green - file is ready for programming and will be programmed
- yellow - the file will not participate in programming
- red - file is required but missing or damaged

There 2 options at the bottom:

- Force program unchanged firmware - if some file in the new calibration level is not changed, FORScan will not write it. This option changes the behaviour and all files will be rewritten.

- Switch *ALL* modules to programming mode (silence on buses) - in this mode FORScan will switch all modules on both buses to programming mode, to make them "silent". Unfortunately, this function properly works only on J2534 adapters with MS-CAN support. ELM327 kind of adapters and J2534 Passthru without MS-CAN can implement it partially (on current bus only) due to adapter limitations. This may cause serious panic in some modules. So it is recommended to use this option ONLY if there is no other way to program a module.

There are 2 buttons on the bottom:
- Download - download missing files from Internet ( Motorcraft site)
- Program! - start the programming process

It has to be counted that not all of firmware files are available on Motorcraft site (only those that allowed
for dealership).

Known problems:

- It is not recommended to use china ELM327, as it is impossible to guarantee stable work in there. ELM327 Adapters that proved their ability to program firmware:
-- OBDLink EX
-- Ford VCMII original
-- VXDiag VCX Nano for Ford/Mazda
-- ELS27 - original (clone may hang after 30-40 minutes of work)
-- OBDLink SX (doesn't support MS-CAN, so may need to be modified for it)
-- VINT-TT55502 USB (marked as Ford/Mazda/FORScan compatible, with HS/MS CAN switch). Update: one user was unable to program SYNC3 with it.
-- VeePeak USB (marked as Ford/Mazda/FORScan compatible, with HS/MS CAN switch). Update: one user was unable to program SYNC3 with it.

- We do not recommend to program in automated module modules that have ECU Configuration * parts in their firmware, FORScan may offer WRONG configuration file. Recommended way is to use Custom mode: find out what firmware files you need and download them, then select Custom mode in dropdown box and select right firmware files, then program.

FORScan shows summarized firmware size and estimated programming time in the warning dialog before start
programming. We recommend to pay attetion to these numbers, as programming time may be very significant (several hours). Time estimate for J2534 adapters may be very inexact yet.

After the firmware update modules usually throw U2100 DTC. The following sequence of actions is enough to clear it:
- Run Module configuration programmin (As Built format) and load *AB factory configuration in there. Please prepare it
advance (download for Motorcraft site by VIN), as current version cannot download it in automated mode yet.
- write All (all blocks!) to the module. If configuration isn't changed change, FORScan will ask to confirm force write,
please confirm it.

After first successful connect to vehicle FORScan will create vehicle profile. We recommend to backup profiles, as they may be helpful in case of restoring.

What we would like to get in case of problems:
- short report about the problem
- FORScan debug information (FORScan.log and dump.bin)
- user logs (content of Log tab in the section Configuration and Programming).

Regards,
FORScan Team

7zip & WinRAR says that the archive is damaged

download and unzip password convers

marekrbk wrote: ↑25 Feb 2020, 14:49 download and unzip password convers

Yep, have this version for a while now. BCMii firmaware update does not work and some users reported that DDM module also can be blocked so watch out what are u doing guys. It is still beta , Official release will be 2.4.1

Yep, take it like an additional tool to try fix the **** when you mess up. If you have other stable tools like UCDS, don't risk it Thanks for sharing the beta!

hi guis

DDM update works for me
now my mirrors automatic open and close after unlock/lock the car
but i have software-incampatible as error rigth now

also bcmi update works without problem

i found in Procedure
DCMii Central configuration(main)
global open/close

there are this options
00 - Not configured
01 - Global open/close deactivated
02 doors enabled (3 seconds)
03 doors and roof hatch
04 open 3s / close 1 touch (0s)

04 musst be the setting for automatic close window when lock the car
so i set this up in bcmii and in ipc (backup)

i reset bcmii ddm and ipc
i relearn windowposition to ddm (full open/press and hold close 1 second when window is fully closed)
window up down automatic works again
but not the 1 touch close
aslo window not open anymore when i hold unlock on remote
so i set all back and window with remote not works....
i reset all modules again...nothing

and specialy for go4it
wich rfa modul you have, the partnumber cuz you was enable to set multichannel with autostart
i want to change the module to have also autostart (not need to press the startbutton until engine runs)
i here that peoble had problems after updating them, the modules locked themself....

C* and D* RFAs can work with AutoStart; A* and B* have older HW and will brick if you put new FW in them.
Mainly you need to write to them the missing CE file.

ok thanks i will look wich module i have

thanks for information

i have this rfa
so it should work with an updaze

As tried and tested, function Open 3s/Close 0s is not related to auto close windows.