Hi,
We performed some tests on EYE Beacons with the purpose of integrating them in our systems: we stumbled upon the transmission power configuration and the impact that this parameter has on the txPower field in the BLE packets, that will later be useful for the computation of RSSI of the beacon and, eventually, its estimated distance from the receiver.
As far as we understand, there are 8 possible values of transmission power: [-14, -11, -8, -5, -2, 2, 4, 8], so we tested all of these values both in iBeacon and Eddystone, knowing that in iBeacon txPower is the reference RSSI measured at 1m distance from the device, while in Eddystone at 0m distance. Please mind that txPower values are the one that everyone can find in the payload of an advertising packet.
These are the results:
Configured Power [dBm] |
txPower1m (iBeacon) |
txPower0m (Eddystone) |
Difference |
8 |
-54 |
-24 |
30 |
4 |
-60 |
-24 |
36 |
2 |
-60 |
-30 |
30 |
-2 |
-60 |
-32 |
28 |
-5 |
-66 |
-34 |
32 |
-8 |
-66 |
-38 |
28 |
-11 |
-74 |
-43 |
31 |
-14 |
-76 |
-44 |
32 |
So our questions are:
- Is it possible that the txPower values for different Configured Powers are exactly the same?
We are asking because at 1 meter, in "somewhat controlled conditions", those are almost always NOT the RSSI values we are getting from the devices, which of course is going to impact even the (already not so reliable) distance calculation.
- From online documentations, we found out that the typical RSSI variation within 1 meter is about -41 dBm: this means that between Eddystone txPower values and iBeacon ones we should see a similar difference, but as you can see in the table, this is never the case (the average difference between the two values is ~31 dBm); also the difference seems to be "jumpy" and not regular/monotonic as intuitively we can expect (but maybe I'm wrong in this supposition).
Is there an explanation for this? Maybe something regarding the calibration of the transmission power?
Thanks in advance.