RE: How to know the actual connection parameters

José Ángel Jiménez — Fri, 20 Feb 2015 00:59:08 GMT

Thanks a lot for your nice response. Now I have a good understanding on how the connection parameter update request negotiation works.

I am now having some issues trying to register/intercept BLE_GAP_EVT_CONN_PARAM_UPDATE, in order to LOG the connection parameters received at each stage of the negociation.

Is there a simple way to attach/register a callback function to this event? I would like to register one of my app's functions so that it is called whenever the event occurs.

Thank you!

RE: How to know the actual connection parameters

Stefan Birnir Sverrisson — Thu, 19 Feb 2015 12:36:04 GMT

Hi José

I do not think the centrals honor the preferred connection parameter information of the peripheral. You will have to send a connection parameter update request to the central when connection has been established. See more about how that works on this thread.

To see what connection parameters are actually used, look at this thread.

Update 23.2.2015 You can see how to receive connection parameter updates from the cenral device in e.g. the heart rate example in the nRF51 SDK. in the main.c file you will find ble_evt_dispatch functions which is called on BLE softdevice events. The ble_conn_params_on_ble_evt function is called in turn to handle the connection parameter update request from the central.