Allowing connections, then switching to connection-less.

RE: Allowing connections, then switching to connection-less.

MartinBL — Wed, 02 May 2018 13:45:18 GMT

Yes, but what it looks like depends on what SDK you use.

If you look at the beacon example in SDK 15 for example, it is configured like this:

static void advertising_init(void)
{
    ....

    // Initialize advertising parameters (used when starting advertising).
    memset(&m_adv_params, 0, sizeof(m_adv_params));

    m_adv_params.properties.type = BLE_GAP_ADV_TYPE_NONCONNECTABLE_NONSCANNABLE_UNDIRECTED;
    m_adv_params.p_peer_addr     = NULL;    // Undirected advertisement.
    m_adv_params.filter_policy   = BLE_GAP_ADV_FP_ANY;
    m_adv_params.interval        = NON_CONNECTABLE_ADV_INTERVAL;
    m_adv_params.duration        = 0;       // Never time out.

    err_code = ble_advdata_encode(&advdata, m_adv_data.adv_data.p_data, &m_adv_data.adv_data.len);
    APP_ERROR_CHECK(err_code);

    err_code = sd_ble_gap_adv_set_configure(&m_adv_handle, &m_adv_data, &m_adv_params);
    APP_ERROR_CHECK(err_code);
}

You can see that in SDK 15 BLE_GAP_ADV_TYPE_ADV_SCAN_IND has been renamed to BLE_GAP_ADV_TYPE_NONCONNECTABLE_NONSCANNABLE_UNDIRECTED.

RE: Allowing connections, then switching to connection-less.

jmag999 — Wed, 02 May 2018 12:27:23 GMT

Thanks. Is there an API to configure the type. I didn't see one. If not, what is the best way to configure this so that I can switch between types?

RE: Allowing connections, then switching to connection-less.

MartinBL — Wed, 02 May 2018 12:18:02 GMT

Hi,

To allow a scanner (central) to read your scan response, but not connect, you should use BLE_GAP_ADV_TYPE_ADV_SCAN_IND. I agree that the documentation of these defines are sparse, but if you search for ADV_SCAN_IND in the Bluetooth Core specification you will find the information you need.

If you use ADV_NONCONN_IND the scanner will neither be able to read your scan response nor connect.