gls example : connect to the bonded peripheral

[MikeLin]

Hello

I am running gls example on SDK14.2.

I paired after flashing program to my DK board, and then turn off power.

And turned on again, but i can't connect to my DK board( nRF connect show that the gls is bonded ).

Why?

another question : everytime I press "disconnect" in nRF connect, but my peripheral has not any event occurred.

Thanks in advance.

[Einar Thorsrud]

Hi,

I believe this is due to a peculiarity in nRF Connect for Desktop. By default, it attempts to do repairing with the GLS example. I have reported an issue to the nRF Connect developers. You can avoid it by disabling "Auto reply security requests" as shown in this image:

Then you will be prompted when there is a security request. The correct answer is "Ignore", which will result in existing bonding information being used. See image:

Clicking "Accept" will make nRF Connect attempt to pair again instead of using existing bonding information, but this will fail and cause a disconnection as allow_repairing is set to false in main.c of the GLS example. Clicking "Reject" will also cause a disconnect, as the GLS example will disconnect on the PM_EVT_CONN_SEC_FAILED event.

The nRF Connect apps for iOS and Android does not have this issue.

[MikeLin]

Thanks !

But my device is android, can you tell me any possible I can't connect to bonded peripheral?

[Einar Thorsrud]

I have not been able to reproduce this on Android. Did you complete the bonding procedure, entering the 6 digit pass key (MITM protection) etc. before disconnecting? If not, the GLS example will delete bonding information and disconnect as it requires MITM.

[MikeLin]

I tried another android device, and it work ! What can I do ?

And can you tell me that when I press "disconnect"  on nRF connect APP ,and not any event occurred on my peripheral.

[Einar Thorsrud]

The Android phone should send a disconnect on air so that the nRF should see it (and log it if you have logging enabled). If not, then the nRF will think the connection is active until there is a supervision timeout. Do you have a sniffer trace?

A few questions:

• Which nRF Connect version did you use on the Android phone where it did not work?
• Which Android version?
• Which Phone model?

[MikeLin]

I want to advertise when nRF connect press "disconnect" , but I can't get any event to do this.

I don't have sniffer.

nRF connect( 4.19.1 ) ; Android( 7.0 ) ; ASUS ZenPad 3S 10 (Z500M)

[Einar Thorsrud]

You will always get a BLE_GAP_EVT_DISCONNECTED on the nRF side when there is a disconnect, and the advertising module used in the GLS example will start to advertise immediately after the BLE_GAP_EVT_DISCONNECTED event. However, the time when this comes depend on the type of disconnect. If the phone sends a disconnect, then the you will get the BLE_GAP_EVT_DISCONNECTED immediately with the disconnect reason  BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION. If the phone did not send a disconnect (for some reason), then you will wait until the supervision timeout and the disconnect reason will be BLE_HCI_CONNECTION_TIMEOUT.