Sync 3 update 3.0 to 3.4, Bezel Diagnostics APIM Calibration Information Not For My VIN

A little background information to explain where and why I have this issue.
I retired in July 2022 and so lost the use of company vehicle, so in October 2022 I purchased a 2017 Ford Focus Titanium X 1.5TDCi with Sync 3 installed, as far as I am aware all parts are original.
The only issue I had was that the Navigation fault pop up was a regular occurrence, sometime it reset itself after key cycle, I found the most convenient way to reset through the Test Settings (Remove Navigation Fault) in the hidden menu (Bezel Diagnostics). To try and correct this fault I downloaded the latest software from the Ford website and installed into the vehicle.
Software Version 2.2 Build 16280 to Version 3.0 Build 20204
Gracenote Version to Version 1.1.11127
Maps Version EU4.15 Version F10.
Following this update I have only had 2 or 3 Navigation fault errors in the last 4 months. Then one day in late February, the Nav fault was continuous, the reset lasted a matter of minutes until the pop up Nav Fault occurred again. I opened the hidden menu and went into the Test Settings Screen to check satellite positions and they took a long time to load up, I did not have as many satellites as normal and there were no ID tags attached to the satellites that did show up. In my frustration I moved all the slide switches across to the on position on the test setting screen, then when I tired to slide them back to the off position, two of the parameters were locked in the on position (Enable GNNS sensor logging and Enable HIP Logging ).
When I checked the satellite positions again there were none, in addition the F10 map version was missing from the about sync screen. The home page on Sync 3 showed Navigation fault, when cleared the loading maps message and the blue loading circle appeared, but the maps never loaded, the blue circle just continued spinning. When the Nav button was pressed nothing happened, the Nav screen did not load. I have obviously done something I should not have and so booked the car into Ford for diagnostic (£70.00), unfortunately (or perhaps fortunately) the earliest slot was April 11. It was time to trawl the internet to see if I could find a fix myself.
I downloaded Forscan (2 month free trial) version 2.3.51, and found a fault code B119F (GPS antenna open circuit) on the APIM module. There were no other faults. Roof mounted antenna issue seems quite common problem on various internet threads so I bought an antenna from Amazon, unplugged the OEM antenna and plugged in the new antenna (both antennas were Fakra female plugs) and mounted the new antenna under the roof with the supplied magnet. The fault on Forscan remained, the sat nav still wasn’t working there were no satellites on the Test Settings page. Time to trawl the internet again.
Various threads indicated the locked enabled GNSS and HIP sensor logging was the issue and upgrading to 3.4 would resolve the issue. The 3.4 update is not available for my vehicle on the Ford web site so I bit the bullet and used Cyanlabls Syn3 Updater.
After reading the documents and watching the video on the Syn3 home page I downloaded 3.4 Build 22110 and Maps F11 to usb using the Syn3 updater software on 07 March. This took some 2 hours. The usb was loaded into the car and downloaded successfully with out errors. I carried out a factory reset after removing the usb. I now have my sat nav back and I also have radio logos but no calm screen. The only minor issue I have found is that when the ignition is turned on the nav error appears, but disappears after about 10seconds and the maps are loaded, the radio logos also take the same time to load. I have checked the satellites on the Test Settings page and I have about 15 to 20, the Amazon antenna is still in use. I was very impressed and have cancelled my diagnostic appointment at the dealers.
Forscan however still shows the antenna fault B119F in the APIM, I cleared the fault but it comes straight back.

What really surprised me is that while my VIN is displayed on the about Sync screen and the Bezel Diagnostics APIM Part Numbers screen, the APIM Calibration in the Bezel Diagnostics is not for my VIN WF05XXXXXXXXX1752, but for VIN WF0AXXXXXXXXXX4717. For example my car is diesel with manual hand brake and ignition on off switch, the bezel diagnostics show gasoline, electric hand brake and key ignition. This second VIN does not show up in Forscan and my APIM settings are for my VIN.

How can I resolve this issue?

SYNC Region: EU

Navigation Variant: Nav

Manufacturer Year: Pre MY20

Install Type: OEM

Old SYNC Version: 3.0.20204

New SYNC Version: 3.4.22110

Do you have a error message, if so what is it?
Only error message is through Forscan, B119F

Update Method: CyanLabs Syn3 Updater

Syn3 Updater Version: (Stable)

Syn3 Updater Documentation Read: yes

Syn3 Updater Log File

Branch: Stable
Operating System: Microsoft Windows 11 Home (2009)

Version: 3.0.20204
Region: EU
Navigation: True
Install Mode: Auto-Detect (reformat)
Install Mode Overridden: False
My20 Protection Enabled: Auto-Detect

Mode: Drive
Model: SanDisk Cruzer Glide USB Device
Size: 28.7GB
FileSystem: FAT32
Partition Type: MBR


; CyanLabs Syn3Updater Stable - reformat  Mode - Sync 3.4.22110 EU

Item1 = REFORMAT TOOL  - 1u5t-14g386-cb.tar.gz
Open1 = SyncMyRide\1u5t-14g386-cb.tar.gz
Options = AutoInstall

FILES (19)
1u5t-14g386-cb.tar.gz (8.5MB)
4U5T-14G423-AC_1615425645000.TAR.GZ (689MB)
5U5T-14G381-EZ_1652218180000.TAR.GZ (869.8MB)
1U5T-14G658-AH_1644006443000.TAR.GZ (57.5MB)
5U5T-14G391-AS_1644006548000.TAR.GZ (1.5GB)
1U5T-14G421-BAJ_1644010894000.TAR.GZ (2.3GB)
1U5T-14G421-BBJ_1644008981000.TAR.GZ (478.9MB)
1U5T-14G421-BCJ_1644009116000.TAR.GZ (1.7GB)
1U5T-14G421-BDJ_1644009729000.TAR.GZ (1.1GB)
1U5T-14G421-BEJ_1644010041000.TAR.GZ (1.6GB)
1U5T-14G421-BFJ_1644010644000.TAR.GZ (2.4GB)
1U5T-14G421-BGJ_1644011311000.TAR.GZ (2GB)
1U5T-14G421-BHJ_1644011371000.TAR.GZ (2.7GB)
1U5T-14G421-BJJ_1644011473000.TAR.GZ (24.1MB)
4U5T-14G422-BAG_1644245686000.TAR.GZ (2.3GB)
4U5T-14G422-BDG_1644012081000.TAR.GZ (2GB)
4U5T-14G422-BBG_1644011700000.TAR.GZ (2.1GB)
4U5T-14G422-BCG_1644011850000.TAR.GZ (1.6GB)
1U5T-14G424-BL_1646159765000.TAR.GZ (1.7KB)

[3/7/2023 3:38:44 PM] Selected Region: EU - Release: Sync 3.4.22110 - Map Version: F11 (2021) - EU (05 2022) 
[3/7/2023 3:38:44 PM] Install Mode: Auto-Detect (reformat) Forced: False 
[3/7/2023 3:38:44 PM] MY20 Protection: Auto-Detect 
[3/7/2023 3:38:44 PM] Formatting USB drive
[3/7/2023 3:38:44 PM] Re-creating partition table as MBR and formatting as ExFat on selected USB drive
[3/7/2023 3:38:53 PM] Checking Existing File: 1u5t-14g386-cb.tar.gz 
[3/7/2023 3:38:53 PM] Downloading: 1u5t-14g386-cb.tar.gz
[3/7/2023 3:38:56 PM] Validating: 1u5t-14g386-cb.tar.gz 
[3/7/2023 3:38:56 PM] Downloaded: 1u5t-14g386-cb.tar.gz 
[3/7/2023 3:38:56 PM] Checking Existing File: 4U5T-14G423-AC_1615425645000.TAR.GZ 
[3/7/2023 3:38:56 PM] Downloading: 4U5T-14G423-AC_1615425645000.TAR.GZ
[3/7/2023 3:40:30 PM] Validating: 4U5T-14G423-AC_1615425645000.TAR.GZ 
[3/7/2023 3:40:33 PM] Downloaded: 4U5T-14G423-AC_1615425645000.TAR.GZ 
[3/7/2023 3:40:33 PM] Checking Existing File: 5U5T-14G381-EZ_1652218180000.TAR.GZ 
[3/7/2023 3:40:33 PM] Downloading: 5U5T-14G381-EZ_1652218180000.TAR.GZ
[3/7/2023 3:42:31 PM] Validating: 5U5T-14G381-EZ_1652218180000.TAR.GZ 
[3/7/2023 3:42:35 PM] Downloaded: 5U5T-14G381-EZ_1652218180000.TAR.GZ 
[3/7/2023 3:42:35 PM] Checking Existing File: 1U5T-14G658-AH_1644006443000.TAR.GZ 
[3/7/2023 3:42:35 PM] Downloading: 1U5T-14G658-AH_1644006443000.TAR.GZ
[3/7/2023 3:42:44 PM] Validating: 1U5T-14G658-AH_1644006443000.TAR.GZ 
[3/7/2023 3:42:44 PM] Downloaded: 1U5T-14G658-AH_1644006443000.TAR.GZ 
[3/7/2023 3:42:44 PM] Checking Existing File: 5U5T-14G391-AS_1644006548000.TAR.GZ 
[3/7/2023 3:42:44 PM] Downloading: 5U5T-14G391-AS_1644006548000.TAR.GZ
[3/7/2023 3:46:16 PM] Validating: 5U5T-14G391-AS_1644006548000.TAR.GZ 
[3/7/2023 3:46:22 PM] Downloaded: 5U5T-14G391-AS_1644006548000.TAR.GZ 
[3/7/2023 3:46:22 PM] Checking Existing File: 1U5T-14G421-BAJ_1644010894000.TAR.GZ 
[3/7/2023 3:46:22 PM] Downloading: 1U5T-14G421-BAJ_1644010894000.TAR.GZ
[3/7/2023 3:51:35 PM] Validating: 1U5T-14G421-BAJ_1644010894000.TAR.GZ 
[3/7/2023 3:51:43 PM] Downloaded: 1U5T-14G421-BAJ_1644010894000.TAR.GZ 
[3/7/2023 3:51:43 PM] Checking Existing File: 1U5T-14G421-BBJ_1644008981000.TAR.GZ 
[3/7/2023 3:51:43 PM] Downloading: 1U5T-14G421-BBJ_1644008981000.TAR.GZ
[3/7/2023 3:52:48 PM] Validating: 1U5T-14G421-BBJ_1644008981000.TAR.GZ 
[3/7/2023 3:52:50 PM] Downloaded: 1U5T-14G421-BBJ_1644008981000.TAR.GZ 
[3/7/2023 3:52:50 PM] Checking Existing File: 1U5T-14G421-BCJ_1644009116000.TAR.GZ 
[3/7/2023 3:52:50 PM] Downloading: 1U5T-14G421-BCJ_1644009116000.TAR.GZ
[3/7/2023 3:56:44 PM] Validating: 1U5T-14G421-BCJ_1644009116000.TAR.GZ 
[3/7/2023 3:56:52 PM] Downloaded: 1U5T-14G421-BCJ_1644009116000.TAR.GZ 
[3/7/2023 3:56:52 PM] Checking Existing File: 1U5T-14G421-BDJ_1644009729000.TAR.GZ 
[3/7/2023 3:56:52 PM] Downloading: 1U5T-14G421-BDJ_1644009729000.TAR.GZ
[3/7/2023 3:59:22 PM] Validating: 1U5T-14G421-BDJ_1644009729000.TAR.GZ 
[3/7/2023 3:59:26 PM] Downloaded: 1U5T-14G421-BDJ_1644009729000.TAR.GZ 
[3/7/2023 3:59:26 PM] Checking Existing File: 1U5T-14G421-BEJ_1644010041000.TAR.GZ 
[3/7/2023 3:59:26 PM] Downloading: 1U5T-14G421-BEJ_1644010041000.TAR.GZ
[3/7/2023 4:03:13 PM] Validating: 1U5T-14G421-BEJ_1644010041000.TAR.GZ 
[3/7/2023 4:03:19 PM] Downloaded: 1U5T-14G421-BEJ_1644010041000.TAR.GZ 
[3/7/2023 4:03:19 PM] Checking Existing File: 1U5T-14G421-BFJ_1644010644000.TAR.GZ 
[3/7/2023 4:03:19 PM] Downloading: 1U5T-14G421-BFJ_1644010644000.TAR.GZ
[3/7/2023 4:08:57 PM] Validating: 1U5T-14G421-BFJ_1644010644000.TAR.GZ 
[3/7/2023 4:09:06 PM] Downloaded: 1U5T-14G421-BFJ_1644010644000.TAR.GZ 
[3/7/2023 4:09:06 PM] Checking Existing File: 1U5T-14G421-BGJ_1644011311000.TAR.GZ 
[3/7/2023 4:09:06 PM] Downloading: 1U5T-14G421-BGJ_1644011311000.TAR.GZ
[3/7/2023 4:13:42 PM] Validating: 1U5T-14G421-BGJ_1644011311000.TAR.GZ 
[3/7/2023 4:13:50 PM] Downloaded: 1U5T-14G421-BGJ_1644011311000.TAR.GZ 
[3/7/2023 4:13:50 PM] Checking Existing File: 1U5T-14G421-BHJ_1644011371000.TAR.GZ 
[3/7/2023 4:13:50 PM] Downloading: 1U5T-14G421-BHJ_1644011371000.TAR.GZ
[3/7/2023 4:20:02 PM] Validating: 1U5T-14G421-BHJ_1644011371000.TAR.GZ 
[3/7/2023 4:20:12 PM] Downloaded: 1U5T-14G421-BHJ_1644011371000.TAR.GZ 
[3/7/2023 4:20:12 PM] Checking Existing File: 1U5T-14G421-BJJ_1644011473000.TAR.GZ 
[3/7/2023 4:20:12 PM] Downloading: 1U5T-14G421-BJJ_1644011473000.TAR.GZ
[3/7/2023 4:20:15 PM] Validating: 1U5T-14G421-BJJ_1644011473000.TAR.GZ 
[3/7/2023 4:20:15 PM] Downloaded: 1U5T-14G421-BJJ_1644011473000.TAR.GZ 
[3/7/2023 4:20:15 PM] Checking Existing File: 4U5T-14G422-BAG_1644245686000.TAR.GZ 
[3/7/2023 4:20:15 PM] Downloading: 4U5T-14G422-BAG_1644245686000.TAR.GZ
[3/7/2023 4:25:29 PM] Validating: 4U5T-14G422-BAG_1644245686000.TAR.GZ 
[3/7/2023 4:25:38 PM] Downloaded: 4U5T-14G422-BAG_1644245686000.TAR.GZ 
[3/7/2023 4:25:38 PM] Checking Existing File: 4U5T-14G422-BDG_1644012081000.TAR.GZ 
[3/7/2023 4:25:38 PM] Downloading: 4U5T-14G422-BDG_1644012081000.TAR.GZ
[3/7/2023 4:30:11 PM] Validating: 4U5T-14G422-BDG_1644012081000.TAR.GZ 
[3/7/2023 4:30:17 PM] Downloaded: 4U5T-14G422-BDG_1644012081000.TAR.GZ 
[3/7/2023 4:30:17 PM] Checking Existing File: 4U5T-14G422-BBG_1644011700000.TAR.GZ 
[3/7/2023 4:30:17 PM] Downloading: 4U5T-14G422-BBG_1644011700000.TAR.GZ
[3/7/2023 4:35:16 PM] Validating: 4U5T-14G422-BBG_1644011700000.TAR.GZ 
[3/7/2023 4:35:23 PM] Downloaded: 4U5T-14G422-BBG_1644011700000.TAR.GZ 
[3/7/2023 4:35:23 PM] Checking Existing File: 4U5T-14G422-BCG_1644011850000.TAR.GZ 
[3/7/2023 4:35:23 PM] Downloading: 4U5T-14G422-BCG_1644011850000.TAR.GZ
[3/7/2023 4:39:08 PM] Validating: 4U5T-14G422-BCG_1644011850000.TAR.GZ 
[3/7/2023 4:39:14 PM] Downloaded: 4U5T-14G422-BCG_1644011850000.TAR.GZ 
[3/7/2023 4:39:14 PM] Checking Existing File: 1U5T-14G424-BL_1646159765000.TAR.GZ 
[3/7/2023 4:39:14 PM] Downloading: 1U5T-14G424-BL_1646159765000.TAR.GZ
[3/7/2023 4:39:14 PM] Validating: 1U5T-14G424-BL_1646159765000.TAR.GZ 
[3/7/2023 4:39:14 PM] Downloaded: 1U5T-14G424-BL_1646159765000.TAR.GZ 
[3/7/2023 4:39:15 PM] Preparing USB drive
[3/7/2023 4:39:15 PM] Checking Existing File: 1u5t-14g386-cb.tar.gz 
[3/7/2023 4:39:15 PM] Copying: 1u5t-14g386-cb.tar.gz 
[3/7/2023 4:39:16 PM] Validating: 1u5t-14g386-cb.tar.gz 
[3/7/2023 4:39:16 PM] Copied: 1u5t-14g386-cb.tar.gz 
[3/7/2023 4:39:16 PM] Checking Existing File: 4U5T-14G423-AC_1615425645000.TAR.GZ 
[3/7/2023 4:39:16 PM] Copying: 4U5T-14G423-AC_1615425645000.TAR.GZ 
[3/7/2023 4:40:24 PM] Validating: 4U5T-14G423-AC_1615425645000.TAR.GZ 
[3/7/2023 4:40:56 PM] Copied: 4U5T-14G423-AC_1615425645000.TAR.GZ 
[3/7/2023 4:40:56 PM] Checking Existing File: 5U5T-14G381-EZ_1652218180000.TAR.GZ 
[3/7/2023 4:40:56 PM] Copying: 5U5T-14G381-EZ_1652218180000.TAR.GZ 
[3/7/2023 4:42:26 PM] Validating: 5U5T-14G381-EZ_1652218180000.TAR.GZ 
[3/7/2023 4:43:08 PM] Copied: 5U5T-14G381-EZ_1652218180000.TAR.GZ 
[3/7/2023 4:43:08 PM] Checking Existing File: 1U5T-14G658-AH_1644006443000.TAR.GZ 
[3/7/2023 4:43:08 PM] Copying: 1U5T-14G658-AH_1644006443000.TAR.GZ 
[3/7/2023 4:43:14 PM] Validating: 1U5T-14G658-AH_1644006443000.TAR.GZ 
[3/7/2023 4:43:16 PM] Copied: 1U5T-14G658-AH_1644006443000.TAR.GZ 
[3/7/2023 4:43:16 PM] Checking Existing File: 5U5T-14G391-AS_1644006548000.TAR.GZ 
[3/7/2023 4:43:16 PM] Copying: 5U5T-14G391-AS_1644006548000.TAR.GZ 
[3/7/2023 4:45:55 PM] Validating: 5U5T-14G391-AS_1644006548000.TAR.GZ 
[3/7/2023 4:47:12 PM] Copied: 5U5T-14G391-AS_1644006548000.TAR.GZ 
[3/7/2023 4:47:12 PM] Checking Existing File: 1U5T-14G421-BAJ_1644010894000.TAR.GZ 
[3/7/2023 4:47:12 PM] Copying: 1U5T-14G421-BAJ_1644010894000.TAR.GZ 
[3/7/2023 4:51:05 PM] Validating: 1U5T-14G421-BAJ_1644010894000.TAR.GZ 
[3/7/2023 4:52:58 PM] Copied: 1U5T-14G421-BAJ_1644010894000.TAR.GZ 
[3/7/2023 4:52:58 PM] Checking Existing File: 1U5T-14G421-BBJ_1644008981000.TAR.GZ 
[3/7/2023 4:52:58 PM] Copying: 1U5T-14G421-BBJ_1644008981000.TAR.GZ 
[3/7/2023 4:53:46 PM] Validating: 1U5T-14G421-BBJ_1644008981000.TAR.GZ 
[3/7/2023 4:54:09 PM] Copied: 1U5T-14G421-BBJ_1644008981000.TAR.GZ 
[3/7/2023 4:54:09 PM] Checking Existing File: 1U5T-14G421-BCJ_1644009116000.TAR.GZ 
[3/7/2023 4:54:09 PM] Copying: 1U5T-14G421-BCJ_1644009116000.TAR.GZ 
[3/7/2023 4:57:04 PM] Validating: 1U5T-14G421-BCJ_1644009116000.TAR.GZ 
[3/7/2023 4:58:29 PM] Copied: 1U5T-14G421-BCJ_1644009116000.TAR.GZ 
[3/7/2023 4:58:29 PM] Checking Existing File: 1U5T-14G421-BDJ_1644009729000.TAR.GZ 
[3/7/2023 4:58:29 PM] Copying: 1U5T-14G421-BDJ_1644009729000.TAR.GZ 
[3/7/2023 5:00:22 PM] Validating: 1U5T-14G421-BDJ_1644009729000.TAR.GZ 
[3/7/2023 5:01:15 PM] Copied: 1U5T-14G421-BDJ_1644009729000.TAR.GZ 
[3/7/2023 5:01:15 PM] Checking Existing File: 1U5T-14G421-BEJ_1644010041000.TAR.GZ 
[3/7/2023 5:01:15 PM] Copying: 1U5T-14G421-BEJ_1644010041000.TAR.GZ 
[3/7/2023 5:04:06 PM] Validating: 1U5T-14G421-BEJ_1644010041000.TAR.GZ 
[3/7/2023 5:05:27 PM] Copied: 1U5T-14G421-BEJ_1644010041000.TAR.GZ 
[3/7/2023 5:05:27 PM] Checking Existing File: 1U5T-14G421-BFJ_1644010644000.TAR.GZ 
[3/7/2023 5:05:27 PM] Copying: 1U5T-14G421-BFJ_1644010644000.TAR.GZ 
[3/7/2023 5:09:37 PM] Validating: 1U5T-14G421-BFJ_1644010644000.TAR.GZ 
[3/7/2023 5:11:34 PM] Copied: 1U5T-14G421-BFJ_1644010644000.TAR.GZ 
[3/7/2023 5:11:34 PM] Checking Existing File: 1U5T-14G421-BGJ_1644011311000.TAR.GZ 
[3/7/2023 5:11:34 PM] Copying: 1U5T-14G421-BGJ_1644011311000.TAR.GZ 
[3/7/2023 5:14:58 PM] Validating: 1U5T-14G421-BGJ_1644011311000.TAR.GZ 
[3/7/2023 5:16:36 PM] Copied: 1U5T-14G421-BGJ_1644011311000.TAR.GZ 
[3/7/2023 5:16:36 PM] Checking Existing File: 1U5T-14G421-BHJ_1644011371000.TAR.GZ 
[3/7/2023 5:16:36 PM] Copying: 1U5T-14G421-BHJ_1644011371000.TAR.GZ 
[3/7/2023 5:21:11 PM] Validating: 1U5T-14G421-BHJ_1644011371000.TAR.GZ 
[3/7/2023 5:23:19 PM] Copied: 1U5T-14G421-BHJ_1644011371000.TAR.GZ 
[3/7/2023 5:23:19 PM] Checking Existing File: 1U5T-14G421-BJJ_1644011473000.TAR.GZ 
[3/7/2023 5:23:19 PM] Copying: 1U5T-14G421-BJJ_1644011473000.TAR.GZ 
[3/7/2023 5:23:22 PM] Validating: 1U5T-14G421-BJJ_1644011473000.TAR.GZ 
[3/7/2023 5:23:23 PM] Copied: 1U5T-14G421-BJJ_1644011473000.TAR.GZ 
[3/7/2023 5:23:23 PM] Checking Existing File: 4U5T-14G422-BAG_1644245686000.TAR.GZ 
[3/7/2023 5:23:23 PM] Copying: 4U5T-14G422-BAG_1644245686000.TAR.GZ 
[3/7/2023 5:27:17 PM] Validating: 4U5T-14G422-BAG_1644245686000.TAR.GZ 
[3/7/2023 5:29:10 PM] Copied: 4U5T-14G422-BAG_1644245686000.TAR.GZ 
[3/7/2023 5:29:10 PM] Checking Existing File: 4U5T-14G422-BDG_1644012081000.TAR.GZ 
[3/7/2023 5:29:10 PM] Copying: 4U5T-14G422-BDG_1644012081000.TAR.GZ 
[3/7/2023 5:32:33 PM] Validating: 4U5T-14G422-BDG_1644012081000.TAR.GZ 
[3/7/2023 5:34:09 PM] Copied: 4U5T-14G422-BDG_1644012081000.TAR.GZ 
[3/7/2023 5:34:09 PM] Checking Existing File: 4U5T-14G422-BBG_1644011700000.TAR.GZ 
[3/7/2023 5:34:09 PM] Copying: 4U5T-14G422-BBG_1644011700000.TAR.GZ 
[3/7/2023 5:37:53 PM] Validating: 4U5T-14G422-BBG_1644011700000.TAR.GZ 
[3/7/2023 5:39:42 PM] Copied: 4U5T-14G422-BBG_1644011700000.TAR.GZ 
[3/7/2023 5:39:42 PM] Checking Existing File: 4U5T-14G422-BCG_1644011850000.TAR.GZ 
[3/7/2023 5:39:42 PM] Copying: 4U5T-14G422-BCG_1644011850000.TAR.GZ 
[3/7/2023 5:42:32 PM] Validating: 4U5T-14G422-BCG_1644011850000.TAR.GZ 
[3/7/2023 5:43:55 PM] Copied: 4U5T-14G422-BCG_1644011850000.TAR.GZ 
[3/7/2023 5:43:55 PM] Checking Existing File: 1U5T-14G424-BL_1646159765000.TAR.GZ 
[3/7/2023 5:43:55 PM] Copying: 1U5T-14G424-BL_1646159765000.TAR.GZ 
[3/7/2023 5:43:55 PM] Validating: 1U5T-14G424-BL_1646159765000.TAR.GZ 
[3/7/2023 5:43:55 PM] Copied: 1U5T-14G424-BL_1646159765000.TAR.GZ 
[3/7/2023 5:43:55 PM] Generating reformat.lst
[3/7/2023 5:43:55 PM] Generating autoinstall.lst

What are the Possible Causes of the Code B119F Ford?

  • Faulty GPS Antenna
  • GPS Antenna harness is open or shorted
  • GPS Antenna circuit poor electrical connection
  • Faulty Audio Control Module (ACM)

Thanks for that but I think the antenna fault is a red herring, since changing the aerial and updating to 3.4 the sat nav is working well, so there is clearly no fault. I dont think I can clear the error in Forscan as I havent changed anything in Forscan as I dont know what to change. Forscan still shows Focus as built data when I plugged in after update, the fault was still there.
The Bezel APIM calibration screen was correct for my diesel Focus as built before I updated sync to 3.4. After update the Bezel APIM calibration info is for a petrol Kuga, so something went wrong with the update.
I am quite happy with the update apart from the incorrect Bezel APIM calibration info and want to know how I can change it back from the Kuga info to my current Focus info either using Forscan or Cyanlabs. I am sure once this is done the antenna fault will clear.

The Bezel Diagnostics/APIM/Configuration Status info is the default calibration used in Sync 3.4. The settings are the base configuration for the asbuilt, and may not reflect the true asbuilt configuration for your vehicle. However, the VIN should populate correctly along with the firmware values in Bezel Diagnostics/APIM/Part Numbers.

Also, check the Location Diagnostics pages in the test menu. You should see info like this:

If you have values that are blank or zero, other than vehicle speed, the antennae are weak and should be replaced.

Hello F150 Chief,
Many thanks for your reply. I guess you noticed I am a total novice with Sync.
I can confirm that my VIN has populated in About Sync screen, Bezel Diagnostics APIM / Part Numbers. The Location diagnostics in Test Settings also look ok to me, but 12seconds for first fix may be a little high.

I have also attached 2 xml log files loaded onto the Syn 3 Interrogator log screen and copied to Notebook file. The first is after the Sat Nav failed in late February, Sync 3.0 20204, this shows the APIM model and the as built configuration (without the check sums). I have checked the as built against the Ford as built downloaded from motorcraft web site and they appear to be the same. The log file opens ok in a browser.
Syn3 Updater Interrogator Log After Nav Failure 25 Feb 23.txt (859 Bytes).

The second xml is after updating to 3.4 22110, but this does not show the APIM model and indicates it is unknown. The as built data is shown as BLANK foe all six blocks. When I try to open the log file in a browser I get an error.
Syn3 Updater Interrogator Log After Update 3.4. 21110.txt (1.2 KB)

Even though Forscan is still saying I have an antenna fault (B119F Open Circuit) I do not think I have an antenna issue as the sat Nav is working ok, even though I get an error message when I switch on the ignition it clears after about 10seconds (first fix?) and then functions ok.

I dont know why the xml file will not open in a browser or why the APIM model is unknown and the as built is BLANK in all 6 blocks in the xml file when opened with Syn Updater.
I understand from your reply that the info in the Bezel Diagnostics / APIM / Calibration screen is the default for 3.4, but why does it show blank in the xml file?
Is it not possible somehow to use my as built data to populate the Apim Calibration screen?

12 seconds is high for the initial lock. Also, the jamming active level is low. You want this level to be in the mid -70’s for better performance. This is a function of the antenna performance in a clear sky environment. You can test this by finding a parking lot area that is larger, clear area and park there with the engine running. Check this level. If it does not improve then your antenna and cabling for the antenna are suspect, most likely. Note: the number of satellites does not improve the reception in most cases as the receiver will only use the number of satellite positions necessary to establish a fix.

Something you can try is to change the gain for the antenna on the APIM. (This has nothing to do with the Sync application.) Roof mount is the lowest gain, the others have a higher gain value.
Go to: GPS Mount Type (GPSMT)
7D0-03-01 x*xx xxxx xx–
Change ‘0’ to ‘1’.
0 = Roof Mount
1 = Instrument Panel (IP) Mount (Non Heated Windscreen)
2 = Instrument Panel (IP) Mount (Heated Windscreen)
3 = Windshield Mount (Non-Heated Windscreen)
4 = Windshield Mount (Heated Windscreen)

You replaced the antenna? What is the model number? OEM?
You say it is a mag mount? OEM antennas are not, so this is another type which is probably the wrong antenna receiver type for the GNSS receiver in the APIM. (Open vs closed type antenna feed.) If this is an open receiver type antenna, the fault will remain, but the antenna will work, though it is not the correct antenna for the application.

Hello F150 Chief,
The antenna I bought from Amazon attached, I bought this based on a few threads on the Ford Focus forum. It is not OEM, it does not say if it is open or closed feed.

LNA Gain 27dB without cable.
I will try your suggestions sometime this week (jamming level and change gain) and let you know.

mounted the new antenna under the roof with the supplied magnet.

This would not be desirable. This antenna needs to be mounted right side up. You could mount it inside the dash just under the dash cover, but inside the roof structure would not be recommended.

This should be a closed receiver antenna, looking at the specs.

Hello F150 Chief,
I found a post on the forum where somebody had similar nav fault problems in the US, and they changed their antenna from a ‘cheap’ model to an xtenz1 XT 91835 purchased through Amazon US and it solved the problem. This antenna is not available on Amazon UK, so I had one shipped in from the US which arrived yesterday. I fitted the xtenzi antenna in the same place as the ‘cheap’ antenna, i.e in the roof space, and fixed to the roof using the magnet so it is adjacent to the oem roof mount antenna. I understand that it would be better under the dash, but I do not want to take the car apart as I have no experience in doing this. The nav fault has gone, I ran a DTC with Forscan and cleared the B119F open circuit fault. It did not return, I now have no error codes in the DTC.

My only issue now is that since the upgrade to 3.4 22110, the interrogator log returns ‘unknown APIM model number’ and blank ‘as built’ blocks.
This is reflected in my Bezel Diagnostics APIM / Configuration data being incorrect. I have attached photos and log files earlier in the thread.
I have only seen 2 posts on this issue, the first where the incorrect interrogator file was used prior to updating, and the second was on a hacked / modified APIM.
Do you know why this has happened and is there a solution to this issue?

I’d hazard a guess and say youre going to have to pull that APIM and physicaly check the attatched labels for numbers

I would not know where to start pulling an APIM, the APIM seems to be working ok despite the interrogator log and incorrect information in the Bezel Diagnostics/apim/configuration.
The interrogator log before upgrade showed APIM model number and as built.

I just find it strange the Interrogator cannot find the APIM model number or the as built data since update to 3.4 but the model number is shown in the Bezel Diagnostics / APIM / Part Numbers since updating to 3.4.
It is also shown in the Module configuration in Forscan since updating to 3.4.

So Istill do not know why this is and if their is a solution

Physically remove it from the car, take pictures of all labels, post pictures in here.

I have no experience or tools to remove the APIM to check the labels. I will have to do some investigation on the internet,
What is the purpose of doing this. Do you think the APIM is not HS7T-14G371-FAE (as shown in Forscan, Bezel DiagonosticS/APIM/Part Numbers and on the interrogator log before the upgrade to 3.4 22110)?
If it is not, what is the next step?
If it is, what is the next step?
I also noticed in Bezel Diagnostics/APIM/Software Versions that there is no VMCU version , but in Bezel Diagnostics / APIM / Part Numbers it says VMCU S/W Part Number:GB5T-14G375-AB.
Why is there no version for VMCU and does this have any relevance?
Please refer to all photos in the post for clarification

1 Like

Sorry should be GB5T-14G375-CB for VMCU part number

Can anybody offer some input into this

I would not spend time on this unless you really need to have it. There is not reason to send the xml to Ford as it will never show on the webpage, since your vehicle was never meant to have SYNC 3.4. THIS IS COMMON WITH THE OLDER PER-MY18.5 UNITS UPGRADED TO SYNC 3.2+.

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