ancs on pca10028

[pbljung]

I have a a new pca10028 DK board and a pca10000 dongle. Using Keil v5.14 and Nordic SDK v7.2 I can compile, download and test several pack examples (e.g. ble_app_hrs, ble_app_alert_notification) to pca10028 and test them using Master Control Panel v3.7.1 or lightblue on a iOS handset.

However I could not follow the instructions for experimental_ble_app_ancs. I can successfully compile and download experimental_ble_app_ancs to the pca10028. A Putty terminal displays uart printfs including "BLE ANCS”. Using lightblue I see "ANCC" peripheral, and I can connect and see notifications and attributes (by adding printf statements) in the terminal.

However I cannot successfully test experimental_ble_app_ancs with the Master Control Panel. In master control panel I select the pca10000 dongle, load the ANCS_central.bin, stop and re-start the server, start discovery, select the ANCC device, and click connect, bond, discover services. I always get a link loss during bonding and then see BTLE_CONNECTION_TIMEOUT in the terminal.

How do I successfully use master control panel to test experimental_ble_app_ancs? Since lightblue works, I suspect that the default settings for ANCS_central.bin are incorrect.

[pbljung]

That is what I have been doing, but I always get Received Link Loss error.

In Master Control Panel I select File>FlashProgramming. I select the MEFW 0.9.0 and click program.

In Master Control Panel I select File>ServerSetup, then File and select ANCS_central.bin. I stop the server, and then I re-start the server. I close the server setup window.

I click Discover, MCP finds the ANCC device. I click ANCC and click select device. I click connect, and the console reports connected, and 5s later it reports that connection parameters are updated.

I click Bond, MCP console reports encryption change, then a few seconds later there is the error "Received link loss".

The last lines of the MCP log (attached) shows that there is a BTLE connection timeout, and then a link loss is reported. How to proceed?

log MCP 20150316.rtf