- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I set the module to the observe mode and receive the contents of the packet on the BLE.
However, the number of data collected is very different from the current number of BLE.
In fact, there may be 1000 BLE packets in 10 seconds, but my UART only shows 5~6 packets.
Does anyone know how this is going to happen?
Is there a filter function in the API that isolates some of the packets?
The picture is that I use the APP on my mobile phone to retrieve it.
The sending period of the BLE device is about 100ms, but I don't seem to receive the content.
I platform is WICED_STUDIO 6.4.
The attachment is my project file.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I think I find the problem.
In wiced_bt_cfg.c the low_duty_scan_interval is too large and the low_duty_scan_window too small, resulting in insufficient scanning time, so I missed a lot of packets.
After I adjusted it, everything was as I expected.
Thanks AnjanaM_61.
Best Regards,
Might
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello MiLe_4471161,
I couldn't find any problem in your code.
When I tested , I was able to see it printing the advertising devices.
Do you mean you are not able to see all the BLE devices around?
Can you please double check ? Please send the logs which you are getting on your side.
Regards,
Anjana
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi AnjanaM_61,
My log file is in the attachment.
I grab a BLE message to describe.
This is repeated for 98 ms to send a message on the red arrow point.
But in my log file, the density received is very different.
I want to receive all the BLE message to print out.
Best Regards,
Might
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I think I find the problem.
In wiced_bt_cfg.c the low_duty_scan_interval is too large and the low_duty_scan_window too small, resulting in insufficient scanning time, so I missed a lot of packets.
After I adjusted it, everything was as I expected.
Thanks AnjanaM_61.
Best Regards,
Might
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Might,
Forgot to ask you to check that. Yes, scan interval & window settings may effect the devices reported.
For full time scanning , you can keep Scant interval & window as same.
Thanks for confirming the fix.
Regards,
Anjana