Are you saying you cannot extract the Tx-power information broadcasted by your ibeacon?
Subject to the availability of a valid MFi license, did you have a chance to walk through the ibeacon apps within the SDK?
Thank you for the reply.
I checked the code in SDK.
There is a function wiced_sense_create in wiced_sense.c, It seems like the firmware sample code.
the code said:
adv.len = 1 + 1; adv.val = ADV_FLAGS;
adv.data = LE_LIMITED_DISCOVERABLE | BR_EDR_NOT_SUPPORTED;
// Set TX power when connected/advertising to 0 dBm.
The comments said it set the txpower to 0dBm, But it seems too large, I got the rssi from android sdk just -50 ~ -70.
Is it the real TxPower value in broadcast packets? if not, what it is?
The upper limit of the tx power of class 2 device is 4dBm. After taking into account of product variation and safety margins to pass bqb, the tx power is often set to between 0 and 2.5dBm. If this is a beacon, then 0dBm could be chosen, to enhance battery life. This value is a MAX value and the actual tx power output is subject to the relative distance between the transmitter and receiver. For example, for the chip to blast out 0dBm, the Tx and Rx could be 10m apart, or furthur. For the very same reason, we have the concept of RSSI to determine just so enough of tx power to maintain a BER of 0.1%.
I believe my Korea colleague will be getting in touch with you shortly.