Proximity Monitor

RE: Proximity Monitor

Ole Morten — Mon, 28 Apr 2014 11:44:08 GMT

This is what I explained above. I don't have any example code for this, but by looking at the struct definition, it shouldn't be very problematic to get the raw advertising data. You'll then have to parse the data yourself, from the format as defined in spec. See Volume 3, Part C, chapter 11.

RE: Proximity Monitor

Gabriel — Wed, 23 Apr 2014 18:18:40 GMT

To explain a little bit more my question. I am doing a Proximity monitor. I have one central(nRF5182-s120) that act as the monitor, and several peripherals (nRF51822-s110) that are only advertising. In the advertising package of the peripherals I also include the battery level with this:

advdata.name_type = BLE_ADVDATA_FULL_NAME; advdata.include_appearance = false; advdata.flags.size = sizeof(flags); advdata.flags.p_data = &flags; [b]advdata.service_data_count = 1; advdata.p_service_data_array = service_data;[/b]

So in the central side I want to read this value without connection. How can I do that?

Thank you!

RE: Proximity Monitor

Gabriel — Mon, 21 Apr 2014 22:30:49 GMT

Hi Ole, Thank you for the answer. Can you tell me if it is also possible to obtain with the s120 the service data being advertised by a peripheral? Basically what I am doing in the peripheral side is include the battery level in the advertising package. So I need to read this value in the central side without connect. Like the nRF Master Control Panel app does. Thank you

RE: Proximity Monitor

Ole Morten — Thu, 13 Feb 2014 16:26:57 GMT

You can do scanning with the S120, and when doing so, you'll get back an ADV_REPORT for each advertising packet received. This will include the address the advertiser used, along with the RSSI. Take a look at the definition of the struct ble_gap_evt_adv_report_t.