URI-Beacons are handy when there is a need to advertise a small amount of information (usually a URL) to any nearby device. They’re really easy to set up: the code is fully available on the mbed website, so all you’ll need to do is tell the beacon what to broadcast. The canonical source for this example lives at https://github.com/ARMmbed/mbed-os-example-ble/tree/master/BLE_URIBeacon
URI-Beacons are handy when there is a need to advertise a small amount of information (usually a URL) to any nearby device. They’re really easy to set up: the code is fully available on the mbed website, so all you’ll need to do is tell the beacon what to broadcast.
What You’ll Need
To get this going, you’ll need:
- To see URIBeacons get the *Physical Web* app installed on your phone:
- One of the BLE platforms listed in the README.md of this repository, for example a Nordic DK board.
Building with mbed CLI
If you'd like to use mbed CLI to build this, then you should refer to the main readme. The instructions here relate to using the developer.mbed.org Online Compiler
In order to build this example in the mbed Online Compiler, first import the example using the ‘Import’ button on the right hand side.
Next, select a platform to build for. This must either be a platform that supports BLE, for example the NRF51-DK, or one of the following:
Or you must also add a piece of hardware and the supporting library that includes a Bluetooth Low Energy driver for that hardware, for example the K64F or NUCLEO_F401RE with the X-NUCLEO-IDB05A1
Once you have selected your platform, compile the example and drag and drop the resulting binary onto your board.
For general instructions on using the mbed Online Compiler, please see the mbed Handbook
Checking for Success
- Build the application and install it on your board as explained in the building instructions.
- Open the *Physical Web* application on your phone. It will start to search for nearby beacons.
figure 1 Start of the *Physical Web* application version 0.1.856 on Android
- When the beacon starts up, the Configuration Service runs for 60 seconds. During this time it is possible to change the URL advertised by the beacon. It is also important to note that during these 60 seconds, your device will not advertise any URL.
figure 2 How to open the beacon configuration view using the *Physical Web* application version 0.1.856 on Android
- Edit the URL advertised by your beacon.
figure 3 How to edit the URL advertised by your beacon using the *Physical Web* application version 0.1.856 on Android
- Save the URL which will be advertised by your beacon.
figure 4 How to save your beacon configuration and start advertising URL using the *Physical Web* application version 0.1.856 on Android.
- Find your device; it should advertise the URL you have set.
figure 5 Display of URL advertised by your beacon using the *Physical Web* application version 0.1.856 on Android.
Please note that the URIBeacon spec requires the URIBeacon app to remain in config mode for the first 60 seconds before switching to being a beacon. So if you're using a physical-web app, you'll only see the beacon after this period; if you're using one of the generic apps for BLE scanning, you should see a configurable beacon being advertised for the first 60 seconds.
You'll find links on Google's project page to client apps to test URIBeacon. Here's a link that should get you an Android App; please browse to `uribeacon-sample-release.apk`. But you should begin with the links to android apps mentioned above.
.mbedignore@20:aba6206ee5d9, 2017-03-01 (annotated)
- Wed Mar 01 18:15:53 2017 +0000
Merge pull request #55 from adbridge/master
Updating mbed-os to mbed-os-5.3.6
Commit copied from https://github.com/ARMmbed/mbed-os-example-ble
Who changed what in which revision?
|User||Revision||Line number||New contents of line|