Microphone Not Working After APIM Replacement + Upgrade

FiSTofFury · 8 May 2024 02:08

UPDATE 2: It wasn’t the APIM or the 3.4 upgrade. Solution marked below.

UPDATE 1: My original non-nav APIM on 3.4 does not have a working mic either. Does not seem to be related to the APIM swap, but rather the 3.4 upgrade.

Hello! I jumped the gun and posted a success story in the Discussions forum, but I’m running into an annoying problem.

I had a non-nav Sync 3 APIM on my 2016 Fiesta ST that I changed out for a OEM Sync 3 nav APIM from another 2016 Fiesta + Fakra GPS antenna. I upgraded the new-to-me nav APIM from 1.0.15139 to 3.4.23188 via Syn3. I know that the microphone was working for calls on my original APIM, but now Voice Commands are hit & miss, and during phone calls over Bluetooth/Carplay, the other person doesn’t hear me.

I master reset and was able to change the radio station via voice command, but later when I tried while driving, voice commands wouldn’t hear me even with the windows up.

There are some threads about changing EQ or ringtone but none of that worked. The voice command itself is a bit hit or miss and the mic doesn’t work at all on bluetooth/carplay phone calls. Siri hears me while on CP, but I’m not sure if that’s through my phone or the car’s microphone.

I am pasting the install log from the creation of the Syn3 Updater flash drive.
I also attached the install log and interrogator log below.

Any ideas? I saw something about restoring my ACM asbuilt? I still have my old APIM but looking for some direction before I rip everything apart again.

Thank you!

Interrogator Log:
InterrogatorLog.xml (10.8 KB)
Install Log:
Install Log.txt (12.5 KB)

SYNC Region: NA

Navigation Variant: Nav

Manufacturer Year: Pre MY20

Install Type: OEM Replacement

Old SYNC Version: 1.0.15139

New SYNC Version: 3.4.23188

Do you have a error message, if so what is it?
N/A

Update Method: CyanLabs Syn3 Updater

Syn3 Updater Version: 2.12.5.0

Syn3 Updater Documentation Read: yes

Syn3 Updater Log File

CYANLABS - SYN3 UPDATER - V2.12.5.0
Branch: Stable
Operating System: Microsoft Windows 10 Home (2009)

PREVIOUS CONFIGURATION
Version: 1.0.15139
Region: NA
Navigation: True
Install Mode: Auto-Detect (reformat)
Install Mode Overridden: False
My20 Protection Enabled: Auto-Detect

DESTINATION DETAILS
Mode: Drive
Model: SanDisk Ultra Fit USB Device
Size: 57.8GB
FileSystem: exFAT
Partition Type: MBR

REFORMAT.LST
VOICE=5U5T-14G391-CS_1660783942000.TAR.GZ
GRACENOTES=4U5T-14G423-CC_1615429225000.TAR.GZ
APPS=NU5T-14G381-AD_1689364279000.TAR.GZ
MAP=4U5T-14G421-CJF_1682462901000.TAR.GZ
MAP=4U5T-14G421-CHF_1682462859000.TAR.GZ
MAP=4U5T-14G421-CFF_1682462169000.TAR.GZ
MAP=4U5T-14G421-CGF_1682462518000.TAR.GZ
MAP=4U5T-14G421-CEF_1682461522000.TAR.GZ
MAP=4U5T-14G421-CDF_1682463264000.TAR.GZ
MAP=4U5T-14G421-CCF_1682461368000.TAR.GZ
MAP=4U5T-14G421-CBF_1682461295000.TAR.GZ
MAP=4U5T-14G421-CAF_1682461100000.TAR.GZ
MAP_LICENSE=4U5T-14G424-CF_1682464057000.TAR.GZ
VOICE_NAV=4U5T-14G422-CAM_1682463335000.TAR.GZ
VOICE_NAV=4U5T-14G422-CBM_1682463581000.TAR.GZ
VOICE_NAV=4U5T-14G422-CCM_1682463747000.TAR.GZ


AUTOINSTALL.LST
; CyanLabs Syn3Updater 2.12.5.0 Stable - reformat  Mode - Sync 3.4.23188 NA

[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 (18)
1u5t-14g386-cb.tar.gz (8.5MB)
PU5T-14G386-BB_1690840002000.TAR.GZ (3.2KB)
5U5T-14G391-CS_1660783942000.TAR.GZ (385.5MB)
4U5T-14G423-CC_1615429225000.TAR.GZ (564.2MB)
NU5T-14G381-AD_1689364279000.TAR.GZ (869.8MB)
4U5T-14G421-CJF_1682462901000.TAR.GZ (693.3MB)
4U5T-14G421-CHF_1682462859000.TAR.GZ (1006.4MB)
4U5T-14G421-CFF_1682462169000.TAR.GZ (1.1GB)
4U5T-14G421-CGF_1682462518000.TAR.GZ (1.1GB)
4U5T-14G421-CEF_1682461522000.TAR.GZ (1.1GB)
4U5T-14G421-CDF_1682463264000.TAR.GZ (1.3GB)
4U5T-14G421-CCF_1682461368000.TAR.GZ (1.1GB)
4U5T-14G421-CBF_1682461295000.TAR.GZ (1.1GB)
4U5T-14G421-CAF_1682461100000.TAR.GZ (1002.3MB)
4U5T-14G424-CF_1682464057000.TAR.GZ (1.6KB)
4U5T-14G422-CAM_1682463335000.TAR.GZ (1.2GB)
4U5T-14G422-CBM_1682463581000.TAR.GZ (784.2MB)
4U5T-14G422-CCM_1682463747000.TAR.GZ (536MB)

LOG
[5/7/2024 2:22:48 PM] Selected Region: NA - Release: Sync 3.4.23188 - Map Version: 2.22 (2022) - NA (06 2022) (Updated Voice) 
[5/7/2024 2:22:48 PM] Install Mode: Auto-Detect (reformat) Forced: False 
[5/7/2024 2:22:48 PM] MY20 Protection: Auto-Detect 
[5/7/2024 2:22:48 PM] Formatting USB drive
[5/7/2024 2:22:48 PM] Re-creating partition table as MBR and formatting as ExFat on selected USB drive
[5/7/2024 2:22:57 PM] Checking Existing File: 1u5t-14g386-cb.tar.gz 
[5/7/2024 2:22:57 PM] Validated: 1u5t-14g386-cb.tar.gz (Skipping Download) 
[5/7/2024 2:22:57 PM] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
[5/7/2024 2:22:57 PM] Validated: PU5T-14G386-BB_1690840002000.TAR.GZ (Skipping Download) 
[5/7/2024 2:22:57 PM] Checking Existing File: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[5/7/2024 2:23:00 PM] Validated: 5U5T-14G391-CS_1660783942000.TAR.GZ (Skipping Download) 
[5/7/2024 2:23:00 PM] Checking Existing File: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[5/7/2024 2:23:03 PM] Validated: 4U5T-14G423-CC_1615429225000.TAR.GZ (Skipping Download) 
[5/7/2024 2:23:03 PM] Checking Existing File: NU5T-14G381-AD_1689364279000.TAR.GZ 
[5/7/2024 2:23:07 PM] Validated: NU5T-14G381-AD_1689364279000.TAR.GZ (Skipping Download) 
[5/7/2024 2:23:07 PM] Checking Existing File: 4U5T-14G421-CJF_1682462901000.TAR.GZ 
[5/7/2024 2:23:07 PM] Downloading: 4U5T-14G421-CJF_1682462901000.TAR.GZ
[5/7/2024 2:23:36 PM] Validating: 4U5T-14G421-CJF_1682462901000.TAR.GZ 
[5/7/2024 2:23:39 PM] Downloaded: 4U5T-14G421-CJF_1682462901000.TAR.GZ 
[5/7/2024 2:23:39 PM] Checking Existing File: 4U5T-14G421-CHF_1682462859000.TAR.GZ 
[5/7/2024 2:23:39 PM] Downloading: 4U5T-14G421-CHF_1682462859000.TAR.GZ
[5/7/2024 2:24:39 PM] Validating: 4U5T-14G421-CHF_1682462859000.TAR.GZ 
[5/7/2024 2:24:43 PM] Downloaded: 4U5T-14G421-CHF_1682462859000.TAR.GZ 
[5/7/2024 2:24:43 PM] Checking Existing File: 4U5T-14G421-CFF_1682462169000.TAR.GZ 
[5/7/2024 2:24:43 PM] Downloading: 4U5T-14G421-CFF_1682462169000.TAR.GZ
[5/7/2024 2:25:31 PM] Validating: 4U5T-14G421-CFF_1682462169000.TAR.GZ 
[5/7/2024 2:25:35 PM] Downloaded: 4U5T-14G421-CFF_1682462169000.TAR.GZ 
[5/7/2024 2:25:35 PM] Checking Existing File: 4U5T-14G421-CGF_1682462518000.TAR.GZ 
[5/7/2024 2:25:35 PM] Downloading: 4U5T-14G421-CGF_1682462518000.TAR.GZ
[5/7/2024 2:26:22 PM] Validating: 4U5T-14G421-CGF_1682462518000.TAR.GZ 
[5/7/2024 2:26:27 PM] Downloaded: 4U5T-14G421-CGF_1682462518000.TAR.GZ 
[5/7/2024 2:26:27 PM] Checking Existing File: 4U5T-14G421-CEF_1682461522000.TAR.GZ 
[5/7/2024 2:26:27 PM] Downloading: 4U5T-14G421-CEF_1682461522000.TAR.GZ
[5/7/2024 2:27:10 PM] Validating: 4U5T-14G421-CEF_1682461522000.TAR.GZ 
[5/7/2024 2:27:14 PM] Downloaded: 4U5T-14G421-CEF_1682461522000.TAR.GZ 
[5/7/2024 2:27:14 PM] Checking Existing File: 4U5T-14G421-CDF_1682463264000.TAR.GZ 
[5/7/2024 2:27:14 PM] Downloading: 4U5T-14G421-CDF_1682463264000.TAR.GZ
[5/7/2024 2:28:12 PM] Validating: 4U5T-14G421-CDF_1682463264000.TAR.GZ 
[5/7/2024 2:28:17 PM] Downloaded: 4U5T-14G421-CDF_1682463264000.TAR.GZ 
[5/7/2024 2:28:17 PM] Checking Existing File: 4U5T-14G421-CCF_1682461368000.TAR.GZ 
[5/7/2024 2:28:17 PM] Downloading: 4U5T-14G421-CCF_1682461368000.TAR.GZ
[5/7/2024 2:29:17 PM] Validating: 4U5T-14G421-CCF_1682461368000.TAR.GZ 
[5/7/2024 2:29:21 PM] Downloaded: 4U5T-14G421-CCF_1682461368000.TAR.GZ 
[5/7/2024 2:29:21 PM] Checking Existing File: 4U5T-14G421-CBF_1682461295000.TAR.GZ 
[5/7/2024 2:29:21 PM] Downloading: 4U5T-14G421-CBF_1682461295000.TAR.GZ
[5/7/2024 2:30:08 PM] Validating: 4U5T-14G421-CBF_1682461295000.TAR.GZ 
[5/7/2024 2:30:13 PM] Downloaded: 4U5T-14G421-CBF_1682461295000.TAR.GZ 
[5/7/2024 2:30:13 PM] Checking Existing File: 4U5T-14G421-CAF_1682461100000.TAR.GZ 
[5/7/2024 2:30:13 PM] Downloading: 4U5T-14G421-CAF_1682461100000.TAR.GZ
[5/7/2024 2:30:51 PM] Validating: 4U5T-14G421-CAF_1682461100000.TAR.GZ 
[5/7/2024 2:30:55 PM] Downloaded: 4U5T-14G421-CAF_1682461100000.TAR.GZ 
[5/7/2024 2:30:55 PM] Checking Existing File: 4U5T-14G424-CF_1682464057000.TAR.GZ 
[5/7/2024 2:30:55 PM] Downloading: 4U5T-14G424-CF_1682464057000.TAR.GZ
[5/7/2024 2:30:56 PM] Validating: 4U5T-14G424-CF_1682464057000.TAR.GZ 
[5/7/2024 2:30:56 PM] Downloaded: 4U5T-14G424-CF_1682464057000.TAR.GZ 
[5/7/2024 2:30:56 PM] Checking Existing File: 4U5T-14G422-CAM_1682463335000.TAR.GZ 
[5/7/2024 2:30:56 PM] Downloading: 4U5T-14G422-CAM_1682463335000.TAR.GZ
[5/7/2024 2:31:47 PM] Validating: 4U5T-14G422-CAM_1682463335000.TAR.GZ 
[5/7/2024 2:31:52 PM] Downloaded: 4U5T-14G422-CAM_1682463335000.TAR.GZ 
[5/7/2024 2:31:52 PM] Checking Existing File: 4U5T-14G422-CBM_1682463581000.TAR.GZ 
[5/7/2024 2:31:52 PM] Downloading: 4U5T-14G422-CBM_1682463581000.TAR.GZ
[5/7/2024 2:32:23 PM] Validating: 4U5T-14G422-CBM_1682463581000.TAR.GZ 
[5/7/2024 2:32:26 PM] Downloaded: 4U5T-14G422-CBM_1682463581000.TAR.GZ 
[5/7/2024 2:32:26 PM] Checking Existing File: 4U5T-14G422-CCM_1682463747000.TAR.GZ 
[5/7/2024 2:32:26 PM] Downloading: 4U5T-14G422-CCM_1682463747000.TAR.GZ
[5/7/2024 2:32:49 PM] Validating: 4U5T-14G422-CCM_1682463747000.TAR.GZ 
[5/7/2024 2:32:52 PM] Downloaded: 4U5T-14G422-CCM_1682463747000.TAR.GZ 
[5/7/2024 2:32:52 PM] Preparing USB drive
[5/7/2024 2:32:52 PM] Checking Existing File: 1u5t-14g386-cb.tar.gz 
[5/7/2024 2:32:52 PM] Copying: 1u5t-14g386-cb.tar.gz 
[5/7/2024 2:32:52 PM] Validating: 1u5t-14g386-cb.tar.gz 
[5/7/2024 2:32:53 PM] Copied: 1u5t-14g386-cb.tar.gz 
[5/7/2024 2:32:53 PM] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
[5/7/2024 2:32:53 PM] Copying: PU5T-14G386-BB_1690840002000.TAR.GZ 
[5/7/2024 2:32:53 PM] Validating: PU5T-14G386-BB_1690840002000.TAR.GZ 
[5/7/2024 2:32:53 PM] Copied: PU5T-14G386-BB_1690840002000.TAR.GZ 
[5/7/2024 2:32:53 PM] Checking Existing File: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[5/7/2024 2:32:53 PM] Copying: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[5/7/2024 2:33:19 PM] Validating: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[5/7/2024 2:33:22 PM] Copied: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[5/7/2024 2:33:22 PM] Checking Existing File: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[5/7/2024 2:33:22 PM] Copying: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[5/7/2024 2:33:58 PM] Validating: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[5/7/2024 2:34:03 PM] Copied: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[5/7/2024 2:34:03 PM] Checking Existing File: NU5T-14G381-AD_1689364279000.TAR.GZ 
[5/7/2024 2:34:03 PM] Copying: NU5T-14G381-AD_1689364279000.TAR.GZ 
[5/7/2024 2:34:59 PM] Validating: NU5T-14G381-AD_1689364279000.TAR.GZ 
[5/7/2024 2:35:07 PM] Copied: NU5T-14G381-AD_1689364279000.TAR.GZ 
[5/7/2024 2:35:07 PM] Checking Existing File: 4U5T-14G421-CJF_1682462901000.TAR.GZ 
[5/7/2024 2:35:07 PM] Copying: 4U5T-14G421-CJF_1682462901000.TAR.GZ 
[5/7/2024 2:35:50 PM] Validating: 4U5T-14G421-CJF_1682462901000.TAR.GZ 
[5/7/2024 2:35:57 PM] Copied: 4U5T-14G421-CJF_1682462901000.TAR.GZ 
[5/7/2024 2:35:57 PM] Checking Existing File: 4U5T-14G421-CHF_1682462859000.TAR.GZ 
[5/7/2024 2:35:57 PM] Copying: 4U5T-14G421-CHF_1682462859000.TAR.GZ 
[5/7/2024 2:37:00 PM] Validating: 4U5T-14G421-CHF_1682462859000.TAR.GZ 
[5/7/2024 2:37:09 PM] Copied: 4U5T-14G421-CHF_1682462859000.TAR.GZ 
[5/7/2024 2:37:09 PM] Checking Existing File: 4U5T-14G421-CFF_1682462169000.TAR.GZ 
[5/7/2024 2:37:09 PM] Copying: 4U5T-14G421-CFF_1682462169000.TAR.GZ 
[5/7/2024 2:38:20 PM] Validating: 4U5T-14G421-CFF_1682462169000.TAR.GZ 
[5/7/2024 2:38:31 PM] Copied: 4U5T-14G421-CFF_1682462169000.TAR.GZ 
[5/7/2024 2:38:31 PM] Checking Existing File: 4U5T-14G421-CGF_1682462518000.TAR.GZ 
[5/7/2024 2:38:31 PM] Copying: 4U5T-14G421-CGF_1682462518000.TAR.GZ 
[5/7/2024 2:39:44 PM] Validating: 4U5T-14G421-CGF_1682462518000.TAR.GZ 
[5/7/2024 2:39:55 PM] Copied: 4U5T-14G421-CGF_1682462518000.TAR.GZ 
[5/7/2024 2:39:55 PM] Checking Existing File: 4U5T-14G421-CEF_1682461522000.TAR.GZ 
[5/7/2024 2:39:55 PM] Copying: 4U5T-14G421-CEF_1682461522000.TAR.GZ 
[5/7/2024 2:41:07 PM] Validating: 4U5T-14G421-CEF_1682461522000.TAR.GZ 
[5/7/2024 2:41:17 PM] Copied: 4U5T-14G421-CEF_1682461522000.TAR.GZ 
[5/7/2024 2:41:17 PM] Checking Existing File: 4U5T-14G421-CDF_1682463264000.TAR.GZ 
[5/7/2024 2:41:17 PM] Copying: 4U5T-14G421-CDF_1682463264000.TAR.GZ 
[5/7/2024 2:42:42 PM] Validating: 4U5T-14G421-CDF_1682463264000.TAR.GZ 
[5/7/2024 2:42:54 PM] Copied: 4U5T-14G421-CDF_1682463264000.TAR.GZ 
[5/7/2024 2:42:54 PM] Checking Existing File: 4U5T-14G421-CCF_1682461368000.TAR.GZ 
[5/7/2024 2:42:54 PM] Copying: 4U5T-14G421-CCF_1682461368000.TAR.GZ 
[5/7/2024 2:44:08 PM] Validating: 4U5T-14G421-CCF_1682461368000.TAR.GZ 
[5/7/2024 2:44:18 PM] Copied: 4U5T-14G421-CCF_1682461368000.TAR.GZ 
[5/7/2024 2:44:18 PM] Checking Existing File: 4U5T-14G421-CBF_1682461295000.TAR.GZ 
[5/7/2024 2:44:18 PM] Copying: 4U5T-14G421-CBF_1682461295000.TAR.GZ 
[5/7/2024 2:45:29 PM] Validating: 4U5T-14G421-CBF_1682461295000.TAR.GZ 
[5/7/2024 2:45:39 PM] Copied: 4U5T-14G421-CBF_1682461295000.TAR.GZ 
[5/7/2024 2:45:39 PM] Checking Existing File: 4U5T-14G421-CAF_1682461100000.TAR.GZ 
[5/7/2024 2:45:39 PM] Copying: 4U5T-14G421-CAF_1682461100000.TAR.GZ 
[5/7/2024 2:46:43 PM] Validating: 4U5T-14G421-CAF_1682461100000.TAR.GZ 
[5/7/2024 2:46:52 PM] Copied: 4U5T-14G421-CAF_1682461100000.TAR.GZ 
[5/7/2024 2:46:52 PM] Checking Existing File: 4U5T-14G424-CF_1682464057000.TAR.GZ 
[5/7/2024 2:46:52 PM] Copying: 4U5T-14G424-CF_1682464057000.TAR.GZ 
[5/7/2024 2:46:52 PM] Validating: 4U5T-14G424-CF_1682464057000.TAR.GZ 
[5/7/2024 2:46:52 PM] Copied: 4U5T-14G424-CF_1682464057000.TAR.GZ 
[5/7/2024 2:46:53 PM] Checking Existing File: 4U5T-14G422-CAM_1682463335000.TAR.GZ 
[5/7/2024 2:46:53 PM] Copying: 4U5T-14G422-CAM_1682463335000.TAR.GZ 
[5/7/2024 2:48:12 PM] Validating: 4U5T-14G422-CAM_1682463335000.TAR.GZ 
[5/7/2024 2:48:23 PM] Copied: 4U5T-14G422-CAM_1682463335000.TAR.GZ 
[5/7/2024 2:48:23 PM] Checking Existing File: 4U5T-14G422-CBM_1682463581000.TAR.GZ 
[5/7/2024 2:48:23 PM] Copying: 4U5T-14G422-CBM_1682463581000.TAR.GZ 
[5/7/2024 2:49:12 PM] Validating: 4U5T-14G422-CBM_1682463581000.TAR.GZ 
[5/7/2024 2:49:19 PM] Copied: 4U5T-14G422-CBM_1682463581000.TAR.GZ 
[5/7/2024 2:49:19 PM] Checking Existing File: 4U5T-14G422-CCM_1682463747000.TAR.GZ 
[5/7/2024 2:49:19 PM] Copying: 4U5T-14G422-CCM_1682463747000.TAR.GZ 
[5/7/2024 2:49:52 PM] Validating: 4U5T-14G422-CCM_1682463747000.TAR.GZ 
[5/7/2024 2:49:57 PM] Copied: 4U5T-14G422-CCM_1682463747000.TAR.GZ 
[5/7/2024 2:49:57 PM] Generating reformat.lst
[5/7/2024 2:49:58 PM] Generating autoinstall.lst
[5/7/2024 2:49:58 PM] ALL FILES DOWNLOADED AND COPIED TO THE USB DRIVE SUCCESSFULLY!

FiSTofFury · 8 May 2024 02:44

After I updated to 3.4 on the nav APIM, I restored my APIM asbuilt file from my non-nav APIM but changed two values: enabled nav, and set the ST splash screen.

I had a backup of my original non-nav 3.4 APIM asbuilt and took one of the new nav APIM asbuilt before I made any changes. There are some differences but I am not sure if it’s related… perhaps the CGEA one in 7D0-01-02?

Original non-nav APIM: 7D0-01-01: 2130-6505-00
New Nav APIM (prior to any changes): 7D0-01-01: 2130-6404-00

The middle block, 2nd digit (4 indicates car has a key, 5 indicates push button, so that’s fine, mine’s a push button).
Middle block, 4th digit (4 indicates HD radio disabled, 5 indicates HD radio enabled – this seemed to work anyway).

Original non-nav APIM: 7D0-01-02: 0298-1708-00
New Nav APIM (prior to any changes): 7D0-01-02: 0288-1708-0A

First block, 3rd digit seems to indicate 9 for stickshift, 8 for automatic. Again that’s okay, my car is a manual.
Last block, 2nd digit indicates 0 on my setup “CGEA 1.2 or C1MCA, Heated Windshield Disabled, Rear Climate Manual w/o Air Flow Mode” and A indicates “CGEA 1.3, Heated Windshield Disabled, Rear Climate Automatic”.
Could the CGEA version be the problem?
If I want to change it to CGEA 1.3 to match what the new APIM had, but retain my old climate setting, I need to change that to “8”: CGEA 1.3, Heated Windshield Disabled, Rear Climate Manual w/o Air Flow Mode

Original non-nav APIM: 7D0-02-01: 5553-0B06-0A
New Nav APIM (prior to any changes): 7D0-02-01: 5553-0101-09

Middle block, 2nd digit “B” is the ST splash screen and “1” is the original Ford splash screen.
Middle block, 3rd & 4th digit = 06 is a hatchback (which mine is), and 01 is a sedan
Last block, 2nd digit: A on my car indicates = B299 Strategy Available, DAFVC Not Available, Hill Start (B-Car) On, ESP (B-Car) Off and 0 on the new APIM = B299 Strategy Not Available, DAFVC Not Available, Hill Start (B-Car) Off, ESP (B-Car) Off

Original non-nav APIM: 7D0-02-02: E224-0000-00
New Nav APIM (prior to any changes): 7D0-02-02: E204-0000-00

First block, 3rd digit. “2” indicates CPL Disabled, PBT Mechanical, ESC Enabled, Rain Sensor Disabled while “0” indicates CPL Disabled, PBT Mechanical, ESC Disabled, Rain Sensor Disabled

Lastly…
Original non-nav APIM: 7D0-07-03: 0004-3052-00
New Nav APIM (prior to any changes): 7D0-07-03: 0004-3053-00

Middle block, 4th digit… I can’t find any info on that in the CyanLabs AsBuilt DB.

bill32399 · 8 May 2024 02:54

There is a chance you Mic wires are in the wrong sport for the APIM now. As you can see below they used 2 different sets of Pins for the microphone in this year. 5 & 6 and then 12 & 13. Maybe try swapping these and see if you can get it to work.

FiSTofFury · 8 May 2024 03:34

Thank you so much for the quick response. What’s weird is the mic briefly worked with voice commands, then just stopped working again. I will compare the pins on both APIMs and try it out this weekend.

Do you think the CGEA 1.2 vs 1.3 value in the asbuilt would affect this? Or should I not worry about the APIM asbuilt

bill32399 · 8 May 2024 03:36

Yea you can’t use the AB your Sync 2 system had for the new Sync 3 system. I’ll check the wire diagrams for Sync3 but I think they are the same. If it briefly worked it might not be the wiring.

Diagrams are the same for a Sync 3 system…

FiSTofFury · 8 May 2024 03:40

My original APIM was Sync 3 as well, just non-nav. I’m aware of the Sync 2 to 3 AsBuilt process but doesn’t apply here.

Original Sync 3 APIM (non-nav, 2016 Fiesta ST): G1BT-14G370-BM (MFG date 09/06/2016)
New Sync 3 APIM (nav, 2016 Fiesta (unsure of model)): g1bt-14g370-cl (MFG date 01/27/2016)

bill32399 · 8 May 2024 03:43

I thought that’s all you did when you upgraded. I think you changed your message while I was typing. If it briefly worked than I doubt it’s the wiring. You could check regardless though if you want. Maybe post you AB here and we can take a look at it.

I vaguely remember an issue like this and you had to downgrade to get it to work and then upgrade after that. Hardware is my specialty not the software part.

FiSTofFury · 8 May 2024 03:46

RE: downgrading - I hope it’s not to 2.2 or 3.0 since that’s not possible from what I’ve read. On the initial 1.0.15139 of the Nav unit, I tried manually updating to 2.2/3.0 and it would just sit, so I used Syn3 and jumped straight to 3.4, since Syn3 didn’t give the option to 3.0.

The AB differences are highlighted in my comment above, but here’s the copies:

My -BM non-nav APIM, upgraded to 3.4: Original 3.4 APIM with ST Logo 05042024.abt (349 Bytes)
The -CL nav APIM, upgraded to 3.4, but otherwise no changes made:
eBay Nav 3.4 Original No Changes 05072024.abt (349 Bytes)
And here’s what I have on the car right now – I applied my -BM asbuilt from the first bullet point after upgrading to 3.4, and I changed a value to enable navigation:
ebay Nav 3.4 with merged changes (ST & Nav) - newest 05072024.abt (349 Bytes)

Thanks for taking the time to help me out, Bill. Here’s hoping it’s fixable!

bill32399 · 8 May 2024 03:48

Yea you can not go down to 3.2 or 3.0. You can only go down to 3.3.19052. I think you can go a couple versions down but well wait for someone who knows more about that.

FiSTofFury · 8 May 2024 04:00

And on the note of changing the pins, I will compare the connector in my car with the one that came attached to the -CL navigation APIM. Rather than guesswork it’ll be easy/obvious to see if I need to move pins. They had sent it with the connector plugged in but they cut it off down to about 6 inches

bill32399 · 8 May 2024 04:23

That makes sense and should work.

FiSTofFury · 8 May 2024 04:24

I have some updates… both original non-nav APIM connector and the new nav APIM connector have pins in 12+13, not 5+6.

I popped in my original non-nav APIM and lo and behold… voice commands + mic does NOT work either (even after a master reset)! I think the last time it worked was on 3.0.x prior to my 3.4 upgrade.

So that leaves two Sync 3 APIMs on 3.4.23188 without a working microphone. It appears to be a software issue at this point so hopefully someone has a suggestion on that end.

@F150Chief suggested a few years ago to downgrade (Sync 3.4 Microphone Fix - #2 by F150Chief)

Is 3.4 19101 still recommended or should I try something else?

bill32399 · 8 May 2024 05:03

There is another thread about this same thing occurring to another person on here that has an F150.

Yes 3.4.19101 is fine. You could go down to that and see if it solves the problem. If it does you could try going back up and see what happens.

FiSTofFury · 8 May 2024 06:06

Man… OK, so downgraded from 3.4.23188 → 3.4.19101 via Syn3. Took ~10 min, did a master reset, connected my bluetooth and it didn’t work. THEN I performed a super sophisticated troubleshooting method – percussive maintenance – on the microphone overhead. I gently hit/aggressively tapped it a few times and the MICROPHONE WORKED! Connected CarPlay and that worked.

Decided to re-upgrade to 3.4.23188 and it still worked! Voice command, bluetooth, carplay, all of the above.

I’ve had the car for a week so who knows if this happened before, and I’m at a loss of words, but it worked.

Thank you @bill32399 for taking the time to troubleshoot this with me. I am going to mark this RESOLVED and now can only laugh at the build quality of a Fiesta. This never happened with my Explorer, not that it was so much better

warlock12118 · 8 May 2024 12:25

Actually really simple solution here.
You’ve got a bad mic or intermittent open on a wire.
Pulling the APIM opened the circuit and the pins either didn’t seat correctly or the mic assembly didn’t power back up afterwards.

Hence the reason it didn’t work on both the old and the new APIM.
Hitting the overhead console and getting it back would lead me down the bad mic assembly path.

bill32399 · 8 May 2024 14:02

Glad to hear you solved it!

system · 10 May 2024 14:03

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