Part Number: CC2652P
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Part Number: CC2652P
Hi,
Thank you for your inquiry; I notified a colleague and he will reply as soon as possible with additional insights.
Ideally the SDK version and a sniffer log with detailed information could help get to the root cause.
Best regards,
Rafael
Hey Zhang,
What scanning parameters are used in the application when you configure the Bluteooth stack? What project have you used as a base?
I do not expect such a great difference in performance. However, keep in mind the Bluetooth stack may have different radio configurations than what the RFlib driver is configured for (I'm not sure how it is configured in your setup so I cannot speak to this). In addition, the stack may also be processing other radio events as they occur, depending on what mode/project is used, as well as other application level events, causing the device to not always be listening for a beacon.
The same test is normal when we put it in a shielded box
Can you clarify this? Do you see a success rate of about 90% in a shielded box using the Bluetooth stack?
the test based on ”simple_broadcaster“project,the scan parameters :scan interval is 500ms,scan windows is 500ms,scan duration is 510ms,Scan period is continuously scanning.With the above parameters, we only let it scan on channel 37
SDK Version:4.40.04.04
An ibeacon base station and a scanning test label are placed in the shielding box, and the success rate is counted according to time, and the success rate is as high as 90%.This has been repeated many times and the results are consistent
Just to confirm, you are seeing expected behavior in the shield box when using the Bluetooth stack. In an open air environment, you see less performance with the same simple_broadcaster project?
the scan parameters :scan interval is 500ms,scan windows is 500ms,scan duration is 510ms,Scan period is continuously scanning.With the above parameters, we only let it scan on channel 37
How often do you trigger a scan? Are the iBeacons advertising only on channel 37 also?