You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 29, 2022. It is now read-only.
I'm curious of the rationale for choosing +16dBm as the transmit power in the TxEddystone-UID example.
I'm assuming this is a guess, since the API doesn't expose a way to know what the MIN, LOW, MEDIUM, etc. constants translate to for a given device (wouldn't that be nice??)…as a guess, this seems high. Is the intent to force the beacon to the top of the range sort?
If it's a guess or derived from some experiement, it would probably be good to document/comment it as such. Many folks will copy that code wholesale.
The text was updated successfully, but these errors were encountered:
You got me -- that was a lazy convenience. I can't be sure right now but I think the 0-meter power of medium is closer to about -25 dBm on something like a Nexus 6. I'll check tomorrow when I'm back in the lab and make it real. Thanks for making me honest. :-)
I'm curious of the rationale for choosing +16dBm as the transmit power in the TxEddystone-UID example.
I'm assuming this is a guess, since the API doesn't expose a way to know what the MIN, LOW, MEDIUM, etc. constants translate to for a given device (wouldn't that be nice??)…as a guess, this seems high. Is the intent to force the beacon to the top of the range sort?
If it's a guess or derived from some experiement, it would probably be good to document/comment it as such. Many folks will copy that code wholesale.
The text was updated successfully, but these errors were encountered: