Peripheral Connection Issues When Configured as Dual Central and Peripheral

RE: Peripheral Connection Issues When Configured as Dual Central and Peripheral

WestCoastDaz — Mon, 26 Nov 2018 23:39:42 GMT

It turns out that I was calling the event handler for the central during a peripheral connection which was messing everything up. Thanks for the help, especially the tip about the disconnection reason.

Darren

RE: Peripheral Connection Issues When Configured as Dual Central and Peripheral

WestCoastDaz — Mon, 26 Nov 2018 17:38:02 GMT

KennethThanks for taking the time to reply! I followed your suggestions to change the NRF_SDH_BLE_TOTAL_LINK_COUNT to 2 and to add the disconnect reason but the issues still persists. The disconnect reason is 0x16 which

BLE_HCI_LOCAL_HOST_TERMINATED_CONNECTION

I also am getting this nRFConnect

Maybe this is a connection handle issue?

Thoughts?

RE: Peripheral Connection Issues When Configured as Dual Central and Peripheral

Kenneth — Mon, 26 Nov 2018 13:15:04 GMT

Hi,

Just to avoid race conditions I suggest you set NRF_SDH_BLE_TOTAL_LINK_COUNT to 2, this means you can have both a peripheral and central link at the same time.

Make sure that you have control of the conn_handle's, since it may for instance be 0 or 1 (or more). This may explain why sd_ble_gap_data_length_update() return NRF_ERROR_INVALID_STATE (No link has been established, see ble_gap.h), if for instance you are trying to initiate the procedure on the wrong conn_handle (link is not established).

I notice it says Disconnected, but what is the disconnect reason? E.g. check p_ble_evt->evt.gap_evt.params.disconnected.reason on BLE_GAP_EVT_DISCONNECTED event. Various reasons listed in ble_hci.h.

Best regards,
Kenneth