Eddystone receiver

RE: Eddystone receiver

Ole Morten — Sun, 10 May 2020 20:39:10 GMT

ble_gap_adv_data_t is used to supply advertising to the stack when starting advertising. You're interested in the data received from an advertiser when scanning, which is in the ble_gap_evt_adv_report_t struct. You should take a look at the nrf_ble_scan module, which deals with scanning and connecting (even though you're just interested in the scanning).

Also note that the different softdevices have different header files, so be sure to look at the ble_gap.h file appropriate for the softdevice you're using.

Finally, I believe this community is meant to deal with one question at the time and find the best answers, Stack Overflow-style rather than forum-style, so accepting an answer for all questions is appreciated, and perhaps creating new questions instead of adding to an old one, when you have a new problem. :-)

RE: Eddystone receiver

Phillip Jacobs — Sat, 09 May 2020 23:43:45 GMT

So I have managed to get the transmitting eddystone beacon address using the blinky example. I just cannot seem to find the data... 😞. I though I got it using this line which I added to the blinky example:

ble_gap_adv_data_t                *p_adv_data        = &gap_ble_evt->evt.gap_adv_data.adv_data.p_data;

Now I am not sure where to find it...

RE: Eddystone receiver

Phillip Jacobs — Thu, 07 May 2020 21:04:15 GMT

Thank you I will try that 🙂

RE: Eddystone receiver

Ole Morten — Thu, 07 May 2020 20:57:01 GMT

To receive advertising packets, you need to be a Central device (strictly speaking a Scanner), and use a corresponding softdevice, which for the nRF52832 is S132. You should then take a look at one of the examples that implements a Central, for instance the Blinky Client, but remove everything that has to do with establishing a connection.

Note that I'm not intimately familiar with Eddystone beacons, so if they are something else than ordinary advertising devices, you may need additional guidance.