Receiving Scan Response Packet

RE: Receiving Scan Response Packet

cherrycherry1 — Tue, 06 Dec 2016 01:27:35 GMT

Hi! Thanks, it's working now.

I checked if the packet was from a device that I was interested in. However, I did this on name, which is not there anymore in a Scan Response Packet. So just:

case BLE_GAP_EVT_ADV_REPORT:
{   
       print_adv_data(&p_gap_evt->params.adv_report);
}break;// BLE_GAP_ADV_REPORT

works fine. I'm working on filtering now, but that's another question (whitelisting on advertisements etc).

RE: Receiving Scan Response Packet

Ulrich Myhre — Mon, 05 Dec 2016 12:51:39 GMT

To add to this: BLE_GAP_EVT_ADV_REPORT is used for both advertisements and scan responses. There is a flag in the event structure stating if it was a a scan response or not. For this to happen, the active field in scam_params must be set (you've done this) and the advertiser must have scan response data to respond with. The advertiser must also be advertising in a mode where scan requests are allowed (ADV_IND or ADV_SCAN_IND, not ADV_DIRECT_IND or ADV_NONCONN_IND). If it has filter policies enabled for scan requests, the scanners identity must be in the advertisers whitelist as well.

RE: Receiving Scan Response Packet

FormerMember — Mon, 05 Dec 2016 09:19:35 GMT

When initiating advertising, ble_advertising_init(..) --> ble_adv_data_set(..) --> sd_ble_gap_adv_data_set(..), both advertising data and scan response data can be set. When a central/scanner sends a scan request, the advertising device will automatically reply with a scan response containing the scan response data provided when initiating the advertising.

The purpose of the event BLE_GAP_EVT_SCAN_REQ_REPORT is to tell the application that a scanner sent a scan response and that this device replied with the scan response.