Is there a standard for beacon configuration services?

RE: Is there a standard for beacon configuration services?

Simon — Fri, 14 Dec 2018 12:39:54 GMT

Sorry, I was too quick to answer.

As far as I know, Nordic does not provide any configuration services for the beacon. Here is a link that I think you might find helpful. Two solutions are proposed, the former involves programming a bootloader onto the chip and configuring the data through OTA DFU. The latter solutions, is as you mentioned, to create your own custom services. This solution requires some more work.

Best regards,

Simon

RE: Is there a standard for beacon configuration services?

Prasad — Thu, 13 Dec 2018 09:26:10 GMT

I think you got my question wrong!

I am asking about the configuration services that are used to configure beacon parameters into the beacon. Take a look at ble_app_eddystone and "nRF beacon for Eddystone" app.

RE: Is there a standard for beacon configuration services?

Simon — Thu, 13 Dec 2018 08:56:40 GMT

I think the BLE Blinky Application would be a nice starting point for your solution. It uses the advertising type BLE_GAP_ADV_TYPE_CONNECTABLE_SCANNABLE_UNDIRECTED, which includes 31 bytes of user configurable data (transmit power, UUID etc..).

However, you would need to modify the example in order to achieve the functionality you mentioned, I would start by modifying the characteristic LED, and send the new beacon data over there. After receiving this, you disconnect and update the adertising data through sd_ble_gap_adv_set_configure(..), and restart the advertising again.

Best regards,

Simon