When using SDK 3.0.6 and trying to scan iBeacon tags, nothing is received by the GAPM_ADV_REPORT_IND handler. The advertisement messages sent by the iBeacon tags are sent with a non-connect advertising indication (defined as GAPM_ADV_NON_CONN in the SDK code).
Detecting regular undirected advertisements works correctly.
Wed, 2015-02-11 14:57
#1
Scanning iBeacon tags
Hi,
What type of scanning are you using? Active or Passive? Are you using observer mode scanning?
I'll have the team look into this issue, but they will probably ask those questions.
I've tried both active and passive scanning.
When using GAP_OBSERVER_MODE the iBeacon is shown. Thank you very much!
Hi
That is great. I will hopefully get an explanation from our experts as to why observer mode makes a difference. I'll post it here as soon as I get something.
Hi again,
The team responded as follows:
The GAPM_ADV_REPORT_IND reports peripherals if scan response is available (page 53 of the RW-BLE-GAP-IS.pdf).
As you may know, from the RW-BLE-GAP-IS v2.06 p.51, it says that we must not set any scan response data when performing non-connectable advertising.
So, thats the reason why, the ibeacon can only be seen when the GAP_OBSERVER_MODE is used because no filtering is performed.
Hi again,
The team responded as follows:
The GAPM_ADV_REPORT_IND reports peripherals if scan response is available (page 53 of the RW-BLE-GAP-IS.pdf).
As you may know, from the RW-BLE-GAP-IS v2.06 p.51, it says that we must not set any scan response data when performing non-connectable advertising.
So, thats the reason why, the ibeacon can only be seen when the GAP_OBSERVER_MODE is used because no filtering is performed.