RE: Distance detection with PCA20006 nRF51822 Bluetooth smart beacon kit

Robert — Fri, 06 May 2016 10:16:20 GMT

A bit late, sorry. Nevertheless many thanks for your answer. We need to redefine the project.

RE: Distance detection with PCA20006 nRF51822 Bluetooth smart beacon kit

tesc — Mon, 25 Apr 2016 11:00:29 GMT

Hi,

phase 1: detect if any bluetooth phone/device is present, without connecting to it

You can detect centrals by advertising using advertising packets with the 'scannable' property, which means either ADV_IND (connectable) or ADV_SCAN_IND (not connectable). The central may choose to send a scan request when receiving the advertising packet, which means you will be able to detect it. Do note that you will only detect active scanners. Passive scanners do not send scan requests, and so it is impossible to tell they are there.

You can detect peripherals by scanning.

phase 2: determine how far that bluetooth phone/device is from the beacon (far, near, close)

You can use the received RSSI value as a rough estimate for distance. As it measures signal strength (and not actual physical distance) it will be affected by the environment such as reflecting walls or objects blocking line of sight, but it can give a good approximation. While in a connection you can use sd_ble_gap_rssi_get() to read the received signal strength. If you need the value for non-connected devices then you can read this on BLE events as described in the RSSI without connection answer.

phase 3: detect if a specific phone/device is near, phase 4: connect with that phone/device.

Using Peer Manager (or the older Device Manager) you can keep track of bonded devices, that is devices which you have previously connected to and initiated a bond with. By using RSSI values found in phase 2 you can for instance initiate directed advertising to the closest device of the devices in the bonding table.

Your questions:

I think it should be possible to do what you want, but it depends a little on what exactly it is. At least something close to what you want should be possible. It will require som work, and I think it would be best to take one step at a time. Use some time to get to know BLE, the SDK and the SoftDevice before you begin (see also answer to 4.).
I would recommend using the latest version of the SDK whenever starting a new project, as this would provide the most features and support the newest hardware. Check the compatibility matrix to see what SDK versions support your hardware revision. There should be some markings on the IC that you can use to read from one of the compatibility matrixes what revision it is. I suggest that you use the newest SDK/SoftDevice that is compatible with each other and with your IC revision.
I would try to find an example from a recent SDK to start from. If the example is not for pca20006 then you should be able to make it work by changing the PCAxxxxxx preprocessor define to PCA20006. Depending on the usage of LEDs and buttons some other changes might be required as well (as the PCA20006 may have fewer LEDs and buttons). There are beacon examples for the PCA20006 in the SDKs as well.
To get familiar with the nRF series, the SDK and the SoftDevice I suggest you have a look at our tutorials, in particular those listed under "Bluetooth Low Energy". Then you will also get more familiar with BLE and get some thoughts about how you can make the things you want to make. But before that, the "Getting Started" tutorials is a great place for starting.

Regards, Terje