I know the BCM920732 Tag board possesses the ability to be used and an RSSI (received signal strength indicator)Proximity FOB, but I'm not sure which sample application is the best to use for this function (proximity_plus?). I need to check with the SW team to determine how the RSSI level for each device being scanned is determined.
As it turns out, the proximity profile we provide works in reverse such that the client determines the proximity using the RSSI of connection with the preripheral.
To get the RSSI when connected, you can use blecm_ReadRSSI() function which will return the current RSSI (or will return 127 when not connected). Note that I'm not sure how accurate the result is that's returned as environmental factors outside of the chip's control come into play here as well. The only real way of knowing is the test the unit within a controlled chamber.
Great thanks for such information.
But is the connected state required for retrieving RSSI from blecm_ReadRSSI()? Will it be available at scanning state?
Ok, so it sounds like you will be running the 20732 in central mode, then have it scanning. In this scenario, the RSSI of a received ADV can be obtained in the ADV_PACKET_REPORT (the call back registered with blecm_RegleAdvReportCb). The parameter passed into the callback has a member called rssi which has the RSSI of the ADV.
I understood that the 20732 in central mode could retrieve RSSI through received ADV from peripheral devices.
On the other hand, is it possible that 20732 in peripheral mode can send RSSI through its ADV packet to central device on the other side while it is advertising?
Yes, the Central 20732 can provide the RSSI since RSSI is a Received Indicator.
However, a Peripheral Mode configured 20732 cannot "send" the RSSI value since RSSI, by its nature, is a "received" indicator.
I think you might want to use the TX Power level in the ADV packet depending on your application.