With S140 6.1.1 not able to scan extended advertising data

I am developping a scanner to detect advertisements from all BLE objects in the room to collect data from the advertisement data.

Some of those BLE objects are broadcasting data with larger size than 31 bytes and on my scanner I am only seeing the "low" part of them.

I mean that I am only seeing all previous data content with size < 31

However here is my scanner configuration

static ble_gap_scan_params_t const m_scan_params =
{
.active = 1,
.extended = 1,
.interval = SCAN_INTERVAL,
.window = SCAN_WINDOW,
.timeout = BLE_GAP_SCAN_TIMEOUT_UNLIMITED,
.scan_phys = BLE_GAP_PHY_1MBPS | BLE_GAP_PHY_CODED,
.filter_policy = BLE_GAP_SCAN_FP_ACCEPT_ALL,
.channel_mask = {0,0,0,0,0},
};

static uint8_t m_scan_buffer_data[BLE_GAP_SCAN_BUFFER_EXTENDED_MIN]; /**< buffer where advertising reports will be stored by the SoftDevice. */

/**@brief Pointer to the buffer where advertising reports will be stored by the SoftDevice. */
static ble_data_t m_scan_buffer =
{
m_scan_buffer_data,
BLE_GAP_SCAN_BUFFER_EXTENDED_MIN //BLE_GAP_SCAN_BUFFER_MIN
};

But each time I get the ADV REPORT event, I never have the extended_pdu bit set or getting more than 31 bytes ...

For information I am using S140 hex for 6.1.1 version. Is it working on this version ?

Parents Reply Children
  • Hi,

    Thanks for your confirmation.

    Actually I made a misunderstood initially on the way advertisement data would be delivered to the scanner.

    Now it's clear to me.

    So in the legacy advertising mode, if the peripheral is scannable, hence it can send it's initial advertising data and then upon scan request from the scanner it could deliver another packet.

    Confirm me that at max in this situation the scannable device could deliver max 31 bytes on first normal advertising, then then max 31 bytes on scan response ?

    For extended advertising, I need the advertiser to be sending extended advertising packets itself by design, not just because amount of data is > 31 bytes ... so it's a different way of advertising signalling I mean ?

    Is it possible with nRF connect tool on Android to generate extended advertisement packets by creating a test advertiser ?

    Regards

    David

  • DaviT said:
    Confirm me that at max in this situation the scannable device could deliver max 31 bytes on first normal advertising, then then max 31 bytes on scan response ?

    Correct.

    DaviT said:
    Is it possible with nRF connect tool on Android to generate extended advertisement packets by creating a test advertiser ?

    I have not tried.

    Kenneth

Related