Note that there are some explanatory texts on larger screens.

plurals
  1. POWhat are the nominal distances for iBeacon "Far", "Near", and "Immediate"
    primarykey
    data
    text
    <p>I've been playing around with using iOS devices as both broadcasters and receivers using the new iBeacon API's in iOS 7.</p> <p>The docs don't go into detail at which distances the receiving device <em>should</em> see each proximity indicator, and specifically calls them out as "relative". When experimenting a with a demo app, I observed these distances (iPhone == receiver, iPad == broadcaster):</p> <p><strong>Far</strong> - 50 feet?</p> <p><strong>Near</strong> - 2-3 feet</p> <p><strong>Immediate</strong> - 2 inches</p> <p>These seemed really small to me, and there is perhaps a hint in the CLBeaconRegion class reference, which allows you to specify the signal strength of your device from 1m away. </p> <blockquote> <p>peripheralDataWithMeasuredPower: </p> <p>Retrieves data that can be used to advertise the current device as a beacon.</p> <p><strong>Parameters</strong> </p> <p><em>measuredPower</em> </p> <p>The received signal strength indicator (RSSI) value (measured in decibels) for the device. This value represents the measured strength of the beacon from one meter away and is used during ranging. Specify nil to use the default value for the device.</p> </blockquote> <p>My amateur calibration yielded -60, which I set and re-tested:</p> <p><strong>Far</strong> - hundreds(ish) feet</p> <p><strong>Near</strong> - ~50 feet</p> <p><strong>Immediate</strong> - 1 meter (slightly less)</p> <p>Are the results from my second test the "ideal" ranges according to Apple? They are really far away from the "default" setting I experienced in the first test.</p> <p>Or should I perhaps consider these ranges "calibratable" depending on my needs?</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload