I installed the Sync 3 APIM and Touchscreen from a 2019 Escape Titanium into my daughters 2013 Escape SEL. The old Sync 2 screen/APIM was dead. The new system is great, I added the gps antenna and most of it seems to be working well.
I only noticed a few issues so far:
-the backup camera video is upside down
-when I increase the volume on the steering wheel control, the volume displayed on the screen shows zero however the volume does turn up
-Forscan shows a DTC in the APIM U0198.00-0B Lost Communication with Telematic Control Module ‘A’
Not sure if the backup camera is a setting I can fix in Forscan or ? I have the Extended License and am familiar with using it just not sure what settings to change…
Software screen shows Sync version 3.0 Build 18093
Gracenote version 1.1.1.1139 (NA-0010)
Nav Maps Version NA 1 17
I’ve updated my 2019 F350 to Sync 3.4 with Cyanlabs so I’d like to do the same for the Escape but need some help to get these items resolved before I got to that next step.
Appreciate the help.
SYNC Region: NA
Navigation Variant: Nav
Manufacturer Year: Pre MY20
Install Type: OEM
Old SYNC Version: 3.0
New SYNC Version: 3.0
Do you have a error message, if so what is it?
None
What you’re describing isn’t something that’s going to get fixed by going to 3.4.x, you’ve got an issue with the APIM backend config (2013 SEL was an MFT vehicle, 2019 tI IS Sync 3.0 native).
The sound system is different, hence to vol control issue, you have no TCU in a 2013.
Here’s the AB from a 2014 Ti conversion that I use as a base, at the very least I would expect that you might need to flip the bits for NAV and/or Sony sound system. Change the extension on the file so that its just .abt since we can’t upload those directly.
Thanks Warlock appreciate you sharing this. I loaded it to the APIM and the steering wheel volume buttons now work as expected and the DTC in the APIM U0198 is cleared.
What do you think of the upside down rear camera, is that from a setting in the APIM or something else? I do also have a DTC B115E Camera Module - Bus Signal/Message Failure - Image Processing Module B.
You likely need to replace the camera with a newer model for Sync 3 from a Sync 3 Escape. There are various threads about this on EU Escape/Kuga sites.
As far as moving to Sync 3.4 on a 2013 Escape, I would not advise this as the vehicle is clearly not designed for this, although some folks have had various levels of success. I would advise installing the latest version of Sync 3.0 first as opposed to 3.4 and see if that is what you are looking for. You will need to perform a 2-step installation to go to Sync 3.0.23219, because Ford broke the installation process from previous CarPlay versions to present.
Thanks for the reponse F150Chief, I’ll see if I can source a 2019 Escape rearview camera.
I’ll give the Sync 3.0 update a shot as I see what you are saying with going to 3.4 on a 2013 vehicle. So it sounds like I need to install Sync 2.2.17011 then install Sync 3.0.20204 or 23219. Is there a reason why I should choose 3.0.20204 vs 3.0.23219?
For the Nav maps is there a way to get the current maps or how new could I go with the this update method?
You would almost need to buy an APIM that already had 3.0.2xxxxx already on it with the NA2.24 maps.
The highest 3.4.x build I take a 2013-2015 Escape to is 3.4.21265, after that you start running into compatibility issues that are a little odd. Either way, with Sync3 on the 2013-2015 Escape, expect a “flashing” screen when you go from light to dark to light (like going under a freeway overpass), it’s not a strobe, just a set light/darks, also the power button function for the HVAC will be reversed (screen shows power on, FCIM shows it off), this can be remedied if you jailbreak the APIM and install the FMODS fix
Thanks Warlock, so with my current Nav maps being Version NA 1 17, this would be 2017 can I go any newer with this APIM or is it not worth it for the other issues it will cause?
You’ve got a newer APIM, the problem is going to be finding someone with an APIM on 3.0 that updated the maps to NA2.24.
Personally, if you can live with the random flicker I would run the interrogator just to make sure that you don’t have a MY2020 APIM (this refers to internal hardware, not the date sticker since dealer replacements even on a 2017 could be MY2020 hardware), if the hardware passes, use the updater and bring the unit to 3.4.21265 with the NA224 maps.