We often get asked the question which beacons are compatible with iOS and Android. All beacons, whether iBeacon, Eddystone or sensor beacons can be used with iOS and Android. The compatibility is achieved through the implementation of common Bluetooth standards on these mobile platforms.
However, there are some caveats:
Android only supported Bluetooth LE as of Android 4.3. Older devices can’t see Bluetooth beacons. Over 95% of users are on Android 4.3 or later so most people can see beacons.
Apple iOS doesn’t have background OS support for Eddystone triggering. While iOS apps can scan for, see and act on Eddystone beacons, the iOS operating system won’t create a notification to start up your app when there’s an Eddystone beacon in the vicinity.
You can find the processor chip in the specification section of our beacon descriptions. Most people don’t know what this means or implies. This article will help you make a more informed choice.
There are currently three main chip families from Texas Instruments (CC25xx, CC26xx), Dialog Semiconductor (DAxxxx) and Nordic Semiconductor (nRF51xxx and nRF52xxx). These chip manufacturers publish standard electronic circuits and software SDKs that beacon OEMs use for their beacons. Hence, most beacons, within a chip family, have very similar designs. Small differences in implementation of board layout in areas such as the power supply, grounding, terminations, connectors and the antenna can cause electrical differences that can cause loss of power.
The strength of the beacon radio signal is affected more by the quality of the beacon implementation, particularly the antenna, rather than the choice of chip. This is also evident in real world tests. We have performed RSSI strength and stability tests on the beacons we sell and haven’t yet found any correlation between signal strength and chip family.
The choice of SoC affects battery use. Newer chip families such as the Nordic nRF52 (as opposed to nRF51) and Texas Instruments CC2640 (as opposed to CC2541) are more power efficient.
Most beacon SoCs transmit up to +4dBm output power for a longer range. A few such as the nRF52840 and CC2640RF can be set to higher output power of +8dBm and +5dBM respectively, with a consequent reduction of battery life. If you are looking for longer range, it’s more usual to use a long range beacon with an additional output amplifier chip.
A growing number of checkin/checkout systems are using iBeacons. Having an iBeacon at an entrance to a building allows employees to be automatically clocked in and out. It provides confirmation that a worker did actually arrive at a certain place that day.
When people move away from their desk, for example for lunch, they often don’t log out. It can be some time before the screen saver kicks in and logs the user out. The paper takes a look at the use of beacons to provide de-authentication when the person moves away from their desk.
Current smart parking systems are very expensive as they rely on image recognition and wireless magnetometers. The image recognition isn’t perfect and sometimes fails to acquire the identity of vehicles under poor illumination or due to obstruction of vehicle registration number plates.
Instead, a system has been developed using low-cost Bluetooth beacons. Beacons are installed in the vehicles and receivers are deployed along the roadside parking spaces.
The system uses Raspberry Pi for receivers and gateways. The Received Signal Strength Indication (RSSI) of beacons is processed, filtered and sent to a gateway. The system detects the occupancy of parking spaces and identifies the vehicles.
It’s unfortunate the researchers didn’t consider Bluetooth Mesh for the receivers and gateways. It’s ideal for situations such as this where nodes are within range of each other and the data is small in size and sporadic. The use of Bluetooth Mesh would have reduced the hardware requirement considerably.
It explains that while a battery has a fixed initial capacity, how you draw current from the battery affects how much of that capacity you get to use. At a relatively low constant current of 0.5mA you get most of the capacity while at 3mA you only get 60%.
For Bluetooth LE the current isn’t usually constant. Instead, it advertises at up to 7mA, for of the order of a milliseconds followed by a pre-set inter-advertising period between 100ms and 10 secs. This gives the battery time to recover.
The article explains how Bluetooth LE firmware should be designed to not turn everything on at initial startup so as to not stress the Battery unduly. It also mentions how it’s also wise to test the battery in the actual situation rather than relying on the battery mAh rating to calculate expected battery life.
We have two new thin beacons in stock. The Meeblue U1 and UL1 are only 4.8mm x 45mm x 25.5mm and weigh only 7g.
These beacons are similar to the iB001M in that they are particularly suitable for wearing by humans or animals. These new models have twice the battery power of the iB001M and use the more battery efficient Nordic Semiconductor nRF52 series system on a chip (SoC).
An accelerometer can be used to provide for motion triggered advertising. The accelerometer is only used for motion triggered broadcast and has adjustable movement threshold. They can also be set up to only advertise when the button is pressed. Advertising can be iBeacon, Eddystone UID, Eddystone URI or user defined. In addition, the UL1, has a light sensor that can be set up to cause the beacon to advertise when it’s either dark or light.