RE: nrf52 SDK13 connection parameter negotiation

pettern — Wed, 02 May 2018 13:26:58 GMT

The connection intervals used as my "custom low power" are (125, 30, 20 000).

I've implemented a connection parameter negotiation 60 seconds after connection, which seem to work well by now. The updated build is tested on Android and Windows devices, and most of them seem to be affected by the connection parameter negotiation.

RE: nrf52 SDK13 connection parameter negotiation

Sigurd — Mon, 23 Apr 2018 15:32:45 GMT

Hi,

[quote user=""] I have verified the connection intervals by current measurements on the nRF52, as well as a nrf sniffer trace.[/quote]

What connection interval is used here? What is the value of your "low power connection intervals" ?

[quote user=""]This should mean that a parameter negotiation should occur for each time a device connects. [/quote]

The negotiation is only started if the received connection parameters are not acceptable, i.e. outside your MIN_CONN_INTERVAL/MAX_CONN_INTERVAL interval.

You could call sd_ble_gap_conn_param_update() with your "low power connection intervals" after e.g. 1-2 min after BLE_GAP_EVT_CONNECTED, if you don't want to change the MIN_CONN_INTERVAL/MAX_CONN_INTERVAL. Also note that for BLE HID keyboard/mouse, you generally want a low connection interval, so that the keyboard/mouse feels responsive for the end-user.