Scan request with extended advertising

RE: Scan request with extended advertising

Kenneth — Sat, 28 Aug 2021 00:07:33 GMT

Found another thread with similar problem.

https://devzone.nordicsemi.com/f/nordic-q-a/78332/slave-send-extended-broadcast-packet-will-protocol-stack-report-event-when-the-master-receive-the-auxiliary-broadcast-package-and-what-event-is-reported-how-do-the-slave-know-that-the-auxiliary-broadcast-packet-has-been-recei/324420#324420

Just had to change the property type in ble_advertising_start() function.

RE: Scan request with extended advertising

Kenneth — Fri, 27 Aug 2021 15:14:42 GMT

Simon,

My peripheral device does not have high duty advertising. I have clean and rebuilt the project, as well as erase the chip before programming. Peripheral still does not receive notification for scan request.

Any other suggestions as to why it is advertising in nonscannable?

Regards,

Ken

RE: Scan request with extended advertising

Simonr — Fri, 27 Aug 2021 13:09:43 GMT

Sorry, I should have mentioned the nRF Sniffer to you in my reply. The fact that the device still advertises in "NONSCANNABLE" is likely why you're seeing this issue. Are you perhaps calling set_adv_mode_directed_high_duty() somewhere in your application, as that will cause the device to advertise in a "NONSCANNABLE" state. Maybe you haven't compiled and built the peripheral project after you changed the application to use SCANNABLE advertising.

Best regards,

Simon

RE: Scan request with extended advertising

Kenneth — Thu, 26 Aug 2021 21:24:59 GMT

Simon,

I managed to get the sniffer going using one of the DK I have.

PDU type is 0011, which seems to be scan request, correct?

A sniff on peripheral adv package for coded PHY

In extended advertising header, it indicates advertising mode as "Connectable Non-scannable" even though advertising property type is set to BLE_GAP_ADV_TYPE_EXTENDED_NONCONNECTABLE_SCANNABLE_UNDIRECTED. Correct me if I'm wrong, but scannable means it is able to receive scan request. I'm not sure why advertising header is showing non-scannable.

Regards,

Ken

RE: Scan request with extended advertising

Kenneth — Thu, 26 Aug 2021 15:20:18 GMT

static void advertising_init(uint8_t phy)
{
    ret_code_t             err_code;
    static ble_advdata_manuf_data_t manuf_specific_data;
    static ble_advdata_manuf_data_t srsp_manuf_specific_data;

    manuf_specific_data.company_identifier = COMPANY_IDENTIFIER;
    srsp_manuf_specific_data.company_identifier = COMPANY_IDENTIFIER;

    memset(&init, 0, sizeof(init));

    manuf_specific_data.data.p_data = (uint8_t *) m_srespons_info;
    manuf_specific_data.data.size   = APP_SRESPONSE_INFO_LENGTH;
    srsp_manuf_specific_data.data.p_data = (uint8_t *) m_srespons_info;
    srsp_manuf_specific_data.data.size = APP_SRESPONSE_INFO_LENGTH;

    init.advdata.name_type               = BLE_ADVDATA_NO_NAME;
    init.advdata.include_appearance      = false;
    init.advdata.flags                   = BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE;
    init.advdata.p_manuf_specific_data = &manuf_specific_data;
//    init.srdata.p_manuf_specific_data = &srsp_manuf_specific_data;
//    init.advdata.uuids_complete.uuid_cnt = sizeof(m_adv_uuids) / sizeof(m_adv_uuids[0]);
//    init.advdata.uuids_complete.p_uuids  = m_adv_uuids;
    if(phy == BLE_GAP_PHY_CODED)
    {
        m_advertising.adv_params.primary_phy = BLE_GAP_PHY_CODED;
        m_advertising.adv_params.secondary_phy = BLE_GAP_PHY_CODED;
    }
    else 
    {
        m_advertising.adv_params.primary_phy = BLE_GAP_PHY_1MBPS;
        m_advertising.adv_params.secondary_phy = BLE_GAP_PHY_1MBPS;
    }
//    m_advertising.adv_params.properties.type = BLE_GAP_ADV_TYPE_EXTENDED_NONCONNECTABLE_SCANNABLE_UNDIRECTED;
    m_advertising.adv_params.properties.type = BLE_GAP_ADV_TYPE_EXTENDED_NONCONNECTABLE_SCANNABLE_UNDIRECTED;
//    m_advertising.adv_params.properties.type = BLE_GAP_ADV_TYPE_CONNECTABLE_SCANNABLE_UNDIRECTED;
    m_advertising.adv_params.scan_req_notification = 1;
    m_advertising.adv_params.p_peer_addr     = NULL;    // Undirected advertisement.
    m_advertising.adv_params.filter_policy   = BLE_GAP_ADV_FP_ANY;
    m_advertising.adv_params.interval        = APP_ADV_INTERVAL;
    m_advertising.adv_params.duration        = APP_ADV_DURATION_UNLIMITED;       // Timeout after 60 s
    m_advertising.adv_params.channel_mask[4] = 0x00;

    init.config.ble_adv_whitelist_enabled = true;
    init.config.ble_adv_fast_enabled  = true;
    init.config.ble_adv_fast_interval = APP_ADV_INTERVAL;
    init.config.ble_adv_fast_timeout  = APP_ADV_DURATION;
    init.config.ble_adv_slow_enabled = true;
    init.config.ble_adv_slow_interval = APP_SLOW_ADV_INTERVAL;
    init.config.ble_adv_slow_timeout = APP_SLOW_ADV_DURATION;
    init.config.ble_adv_extended_enabled = true;
    if(phy == BLE_GAP_PHY_CODED)
    {
        init.config.ble_adv_primary_phy = BLE_GAP_PHY_CODED;
        init.config.ble_adv_secondary_phy = BLE_GAP_PHY_CODED;
    }
    else
    {
        init.config.ble_adv_primary_phy = BLE_GAP_PHY_1MBPS;
        init.config.ble_adv_secondary_phy = BLE_GAP_PHY_1MBPS;
    }


    init.evt_handler = on_adv_evt;

    err_code = ble_advertising_init(&m_advertising, &init);
    APP_ERROR_CHECK(err_code);

    ble_advertising_conn_cfg_tag_set(&m_advertising, APP_BLE_CONN_CFG_TAG);

    err_code = sd_ble_gap_tx_power_set(BLE_GAP_TX_POWER_ROLE_ADV, m_advertising.adv_handle, TX_POWER_LEVEL);
    APP_ERROR_CHECK(err_code);
}


#define APP_ADV_INTERVAL                320                       /**< The advertising interval (in units of 0.625 ms. This value corresponds to 150 ms). */
#define APP_ADV_DURATION_UNLIMITED      0                                           /**< Unlimited period .*/
#define APP_ADV_DURATION                2000                         /**< The advertising duration (60 seconds) in units of 10 milliseconds. */
#define APP_SLOW_ADV_INTERVAL           2400                  /**< The advertising interval (in units of 0.625 ms. This value corresponds to 2000 ms). */
#define APP_SLOW_ADV_DURATION           2000

I don't have a BLE sniffer. Is there another method of checking central's scan request message?

Regards,

Ken

RE: Scan request with extended advertising

Simonr — Thu, 26 Aug 2021 11:23:20 GMT

Can you also show me the advertising parameters, in the scan_req_notification define, it is stated that this parameter is ignored if ble_gap_adv_properties is set to a non-scannable advertising type.

You can also take a sniffer trace to check whether a scan request is actually sent by the central device.

Best regards,

Simon