BLE_GAP_PHY_CODED connect immediate timeout

RE: BLE_GAP_PHY_CODED connect immediate timeout

Simonr — Wed, 21 Aug 2019 09:04:50 GMT

Hi Kim

2. Please see this post for a thorough explanation of sd_ble_gap_connect().

3. If your application is set to BLE_GAP_PHY_AUTO, the SD_BLE_GAP_PHY_UPDATE function will select PHY based on the peer's PHY preferences and the local link configuration. The PHY update procedure will for this case result in a PHY combination that respects the time constraints configured with sd_ble_cfg_set and the current link-layer data length. If the peer doesn't support the PHY Update Procedure, the resulting PHY_UPDATE will have a status set to BLE_HCI_UNSUPPORTED_REMOTE_FEATURE.

Note that BLE_GAP_PHY_AUTO will also be compatible with the BLE_GAP_PHY_2MBPS, so if you don't want to connect to devices preferring that, you might want to take a look at how to decide the PHY by way of I.E. a button press, in our BLE long-range demo.

Best regards,

Simon

RE: BLE_GAP_PHY_CODED connect immediate timeout

Kim Djernæs — Wed, 21 Aug 2019 07:48:46 GMT

After a long time I'm now coming back to this.

I was wondering if I could get a more definite answer to #2 and #3?

Regards
Kim

RE: BLE_GAP_PHY_CODED connect immediate timeout

Simonr — Fri, 01 Feb 2019 07:52:34 GMT

Hi Kim

1. Can you try scanning and connecting using only BLE_GAP_PHY_CODED, just to make sure that the problem isn't there. I think the problem is that when you get scan reports you don't know if they are CODED or 1MBPS, so the timeout occurs because you try connecting a 1MBPS advertiser to a PHY scanner, or the other way around. Also see what happens when you try to connect in BLE_GAP_EVT_ADV_REPORT. You can try calling the function nrf_ble_scan_connect_with_target in the BLE_GAP_EVT_ADV_REPORT as well, although I suspect it is already being called.

2. Yes, I think so.

3. I haven't looked too much into this, but I suspect you have to specify the correct scan_phy parameter, although I am not sure about this. We might find out together!

Best regards,

Simon