Unwanted disconnection after notification

RE: Unwanted disconnection after notification

Guillaume Levant — Tue, 03 Jan 2017 15:07:52 GMT

Thanks a lot ! I forgot to set one parameter that is needed for sd_ble_gatts_rw_authorize_reply, so this function returns the error NRF_ERROR_INVALID_PARAM and doesn't send the reply.

RE: Unwanted disconnection after notification

Hung Bui — Tue, 03 Jan 2017 14:21:04 GMT

Hi Guillaume,

From the trace I can see that it's not disconnect right after you send notification. What you capture in your image in the question is the LL_TERMINATE_IND packet which mean it's the termination packet from the Master/central to disconnect.

The disconnection happen 30 second after a write request (packet 637) it's a timeout for the write request because there is no write response for it.

Usually this happens when you set a characteristic with authorization and in the application you don't response to the BLE_GATTS_EVT_RW_AUTHORIZE_REQUEST event. Please have a look here.

The write request is for attribute at handle ID 0x0f, you may want to check. Same write response to handle 0x10 (packet 302)had no issue.

RE: Unwanted disconnection after notification

Guillaume Levant — Tue, 03 Jan 2017 13:40:43 GMT

I send it to you via PM right away.

RE: Unwanted disconnection after notification

Hung Bui — Tue, 03 Jan 2017 13:22:51 GMT

Please upload the whole sniffer trace file. If there is confidential information, you can send me via PM.

RE: Unwanted disconnection after notification

Guillaume Levant — Tue, 03 Jan 2017 13:10:36 GMT

I finally managed to get a sniffer. I added in my question the information catched from the message which came at the same moment than the disconnection event.

RE: Unwanted disconnection after notification

Hung Bui — Mon, 02 Jan 2017 11:37:05 GMT

Have you managed to catch the sniffer ?

Also please try to test using the nRFConnect app.

RE: Unwanted disconnection after notification

Guillaume Levant — Mon, 02 Jan 2017 10:26:38 GMT

Yes I can receive the data on the phone without any problem. And if I only enable CCCD, the device stays connected.

RE: Unwanted disconnection after notification

Hung Bui — Fri, 23 Dec 2016 14:29:01 GMT

A sniffer trace would really be helpful. You would need a nRF51 dongle/DK to use as a sniffer trace.

One question, do you receive the data on the phone, from your notification ? If you don't send the notification (but enable CCCD), the link will still keep with no disconnection?

RE: Unwanted disconnection after notification

Guillaume Levant — Fri, 23 Dec 2016 14:18:06 GMT

Sorry I didn't want to convert you comment... I use LightBlue to make my test, and I noticed that the device disconnect each time 30 seconds after the last notification. I saw that NEXT_CONN_PARAMS_UPDATE_DELAY was set to 30 sec, so I set it to 20 sec to check if it is related to my problem, but the disconnection still happens 30 sec after the last notification.

RE: Unwanted disconnection after notification

Hung Bui — Fri, 23 Dec 2016 13:49:24 GMT

Could you try to test with the nRFConnect app ? the DISCONNECTED event came right after the notification or only when you see that it's only disconnected on the phone (after a few seconds) ?

RE: Unwanted disconnection after notification

Guillaume Levant — Fri, 23 Dec 2016 09:42:39 GMT

Hi, I checked the reason, it is BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION, but the central didn't crash, and the device is working perfectly after the disconnection event.

RE: Unwanted disconnection after notification

Hung Bui — Thu, 22 Dec 2016 09:37:11 GMT

Hi,

Most probably either your device or the central crashed after the notification is sent. I can't guess the reason. You may need to check what disconnect reason is (check the parameter when the DISCONNECTED event occurs) and check if your central device is crashed. A sniffer trace would be useful.