FORScan forum

cezarg1410 wrote: Thu Sep 10, 2020 3:59 pm I didn't remove the old one and it still works fine.
So... did anyone updated any firmware via STN 1170 ? I am bit stressed before that

Els27 v3

fordsmax471 wrote: Thu Sep 10, 2020 4:01 pm

cezarg1410 wrote: Thu Sep 10, 2020 3:59 pm I didn't remove the old one and it still works fine.
So... did anyone updated any firmware via STN 1170 ? I am bit stressed before that

Els27 v3

No.
Viaken STN 1170

Els27 v3 ---died after the upgrade

Viaken STN 1170 --do not know

ask the adapter manufacturer first

Tried everything, still no luck, same results as my first post.

I uninstalled 2.4.1, removed all settings and profiles from my HDD.
Installed 2.4.2 clean, created a new profile, connected via wifi, phone, wired connection, always the same results, no available firmware and blank boxes.

Maybe it has to do with the unofficial sync 3.4 update ? Or maybe my hardware is not known (2017 EU NAV APIM) ?

Kinda bought an extended license for this sole purpose, will monitor dev progress... Feel free to contact me if I can help in anyway to speed up the process.

EDIT : Most of my other modules also show no available firmware (blank boxes). Only my IPMA lists 2 available choices, one that is already what's installed, and another that seems older (if version number is in alphabetical order).

I also have unofficial sync 3.4 and forscan correctly shows upgrades.
Dont wait for magic fix. Just ZIP forscan debug log and sent it to forscan team. Then they will fix it:)

Alright, will do.
Is the debug log in the Forscan directory ? I don't know for sure if it will log any error as it does not seem to encounter any... it just does not detect any available version.

personne123 wrote: Thu Sep 10, 2020 6:47 pm Alright, will do.
Is the debug log in the Forscan directory ? I don't know for sure if it will log any error as it does not seem to encounter any... it just does not detect any available version.

I found this here - https://www.forscan.org/contactus.html - :

"FORScan for Windows

Note: FORScan for Windows has Debug Mode setting enabled by default so debug information is recorded always. So all what user needs is to send the information from the laptop. The instruction below explains how to do it. However, if the Debug Mode setting was previously disabled for some reason, you have to enable it, remove vehicle profile (Vehicles->Profiles, delete vehicle from the list), connect and reproduce the problem before move forward with the steps below.

1. Make sure FORScan is closed.
2. Open FORScan Log folder.
2.1.Windows 7 and older: press Windows Start button->All programms->FORScan->FORScan Log folder.
2.2. Windows 8 and newer: click on the Windows icon at the bottom left corner. Find FORScan group in the list (under letter 'F'). Expand the group. Find FORScan Log folder item in the expanded group and click on it.
3. Folder with logs will be opened, you should see 2 files there: dump.bin and FORScan.log (may be more). Please zip them (if possible) and email to us."

I've attempted custom as I already have the files but the 3 buttons wont click for me to select the file.

RyanE wrote: Thu Sep 10, 2020 8:02 pm I found this here - https://www.forscan.org/contactus.html

Alright, debug info sent, thanks for the heads up.

Has anyone here with an unofficially updated SYNC unit to version 3.4 successfully updated their APIM with a "current" version of FORScan ? Just trying to pinpoint the issue, if it can be related to SYNC updates in any way.

personne123 wrote: Thu Sep 10, 2020 9:36 pm

RyanE wrote: Thu Sep 10, 2020 8:02 pm I found this here - https://www.forscan.org/contactus.html

Alright, debug info sent, thanks for the heads up.

Has anyone here with an unofficially updated SYNC unit to version 3.4 successfully updated their APIM with a "current" version of FORScan ? Just trying to pinpoint the issue, if it can be related to SYNC updates in any way.

cezarg1410 said a few posts above that

"I also have unofficial sync 3.4 and forscan correctly shows upgrades.
Dont wait for magic fix. Just ZIP forscan debug log and sent it to forscan team. Then they will fix it:)"

So it works for at least one of us goofballs who updated their SYNC head unit