Unable to access APIM via Forscan after the update

Hello, sorry for the second post in a short span of time. After the update to sync 3.4, when I try to read the APIM module configuration via Forscan, it gives me this warning:

"Checking vehicle configuration …

SYNC version: SYNC 3 . Please make sure the module version is correct.

WARNING! It is not allowed to use configuration and programming functions in case of wrong
version specified, as it may cause module damage. If the module version is not correct, please
remove vehicle profile and reconnect, specifying correct version."

I know this is a Forscan related issue maybe, but since this has happened after the update to sync 3.4, I thought it was relevant for this forum too. I already deleted the profile and reconnected the vehicle with no luck.
Do you have any suggestions?


SYNC Region: EU

Navigation Variant: Nav

Manufacturer Year: Pre MY20

Install Type: OEM

Old SYNC Version: 3.0.20204

New SYNC Version: 3.4.23188

Do you have a error message, if so what is it?
Forscan warning whean reading APIM module:
Checking vehicle configuration …

SYNC version: SYNC 3 . Please make sure the module version is correct.

WARNING! It is not allowed to use configuration and programming functions in case of wrong
version specified, as it may cause module damage. If the module version is not correct, please
remove vehicle profile and reconnect, specifying correct version.

Update Method: CyanLabs Syn3 Updater

Syn3 Updater Version: V2.13.1.0

Syn3 Updater Documentation Read: yes

Syn3 Updater Log File

CYANLABS - SYN3 UPDATER - V2.13.1.0
Branch: Stable
Operating System: Microsoft Windows 11 Pro (2009)

PREVIOUS CONFIGURATION
Version: 3.0.20204
Region: EU
Navigation: True
Install Mode: Auto-Detect (reformat)
Install Mode Overridden: False
My20 Protection Enabled: Disabled / Not MY20

DESTINATION DETAILS
Mode: Drive
Model: Kingston DataTraveler 3.0 USB Device
Size: 28,9GB
FileSystem: exFAT
Partition Type: MBR

REFORMAT.LST
VOICE=5U5T-14G391-AT_1660763323000.TAR.GZ
GRACENOTES=4U5T-14G423-AC_1615425645000.TAR.GZ
ENH_DAB=1U5T-14G658-AH_1644006443000.TAR.GZ
APPS=NU5T-14G381-AD_1689364279000.TAR.GZ
MAP=1U5T-14G421-BAL_1723658080000.TAR.GZ
MAP=1U5T-14G421-BBL_1723560114000.TAR.GZ
MAP=1U5T-14G421-BCL_1723600422000.TAR.GZ
MAP=1U5T-14G421-BDL_1723600797000.TAR.GZ
MAP=1U5T-14G421-BEL_1723601194000.TAR.GZ
MAP=1U5T-14G421-BFL_1723601450000.TAR.GZ
MAP=1U5T-14G421-BGL_1723602075000.TAR.GZ
MAP=1U5T-14G421-BHL_1723602658000.TAR.GZ
MAP=1U5T-14G421-BJL_1723602553000.TAR.GZ
VOICE_NAV=4U5T-14G422-BAL_1723663279000.TAR.GZ
VOICE_NAV=4U5T-14G422-BBL_1723666341000.TAR.GZ
VOICE_NAV=4U5T-14G422-BCL_1723745202000.TAR.GZ
VOICE_NAV=4U5T-14G422-BDL_1723746662000.TAR.GZ
MAP_LICENSE=1U5T-14G424-BN_1727700842000.TAR.GZ


AUTOINSTALL.LST
; CyanLabs Syn3Updater 2.13.1.0 Stable - reformat  Mode - Sync 3.4.23188 EU

[SYNCGen3.0_ALL_PRODUCT]
Item1 = RWDataCleaner TOOL - PU5T-14G386-BB_1690840002000.TAR.GZ
Open1 = SyncMyRide\PU5T-14G386-BB_1690840002000.TAR.GZ
Item2 = REFORMAT TOOL  - 1u5t-14g386-cb.tar.gz
Open2 = SyncMyRide\1u5t-14g386-cb.tar.gz
Options = AutoInstall

FILES (20)
1u5t-14g386-cb.tar.gz (8,5MB)
PU5T-14G386-BB_1690840002000.TAR.GZ (3,2KB)
5U5T-14G391-AT_1660763323000.TAR.GZ (1,5GB)
4U5T-14G423-AC_1615425645000.TAR.GZ (689MB)
1U5T-14G658-AH_1644006443000.TAR.GZ (57,5MB)
NU5T-14G381-AD_1689364279000.TAR.GZ (869,8MB)
1U5T-14G421-BAL_1723658080000.TAR.GZ (2,5GB)
1U5T-14G421-BBL_1723560114000.TAR.GZ (539,6MB)
1U5T-14G421-BCL_1723600422000.TAR.GZ (1,8GB)
1U5T-14G421-BDL_1723600797000.TAR.GZ (1,1GB)
1U5T-14G421-BEL_1723601194000.TAR.GZ (1,8GB)
1U5T-14G421-BFL_1723601450000.TAR.GZ (2,5GB)
1U5T-14G421-BGL_1723602075000.TAR.GZ (2,1GB)
1U5T-14G421-BHL_1723602658000.TAR.GZ (2,6GB)
1U5T-14G421-BJL_1723602553000.TAR.GZ (26MB)
4U5T-14G422-BAL_1723663279000.TAR.GZ (2,4GB)
4U5T-14G422-BBL_1723666341000.TAR.GZ (2,3GB)
4U5T-14G422-BCL_1723745202000.TAR.GZ (1,7GB)
4U5T-14G422-BDL_1723746662000.TAR.GZ (2,1GB)
1U5T-14G424-BN_1727700842000.TAR.GZ (1,7KB)

LOG
[20/02/2025 00:13:25] Selected Region: EU - Release: Sync 3.4.23188 - Map Version: F13 (2023) - EU (10 2024) 
[20/02/2025 00:13:25] Install Mode: Auto-Detect (reformat) Forced: False 
[20/02/2025 00:13:25] MY20 Protection: Disabled / Not MY20 
[20/02/2025 00:13:25] Formatting USB drive
[20/02/2025 00:13:25] Re-creating partition table as MBR and formatting as ExFat on selected USB drive
[20/02/2025 00:13:35] Checking Existing File: 1u5t-14g386-cb.tar.gz 
[20/02/2025 00:13:35] Validated: 1u5t-14g386-cb.tar.gz (Skipping Download) 
[20/02/2025 00:13:35] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
[20/02/2025 00:13:36] Validated: PU5T-14G386-BB_1690840002000.TAR.GZ (Skipping Download) 
[20/02/2025 00:13:36] Checking Existing File: 5U5T-14G391-AT_1660763323000.TAR.GZ 
[20/02/2025 00:13:41] Validated: 5U5T-14G391-AT_1660763323000.TAR.GZ (Skipping Download) 
[20/02/2025 00:13:41] Checking Existing File: 4U5T-14G423-AC_1615425645000.TAR.GZ 
[20/02/2025 00:13:44] Validated: 4U5T-14G423-AC_1615425645000.TAR.GZ (Skipping Download) 
[20/02/2025 00:13:44] Checking Existing File: 1U5T-14G658-AH_1644006443000.TAR.GZ 
[20/02/2025 00:13:44] Validated: 1U5T-14G658-AH_1644006443000.TAR.GZ (Skipping Download) 
[20/02/2025 00:13:44] Checking Existing File: NU5T-14G381-AD_1689364279000.TAR.GZ 
[20/02/2025 00:13:48] Validated: NU5T-14G381-AD_1689364279000.TAR.GZ (Skipping Download) 
[20/02/2025 00:13:48] Checking Existing File: 1U5T-14G421-BAL_1723658080000.TAR.GZ 
[20/02/2025 00:13:57] Validated: 1U5T-14G421-BAL_1723658080000.TAR.GZ (Skipping Download) 
[20/02/2025 00:13:57] Checking Existing File: 1U5T-14G421-BBL_1723560114000.TAR.GZ 
[20/02/2025 00:13:59] Validated: 1U5T-14G421-BBL_1723560114000.TAR.GZ (Skipping Download) 
[20/02/2025 00:13:59] Checking Existing File: 1U5T-14G421-BCL_1723600422000.TAR.GZ 
[20/02/2025 00:14:05] Validated: 1U5T-14G421-BCL_1723600422000.TAR.GZ (Skipping Download) 
[20/02/2025 00:14:05] Checking Existing File: 1U5T-14G421-BDL_1723600797000.TAR.GZ 
[20/02/2025 00:14:10] Validated: 1U5T-14G421-BDL_1723600797000.TAR.GZ (Skipping Download) 
[20/02/2025 00:14:10] Checking Existing File: 1U5T-14G421-BEL_1723601194000.TAR.GZ 
[20/02/2025 00:14:17] Validated: 1U5T-14G421-BEL_1723601194000.TAR.GZ (Skipping Download) 
[20/02/2025 00:14:17] Checking Existing File: 1U5T-14G421-BFL_1723601450000.TAR.GZ 
[20/02/2025 00:14:17] Validate: 1U5T-14G421-BFL_1723601450000.TAR.GZ (Failed!, Downloading)
[20/02/2025 00:14:17] Downloading: 1U5T-14G421-BFL_1723601450000.TAR.GZ
[20/02/2025 00:17:15] Validating: 1U5T-14G421-BFL_1723601450000.TAR.GZ 
[20/02/2025 00:17:25] Downloaded: 1U5T-14G421-BFL_1723601450000.TAR.GZ 
[20/02/2025 00:17:25] Checking Existing File: 1U5T-14G421-BGL_1723602075000.TAR.GZ 
[20/02/2025 00:17:25] Downloading: 1U5T-14G421-BGL_1723602075000.TAR.GZ
[20/02/2025 00:19:42] Validating: 1U5T-14G421-BGL_1723602075000.TAR.GZ 
[20/02/2025 00:19:50] Downloaded: 1U5T-14G421-BGL_1723602075000.TAR.GZ 
[20/02/2025 00:19:50] Checking Existing File: 1U5T-14G421-BHL_1723602658000.TAR.GZ 
[20/02/2025 00:19:50] Downloading: 1U5T-14G421-BHL_1723602658000.TAR.GZ
[20/02/2025 00:22:22] Validating: 1U5T-14G421-BHL_1723602658000.TAR.GZ 
[20/02/2025 00:22:33] Downloaded: 1U5T-14G421-BHL_1723602658000.TAR.GZ 
[20/02/2025 00:22:33] Checking Existing File: 1U5T-14G421-BJL_1723602553000.TAR.GZ 
[20/02/2025 00:22:33] Downloading: 1U5T-14G421-BJL_1723602553000.TAR.GZ
[20/02/2025 00:22:37] Validating: 1U5T-14G421-BJL_1723602553000.TAR.GZ 
[20/02/2025 00:22:37] Downloaded: 1U5T-14G421-BJL_1723602553000.TAR.GZ 
[20/02/2025 00:22:37] Checking Existing File: 4U5T-14G422-BAL_1723663279000.TAR.GZ 
[20/02/2025 00:22:37] Downloading: 4U5T-14G422-BAL_1723663279000.TAR.GZ
[20/02/2025 00:24:48] Validating: 4U5T-14G422-BAL_1723663279000.TAR.GZ 
[20/02/2025 00:24:57] Downloaded: 4U5T-14G422-BAL_1723663279000.TAR.GZ 
[20/02/2025 00:24:57] Checking Existing File: 4U5T-14G422-BBL_1723666341000.TAR.GZ 
[20/02/2025 00:24:57] Downloading: 4U5T-14G422-BBL_1723666341000.TAR.GZ
[20/02/2025 00:27:03] Validating: 4U5T-14G422-BBL_1723666341000.TAR.GZ 
[20/02/2025 00:27:12] Downloaded: 4U5T-14G422-BBL_1723666341000.TAR.GZ 
[20/02/2025 00:27:12] Checking Existing File: 4U5T-14G422-BCL_1723745202000.TAR.GZ 
[20/02/2025 00:27:12] Downloading: 4U5T-14G422-BCL_1723745202000.TAR.GZ
[20/02/2025 00:28:53] Validating: 4U5T-14G422-BCL_1723745202000.TAR.GZ 
[20/02/2025 00:29:00] Downloaded: 4U5T-14G422-BCL_1723745202000.TAR.GZ 
[20/02/2025 00:29:00] Checking Existing File: 4U5T-14G422-BDL_1723746662000.TAR.GZ 
[20/02/2025 00:29:00] Downloading: 4U5T-14G422-BDL_1723746662000.TAR.GZ
[20/02/2025 00:30:42] Validating: 4U5T-14G422-BDL_1723746662000.TAR.GZ 
[20/02/2025 00:30:50] Downloaded: 4U5T-14G422-BDL_1723746662000.TAR.GZ 
[20/02/2025 00:30:50] Checking Existing File: 1U5T-14G424-BN_1727700842000.TAR.GZ 
[20/02/2025 00:30:50] Downloading: 1U5T-14G424-BN_1727700842000.TAR.GZ
[20/02/2025 00:30:51] Validating: 1U5T-14G424-BN_1727700842000.TAR.GZ 
[20/02/2025 00:30:51] Downloaded: 1U5T-14G424-BN_1727700842000.TAR.GZ 
[20/02/2025 00:30:51] Preparing USB drive
[20/02/2025 00:30:51] Checking Existing File: 1u5t-14g386-cb.tar.gz 
[20/02/2025 00:30:51] Copying: 1u5t-14g386-cb.tar.gz 
[20/02/2025 00:30:52] Validating: 1u5t-14g386-cb.tar.gz 
[20/02/2025 00:30:52] Copied: 1u5t-14g386-cb.tar.gz 
[20/02/2025 00:30:52] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
[20/02/2025 00:30:52] Copying: PU5T-14G386-BB_1690840002000.TAR.GZ 
[20/02/2025 00:30:52] Validating: PU5T-14G386-BB_1690840002000.TAR.GZ 
[20/02/2025 00:30:52] Copied: PU5T-14G386-BB_1690840002000.TAR.GZ 
[20/02/2025 00:30:52] Checking Existing File: 5U5T-14G391-AT_1660763323000.TAR.GZ 
[20/02/2025 00:30:52] Copying: 5U5T-14G391-AT_1660763323000.TAR.GZ 
[20/02/2025 00:32:33] Validating: 5U5T-14G391-AT_1660763323000.TAR.GZ 
[20/02/2025 00:32:51] Copied: 5U5T-14G391-AT_1660763323000.TAR.GZ 
[20/02/2025 00:32:51] Checking Existing File: 4U5T-14G423-AC_1615425645000.TAR.GZ 
[20/02/2025 00:32:51] Copying: 4U5T-14G423-AC_1615425645000.TAR.GZ 
[20/02/2025 00:33:35] Validating: 4U5T-14G423-AC_1615425645000.TAR.GZ 
[20/02/2025 00:33:44] Copied: 4U5T-14G423-AC_1615425645000.TAR.GZ 
[20/02/2025 00:33:44] Checking Existing File: 1U5T-14G658-AH_1644006443000.TAR.GZ 
[20/02/2025 00:33:44] Copying: 1U5T-14G658-AH_1644006443000.TAR.GZ 
[20/02/2025 00:33:48] Validating: 1U5T-14G658-AH_1644006443000.TAR.GZ 
[20/02/2025 00:33:49] Copied: 1U5T-14G658-AH_1644006443000.TAR.GZ 
[20/02/2025 00:33:49] Checking Existing File: NU5T-14G381-AD_1689364279000.TAR.GZ 
[20/02/2025 00:33:49] Copying: NU5T-14G381-AD_1689364279000.TAR.GZ 
[20/02/2025 00:34:45] Validating: NU5T-14G381-AD_1689364279000.TAR.GZ 
[20/02/2025 00:34:56] Copied: NU5T-14G381-AD_1689364279000.TAR.GZ 
[20/02/2025 00:34:56] Checking Existing File: 1U5T-14G421-BAL_1723658080000.TAR.GZ 
[20/02/2025 00:34:56] Copying: 1U5T-14G421-BAL_1723658080000.TAR.GZ 
[20/02/2025 00:37:39] Validating: 1U5T-14G421-BAL_1723658080000.TAR.GZ 
[20/02/2025 00:38:10] Copied: 1U5T-14G421-BAL_1723658080000.TAR.GZ 
[20/02/2025 00:38:10] Checking Existing File: 1U5T-14G421-BBL_1723560114000.TAR.GZ 
[20/02/2025 00:38:10] Copying: 1U5T-14G421-BBL_1723560114000.TAR.GZ 
[20/02/2025 00:38:44] Validating: 1U5T-14G421-BBL_1723560114000.TAR.GZ 
[20/02/2025 00:38:51] Copied: 1U5T-14G421-BBL_1723560114000.TAR.GZ 
[20/02/2025 00:38:51] Checking Existing File: 1U5T-14G421-BCL_1723600422000.TAR.GZ 
[20/02/2025 00:38:51] Copying: 1U5T-14G421-BCL_1723600422000.TAR.GZ 
[20/02/2025 00:40:47] Validating: 1U5T-14G421-BCL_1723600422000.TAR.GZ 
[20/02/2025 00:41:10] Copied: 1U5T-14G421-BCL_1723600422000.TAR.GZ 
[20/02/2025 00:41:10] Checking Existing File: 1U5T-14G421-BDL_1723600797000.TAR.GZ 
[20/02/2025 00:41:10] Copying: 1U5T-14G421-BDL_1723600797000.TAR.GZ 
[20/02/2025 00:42:24] Validating: 1U5T-14G421-BDL_1723600797000.TAR.GZ 
[20/02/2025 00:42:38] Copied: 1U5T-14G421-BDL_1723600797000.TAR.GZ 
[20/02/2025 00:42:38] Checking Existing File: 1U5T-14G421-BEL_1723601194000.TAR.GZ 
[20/02/2025 00:42:38] Copying: 1U5T-14G421-BEL_1723601194000.TAR.GZ 
[20/02/2025 00:44:36] Validating: 1U5T-14G421-BEL_1723601194000.TAR.GZ 
[20/02/2025 00:44:58] Copied: 1U5T-14G421-BEL_1723601194000.TAR.GZ 
[20/02/2025 00:44:58] Checking Existing File: 1U5T-14G421-BFL_1723601450000.TAR.GZ 
[20/02/2025 00:44:58] Copying: 1U5T-14G421-BFL_1723601450000.TAR.GZ 
[20/02/2025 00:47:45] Validating: 1U5T-14G421-BFL_1723601450000.TAR.GZ 
[20/02/2025 00:48:17] Copied: 1U5T-14G421-BFL_1723601450000.TAR.GZ 
[20/02/2025 00:48:17] Checking Existing File: 1U5T-14G421-BGL_1723602075000.TAR.GZ 
[20/02/2025 00:48:17] Copying: 1U5T-14G421-BGL_1723602075000.TAR.GZ 
[20/02/2025 00:50:35] Validating: 1U5T-14G421-BGL_1723602075000.TAR.GZ 
[20/02/2025 00:51:01] Copied: 1U5T-14G421-BGL_1723602075000.TAR.GZ 
[20/02/2025 00:51:01] Checking Existing File: 1U5T-14G421-BHL_1723602658000.TAR.GZ 
[20/02/2025 00:51:01] Copying: 1U5T-14G421-BHL_1723602658000.TAR.GZ 
[20/02/2025 00:53:55] Validating: 1U5T-14G421-BHL_1723602658000.TAR.GZ 
[20/02/2025 00:54:27] Copied: 1U5T-14G421-BHL_1723602658000.TAR.GZ 
[20/02/2025 00:54:27] Checking Existing File: 1U5T-14G421-BJL_1723602553000.TAR.GZ 
[20/02/2025 00:54:27] Copying: 1U5T-14G421-BJL_1723602553000.TAR.GZ 
[20/02/2025 00:54:30] Validating: 1U5T-14G421-BJL_1723602553000.TAR.GZ 
[20/02/2025 00:54:30] Copied: 1U5T-14G421-BJL_1723602553000.TAR.GZ 
[20/02/2025 00:54:30] Checking Existing File: 4U5T-14G422-BAL_1723663279000.TAR.GZ 
[20/02/2025 00:54:30] Copying: 4U5T-14G422-BAL_1723663279000.TAR.GZ 
[20/02/2025 00:57:06] Validating: 4U5T-14G422-BAL_1723663279000.TAR.GZ 
[20/02/2025 00:57:37] Copied: 4U5T-14G422-BAL_1723663279000.TAR.GZ 
[20/02/2025 00:57:37] Checking Existing File: 4U5T-14G422-BBL_1723666341000.TAR.GZ 
[20/02/2025 00:57:37] Copying: 4U5T-14G422-BBL_1723666341000.TAR.GZ 
[20/02/2025 01:00:07] Validating: 4U5T-14G422-BBL_1723666341000.TAR.GZ 
[20/02/2025 01:00:36] Copied: 4U5T-14G422-BBL_1723666341000.TAR.GZ 
[20/02/2025 01:00:36] Checking Existing File: 4U5T-14G422-BCL_1723745202000.TAR.GZ 
[20/02/2025 01:00:36] Copying: 4U5T-14G422-BCL_1723745202000.TAR.GZ 
[20/02/2025 01:02:27] Validating: 4U5T-14G422-BCL_1723745202000.TAR.GZ 
[20/02/2025 01:02:49] Copied: 4U5T-14G422-BCL_1723745202000.TAR.GZ 
[20/02/2025 01:02:49] Checking Existing File: 4U5T-14G422-BDL_1723746662000.TAR.GZ 
[20/02/2025 01:02:49] Copying: 4U5T-14G422-BDL_1723746662000.TAR.GZ 
[20/02/2025 01:05:02] Validating: 4U5T-14G422-BDL_1723746662000.TAR.GZ 
[20/02/2025 01:05:28] Copied: 4U5T-14G422-BDL_1723746662000.TAR.GZ 
[20/02/2025 01:05:28] Checking Existing File: 1U5T-14G424-BN_1727700842000.TAR.GZ 
[20/02/2025 01:05:28] Copying: 1U5T-14G424-BN_1727700842000.TAR.GZ 
[20/02/2025 01:05:29] Validating: 1U5T-14G424-BN_1727700842000.TAR.GZ 
[20/02/2025 01:05:29] Copied: 1U5T-14G424-BN_1727700842000.TAR.GZ 
[20/02/2025 01:05:29] Generating reformat.lst
[20/02/2025 01:05:29] Generating autoinstall.lst
[20/02/2025 01:05:29] ALL FILES DOWNLOADED AND COPIED TO THE USB DRIVE SUCCESSFULLY! 

It’s not a Forscan issue, it is just a warning and if you have done what they told you to do than you can just ignore it.

1 Like

Oh I see, thank you. By saying “doing what they told you” you mean following the installation instruction of sync 3.4 carefully? Or is there something else to do?

No, I was talking about Forscan and if you have done what they wanted than you could ignore the message.

Hey there, thank you again for replying! Sorry maybe I explained myself badly:

Before updating to Sync 3.4, I used Forscan and was able to access the APIM module without any warning. This means that Forscan is setup properly and I have no issue with it.
After updating Sync 3.4 I have this warning when I access the APIM module only: no warning is prompted when I access other modules.

In my original question, I was asking if there is a particular procedure to follow after updating from sync 3.0 to sync 3.4 in order to make forscan recognize this update, thus to make the warning disappear

Try deleting your current Forscan profile and start over

Sadly I already tried that :frowning:

How does this happen? Where is the Sync module version stored? If the version is read when Forscan reads the module, deleting the profile should solve the issue, bad this is not the case

UPDATE: after searching through the forscan forum, I found this post
https://forscan.org/forum/viewtopic.php?f=5&t=25475

It seems that if a module did not come out with the car from the factory, forscan doesn’t have it in its database. Since my mk8 does not officially support sync 3.4 but only 3.0, I suppose that’s why I get that warning. The strange thing is: how is it possible that I am the first posing this question haha? If my findings are correct, everyone which has updated their sync module to an unsupported version via cyanlabs, would get this message.

In any case, I will try to find a forscan profile of a car with sync 3.4 officially supported (if you are reading this and you have it, kindly provide it? :pray:), and check if the warning disappears. I will update this post in case someone has the same issue :slight_smile:

I have had forscan detect my sync 4 unit that I retrofitted to my mk8 fiesta st, so I don’t fully believe that forum post.

1 Like

Forscan also detects TCU’s in models that never came with them and before TCU’s existed in Ford models.

1 Like

I see, thank you both. So when you retrofitted the sync 4 module forscan recognized it right away and didn’t give you the warning I get after updating to sync 3.4? (Sorry for the direct ping, @CyanLabs)

If so, do you have any suggestions on what to try? I’m thinking trying with another computer, maybe even if I delete the profile stored where I had sync 3.0, forscan still uses some info about the old profile, I really have no clue

tbh I’m not sure what i did, it was years ago and I barely use forscan since I have ucds, I wouldn’t take what I’ve said as fact, that said other modules do seem to het detected even when not factory options though

That warning is normal. It appeared for me on Sync 1 and it has appeared for me on Sync 3.0 and 3.4.

It’s just warning you to check that Forscan has detected the correct APIM version. if it’s correct, hit Yes and carry on with what you were doing.

Thank you for replying! The problem is that I think Forscan has not detected the correct APIM version in my case, since it says it expected to find Sync 3, while I updated to 3.4

Did you have also the version mismatch warning? i.e., after updating sync 1 to sync 3, did forscan prompt the warning where it says it expected to find sync1 as APIM version?

ForScan isn’t interested in the software version, Sync 3.4 is still Sync 3 as far as ForScan is concerned.

It’s just an informational warning - it’s telling you that if Forscan pops up Sync 1 on that box but you have Sync 3 then you shouldn’t use the configuration and programming features. If it pops up Sync 3 and you have a Sync 3 APIM then everything is fine.

Thank you, now it’s perfectly clear. Yeah I mean I was just being extra careful, I thought that sync 3.4 is practically the same as 3.0 and forscan was just warning me for a version mismatch, but I asked here to be sure

Just as a curiosity, you said you upgraded from sync 1 to sync 3.4 if I understood correctly: in that case the warning isn’t like a REAL warning? how did you handle using forscan in that case?

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.