Sync Programming Gen 1, Gen 2, Sync 3 (24-7088)

EQUIPMENT, TOOLING AND DEALER INFRASTRUCTURE

The FDRS scan tool (IDS tool if applicable) utilizes a cloud-based architecture. The benefits of such an architecture include the ability for Ford to make real time improvements without the need for dealers to complete a lengthy diagnostic tool update. A cloud-based architecture reduces scan tool installation time by reducing installation package size. A result of this architecture may be that dealers experience extended software download time during module programming events if their dealer infrastructure does not meet Ford recommendations. Poor internet connection or upload/download (megabytes per second [Mbps]) times may contribute to extended software download times during module programming. These minimum dealer infrastructure requirements depend on several factors, including the number of devices connected to the dealers' network.

INTERNET SERVICE MINIMUM BANDWIDTH SPECIFICATIONS

TABLE 1

Number Of Connected Devices	Network Download (Mbps) Speed Requirements	Network Upload (Mbps) Requirements
Less than 20 devices	Greater than 100 Mbps	Greater than 10 Mbps
20-100 devices	Greater than 300 Mbps	Greater than 30 Mbps
Greater than 100 devices	Greater than 500 Mbps	Greater than 50 Mbps

MINIMUM RECOMMENDATIONS - DIAGNOSTIC EQUIPMENT (EXAMPLE - FDRS)

TABLE 2

Item	Minimum Recommendation
Processor	Intel i5 10th Gen or AMD equivalent
System Memory (RAM)	16 Gigabyte (GB)
Hard Disk Drive	Solid State 500 GB
USB Ports	2 USB 3.1. 3.2)
Display	15 inch monitor minimum (1600x900 minimum resolution)
Network Adapter	Wired: Recommend Ethernet-based if available (1 Gigabit); Wireless: 802.11ac, 802.11ax preferred
Operating System	Microsoft Windows 11/latest 10 Windows

APIM PROGRAMMING

Due to decommission of Internet Explorer (IE), all generations of SYNC use FDRS for APIM programming. PTS SYNC programming is no longer supported.

WHEN IS APIM PROGRAMMING NECESSARY?

If the APIM is replaced, a PMI is required. Each replacement module comes with the latest software and upgrades/improvements are provided with each software release. Review applicable SSM, TSB, FSA , or GSB for additional details.

NOTE: Gen2 equipped hybrid vehicle powertrain modules require the latest software in order to download the latest APIM -SYNC software. Some vehicles may have a standard APIM programming option in FDRS only while others have a software update option. The software update option only downloads the latest available software. Once the update completes successfully, the FDRS removes it from the software update list.

APIM PROGRAMMING TIPS USING FDRS PROGRAMMING

Prior to performing any APIM programming, confirm SYNC function by pressing the phone button on the steering wheel or on the instrument panel for especially for every Gen 1 or Gen 2 equipped vehicle. If SYNC does not play "Please Say A Command" through the front speakers, the APIM programming will fail. Follow normal WSM diagnostics.

Refer to WSM . Section 418-01 - General Procedures - Module Programming and/or Section 415-00 - General Procedures - SYNC Module Programming for detailed programming steps.

NOTE: Directions in the WSM for earlier vehicles will advise to use PTS for SYNC programming. All generations of SYNC including Gen 1, Gen 2, and SYNC 3 use FDRS only. Continue with starting a vehicle session using the FDRS scan tool > Go to the Toolbox Tab > Select APIM > Choose the appropriate APIM programming procedure. PMI. Module Replacement Programming, or Standard Programming will be available.

GEN 2 SYNC APPLICATIONS - NORTH AMERICA

The required applications are listed in the table below. Traffic, Direction, & Information (TDI) and Vehicle Health Report (VHR) application with base part number 14D546 is no longer supported for any Gen 2 SYNC equipped vehicle. Global navigation with base part number 14F657 needs to be selected only when vehicles are built with navigation from the factory. Check the window sticker on PTS located under the diagnostic tab.

Make sure to select the appropriate display applications during APIM programming or when programming replacement APIM . If vehicle is a Mustang, Black Label, Raptor, etc, select the correct custom animation application base part number 14F496 instead of the Ford or Lincoln graphics pack. Check the window sticker on PTS located under the diagnostic tab as needed. All Ford and Lincoln vehicles equipped with Gen 2 SYNC can receive the latest v3.10 software version except various BEV Focus.

Ford Vehicles	Lincoln Vehicles
Emergency Assistance application (911 Assist) - base part number 14D546	Emergency Assistance application (911Assist) - base part number 14D546
8 in. Ford graphics pack (only select for a Ford vehicle) -base part number 14F496	8 in. Lincoln graphics pack (only select for a Lincoln vehicle) - base part number 14F496
English (US) language pack (only select if the vehicle is in North America) - base part number 14F497	English (US) language pack (only select if the vehicle is in North America) - base part number 14F497
Global navigation application - base part number 14F657	Global navigation application - base part number 14F657

12-VOLT BATTERY TESTING, CHARGING, MAINTENANCE AND STATE OF CHARGE FOR MODULE PROGRAMMING - BATTERY HEALTH AND VOLTAGE MAINTENANCE

It is recommended to test the 12-volt battery(ies) using approved Rotunda tools prior to a programming event. Ford warranty supports the use of the GRX-3590 and/or DCA-8000 units to perform 12-volt battery testing. The battery(ies) should be fully charged or replaced prior to programming based on the test results from the approved Rotunda tools.
Once battery health is determined using approved Rotunda tools, the battery should be maintained in the 12.9 volt-13.6 volt range for APIM programming. It may be necessary to verify that the voltage is within the desired range using displays on the charger, the battery monitor status at the bottom right corner of the FDRS scan tool or using a digital volt ohm meter (DVOM) connected to the battery.
If equipped, the tool being utilized to maintain the battery should be adjusted to the maximum time limit possible, to prevent charger/maintainer time outs during long flash events. Battery charging should be performed per WSM , Section 414-01 > General Procedures. Always refer to the specific WSM , Section 414-01 for the vehicle in question.

NOTE: Connecting the battery charger negative clamp directly to the battery negative terminal might result in the SOC PID not immediately reflect the improvement from charging. It is not necessary to perform a BMS reset unless the battery is replaced or the battery is disconnected when charged. If the battery is charged with the battery charger negative clamp directly on the battery negative post while the battery is fully connected to the vehicle, it may take hours for the BMS PID to update.

BATTERY STATE OF CHARGE PERCENTAGE (BATT_SOC%)

The BCM calculates the battery SOC using inputs from the BMS, known battery capacity, battery voltage, battery time in service and battery temperature. The battery SOC can be used to verify that the battery will support vehicle current consumption demands during module programming. If the battery is in poor condition and the BCM PID for BATT_SOC reports that SOC is low, off board battery chargers may not be able to maintain the voltage or current demands required of both the battery and the vehicle, leading to programming faults. The FDRS programming applications will call attention to the SOC% requirement. It is generally recommended that the battery SOC % be at 50% or greater to be sure of successful programming.

Performing APIM programming with poor SOC is unacceptable. This applies to PMI , Module Replacement Programming, Standard Programming, and software updating. Poor SOC will induce module failures leading to excessive down time and potential module replacement that can be avoided. Make sure the battery charger is set to maintain 12.9v-13.5v. Confirm the BCM 12v battery SOC percent is greater than 50%. Charging at 15v and higher is excessive and is not a suitable environment. The APIM can go into a self-protection strategy preventing FDRS from programming the module.

NOTE: When charging the 12v, connect possible battery connection to positive battery post and negative battery connection to chassis ground. This makes sure the vehicle BMS sensor detects current flow and the SOC will continue increasing as result. Confirm the BCM 12v battery SOC percent is greater than 50% and perform the BMS reset as needed. Make sure the battery charger is set to maintain 12.9v-13.5v and continue with APIM programming. FDRS example error message during APIM programming with poor SOC present.

"Poor battery condition! Battery Voltage = 11.585v Minimum required = 10.0v Battery Estimated State of Charge = 29% Minimum required = 50% This will most likely cause issues with the USB software update process. Please connect an appropriate battery charger and/or run the BCM-Reset Battery Monitoring System Learned Values application. What would you like to do?"

A hard-wired internet connection is strongly recommended. If a hard-wired internet connection is not available, higher speed Wi-Fi connections are strongly recommended. Using a slower Wi-Fi source will result in programming errors. Recommend using a mobile hotspot as needed when internet provider connection issues are suspected.

Make sure the proper SYNC USB 2.0 A-Male to A-Male cable and SYNC USB 2.0 A-Female to Mini B Female 5-pin adaptor is being used for SYNC Gen1 and Gen2. This is recommended for APIM replacement programming and APIM CIP programming.

USB DRIVE SIZE

For SYNC 3 vehicles, recommended size for the USB drive is 32GB or larger. The USB drive must be formatted to exFAT. Using a 16GB, 8GB, 4GB, or incorrectly formatted flash drive will induce SYNC programming issues potentially resulting in APIM failure.

For Gen 2 SYNC equipped vehicles, recommended size for the USB drive is 16GB. The USB drive must be formatted to FAT32. Using a 4GB, 8GB, or incorrectly formatted flash drive will induce SYNC programming issues potentially resulting in APIM failure.

Gen 1 SYNC does not require a USB drive for APIM programming.

USB FLASH DRIVE FORMATTING

Make sure the USB flash drive being used is formatted correctly. To see the available drives, hold down the Windows icon keyboard key and press the E keyboard key. Right click on the USB flash drive and select Properties. If File System under the General tab is not exFAT, the drive must be formatted.

To format the USB flash drive:

Right click on the USB flash drive
Select Format, select exFAT for the File System
Select Default Allocation Size for the Allocation Unit Size

De-selecting Quick Format is not necessary and will result in a lengthier operation.

NOTE: Do not select or use new technology file system (NTFS). The NTFS formatting option is not supported to program any generation of SYNC.

NOTE: Full format can take up to 15 minutes to complete.

NOTE: If all normal WSM, TSB, SSM and/or GSB diagnostics have been performed, there may be a SYNC server issue preventing SYNC programming. If all above diagnostics, as well as all below diagnostics, have been performed, it may be necessary to contact the Ford TAC to restore the SYNC server information as instructed in the dealer escalation process.

WINDOWS 10/11 (HIDDEN FILES)

In order to access the SYNC cache folder, the hidden files function needs to be enabled:

Use the magnifying glass in the bottom left hand corner of the Windows bar, search for This PC. This will show the This PC application.
Select the application and a new window will open titled This PC. Select the View tab at the top of this window.
Find the Hidden Items check box at the upper right corner of the window and check the box. This will show hidden files.

SYNC CACHE FOLDER

Press the Windows Key located in lower left hand corner of the keyboard. Select This PC (or My Computer) >

C: Drive > Program Data > Ford Motor Company > SYNC > Cache.

SYNC/APIM REBOOT-RESET PROCEDURE (GEN 1 SYNC, GEN 2 SYNC, AND SYNC 3)

The SYNC reset/reboot procedure is performed by pressing and holding the seek forward/seek up button (> >) while pressing and holding the radio power button located on the center display screen. Release both buttons after 3-4 seconds and allow the reset to complete.

FDRS APIM - RESET SYNC MODULE OPTION (AVAILABLE FOR SOME VEHICLES)

Start vehicle session using the FDRS scan tool > Go to the Toolbox Tab > Select APIM > APIM - Reset the SYNC Module.

NOTE: An APIM /SYNC reset/reboot consists of an APIM software cold boot. It may not be necessary to perform a master reset after performing a cold boot if the concern is resolved. The SYNC reset/reboot procedure does not remove or delete any stored user information that occurs when performing an APIM master reset.

REPAIR VALIDATION CODE (RVC) REQUIREMENTS

Refer to the Components Requiring A Repair Validation Code form located on PTS homepage - Technical Assistance dropdown. SYNC 3 and newer generations of SYNC requires an RVC only using the FDRS. An RVC is no longer for required for any Gen 1 or Gen 2 SYNC equipped vehicle. When attempting to manually generate an RVC. a message displays stating "The RVC Assistance Form Is Not Available For This Vehicle And Market. Contacting Technical Assistance is not required."

NOTE: The Guided Routine process has been updated. Make sure to complete entire WSM pinpoint test or guided routine in order to generate the RVC .

UNIVERSAL SYNC 3 USB UPDATER CONCERNS OR ISSUES

Error State/Message	Possible Causes	Solution
Corrupt USB tool detected	Outdated version of the desktop tool being used to update thumb drives Missing file from the universal USB tool	Make sure that the desktop application being used is 1.0.3.1 or higher Update the universal USB thumb drive with the updated desktop application and it will resolve any missing files
USB tool inserted provided no indication of programming on the screen "Indexing" populates instead of "Software Update In Progress" Repeat errors (INST, LIST, VER, PKG, MEM) instead of "Software Update In Progress"	Vehicle in transport mode (verify that the vehicle is out of transport mode) Master reset was performed before USB was inserted without a key cycle Missing file in the universal USB thumb drive Perform the "Clear All Data" Routine using FDRS located under "Reset The APIM" options	Make sure that the desktop application being used is 1.0.3.1 or higher Update the universal USB thumb drive with the updated desktop application and it will resolve any missing files Perform "Clear All Data" Routine per Special Service Message. Retry universal USB updater. Shut the vehicle off, open the door, restart the vehicle, verify that SYNC is fully booted and reinsert the USB thumb drive
Incompatible SYNC version indicated on the screen	Universal USB updater was overwritten by a different process such as FDRS , map update or consumer website update	Make sure that the desktop application being used is 1.0.3.1 or higher Update the universal USB thumb drive with the updated desktop application and it will resolve any missing files

APIM PROGRAMMING CONCERNS OR ISSUES AFTER APIM REPLACEMENT - SYNC 3 EQUIPPED VEHICLES

Error State/Message	Possible Causes	Solution
SYNC voice no longer operates with original module Loss of voice prompts, "Please Say A Command" no longer operates after update or module replacement.	Concern during APIM programming process Concern with front speakers Concern with mono/SYNC Alert circuits	Perform SYNC reboot according to this article and APIM configuration. APIM master/factory reset as needed. Perform speaker walk around test to confirm both speakers operate Diagnose speakers or SYNC Alert circuits per pinpoint test direction in WSM as needed
Repeat MEM_ERR, SIGN_ERR, LST_ERR, PKG_ERR, INSTL_ERR, or VER_ERR Replacement APIM with MEM_ERR, LST_ERR, PKG_ERR, INSTL_ERR, or VER ERR	Incorrect USB format, damaged USB flash drive, or SYNC software concern with the original module Poor Wi-Fi causing partial download Concern with the replacement module Customer modified APIM data using aftermarket tool	Relocate vehicle to better Wi-Fi signal, performed a master reset and retry programming Try Universal USB Updater method to update SYNC Try Universal USB Updater with replacement module Follow dealer escalation process. Multiple APIM replacement is not recommended.
Invalid Software/Incompatible Hardware	Replacement APIM is incorrect for the vehicle	Select On-line 1878 at the bottom of PTS after entering the VIN and contact Customer Online Parts Inquiry System (COPIS) If replacement module is correct, please follow dealer escalation process. Multiple APIM replacement is not recommended
Data Corrupted, Error Return, GetVehicleNodeInfo Direct configuration data is missing, or Error during programming Reduced, incorrect, or half screen display/FDIM after programming "Procedure Unsuccessful-MainUpdateProcess Failed to restore module configuration"	APIM data missing from the server. Incorrect APIM data on the server. Incorrect APIM data	Make sure latest FDRS software version is installed. Delete current session, start new FDRS session, retry APIM programming. Follow dealer escalation process. Multiple APIM replacement is not recommended.
"Warning: Applications are currently not loaded - follow Custom programming and select the current assembly indicated by the check marks current on SYNC page."	Applications missing from the SYNC server or missing from the SYNC page USB drive was not re-inserted into the scan tool when prompted at the end of the SYNC programming	Start FDRS session. Perform a network test to update the SYNC server and refresh the SYNC page. Follow dealer escalation process. Multiple APIM replacement is not recommended.
Update does not start automatically when inserting the USB into the vehicle and 5 minutes have elapsed	USB not properly formatted Downloaded files are still compressed (double zipped) The auto install 1st file is missing from the USB drive	Verify operation of the USB port using the MIT tester Verify 32GB USB drive is properly formatted to exFAT Verify the autoinstall.1st file is present on the USB drive Verify all downloaded files are extracted/decompressed Access the USB drive, open the SyncMyRide Folder and Autoinstall File to confirm gz Archive file (tar.gz.) is displayed Full format the flash drive and retry the SYNC programming
Select/No/Flash, blank SYNC page, or MainUpdateProcess Failed	Poor internet connection Missing SYNC software on the server. SYNC software flashing concern	Use an alternate internet source and retry the SYNC programming Follow dealer escalation process. Multiple APIM replacement is not recommended.
Module stuck in bezel diagnostics mode	Concern occurred during programming or software update attempt Non-responsive center display screen	Perform SYNC reboot by pressing and hold the power button with the seek forward (if equipped) up to 10 seconds Perform the APIM configuration programming using FDRS Follow WSM , Section 415-00 for not responsive to touch
"Unable to find/USB Dis/VIN.1st" "Unable to find/VIN.1st"	The autoinstall.1st file is missing from the USB drive Downloaded files are still compressed (double zipped) USB drive not properly formatted Poor internet connection	Verify the autoinstall.1st file is present on the USB drive. Attempt an alternate internet source Use a new USB flash drive and verify formatting Access the USB drive, open the SyncMyRide Folder and Autoinstall file to confirm gz Archive file (tar.gz.) is displayed Full format flash drive properly, and retry SYNC programming
Repeat message stating "Installation In Progress" populates after SYNC programming attempt Repeat message stating "Voice Recognition Not Ready" Center display screen stays on after programming attempt. Stays on with ignition off.	Error occurred during programming or with software update APIM stuck in programming mode or step(s) skipped during programming process APIM is in programming mode. Programming was stopped or was not completed	Perform SYNC reboot according to this article. APIM master reset, turn off automatic updates. Complete APIM configuration programming or standard programming without any applications selected. Perform SYNC reboot according to this article 2x. APIM master reset, and complete APIM programming again Check SOC , Attempt PMI or APIM configuration programming and reevaluate.

APIM PROGRAMMING CONCERNS OR ISSUES AFTER APIM REPLACEMENT - GEN 2 SYNC AND GEN 1 SYNC EQUIPPED VEHICLES

Error State/Message	Possible Causes	Solution
Flashing FDIM after APIM replacement (Gen 1) Center display screen inoperative or blank after APIM replacement (Gen 1 SYNC)	MS-CAN concern between center display screen and ACM Power/ground concern at center display screen and/or ACM Issue with ACM that controls center display screen in Gen 1 navigation system. Power/ground concern at ACM	Diagnose MS-CAN concern between center display screen and ACM, APIM replacement not recommended. Diagnose ACM concern. APIM controls only controls SYNC in Gen 1 systems. APIM replacement is not recommended.
SYNC voice no longer operates with original module Loss of voice prompts, "Please Say A Command" no longer operates after update or module replacement.	Concern during APIM programming process. Concern with front speakers. Concern with Mono/SYNC Alert circuits.	Perform SYNC reboot according to this article and APIM configuration. APIM master/factory reset as needed. Perform speaker walk around test to confirm both speakers operate. Diagnose speakers or SYNC Alert circuits per pinpoint test direction in WSM as needed.
"Exception entering sboot mode ECU fault reason: IPC link down"	Missing Sboot driver. SYNC programming cables not connected.	Make sure the APIM is functional by pressing voice button, Sboot drivers are downloaded, and attempt programming again. Follow the dealer escalation process. Multiple APIM replacement is not recommended.
Screen display Module Is Not Provisioned after programming the replacement APIM . (Gen 2 SYNC) Center display screen stays on after programming attempt. Stays on with ignition off.	Applications were not installed on the new module using the USB flash drive Service Provisioning app was not selected during PMI-Module Replacement programming (FDRS ) APIM is in programming mode. Programming was stopped or was not completed.	Format 16GB or 32GB USB drive to FAT32. Retry APIM programming Perform standard programming to add factory equipped applications Open FDRS and click on PMI or CIP . Select the application titled BT4T-14 D546-DA (service provisioning only select when a new module is installed). Complete the APIM programming and retest. Check SOC . Attempt PMI or APIM configuration programming and reevaluate.
Wireless provisioning is not functional or Wireless Access Points is displayed on the center display screen. (Gen 2 SYNC)	Wireless Provisioning button was selected during provisioning. This is for in-plant use only.	Wait approximately 40 minutes KOEO . The APIM will deactivate the wireless provisioning automatically. An APIM soft reset or power reset will not reset or alter the internal timer.
Provisioning Error (Gen 2)	Partially zipped/compressed SYNC files on the USB drive Damaged USB drive Incorrect CIP files SYNC server concern	Verify all downloaded SYNC files are extracted/decompressed Use a different USB drive Perform PMI and select "Force CIP" (FDRS ) Follow dealer escalation process. Multiple APIM replacement is not recommended.
"Data Corrupt", "GetVehicleNodeInfo Error", or "StatusCode: 500 Error VM-PB-E07-Unable to resolve Variant ID" during APIM programming (Gen 2 SYNC and Gen 1 SYNC)	APIM data missing from server. Incorrect APIM data on server.	Follow dealer escalation process. Multiple APIM replacement is not recommended.
Module stuck in bezel diagnostics mode "Sirius Not Equipped" after programming. Gen 1 SYNC equipped with center display screen.	Concern occurred during programming or software update attempt. Configuration concern with APIM, ACM , or FCDIM	Perform SYNC reboot by pressing and hold the power button with seek forward (if equipped) up to 10 seconds Format 16GB or 32GB USB drive to FAT32 only. Perform PMI and select "Force CIP" (FDRS ) As-built programming FCDIM and ACM . Standard or configuration APIM programming and retest
"Applications Desktop Error" during or after SYNC update. (Gen 2 SYNC)	Occurred during software update Outdated or faulty SD card causing indexing issue	Format flash drive to FAT32 then proceed with standard APIM programming Remove SD card and perform SYNC reboot. If error is resolved, SD card replacement is required
Center display screen response/calibration. (Gen 2 Only)	Center display screen not calibrated Configuration error during APIM programming	Configure the center display screen's touchscreen per general procedures in WSM . Section 415-00 Perform "Force CIP" (FDRS ) and click on the "Touchscreen Calibration" option
Any of the following messages: Unsupported/Corrupt Device/Installation Has Run Out Of Space/Does Not Work With This Version	Master reset not performed prior to the attempted installation of software Standard programming performed while APIM is already at the latest level; applications are attempted to be installed twice	Perform an APIM master reset as per the appropriate WSM . Section 415-00 (Gen 2) Perform standard APIM programming (FDRS)
"Invalid or unsigned file-your package may have corrupted, the package signature may have failed or the signature may have been revoked"	The Global Navigation Application requires a second, hidden application to be loaded in the background during APIM programming. (SYNC Gen 2 MyTouch)	Perform standard APIM programming per the appropriate WSM , Section 415-00: only select App To Correct Modules That Report Null ESN. Complete APIM programming. Perform "Standard APIM" programming again and only select "Global Navigation Application" and complete APIM programming
"Select/no Preinstall Restore" - unable to program replacement APIM . (Gen 1 SYNC)	Incorrect APIM installed Updating from v1 APIM to v2 APIM to support 911 Assist Incorrect vehicle data on the SYNC server	Verify the correct APIM is installed Make sure the RCM and IPC are updated to latest software level to support 911 Assist with v2 replacement APIM , retry APIM Programming Follow dealer escalation process. Multiple APIM replacement is not recommended.
VIP /CIP missing on the SYNC page in OASIS Electric vehicle VIP /CIP software installed in a non-electric vehicle. (Gen 1/Gen 2)	Information was not uploaded to the SYNC database Hybrid powertrain modules not updated (PCM, BECM, DCDC, ACCM, SOBDM, TCM/SOBDMB ) Incorrect VIP/CIP software installed	Perform the "Read VIN And DTC" function. If missing still, contact the TAC to have corrections made. Reprogram the hybrid powertrain modules and retry SYNC programming (as directed in FSA ) Follow dealer escalation process. Multiple APIM replacement is not recommended.
"Install ActiveSync, ActiveSync Is Present" message (Gen 1 and Gen 2)	Incorrect APIM is installed SYNC server data is incorrect Turn off/disable-ActiveSync	Select On-line 1878 at the bottom of PTS after entering the VIN . If the replacement module is correct, follow dealer escalation process. Multiple APIM replacement is not recommended. Disable active SYNC and retry SYNC programming

MAP SOFTWARE UPDATING/MAP SOFTWARE ERRORS - GEN 1, GEN 2, SYNC 3

Error State/Message	Possible Causes	Solution
Installation error. (SYNC 3) Message stating "SYNC Must Be Updated Before This Map Update Can Be Applied. Please Remove The USB Drive" or "VER ERR" 01-06 (SYNC 3)	Error with map software or SYNC 3 software installed Attempting to add update map software with outdated SYNC software (v2.2 or earlier) USB/drive connected to USB port after update completed	Perform an APIM master reset as per the appropriate WSM . Section 415-00, turn off automatic updates, and attempt the map software update again Complete standard programming to update SYNC software and attempt maps software update again Contact CRC or refer to the Owner's Manual for the map supplier to receive a new USB/drive that contains updated map software
"Installation Failed: BGMAP ERR" 01-05. (SYNC 3)	USB /drive connected to the USB port after update completed Map software/hardware has incorrect version Concern with map software/hardware installed on USB/drive Vehicle is not equipped with navigation	Perform an APIM master reset as per the appropriate WSM , Section 415-00, turn off automatic updates, and attempt the map software update again Contact CRC or refer to the Owner's Manual for the map supplier to receive a new USB /drive that contains updated map software Verify the vehicle was built with navigation from the factory
"Installation Failed" (SYNC 3)	USB /drive connected to USB port after update completed Incorrect USB format or concern with the USB flash drive USB connection interrupted SYNC or USB /drive storage limitation Corrupted software/hardware installed on USB /drive	Format or full format the 32GB USB drive to ExFAT, re-download map software per the navigation site or receive a new USB drive Perform APIM master reset, turn off automatic updates, retry software update, leave USB connected to the USB port for at least 5 minutes Replace the map software USB drive again
Navigation voice stopped after map software update. Message stating "Installation In Progress" populates after SYNC programming or map software update (stay on after programming).	Error occurred with map software or with SYNC 3 software installed Error occurred during software update. APIM stuck in programming mode	Perform SYNC reboot according to this article, APIM master reset, turn off automatic updates, and complete standard programming without any applications selected Perform SYNC reboot according to this article 2x. APIM master reset, and complete standard programming without any applications selected
Navigation missing after programming or module replacement (Gen 2) SD card concern after replacement. (Gen 2)	Nav app EA5T-14F657-AG wasn't selected during programming (Gen 2) Vehicle not built with navigation (Gen 2) Outdated SYNC software Concern with SD card	Confirm vehicle was built with navigation (Gen 2) Perform "Force CIP" (FDRS ) standard programming, select correct Nav app 14F657 and retest. (Gen 2). Then proceed installing latest v3.10. Replace SD card as needed. (Gen 2).

FDRS RELATED ERRORS

Error State/Message	Possible Causes	Solution
"Unable To Communicate With The Module" "Could Not Communicate With The VCM" "Procedure Unsuccesful-EstablishComms Could Not Communicate With The VCM." "Make Sure That All Cables Are Connected" "Unable To Communicate With The Vehicle. Check All Cable Connections And Make Sure The Ignition Is Switched On."	FDRS was unable to communicate with the module. This may be due to a fault on the vehicles network or with communication to a specific module. It may also be possible that a diagnostic file used by the FDRS scan tool or information within the FDRS servers is incorrect.	Delete the VIN from the previous sessions list, make sure latest FDRS software version is downloaded, and retry. Re-attempt the programming application with a different laptop. Uninstall/reinstall FDRS. retry programming. Determine if the module can complete an on-demand DTC self-test and pass a network test. If the module(s) fail either test, suspect a module or network communication fault. Follow the dealer escalation process.