This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

BLE disconnect with 0x16 reason

Hi,

I have two nrf51822 device, on work as GAP Central, another work as GAP Peripheral.The two device use different connection parameters, after the connection is established, Peripheral device send BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST to the Central,usually my code in Central device accept the request and update the connection parameters use

sd_ble_gap_conn_param_update(p_gap_evt->conn_handle,
                                        &p_gap_evt->params.conn_param_update_request.conn_params);

function,and now i wanna improve the speed so i ignore the request(mean's i do nothing when i receive BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST event),then after a certain time the connection will disconnect. I debug the code of Peripheral device and found the reason of DISCONNECT_EVENT is 0x16,it seems because "L2Cap connection parameter update timeout", so must I response BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST? If so,what should i do to reject the request? Is sd_ble_gap_conn_param_update(NULL) ok?

Nordic SDK file told me when Central receive BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST it can then:

1、Accept the request and respond with sd_ble_gap_conn_param_update(connection parameters) to update the connection parameters

2、Reject the request and respond with sd_ble_gap_conn_param_update(NULL)

3、Ignore it.

I accept it before, but now i wanna reject it so i ignore it, but no one tell me this will cause connection disconnect.

Parents
  • Yes, use sd_ble_gap_conn_param_update(p_gap_evt->conn_handle, NULL) can avoid peripheral disconnect the connection. Central must response BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST, if central ignore it, the peripheral will disconnect.

Reply
  • Yes, use sd_ble_gap_conn_param_update(p_gap_evt->conn_handle, NULL) can avoid peripheral disconnect the connection. Central must response BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST, if central ignore it, the peripheral will disconnect.

Children
No Data
Related