RE: How to get device details of BLE devices seen by NRF52?

Gaurav — Mon, 15 Oct 2018 06:56:10 GMT

Where to use this structure and what should be the initializing value of gsp_ble_evt.

RE: How to get device details of BLE devices seen by NRF52?

endnode — Sun, 26 Feb 2017 09:14:35 GMT

Hi QDI,

As Roger pointed out, the "proper" way would be to scan and log (or report over wired interface if you have it) all broadcasters. Usual way is to distinguish BLE devices by MAC address (aka Adv. address) which is 6-byte filed you mentioned. But some of them might not be static so it's question how useful this information will be. You can support it by logging whole content of ADV_xxx (and SCAN_RSP) data but these can also change any time so if some device wants to be immune to your tracking it can achieve it (of course;).

Here is example of how to extract Adv. address from received packet in GAP Scanner/Central role (on BLE_GAP_EVT_ADV_REPORT event received):

// Local variables.
ble_evt_t *gsp_ble_evt;

// ...

// Extract Adv. address from the event structure.
uint8_t * adv_address = (uint8_t *)gsp_ble_evt->evt.gap_evt.params.adv_report.peer_addr.addr;
uint8_t adv_address_type = (uint8_t)gsp_ble_evt->evt.gap_evt.params.adv_report.peer_addr.addr_type;
LOG_DEBUG("Adv. Address = 0x%02X:%02X:%02X:%02X:%02X:%02X.", adv_address[0],
                                                             adv_address[1],
                                                             adv_address[2],
                                                             adv_address[3],
                                                             adv_address[4],
                                                             adv_address[5]);

// ...

Cheers Jan

RE: How to get device details of BLE devices seen by NRF52?

Roger Clark — Sat, 25 Feb 2017 20:45:45 GMT

You can get the full advertising packet from the scan response callback.

Just parse the whole packet and extract whatever data you want to collect