LEMON Manuals: Even more car manuals for everyone
Home >> Mercury >> 2010 >> Milan Base, Standard >> Repair and Diagnosis >> External Pages >> Different car >> Section 1245 (Information System And Entertainment System) >> Diagnosis And Testing >> Information and Entertainment System >> Pinpoint Tests >> Pinpoint Test W: Unable To Pair Bluetooth Device >> Pinpoint Test W: Unable To Pair BLUETOOTH Device

Pinpoint Test W: Unable To Pair BLUETOOTH Device

WARNING: This page is about a different car, the 2010 Mercury Mariner and 2010 Ford Escape. However, it is still accessible from the selected car via links, so may be relevant.
  1. W1 CHECK THE BLUETOOTH CONNECTION 
    NOTE: Carrying out a Master Reset returns all preference settings to the factory defaults, erases all the phone book and call histories and deletes any devices paired with the SYNC system.
    • Connect: Multi-Media Interface Tester.
    • Using the Multi-Media Interface Tester, connect to the SYNC system using Bluetooth.
    • Enter the following diagnostic mode on the scan tool: APIM  DataLogger.
    • Monitor the Bluetooth device paired PID (BT_PAIR) and the Bluetooth device connected PID (BT_CONN).
    • Do the PIDs BT_PAIR and BT_CONN both read "Yes"? 
    • Yes:  The SYNC system is operating correctly at this time. CARRY OUT a SYNC system Master Reset. REFER to the Owner's Literature.

      REVIEW the pairing process with the customer. If the customer device still does not pair, the fault is with the customer device.

    • No:  GO to W2  .
  2. W2 CHECK FOR CORRECT APIM OPERATION 
    • Disconnect the APIM  connector.
    • Check for:
      • corrosion
      • damaged pins
      • pushed-out pins
    • Connect the APIM  connector and make sure it seats correctly.
    • Wait 2 minutes for the APIM  to re-initalize.
    • Operate the system and verify the concern is still present.
    • Is the concern still present? 
    • Yes:  INSTALL a new APIM  . REFER to ACCESSORY PROTOCOL INTERFACE MODULE (APIM) . TEST the system for normal operation.
    • No:  The system is operating correctly at this time. The concern may have been caused by a loose or corroded connector.