(NRF52810) Subscribe to characteristics fail and issues disconnect to board.

RE: (NRF52810) Subscribe to characteristics fail and issues disconnect to board.

Sigurd — Mon, 18 Mar 2019 15:03:08 GMT

What is the link supervision timeout set to ? Could you increase it to 4 sec?

Do you have any logs(either over UART or Segger RTT) from the peripheral side?

RE: (NRF52810) Subscribe to characteristics fail and issues disconnect to board.

laird_user — Wed, 13 Mar 2019 19:49:02 GMT

We don't have nRF sniffer. We are using Bluegiga Interface tool.

Our board acts as a Peripheral and BLED112 as the BLE dongle for the windows machine.

Logs when I click connect button on the interface tool --

2019.03.14 00:59:49.687 ble_cmd_gap_connect_direct address: bb d1 4f 9c 91 c3 addr_type: 1 (0x01) conn_interval_min: 60 (0x003c) conn_interval_max: 76 (0x004c) timeout: 100 (0x0064) latency: 0 (0x0000)
2019.03.14 00:59:49.693 TX: 000f0603bbd14f9c91c3013c004c0064000000

2019.03.14 00:59:49.698 ble_rsp_gap_connect_direct result:0x0000 ['No Error'] connection_handle: 0 (0x00)
2019.03.14 00:59:49.699 RX: 00030603000000

2019.03.14 00:59:49.742 ble_evt_connection_status connection: 0 (0x00) flags: 5 (0x05) address:c3:91:9c:4f:d1:bb address_type: 1 (0x01) conn_interval: 60 (0x003c) timeout: 100 (0x0064) latency: 0 (0x0000) bonding: 255 (0xff)
2019.03.14 00:59:49.746 RX: 801003000005bbd14f9c91c3013c0064000000ff

2019.03.14 00:59:50.848 ble_evt_connection_disconnected connection: 0 (0x00) reason:0x0208 ['Link supervision timeout has expired.']
2019.03.14 00:59:50.863 RX: 80030304000802

Clearly the last packet is the disconnect event received. I believe it should have been version_ind_event.

When we configured the board to act as CENTRAL and the mobile app as peripheral, the board kept connected-disconnected. It didn't stay connected even for a second. Reason for disconnection printed was 62.

POINT TO NOTE - our board doesn't have external oscillator instead is using the in-built RC oscillator. And the two configs of setting RC and its value to 250PPM in zephyr is set properly.

RE: (NRF52810) Subscribe to characteristics fail and issues disconnect to board.

Sigurd — Wed, 13 Mar 2019 17:44:00 GMT

Hi,

Could you attach the packet sniffer logs here ? What sniffer are you using ? nRF sniffer ?

If you connect to the BLE peripheral using a smartphone, e.g. with nRF Connect for mobile, do you see the same issue?

[quote userid="77675" url="~/f/nordic-q-a/44634/nrf52810-subscribe-to-characteristics-fail-and-issues-disconnect-to-board/175324"]Most of the people in the support groups have mentioned that upgrading the zephyr code has resolved the issue. Do you think the same could be with our case? If yes then which tag and version should we be using of zephyr?[/quote]

You could maybe ask in the support group where you find this information about what zephyr version they upgraded to. You could maybe try the latest release(v1.13.0), or latest release candidate(v1.14.0-rc1).

RE: (NRF52810) Subscribe to characteristics fail and issues disconnect to board.

laird_user — Mon, 11 Mar 2019 12:56:28 GMT

From the packet sniffers, what we understood is ble_evt_connection_version_ind event is not getting generated from the board. No communication happens for a while and then suddenly "ble_evt_connection_disconnected connection: 0 (0x00) reason:0x0208 ['Link supervision timeout has expired.']" is received by the central.

Most of the people in the support groups have mentioned that upgrading the zephyr code has resolved the issue. Do you think the same could be with our case? If yes then which tag and version should we be using of zephyr?

RE: (NRF52810) Subscribe to characteristics fail and issues disconnect to board.

laird_user — Mon, 11 Mar 2019 11:13:03 GMT

Any inputs on this please???

RE: (NRF52810) Subscribe to characteristics fail and issues disconnect to board.

laird_user — Sun, 10 Mar 2019 18:07:47 GMT

Another update -
Checked with other centrals also and tried to sniff the packet. What we understood is that moment after connect happens, in a while disconnect event with error 0x0208 is sent.

Also observed one thing, addr_type set in our board is Random. ( this thing we noticed while we were comparing with other logs).

RE: (NRF52810) Subscribe to characteristics fail and issues disconnect to board.

laird_user — Sun, 10 Mar 2019 13:01:32 GMT

Our further analysis -
At the central side, When the python script starts fetching the Characteristics it sends the Request as attclient_find_information to which the response is successful. This command is followed by Bluetooth attclient_procedure_completed to which the response is [128, 3, 3, 4, 0, 8, 2] which means disconnect.
Hence, it means that controller issued a response to disconnect instead of the version_ind_packet

Going through the version_ind_send code in blue tooth, it sends an empty packet and I think waits for the next connection interval to send the actual data. The central has predefined expectation of data and hence is not ack-ing? to which the peripheral sends the disconnect event.

Is this the right direction we are in ??

Really looking forward to a reply on it. Thank you so much !