connection parameter update request

RE: connection parameter update request

bloobird0 — Wed, 05 Oct 2016 10:11:38 GMT

excellent! Thanks a lot, it solved my problem. I called the gap_params_init() function after conn_params_init() for some reason.

RE: connection parameter update request

FormerMember — Wed, 05 Oct 2016 07:30:48 GMT

sd_ble_gap_ppcp_set(..) has to be called before conn_params_init(): conn_params_init() retrieves the set preferred connections parameters (ppcp) and use the retrieved parameters to check if, during a connection, the connection parameter are ok, see ble_conn_params_init(..) and conn_params_negotiation() --> is_conn_params_ok(..). Therefore, if sd_ble_gap_ppcp_set(..) is called after conn_params_init(), m_preferred_conn_params will not contain the ppcp, and hence, the device won't initiate a connection parameter update.

RE: connection parameter update request

bloobird0 — Tue, 04 Oct 2016 08:41:33 GMT

Yes this method is called before I connect. sd_ble_gap_ppcp_set() is called with the valid parameters and returns 0x00.

I can also read the GenericAccess service/Peripheral Preferred Connection Parameters with the correct values: 20ms/200ms/0/400.

Can this sd_ble_gap_ppcp_set() function be called at anytime or should it be called absolutely before some other BLE initialization?

RE: connection parameter update request

FormerMember — Mon, 03 Oct 2016 08:04:21 GMT

In your application, do you call gap_params_init(..)? In gap_params_init(..), the peripheral preferred connection parameters are set. Setting those parameters should apply those parameters during a connection parameter update.

I would think that the reason for no connection parameter update when running ble_app_uart is that the original parameters set by the central is within the connection interval range for the peripheral.