Pairing and key exhange with ANCS

RE: Pairing and key exhange with ANCS

Matts — Mon, 25 Apr 2016 12:10:05 GMT

Now also the notifications go trough. Thanks for the support!

RE: Pairing and key exhange with ANCS

Hung Bui — Mon, 25 Apr 2016 07:43:03 GMT

Hi Matts,

Correct, you would need an extra board to sniff the connection. I can't think of anything else other than the issue with Android since the proximity app should work. I assume that you did a full erase of the chip when testing it, just to make sure the old bond information is erased.

RE: Pairing and key exhange with ANCS

Matts — Mon, 25 Apr 2016 07:30:01 GMT

Ok, now the connection is not dropping anymore. I think this issue is solved.

However just for future use, could you answer the sniffer question?

RE: Pairing and key exhange with ANCS

Matts — Mon, 25 Apr 2016 07:15:00 GMT

Ok, the pairing succeeded atlast! Bluetooth off + shutdown + battery off repeated 3 times did the trick! The connection is still dropped in 5 seconds, but some progress!

RE: Pairing and key exhange with ANCS

Matts — Mon, 25 Apr 2016 06:47:21 GMT

Hi.

No asserts with the nrf board. the board version is PCA10040 V1.1.0 2016.9 SDK is nRF5_SDK_11.0.0_89a8197.

I'll try to get another phone HW. I was involved with another project related to bluetooth year a go. We run into situation in android end that something in non-volatile data corrupted (some setting or something) and it didn't recover without several reboots and removal of battery. This might be similar case.

Regarding sniffer: How should I sniff the connection? I mean I have only one nrf board. Can I connect to sniffer with the android and use the siffer to analyze the connection? The setup in the instructions seems to be that two separate devices communicate and sniffer just sniffs in the side.

RE: Pairing and key exhange with ANCS

Hung Bui — Fri, 22 Apr 2016 13:56:01 GMT

I suspect there could be something wrong with the phone. Could you try to test with other phone ? Also a reset on the current phone is worth to try.

Could you check if there is any assert on the nRF52 ? Did it reset when the bonding failed ?

Also please let me know the chip revision and the SDK, softdevice version you are testing .

RE: Pairing and key exhange with ANCS

Matts — Fri, 22 Apr 2016 12:31:24 GMT

And just to clarify:

Just trying to connect with nRF MCP app with the nrf52 + ANCS example app fails similarily as my app.

I also tested the proximity example, and I couldn't pair it, nor connect to it with nRF control panel. I get error 129 (0x81) GATT INTERNAL ERROR and Error 8 (0x08): GATT CONN TIMEOUT.

RE: Pairing and key exhange with ANCS

Hung Bui — Fri, 22 Apr 2016 12:23:12 GMT

Hi Matts,

Please capture the sniffer trace.

And please test bonding with any example such as the proximity example. From the nRF MCP log, it's showing that the device disconnect in the pairing process. Have you made sure you don't exceed the maximum number of bonded central ?

RE: Pairing and key exhange with ANCS

Matts — Fri, 22 Apr 2016 12:18:08 GMT

Ok, I have that installed. I also found some logging from the nRF MCP and it's attached to question above. Also I've got HCL logs open in wireshark. Anything specific I could check from those?

And yes, the nRF52 with example works just fine with iPhone. And what I'm trying to do here, is to get similar communication protocol for android app so that we do not have to have both ANS and ANCS supports in the nRF board.

RE: Pairing and key exhange with ANCS

Hung Bui — Fri, 22 Apr 2016 11:22:39 GMT

Hi Matts,

I was talking about the nRF Master Control Panel on Android (or iOS). We also have an app for the mobile platforms.

I don't think we have any further than the documentation from Apple about ANCS here.

Could you clarify that you have tested and everything worked fine when you test with iOS device instead of Android ?

The concept should be the same, on Android and iOS. The only difference is on Android you need to make the server yourself, and handle the notification provider on your own.

The flow of communication is described in the diagram in the documentation from Apple above. You connect and bond from the phone (the ANCS server) after that the client should start to discover the service and subscribe to the characteristic(s).

Seems that you has problem with bonding, please try to test bonding with other example, such as proximity example.

RE: Pairing and key exhange with ANCS

Matts — Fri, 22 Apr 2016 08:50:53 GMT

Also regarding the communication initialization:

Does the Content Provider connect the Consumer directly? I get connection to GattServer just by making the bond call. If the CP should connect directly, should that be via GattServer.connect or via gatt client (bluetoothdevice.connectGatt)?

Also should the Content provider read/write something to Content Consumer (nrf board)?

Hopefully I can get the jlink ultra connected to this today and get more info what happens in the nrf board. Also trying to get HCL logs from the android side.

RE: Pairing and key exhange with ANCS

Matts — Thu, 21 Apr 2016 13:40:10 GMT

I've seen the apple document for content consumer developers. But is there any flow how the initial communication should go? I mean in the apple document there wasn't even mention about the CCCD:s in the characterics.

RE: Pairing and key exhange with ANCS

Matts — Thu, 21 Apr 2016 13:38:23 GMT

Hi Hung Bui!

I cannot use the nRF MCP as I do not have windows machine. I have however iPhone 5 for testing purposes and it connects OK with the nRF52.

Regarding that connection dropping. I have GattServer with that new service running in the android phone. I've tried connecting with the device both via regular gatt connection and server connection. Not sure which is the correct way, but result is the same.

In onConnected callback I'll try to do the bonding (bluetoothdevice.createBond() -call). It gives me first BluetoothDevice.ACTION_BOND_STATE_CHANGED to BluetoothDevice.BOND_BONDING. However right after that (300ms later) I get onConnectionStateChange -callback with disconnected state and callback to BluetoothDevice.ACTION_BOND_STATE_CHANGED with value BOND_NONE.

What most bothers me, that I get error status (on connection drop) that no read rights or value 62.

RE: Pairing and key exhange with ANCS

Hung Bui — Thu, 21 Apr 2016 12:10:13 GMT

Hi Matts,

You should have BOND_BONDED if it's successfully bonded. I suspect there could be an issue here. You may want to capture a sniffer trace to see what was wrong. If you use nRF Master Control Panel to connect and bond, do you have any problem ? Note that the key exchange process is handled by Android and the app doesn't need to do anything (except for triggering the bonding process)

Could you explain "but it drops it right away" ? Does that mean the connection was dropped ? Again, a sniffer trace would reveal more info.