You can experiment with various filtering methods, but the distances will rarely be spot-on. Small rooms can complicate matters due to multi-pathing and other issues. Once you've set the calibrated power, if you change the transmit power you'll need to re-calibrate.Īlso note that your distance values can vary quite a lot. Make sure not to confuse the calibrate power value with the transmit power setting. Save your changes, and you should be all set. Note the RSSI value it returns, then tap back and enter that value in the Calibrated Power field. If you are using Eddystone the phone should be at 0 meters. The US29 RadBeacon USB (left in image at the top of this post) is a tiny USB dongle that can be plugged into any standard USB adapter for power, while the 39 RadBeacon Tag (the white tag in. If you are using Altbeacon or iBeacon frame types the phone should be 1 meter away. Tap on the beacon result in the app, and tap the menu icon in the top right. Once you see the beacon you want to calibrate, enable connections on the beacon (in the case of the Radbeacon dot, hold the button down for a couple seconds. With the app open, and the beacon on, hit scan. If you're using the Radbeacon dot, you can configure the advertised RSSI using the Radbeacon app (link is for the Android version). When configuring Eddystone broadcasts, the picked calibration value will automatically match the advertisement's transmission power."ĭavidyoung is right. "The txPower calibration for Eddystone broadcasts is done internally by our beacons and SDKs. The following is how the beacon's settings (in the owner app) looks like: I cannot specify the RSSI value at 1 meter, I can only pick one of the Transmission power (dBm and distance). The phone was 1m away from the phone, and I got the following results: I made a measurements with the app with the Android Beacon Library. I thought it was due to the power of the signal, which I tried to change but it wasn't the solution, since it was broadcasting the maximum power.Īnybody with the same problem that found a solution? I did an app with that tutorial and when measuring the distance it tells me that the one that is 0,2 m away is 1.6m away, the one that is 10m says is at 70-90 m away and the other at 7m is at 40-60m. I tried to look for a solution here, but seems like everybody gets a better distance. With this, while sitting on a corner i have one in front of me (less that 0.2m) the other one at 10m (aprox, that's the diagonal of the room) and the other one at 7m. I have read that it gives some fluctuations but I have three beacons in a room that is 7m x 7m one in each corner. The alternative, of course, is to train an intern (or your little sister) to do this manually, and pay him or her for the trouble.I have followed the tutorial from RadiusNetwork to get the distance from a beacon using Android Beacon Library. So the best case level of effort to get all beacons configured is 9 hours. I have lots of experience with these kinds of apps, and would expect it to take me at least 8 hours, probably much more. You'll also have to account for the time it takes you to write the config app and debug it until it is working reliably and as quickly as possible. So best case scenario, you're talking 5 secs x 700 = one hour to get them all configured. Since bluetooth connections can be a bit finicky, this might take 5 secs or more with retries. You will still, however, need to put each RadBeacon Dot into configuration mode one by one and wait for your custom configuration app to connect via bluetooth and configure the beacon. ![]() If you can get your hands on such a SDK, you could build an iOS, MacOS or Android app that does all of these configuration steps. I would email or call support at Radius Networks and ask if you can get access to a private SDK to configure your beacons for iOS, MacOS or Android.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |