Hi i upgraded my Sync 1 to Sync 3 (APIM from Spain EU outsourced from a Fiesta ) this weekend, Unfortunately, some things aren’t working:
Navigation: No voice prompts for turns.
PDC (Park Distance Control): It’s audible, but the lines are missing on the screen.
Auto Park Assist(SAAP): No longer visible on the display.
Steering Wheel Controls: Not working.
Sound and Balance Settings: Don’t save permanently. Treble, bass, and mids always jump back to max on the right, and the same happens with balance and fader settings.
what should i do to get it working ? should i reformat the apim and start from scratch to make it think its from an focus ?
i also have the logfile:
Lets start with what model/year is your vehicle?
What year/trim was the donor?
What build of Sync3 is in this?
What was the part number on the APIM?
Who provided the custom config?
It’s a 2012 Ford Focus MK3 Titanium (Germany, European model).
The APIM is from a 2017 Ford Fiesta from Spain, but it’s a 64 GB version (EU).
SYNC 3, Software Version: 3.3
Build 18201
APIM Part Number: KU5T-14G371-GDE
No one provided me with the configuration. I entered the VIN from a 2018 Ford Focus with identical vehicle features to mine on the Ford website to generate new As-Built data. Then, I uploaded this data to the car using FORScan.
Ok, well first thing is that if the APIM is a K series coming out of a 2017 I’m going to guess based on a quick pass of the EU parts sites the donor had the APIM replaced/upgraded or it came from a 2019 not a 2017.
Since the Focus is really close to a Kuga, I’d start with using a build from either a 2016 Kuga or Focus as with this type of upgrade you want to start with a config from the year closest to your model year, not one closest to the APIM year.
Looks like the first year for Sync3 on a Kuga was 2017.
Found you a VIN from a 2018 Kuga Vignale on a salvage site, I’m not sure why the dealers don’t publish VINs on used car listings in the EU.
WF0AXXWPMAJL45872
This has NAV, according to the listing, so if it doesn’t show, the first thing you’ll want to do is flip 7D0-01-02 xXxx-xxxx-xxxx from 0 to a 2 .
You can actually use the AB as downloaded from Ford and upload it if you want.
Doing this in ForScan ONLY updates the module you’re working in, not the entire car.
You can also use AsBuilt Explorer to compare this VIN vs what you used as a source vs what is currently in the car to find the deltas and then look them up in the CyanLabs APIM DB.
Thank you, I’ll try that this weekend. I have one more question, if that’s okay. Does the Sync system use the voice files stored in the APIM module itself when I use Android Auto, CarPlay, or the internal Ford navigation?
Since the APIM is from a Spanish car, it might be missing the German voice files. Or is the ACM incorrectly configured? I’m asking because I don’t hear any voice guidance when navigating with my Samsung S23 (Android Auto) or my wife’s iPhone 12 Pro Max (CarPlay), both connected directly via cables to the new Chinese hub, which is working well so far.
Music via Bluetooth or radio, as well as CarPlay and Android Auto, works perfectly. Bluetooth calls also work fine.
the NAV voice for the built in NAV doesn’t have anything to do with what comes from Google Maps/Apple Maps. All of those though have their own volume settings, you have to adjust the volume while the voice is speaking.
Google Maps/Apple maps don’t use BT for the voice sounds
if you haven’t done it already bring the Sync3 build up to say 3.4.21265 (assuming your info is right that this is on 3.3 if not bring it to 3.0.23219)
The updater is built around getting you to Sync 3.4.
IF you are on 3.3.x the updater can can raise the level to 3.4.x without reformating.
IF you are on 3.0.x, you would need to hand build a USB to raise the build using a download from the IVSU DB SYNC 3 APIM Software (IVSU) Database - CyanLabs.
IF you want to try and bring it to 3.4.x from 3.0.x this requires reformatting which the updater can do, just make sure you run the interrogator first to make sure the APIM hardware isn’t MY2020 (a 2019 date doesn’t guarantee its not a MY2020)
So, I just revised the APIM AsBuilt a bit. The steering wheel control was disabled there.
I also had to disable DSP, as the APIM kept searching for one, and the sound settings were not adjustable. Now, for example, Sync works, it hears my commands, etc. I can finally hear the navigation voice output as well. Auto-dimming for the display also works. The only thing I couldn’t get to work was displaying the PDC on the screen. Despite changing the following value to (b):
7D0-01-01: #x##-####-#### A = Parking Sensor Display Enabled & Camera Enabled Illumination FNA (USA Default - Camera & Sensor) B = Parking Sensor Display Enabled & Camera Enabled Illumination FoE (UK Default - Camera & Sensor)
And also this value: Enable Flank Guard: 7D0-02-02: #x##-####-#### 3 = Enable Flank Guard Display (Also enables temperature readout in the top bar of Sync 3)
Audio issues if the type of sound config isn’t right are pretty common.
Car has Sony and it gets set for none or B&O, car doesn’t have Sony or B&O, etc.
Its one of the reason why you have to pay attention to exactly what the donor or source had in it.
Switch pack and camera are the same way, I’ve seen more than one person drop a APIM from a 2019/2020 Fusion into a 2013-2018 and not understand why they lost lost the RVC and right wheel controls.
There are a few threads on here where some have gotten PDC to work and others haven’t, on the daughter’s 2014 Escape Ti I was never able to get the PDC working even with a PAM update.
Yeah, it’s really complicated until you get a proper overview!
Is there a way in the AsBuilt settings to make the Sync unit turn on when I open the door? Right now, I always have to press the power button to turn it on, otherwise it stays off. :
No, the only 2 ways that it wakes up are by turning/pressing the ignition to start/accessory or by pressing the button.
If it’s not waking up when you turn on the ignition you’re got something else going on.
As far as I know that’s referring to MY2020 hardware, the part number you listed KU5T-14G371-GDE isn’t MY2020 according to the database.
Save out you current APIM AB and post it so we can get some eyes on it.
