nrf52832 ble_app_beacon example problem

[rozpruwacz]

Hi all,

I have a problem with ble_app_beacon example. I'm using sdk v15.2 and my board is this. The problem is that I can see the beacon alive in the nRF Connect app on my phone but the beacon is not listed in the system bluetooth settings page on the same phone (Android) nor is detected by any other device (like other phones, pcs or raspberry pi 3). I uploaded the hex file that is suplied with the sdk (hex/ble_app_beacon_pca10040_s132.hex). I also build the app with armgcc and uploaded that. Both give the same result. Is there something missing in this example that prevents it to be detected by other bluetooth devices ?

[AmbystomaLabs]

A beacon by definition is non-connectable, therefore it doesn't show up in system bluetooth settings since that is where you pair with devices and a non-connectable device cannot be paired with.

You will only see a beacon by using an app like nRF Connect.

[Ameer Usman]

If possible, could you elaborate how to make the beacon connectable, as I have seen some connectable Beacons as well.

[AmbystomaLabs]

Yeah I worded that poorly.  I'm not the best BLE expert. The beacon advertisement becomes the top level advertisement for a peripheral mode device and allows the other device (smartphone) to discover its services.

I think the IoT Thingy has multiple connectable services and also broadcasts as a beacon.  You should look at that example.

Here is a nice TI paper on beacon types: http://www.ti.com/lit/an/swra475a/swra475a.pdf