FORScan v2.4.1 release notes

[mf11mf11]

Hi, is there any way to get the download link as registered member?

[glini]

As it seems not possible to contact FORScan (Admin) per PN and no response from obdlink either: I want to upgrade my APIM fw (for using calm screen on sync 3). I am a registered user with an unlimited licence. I have an original ELS27 from Russia (no chinese clone). How can I get the needed FORScan version? Thank you in advance for any help.

[tractmec]

As it seems not possible to contact FORScan (Admin) per PN and no response from obdlink either: I want to upgrade my APIM fw (for using calm screen on sync 3). I am a registered user with an unlimited licence. I have an original ELS27 from Russia (no chinese clone). How can I get the needed FORScan version? Thank you in advance for any help.

I assume by "Unlimited you mean Lifetime or a Paid license? If you wish to obtain the 2.4.3x branch you will have to send a request to email address. The contact support information is outlined on this page https://forscan.org/contactus.html on the Forscan Home page.

Be prepared to show your "Paid License invoice number in your request as recently the team has stopped taking support requests from standard and trial license holders and is only responding to "Paid License" support requests!

[glini]

Yes, lifetime is the right expression. Thank you for pointing me in the right direction

[davetcollection]

Any updates on when 2.4 will be available again?

[mrdot]

i downloaded this in 09/2020 directly from the site, follow the guide, got the new corded programmer and it ending up bricking my fcdim module.

[Lincjsd]

Is there a link that i can get that contains previous 2.4.X builds, ive searched forums no avail that i could find. All links were broken i clicked on. I want to try a previous version, ive apparently bricked my PAM but its weird every single time i try to flash it, it keeps going further and further sometimes fails instantly, but each time is inconsistent with the previous. The adapter is pinging at 2-3 Ms with excellent read ability, i can access plethora of modules, yet it says its not recommended for the software. What makes it incompatible? I thought read spead and interpreting speed was the biggest issue, if im reading excellent what is the issue with the adapter im using? Its called a Forscan pro and was made specifically for software. I cant access PATS either with it tho it shows the module. Can I crack it open and change something to make it more compatible? or would a previous build be better to try first?

Thanks for any input,

2016 Lincoln MKZ Reserve ii, 3.7L FWD w/Sync3, LTE TCU, and 8 parking sensors, (considering upgrading to 10 if new PAM can read them all)

[oldtinfords]

The first thing I'd do is get a recommended adapter. I've tested various adapters that claim to be made for Forscan & they just don't cut it. Plug the vLinker FS in & the programming completes successfully where other adapters fail.

The recommended adapters are constantly receiving firmware updates in line with Forscan updates to ensure everything works as it should. Forscan doesn't test the other adapters & therefore may not be advising the manufacturer of faults & improvements that need to be implemented.

The vLinker FS is cheap, has 18v FEPS for PCM programming where required & is a very good adapter. The OBDLink EX is good, no 18v FEPS support & more expensive. I prefer the vLinker, so the OBDLink EX stays in the cupboard.


Have a read of the vLinker FS changelog below to see the extra commands, switching etc that have been added to ensure it works.
If these or any other required commands haven't been implemented in your cables firmware, they could be the reason you are having problems.

MIC3322_changelog_v2.3.02.txt

[Lincjsd]

The first thing I'd do is get a recommended adapter. I've tested various adapters that claim to be made for Forscan & they just don't cut it. Plug the vLinker FS in & the programming completes successfully where other adapters fail.

The recommended adapters are constantly receiving firmware updates in line with Forscan updates to ensure everything works as it should. Forscan doesn't test the other adapters & therefore may not be advising the manufacturer of faults & improvements that need to be implemented.

The vLinker FS is cheap, has 18v FEPS for PCM programming where required & is a very good adapter. The OBDLink EX is good, no 18v FEPS support & more expensive. I prefer the vLinker, so the OBDLink EX stays in the cupboard.


Have a read of the vLinker FS changelog below to see the extra commands, switching etc that have been added to ensure it works.
If these or any other required commands haven't been implemented in your cables firmware, they could be the reason you are having problems.

MIC3322_changelog_v2.3.02.txt

You were correct, it was all in the adapter I was able to un-brick (soft brick) my PAM module, as per your reply i decided to go with VLinker Vgate FS and re-flashing unit was like cake thank you!