Timeline for How to scan for all available beacons with BLE?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 10, 2014 at 22:24 | comment | added | Vegar Westerlund | A BLE advertisement packet only takes up some 300-400 micro seconds pr channel (I checked one packet and it took 296us). So ideally there should room for some 2500 packets pr second. Given this, it should be possible with more than 500 beacons in one area if you configure them to advertise only say once pr second. They should still be fairly quick to find and the built in randomness in the protocol should to some degree mitigate devices that collide by chance. | |
| Jul 25, 2013 at 17:30 | comment | added | Mikko Virkkilä | I would say that it is unlikely that the iBeacons would be fundamentally incompatible with Android, as from what I understand it is going to be just based on standard BLE technology. Unfortunately there isn't currently enough information to create iBeacons, and the iBeacons are more about regions than anything else. | |
| Jul 25, 2013 at 3:06 | comment | added | Michael Sayapin | Thank you for the detailed answer. I will definitely update the info when we test the real live beacons. It should be somewhere in late Fall. For now it seems like Apple is targeting their iBeacons to do almost what we want, though we would love some Android compatibility too. :) | |
| Jul 24, 2013 at 23:17 | history | answered | Mikko Virkkilä | CC BY-SA 3.0 |